I think the KDE vs Gnome thing in general for a lot is familiarity, but I gotta say as a primarily Gnome user, I find Dolphin harder(or maybe less intuitive) to use. It’s not bad, and in a number of ways I would agree is absolutely superior to Nautilus, but for whatever reason, between the two, I generally would prefer Nautilus.

wouldn’t that be chili sin carne?

I primarily use logseq but have obsidian configured to use the same directory. I then use logseq for journaling and some tag notes that have searches and links kind of built in. Then I have obsidian for wiki or KB type notes. I can then link to parts of that in logseq. I also use obsidian for a few niche situations where the plugins add value. Its not a perfect solution but it works pretty well for me. I also typically use obsidian to folder directory organize my non journal notes, bit really you could just as easily use your file browser for that.

It’s only been around for less than a year as far as I’m aware and from what I gather still seems to be finding its sea legs as far as balancing between what rolls in immediately(ish) and what comes in through the big “tumbles”

I miss Unity. It never got the love it deserved from a praise nor development standpoint. My typical Gnome desktop typically ends up being a quasi-Unity layout. I need to spin up the latest Ubuntu Unity spin for nostalgia’s sake.

in fstab, there’s a nofail option that I started using when mounting NFS and other disks that may be missing and I don’t want to kill my bootup

main thing to note is that NFS is an object based storage (acts like a share) where iSCSI is block based (acts like a disk). You’d really only use iSCSI for things like VM disks, 1:1 storage, etc. For home use cases unless you’re selfhosting (and probably even then) you’re likely gonna be better off with NFS.

if you were to do iSCSI I would recommend its own VLAN. NFS technically should be isolated too, but I currently run NFS over my main VLAN, so do what ya gotta do

I would just append that judging people is a good thing, often blanket misinterpreted as a bad thing. You should make an initial judgement upon meeting someone (it doesn’t really matter, your subconscious will anyway). The important part is being willing to update that judgement based on learning more.

Subbed. Just curious as to how (or if) you intend to differentiate yourself from the Jupiter Broadcasting team’s Selfhosted.show podcast?

I actually use both Logseq and Obsidian. It’s not perfect, but Obsidian is more my knowledgebase and Logseq is my journal and sort of TODO manager. I have them all within the same directory so I can reference my knowledgebase, append to it, etc. from within logseq or the inverse. main issue is since logseq loves the bullet points it tends to whack out my headings and stuff in obsidian made notes

I’m a logseq user of about 6 months and overall really like it. It’s mostly built around the daily journal, which mostly works if you lean into it. I basically write what I did, todo’s or random thoughts for the day in there. I typically segregate my root bullet points into a handful of main “buckets” like a job, client or project. I used to do those with a hashtag like #job1 but moved to page tags like [[job1]] with sub bullets for main tasks, todos, notes, etc from each. i have many relevant hashtags for relevant subsystems/topics relating to the main ones.

from there I have setup some basic pages for things like [[job1]] with a query to show TODOs with that task (see below), then some relevant reference notes, and sometimes some links to bullets from previous journals if i find i will likely reference them frequently. you also can see below the linked references, which is frequently useful. i also frequently put tags to other tags, pages, etc. within to help map everything together

here’s an example of a very basic query I would keep at the top of the [[job1]] page {{query (and [[job1]] (task NOW LATER DOING IN-PROGRESS TODO WAIT WAITING))[[job1]]}}

to your above, you have #workimprovements, you can either just jot those at the root as they come to you and include the full hashtag, or you could have a starting section of either [[workimprovements]] with various ideas below, but i would also suggest adding in other relevant hashtags for subtypes, areas, etc. another tip about hashtags, don’t go crazy with them – too many hashtags just makes a mess – but don’t skimp on them either. If you think you’ll use it frequently enough, or at least want to go back and reference it easily in the future, make a hashtag. you can use the hashtag plugin after the fact to find unused and remove hashtags you didn’t end up using.

one thing I really wish they would add is similar to hashtags, but for people. Right now, I “tag” people with an @ in front of their name, so I might have @BobS requested X which sort of helps to go back and search for things related to @BobS, but it’s not natively done for fully fleshed out. It would be awesome if there was either native or a plugin functionality to more gracefully tie it together

anyway, there’s my logseq ramble, hopefully it helps.

was coming in here to mention rclone, which is pretty cool stuff. this sort of sounds like a pretty wrapper for rclone, which means this should be pretty neat too. I’ll have to check it out.

yeah, the clickbait title almost turned me off, but I did end up watching video. I’m not really into STT (or voice assistants in general), but the keyboard they are allegedly working on does sound pretty sweet and I would definitely be interested in that.

Being that even if you go to their site https://futo.org there is no mention that I could see of this STT/voice input product, I wonder if I’ll ever be able to find out about said keyboard, should it actually release. For reference, the direct link to the voice input site is https://voiceinput.futo.org

edit: I also wanted to add that I was unaware of the saved recordings thing, which is horrifying, yet unsurprising… makes me glad I don’t/didn’t use STT… I think… maybe I should go check…

Yeah. I often kick myself for getting an nvidia card. My former distro was Ubuntu so I’m familiar with it from that end. I can see how having a constantly updating kernel could cause pain with the nvidia drivers. Even on leap or Ubuntu any tine the nvidia drivers updated it took a fair bit of extra time for regular apt/zypper processing kernel stuff and whatnot.

im going to keep a sharp eye on slowroll. I might be crazy enough to (eventually) try to convert from leap 15.5 to tumbleweed to slowroll. If it all blows up I was probably going to have to do that anyway.

Tell me more about your Tumbleweed+NVIDIA problems. I’m on Leap 15.5, but with all this I’ve thought about moving over to Tumbleweed or Fedora. My card is NVIDIA, so I’m not looking for a big headache.

Plex probably isn’t the best example, but yes, you can use Tailscale to create a sort of mesh network to access devices within private networks. Essentially any device that’s connected to tailscale can be contacted by other clients connected to tailscale. There are extra routing things you can do to use a tailscale device as a sort of “exit node”, but that’s the basic gist.

Neat! SUSE was technically my first Linux distro I installed probably circa 2006 via 3 or 4 CDs on some old donated hardware. I played around with it for a bit but never really dove in. A few years later I tried Ubuntu from a “demo” CD I got in Linux magazine and outside of a bit of experimental distro hopping I’ve been mostly on Ubuntu for the last 17ish years. Just about 3 weeks ago, I decided to install openSUSE again. Was split between tumbleweed and Leap, but decided to go with Leap (15.5). It’s a bit different coming from a .deb based system, but I’m digging it so far. Kind of crazy that the build I installed so long ago was probably one of the first releases of SUSE.

Seconded for simplicity. If OP is looking for complex statistics, it may not do the trick, but it’s about as straightforward and quick to set up as a monitoring solution can get.

Put this on my list of projects to dig into when I have time. I briefly tried Grocy a while back thinking I may be able to use it for inventory mgmt, but it didn’t stick. I want to say I found some other self hosted home inventory project at one point but didn’t stick with that one either. It’s one of those things that I think you have to really invest in to get ROI back, but that’s hard to do, especially when it’s more than just yourself (wife-factor) planning to utilize it that also has to buy-in and commit.

I’ve only ever run ZFS on a proxmox/server system but doesn’t it have a not insignificant amount of resources required to run it? BTRFS is not flawless, but it does have a pretty good feature set.