squaresinger

So, a gas chamber? Back to 1938, are we?

One relevant part that I couldn't really find in the article is that helium is so light that it escapes Earth's atmosphere when released into the air.

So any helium that is released to the air is permanently gone.

There is also no known way to synthesize helium, and it also doesn't renew itself at all on Earth.

It's also the only substance we have to cool stuff really far down. That's why e.g. MRIs depend on it.

And we put this precious, finite and often life saving substance into kids' balloons to make them bobble nicely through the air.

The problem is that only people who came into power using the current system would have a chance to change the system. And why would anyone want to change the system that brought them to power?

E-mail. E-mail does support small servers.

Btw, I think you are mixing up a few topics here, so let's see what you actually want.

• Protocols are what computers use to communicate with each other. No protocols means no interaction between different computers/servers. Without protocols, none of the things you ask for can be possible.
• Federated services don't have single sign on. On the contrary, single sign on is a centralized service not a distributed one. To clarify that: I cannot log into lemmy.world with my feddit.de accout, same as I cannot log into hotmail with my gmail account. In both cases I log into my instance/provider and this allows me to communicate with people on other instances/providers. Federation is the process of sharing content between instances. SSO on the other hand is a centralized service that then communicates with other services to let you log into these other services. For example, I can log into my Google account and then use this to login to other sites. This only works because people trust Google. This would not work as a decentralized service with untrusted servers.
• Duplication is used on federated services for a few reasons. First, it's a kind of caching mechanism distributing the load. If someone posts something on one instance, it's transferred only once to the other instances which then serve it to all their users. Without duplication, each individual view would have to be requested again from the original instance. The other advantage is that the admins of all the instances retain control over the content. If the other instance goes offline, users can still see "their" copy of the content. And if the other instance doesn't moderate their content, the mods/admins of your instance can do that themselves.

So as you see, these concepts aren't there just for fun, but for a purpose.

A squadron of military planes is a bit hard to come by as a private person.

But I wonder if people would also be that fascinated after 25+ years if I flew some DJI drones at 1-2km height in the night with bright LEDs on their bottom and dropped some pyrotechnics from them.

This has been confirmed independently multiple times as two groups of A-10 military aircraft dropping flares with parachutes for training purposes.

And still you see videos titled "Still no answers 26 years after the lights appeared over the valley". Well, no answer that these guys want to hear.

And what it looked like is quite easy to check, since there are tons of photographs of that incident.

There are two issues with that:

• The GDPR notice on feddit.de is not GDPR compliant, and the link isn't even visible on mobile.
• If you request deletion, they can't guarantee that the data is deleted on federated servers. They can send deletion messages, but federation is constantly not working correctly, other instances can decide themselves whether they do delete stuff, and if an instance is unreachable for a while, the deletion message will be dropped.

Lemmy, or even ActivityPub are designed to be non-GDPR compliant. (Probably not on purpose, but the way it works makes it basically impossible to be GDPR compliant.)

That already exists. The person who created a post or comment can delete it. But it only works sometimes, since federation is constantly not working correctly.

That's true, but neither the article nor the discussion are about ActivityPub.

Both are specifically about Lemmy, and Lemmy does have private messages.

I said: Code changes are easy, all the other things in regards to supporting playing on Linux (anticheat, support requests, testing, ...) is hard.

You said: But code changes are easy because steam has libraries to unify distribution.

Do you see the problem here?

What are you going to tell me next? That code changes are easy?

And the content of private messages.

How about private messages which are also unencrypted?

It's actually not wrong if you look at it in another way.

• Big tech will abuse your data, but it will do within legal constraints, and there is actuall (though weak) accountability of these companies due to the legal system.
• On federated services like Lemmy, instances are hosted by anonymous individuals. Most social media laws don't apply to them, and their legal accountability is basically zero.
• Lemmy, for example, does not comply with GDPR. There is no legal notice, no privacy contact person, no banner asking whether you are ok with the fact that your data is sent to unknown servers in random nations, no nothing. Private messages aren't even encrypted, so any admin can read them without issues.
• There is no way to actually delete your data, as the GDPR requires. Deleted posts are only marked as deleted and you can see their plain text content by just pressing the "reply" button in any of the apps. There isn't any kind of guarantee, that your post will be deleted on other instances. If federation has problems, the post will remain on other instances and is now permanently undeletable by the user.
• There are no moderation standards. Some instances will delete nazi content, some basically require nazi content. And some instance admin might even edit your posts to say something completely different. It's all possible and in the hands of random people on the internet.
• Hobbyist-run services are much worse when it comes to availability and reliability. If something happens while the admin is on holiday, nothing will get fixed. If the admin runs out of money, doesn't care anymore or even dies, the instance with all it's content and users is just gone.

So there are very real risks attached to a hobbyist-run service with no legal accountability and no transparency at all.

We all know the downsides of Big Tech though, so it's everyone's personal choice to figure out which disadvantages hurt them personally more.