Because DNS is the user-facing part of the whole system. There is plenty of trouble with everything else, but you usually don't see that as a user. Also it's a hierarchical system with big providers/governments handing out and taking back names as they see fit, so there is always the possibility to get screwed.
shrugal
joined 1 year ago
Looks good so far, but two major features I want from a note taking app are still missing: Handwriting and table calculations. If they can add good support for those then I'll definitely switch!
RHEL is not Fedora. It's still lead by a community council, even if you don't agree with some of their decisions.
In case of your first link it wasn't even about making a decision. The project has always had the clear stance to not include patented works, so there were no two ways about it.
What's wrong with Fedora?
Afaik it is all connected to the domain name, so they could definitely start to impersonate any .ml instance. Other instances could detect that the signing key for federation messages changed, but that's about it. Their admins would probably have to block/defederate them manually.
Not really. Most centralized services are accessible via multiple domains, e.g. for different countries. This would just disable one of them, but users could still use another to log into their accounts. For the Fediverse it "disables" an entire instance, cuts it off from federation and locks out users.
Lets not put a positive spin on a situation that exposes a weakness of the current system. The federation protocol needs to be able to handle these things gracefully, like propagating domain changes and migrating accounts between instances!
A domain takedown was never able to shut a server down, not even with centralized servers. Most big services are accessible via multiple domains of different countries, and this would just disable one of them. But for the Fediverse that means that they also "disabled" an entire instance with all its users.
This actually shows us that relying on domains can be a problem for the Fediverse! Imo we need to upgrade the federation protocol to be able to handle these things, like propagating a domain change or migrating accounts to other instances.
This is suspicion on the level of "you can't be sure reality didn't just pop into existence 10 seconds ago". You can never be 100% sure of what others are doing on their hardware, or of anything really, especially if other people are involved. Your chat partners could leak all your chats and metadata for all you know!
What we do know is that Signal is operated by a non-profit foundation, their client and protocol are open source and considered the gold standard for privacy by pretty much every expert on the subject, they had multiple independent audits and a very good track record, they were subpoenaed and couldn't comply because they didn't have the requested data. That's about as good as you can get.
You can install Libretube and make it the default handler for youtube and many public piped domains. This way when you click on a yt link it opens in Libretube and plays the video via your piped instance.
On my phone it's in the system settings for the app under "Open by default".
This is not the solution! Being able to pick a server to trust your data and content moderation with is a feature, not a bug.
What we do have to do is make this feature more resilient and easier to use. Like adding the ability to easily transfer accounts and communities between instances, or even change the domain name of an entire instance.