Ha I saw 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'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...

Pinetime isn't the most robust of smartwatches, but I would say it fits the bill.

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.

Check your library. Mine has one available to use at many of the branches in my area. If I ever come up with something to print instead of buying one I'm going to try that out. Then if I decide to get really into it, I'll have practical knowledge to know what I'd actually want to buy.

Instead, I've just never done any 3D printing, which is also fine.

Not OP, but I have two because there was too much contention on a single household switch. My household collectively also owns/owned 2xWii and 1xWiiU.

My opinion is probably in line with most; that for general "news" it's just fine. For niche topics, most aren't here or at least aren't as robust as Reddit

There are two relatively minor features that I do wish would be implemented:

1. homepage defaults to Subscribed instead of all, or at least a way to set that as the default

2. a quick jump to top of page button that stays present when you've scrolled way down the page. Not sure if that was a RIF addition or native to Reddit, but that was a nice quality of life feature

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.

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.