Selfhosted services like Nextcloud/Immich aren’t nearly as dependent on a critical user mass like Discord/Matrix, but the principle is the same.
If you host for family or friends, they may even use it if you convince them to switch. But when the setup, which doesn’t consist of redundant instances and isn’t maintained by a small army of SysAdmins 24/7, inevitably breaks for longer than a few minutes, most will switch back to the easy, reliable option.
I’d love to be able to disagree in any of your points, but I can’t.
The vast majority of users want something that simply works, is polished and intuitively usable. Reading docs, remembering anything other than the bare minimum, running into issues that don’t get magically resolved within 5 minutes will turn them away forever.
Even people with a technical background will at least partially compromise and migrate towards the services with the most users to not isolate themselfs.
Matrix is neat, Lemmy is neat, Nextcloud is neat (well, in theory), Immich is neat, so many other privacy friendly solutions are neat. But they’ll always be irrelevant in the global context.
Signal and DeltaChat, as well as Simplex and some others e2e communication solutions, are adequate from a technical point of view.
The main issue is always adoption. You can have the most convenient way to safely communicate with people, it’ll be useless if nobody you’re talking to wants to use it.
So, since Signal is very easy to set up and use as well as the most adopted, it’s currently the best pick for regular conversations.
Telcos know that authentication is about the only remaining use case for SMS and are not going to turn down the revenue stream.
And it can’t die fast enough, as it’s essentially the same as broadcasting your sensitive information over unencrypted radio.
Apart from security, phone number based user identification is such a half-assed approach and I still don’t get why Signal wants to die on that hill. It’s inconvenient, yet trivial, for anyone to register a second, third or tenth phone number. With a bit more knowledge and inconvenience, even anonymously. It adds so little.
Sweet, now I get to put “worked with NASA” in my résumé.
Their issue tracker is probably the best bet.
I never use dubious sources like this, especially banking apps.
Oh yeah, it’s usually a very bad idea, especially regarding apps handling sensitive information. Since my use case for APKMirror strictly consists of apps without internet permission in a dedicated, otherwise empty profile, the risk is acceptable.
I’m a bit disappointed with the hypocrisy of some commenters here.
So many very questionable articles, posts and statements that can’t be verified regarding IDF crimes get treated as the absolute truth. Yet a statement regarding a fake story, verified by Hamas and Al Jazeera, gets reported and isn’t trustworthy, since it’s from an institution aligned with Israel?
Holy echo chamber, batman.
That’s certainly one of the takes of all time.
Not even touching the problematic ethics here, you expect China and Russia to simply watch the nuclear warheads rain down on their cities and beg for forgiveness afterwards instead of retaliating?
open from a direct link from the Play store (in which the app page opens, however, with almost no information, such as version, permissions, size and so on, and the download doesn’t start.
Tested this myself, as that used to be the workaround for apps not appearing, but I’m facing the same issue on some apps. For the time being, installing/updating manually via APKMirror isn’t ideal, but I’m not installing the Play Store.
Steganography is a (fascinating) bitch. There are a lot of ways to hide a message in an image which is very resilient to manipulations like resizing, compression or even the loss of information by actually filming a screen versus taking a screen capture.
If you adjust your approach to not rely on a single picture to reliably convey a short message, but part it out over tens or hundreds of frames in a video, it’s basically impossible to make sure that the message was erased without knowing the algorithms used or rendering the video unwatchable.
It’s an awesome field and nothing new.
What? So your advice for improving privacy is to not use a VPN, because the provider may log stuff and instead keep accessing stuff directly through your ISP who will log everything you do and simply use DNS over HTTPS/TLS, which does pretty much nothing for your privacy since your ISP still sees the servers you connect to?
That’s terrible advice.
Mullvad certifiably doesn’t log. Their VPN infrastructure even transitioned to RAM-only a few months back. They’ve been raided by the police and nothing was confiscated because there was nothing to confiscate. Obviously they have a list of registered accounts and payments, but without any connection to - well, connections.
I get what you mean though and mostly agree: There are only a few providers I trust enough to shift said trust from the ISP to them.
As mentioned in the comment you replied to: Yes, trusting a third party is a compromise. But you are also trusting a third party when renting a server for a private VPN endpoint, as well. A third party provider with probably a lot more logging going on than a trusted service such as Mullvad. While being way more exposed.
Since TOR isn’t feasible for most users 24/7, trusted commercial VPNs are the next best thing when the alternative is your ISP logging everything you do.
This is something I’ve not understood yet. If you rent a server somewhere to use as a private VPN endpoint, your clear IP will be pretty much the only one connecting to the server. Correlating your traffic and your clear IP to your masked IP is easy for sufficiently motivated, able actors.
Meanwhile, the main benefit of a shared VPN such as Mullvad is that many users simultaneously use the same endpoint, making it much harder to identify the user (taking only IP and traffic into account), provided they don’t log your traffic.
So while having control over your endpoint is nice, how does that actually contribute anything meaningful to your privacy?
Yikes. This has the potential to seriously damage the reputation of Mozilla. I guess there are 3 possibilities:
In any case: Personally, I’ll never not be grateful towards Mozilla for continuing to support and develop Firefox, which is quite literally the only relevant engine standing against the monopoly of chromium and all the bad that entails. But I trust other companies/initiatives/projects more when it comes to services other than the browser engine.
I’d support removing the post.
CEPA receives funding from various donors, including major technology companies such as Google and Amazon Web Services and key players in the defense industry like Lockheed Martin and BAE Systems. While they list supporters, CEPA doesn’t disclose specific financial amounts. This lack of transparency among think tanks raises concerns about potential biases in their research and publications.
Ah, the meaning of my comment went straight over your head and you resort to throwing insults around.
I’ll spell it out then: The fact that the first shot merely went through his mouth, from one cheek to the other makes it entirely possible, even probable, that Gary Webb commited suicide. Even his ex-wife said so:
Webb’s ex-wife, Susan Bell, told reporters that she believed Webb had died by suicide.[72] “The way he was acting it would be hard for me to believe it was anything but suicide,” she said. According to Bell, Webb had been unhappy for some time over his inability to get a job at another major newspaper. He had sold his house the week before his death because he was unable to afford the mortgage.
Spreading unfounded, exaggerated conspiracy theories while not even getting the facts straight isn’t helping anyone but the perpetrators, especially when the CIA actually did commit some atrocious crimes that can be cited by stating facts instead of fiction.
The first shot went through his face, and exited at his left cheek. The coroner’s staff concluded that the second shot hit an artery.
Not quite the back of the head.
Gaming on Linux has come a long way and I always prefer to run it on Linux rather than a dedicated Windows boot, if possible.
But if you rely on VRR, DLSS and have a decent HDR display, Linux unfortunately still isn’t quite there yet. VRR/HDR is mostly unsupported systemwide currently. DLSS sometimes works, sometimes requires a lot of debugging and ends up actually hurting the performance.
If your hardware setup allows you to run your games at a decent framerate without DLSS/VRR, this likely won’t be an issue for you.
And obviously that account isn’t even a day old. Trust him guys, he’s only here to debate! What do you mean russian bot/troll account? Naahhhh. Anyway, on an unrelated note, US bad, amirite?
Für die Leute, die keine offene Browser Session haben, hier ein kleines, aber funktionales Bash Script, welches im Ausführungsverzeichnis eine
myFedditUserData.json
erstellt, welche bei anderen Instanzen importiert werden kann.Anforderungen:
sudo apt install -y jq
Anleitung:
.sh
Endung abspeichern, z.B.getMyFedditUsserData.sh
chmod +x getMyFedditUsserData.sh
ausführen (Namen eventuell anpassen)myFedditUserData.json
Anmerkung: Das Script ist recht simpel, es wird ein JWT Bearer Token angefragt und als Header bei dem GET Aufruf von https://feddit.de/api/v3/user/export_settings mitgegeben. Wer kein Linux/Mac OS X zur Verfügung hat, kann den Ablauf mit anderen Mitteln nachstellen.
Das Script:
#!/bin/bash # Basic login script for Lemmy API # CHANGE THESE VALUES my_instance="https://feddit.de" # e.g. https://feddit.nl my_username="" # e.g. freamon my_password="" # e.g. hunter2 ######################################################## # Lemmy API version API="api/v3" ######################################################## # Turn off history substitution (avoid errors with ! usage) set +H ######################################################## # Login login() { end_point="user/login" json_data="{\"username_or_email\":\"$my_username\",\"password\":\"$my_password\"}" url="$my_instance/$API/$end_point" curl -H "Content-Type: application/json" -d "$json_data" "$url" } # Get userdata as JSON getUserData() { end_point="user/export_settings" url="$my_instance/$API/$end_point" curl -H "Authorization: Bearer ${JWT}" "$url" } JWT=$(login | jq -r '.jwt') printf 'JWT Token: %s\n' "$JWT" getUserData | jq > myFedditUserData.json