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?
What can you get to within a 15-minute walk of your house?
Shot.
Just kidding, I live in Europe. :) All the things in the list except the arena.
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
Hopefully like https://mobian-project.org/
I did the survey but please would you mind identifying yourself and linking to the research paper when it’s ready?
I’m not a psychologist but it sounds a bit like https://en.wikipedia.org/wiki/Reaction_formation - “You want me not to pollute so I pollute even more”
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.
I’m surprised nobody pointed out that tyres are extremely polluting:
https://www.theguardian.com/environment/2022/jun/03/car-tyres-produce-more-particle-pollution-than-exhausts-tests-show
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.
This is debatable. The GPL allow redistribution of a given version of the software without additional restriction. If the user receives that copy knowing in advance that redistribution will lead to retaliatory actions this can be treated as an additional restriction.
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.
This is not correct. APT always verifies cryptographic signature unless you explicitly disable it. Yet it’s very important to understand who is signing packages. What kind of review process did the software go through? What kind of vetting did the package maintainer themselves go through?
If software is signed only by the upstream developer and no 3rd party review is done by a distribution this means trusting a stranger’s account on a software forge.
Update: the Debian infrastructure supports checking gpg signatures from upstream developers i.e. on the tarballs published on software forges.
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.
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.