Headline sort of buries the lede of how important those two were to building lxd and supporting the container ecosystem on linux. Sad to see. I have been using lxd on my home network and vps instances for years. Disliked when the project moved to snap-only distribution, but at least other projects picked up native packaging. And it doesn’t seem like lxd is going away, which is nice. But Canonical explicit seizure of control withers confidence I had in the long-term viability of the software for my own use.

Is Reddit easy to explore for new places? Maybe it got better in the new UI, but search was historically bad and discovering relevant subs was pretty difficult. I sort of think people dipping their toes in fediverse waters forget how rough around the edges Reddit was/is. I agree that lemmy and its ilk have a lot of room to improve on usability, but the bar doesn’t seem exceptionally high.

I like miniflux as well. Probably worth noting that the dev offers paid hosting.

For grocery, KitchenOwl. And you can add custom items. Doesn’t really work as a todo list though.

The rise of distributed computing was at a time that CPUs didn’t really throttle down. CPUs in general were just a lot more power hungry. But if you had to leave the computer on for some reason and had spare CPU cycles, it made sense to contribute them to a distributed computing project - the power was being spent anyway and it seemed like a good cause. Today, modern CPU sip power and throttle down and you are actively driving power consumption by taxing the CPU. There is a much less favorable cost/benefit equation today, but in terms of the cost of the power consumed AND the climate cost of the power consumed.

Looks very nice. Lots of self-hostable paste share software, but very little with e2ee.

Is it text only? xmpp should be lightweight and smooth sailing. prosody configured to never expire messages would give you a forever archive on the server. There are good mobile clients, plus web/pwa and native desktop clients.

Long period of underemployment and gradual employment gains following the credit fueled recession in 2009, is possibly one factor. In other words, the slack finally came out.

Notification works like any other message. http upload is just the method the client uses - it’s more or less transparent to the clients involved. It’s still sending and receiving as you would expect from a messenger.

What install method are you following?

Two ideas:

1. xmpp works, but the domain needs to resolve correctly. I’d just use a free domain that you point at the server LAN ip, plus an acme client that can do a dns challenge. Prosody is pretty bulletproof and very lightweight.

2. deltachat + email. Set up a little IMAP server for the lan and use Delta chat to create a messaging over it. Or just use an email client.

xmpp has a number of file transfer modes. http upload has been smooth sailing for me. It uploads the file to the server and holds it according to a retention period you configure. Shows up in the client you sent it to.

The standalone converse app was problematic when I tried it last. Also, there was a summer of code attempt at bringing jingle a/v sessions to converse, but it was never completed and nobody seems to have picked it up.

There is also Cheogram (conversations fork), which is actively developed/tweaked by the jmp.chat folks - very nice. Also Snikket (conversations fork) that is themed and tweaked to use with a snikket server, but it happily works with other servers.

Another interesting tidbit. Chromebooks integrate the Android runtime to run play store apps. Windows 11 is also kinda/sorta shipping an Android runtime, but not by default. You can also spin up an Android runtime on Linux. I tested the snikket android app on Windows 11 and ChromeOS - works perfectly. So, I suspect all conversations forks can run across Android, Windows, ChromeOS, and Linux platforms - pretty neat. Doesn’t solve the iOS gap and getting the runtimes going could use polish on Windows and Linux. And nothing against the other desktop apps in development, but the ability to essentially run the Android app against most major environments makes me want to contribute to that code base (if I had any ability to develop for android, that is).

If a sizable chunk of the Reddit community can move to an alpha/beta grade link aggregator platform that can’t handle the load because we believe in the decentralization or the instance’s mission or the overall concept of federation, why is it too late for the community to re-adopt a mature messaging platform that mirrors those ambitions?

xmpp has clients doing voice and video - it has for years. It is p2p and falls over in some nat to nat situations, which is where stun/turn come in on the server. Check out jmp.chat - they built a voip phone service using xmpp clients.

https://twitter.com/elliotswartz/status/1483433664616669184?s=21

I don’t think that cultivated meat technically requires the death of an animal at all.

There is no real way to scale production without eliminating fetal bovine serum.

I would like to hear more about what you’re doing / how you have it set up. I’ve used xmpp to relay messages from home automation stuff - which usually involves piping something to a script calling a library.