Thanks!

How does it compare with Paperwork? https://www.openpaper.work/en/

You are better off with an encrypted password store and a 2FA on a phone. You can back up both, easily, and they are both protected with fingerprints and/or global passwords.

Radicle has plenty of red flags, see https://lemmy.ml/comment/8982169

People panic about face scan while the ongoing massive privacy breaches exist around online services and electronic devices. The amount of personal data that people pour into smartphones is enormous compared to using that vending machine. We need more GDPR.

I would come along a question that I was well educated on, and the top voted responses were all very clearly wrong, but sounded correct to someone who didn’t know better.

This can be said to https://news.ycombinator.com/ as well. I wonder how much of this is due to sock puppets and bots.

This tends to give more influence to people who spend more time on it and write more. And they are less likely to be subject matter experts.

Honest question: deleted comments might be just hidden and still up for sale, do people know if GDPR can come to the rescue here?

Github is designed to centralize git (as the word “hub” suggests). You can still migrate away code, issues and wikis, but contributors, followers, wiki editors, issue subscribers, visibility in general and github stars are locked in. Discoverability matters to projects trying to attract contributors.

Count me in! (Or shall I say: you have my sword?)

Because Valetudo is not a custom firmware, it cannot change anything about how the robot operates.

Source: https://valetudo.cloud/pages/general/newcomer-guide.html

I did the survey but please would you mind identifying yourself and linking to the research paper when it’s ready?

Does OrganicMaps have editing abilities?

signal is designed not to trust the server

Unfortunately this is not enough. A malicious Signal server can mount a timing correlation attack and infer the social graph of an user. Having a centralized server makes it more difficult to mitigate such risk.

Then yes there’s EEE danger. Hopefully the Mastodon developers will resist that.

Unfortunately developers can do very little to prevent that. EEE works by first attracting a large userbase into a service and later on prevent them from leaving. It’s up to instances admins and users to defederate to prevent EEE.

Here’s a summary: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

That’s besides the point. Of course it’s always possible to create new communities on new instances, and import posts from various sources, but the original community would be still gone.

If an instance is shut down or becomes unusable for a long time there is no way to automatically migrate users to a new instance. Additionally, there is also no guarantee that all users will move to the same alternative instance. This can also cause unnecessary conflict around which alternative instance becomes the “legitimate” successor.

What you are describing is just a local cache of !lemmy@lemmy.ml on your instance and it works only if it has been populated before the downtime of lemmy.ml. If lemmy.ml never comes back to life nobody can post to !lemmy@lemmy.ml proper. All the communities on in would be dead.

This is not a communication problem. Communities are indeed centralized and if an instance is shut down permanently or loses its data all the communities are gone. This is a big design problem of Lemmy.

Edit: it’s sometimes possible to rebuild new communities on another instance and recover past messages that have been replicated on other instances (if there were full replicas) but this requires all users and moderators to agree on where to migrate and avoid splits and so on.

If say lemmy.ml is down, what’s the point of other servers existing, if most of the content and users are here?

There is no replication and failover so the problem is not solved.

blockchain technology

Urgh, no way. Replication and some basic message signing would be enough.