But their internet is down, so it'll fail to send to telegram. Realistically it needs to be an external system that is tracking when it receives pings from the home network, so it can show periods where the bash script didn't ping for a while.

My favourite one is renaming a directory full of files in nnn. It opens in vim, and I'm in my happy place, where I really know how to edit text (or, in this case, filenames). Great when there's some minor variation between a lot of files. Full previewing before saving, multiple operations handled before doing anything etc.

This actually already exists, it's just not in the UI yet. Hiding communities can be done via the API. I was planning on putting in a PR to expose the functionality on the front-end at some stage.

It's absurd how much better it makes the vacuums to use. Interaction through the Web UI is just instant, instead of having to bounce to servers halfway around the world before acting on it. It's the primary decider of which vacuum I consider now.

I'm also on Migadu for email, and I can say the experience has been pretty excellent. They have good instructions for setup stuff, and their pricing model is great. The pricing model has things in common with rsync.net, where they impose a soft limit on storage and reach out if you start exceeding it to talk about upgrading.

I do wonder if other mail providers will at some stage support jmap, it seems like it could take away some frustrations.

This is using matrix. You can even connect to it from any matrix client.

The bridges are all open source, and they use matrix synapse as their server installation - though their client is a closed source fork of element with changes. You can use any matrix client to connect to it, and they say it's a standard synapse setup.

If privacy is a concern, bringing your own client should remove that concern as the rest is open source. It's also e2e encrypted, as any matrix server is.

I self host my own matrix homeserver with bridges set up using their code. The only bit of their stack I can't use is the client. I don't like that that's closed source, that's frustrating.

Edit: while writing this two more people made the same comment. Sorry!

This is very well written and gets to the core of the issue. The aboriginal people have already spoken - years ago. The Uluru Statement from the Heart is the only piece of documentation anyone should need as to whether the aboriginal people as a representative body want this.

Sure, fair enough. There are other distros supported by the community if you want to check that out too.

You honestly won't find better than the support for framework in the laptop space. The arch wiki entry for it is fantastic, and having multiple supported distros is almost unique.

Those are the officially supported distros. You can install other ones just fine. I doubt you'd find another laptop that had even just more than 1 officially supported distro.

Up and down votes are federated with your username, along with posts and comments (obviously).

Clicking on links, favourites, email address (if you put one in when signing up), password and IP address are all only on your local instance.

Basically, unless another server needs to know about it for federation to work, it's going to be local to the instance you're using.

They mean the android community having moved over here. It's just a merger in name, there isn't any technical work happening in that process.