Wait for the next hardware upgrade and then set up a new system while keeing the old system running in parallel.

It requires a bunch of browser features that non-user browsers don’t have, and the proof-of-work part is like the least relevant piece in this that only gets invoked once a week or so to generate a unique cookie.

I sometimes have the feeling that as soon as some crypto-currency related features are mentioned people shut off part of their brain. Either because they hate crypto-currencies or because crypto-currency scammers have trained them to only look at some technical implementation details and fail to see the larger picture that they are being scammed.

This goes to the main developer, which is a person in Canada. But I think they have a few collaborators that will likely get on board more now that they want to set up a non-profit (?) foundation to manage the Pixelfed codebase and IP.

Most of human history…hmm checks notes… since the invention of capitalism about 400 years ago, yes.

Even serfs under feudal lords had significantly more free time and while basic child labor was common, it was mostly in family run farms.

And water is wet 🙄 Those 20% AfD voters are not ghosts that only come out when there is an election.

This is or at least was a problem with cross-posts in the same community in Lemmy as well. I think now Lemmy just prevents posts with the same URL to be counted as crossposts when they are in the same community.

The server can swap to a modified JS that exfiltrates the e2ee key and thus allows the server owner to decrypt the messages, or in more advanced encryption schemes add additional keys without you knowing and achieve the same thing.

Yes you can juryrig something like that with cookies, but it is highly fragile and browser based e2ee is basically a scam anyways as the server serving the website can always swap out the javascript that decrypts the messages.

e2ee is not really compatible with what you want due to necessary key management, and once you drop that there are so many possible options for what you want that I don’t want to list them all here.

Probably the opposite. By staying in NATO, but rendering it mostly obsolete, attacking Canada would be much less of a clear case of being an attack on NATO.

However, realistically speaking the rest of NATO has only limited force projection capabilities and thus wouldn’t be able to help Canada much.

Movim does, for Libervia and Dino I am not 100% sure right now, but at least for Libervia the browser version should have it as it is really more of a general Webrtc browser feature than client specific.

If it was an article about an organisation that is 95% or so female then yes 🤷

Maybe it was based on the “lifetime” of their hamster 🤷

I wonder why the BBC author seems to have explicitly chosen only images with what appears to be female Bundeswehr soldiers? Kinda odd choice 🤔

https://join-lemmy.org/docs/administration/configuration.html

You need to set it to proxy all images.

The currently common older implementation of e2ee in xmpp has the same issue with only the message body being encrypted. There are newer specs of OMEMO that have better metadata protection, but its adoption in xmpp clients has been very slow.

Prosody is more of a sandbox, with Snikket being a preconfigured version of it, but yes running Slidge will be a bit easier with a normal Prosody server.

Well, maybe. But in which scenario would such a tactical nuke be used against an enemy that also has nukes? Most likely in one where the large scale conventional attack is already happening.

At least in Europe these tactical nukes are supposed to be a counter against a large scale conventional attack that can not be defended against with existing conventional means.

Then you have not enabled to full image proxy (and note that it does not work retroactively). Here on our instance all the Nicole images were proxied correctly to protect the privacy of our members.

Today xmpp uses a distant relative of those original jingle specifications, which have been modernized to use Webrtc.

Lemmy does have a functional image proxy, but due to the storage and bandwidth requirements many larger instances have chosen to not enable it.