Q: "Will Meta get my data or be able to track me?"
A: Mastodon does not broadcast your email or IP address, so Meta will only be able to extract every piece of information from your public profile data, public posts, and followers-only posts and DMs targeted at users on Threads.
They can and will do so to a degree none of the hobbyist fediverse search engines could even dream of, but that's no reason to overreact and threaten that sweet Meta money we're receiving.
Movim 0.22.1 is out! 🥳
Bug fixes and performances improvements for this version. Check our release note on our blog to know more https://mov.im/node/pubsub.movim.eu/Movim/ab724b18-7b9d-4f14-8111-aada074a73bd 😋
very muito bom #metal #rock #psy #kglw https://youtu.be/IpUKO-WKaqo
One of the issue preventing #LinuxMobile distros from shipping a #PipeWire / #libcamera camera stack is the fact that it requires #wireplumber as session manager, which again does not always play nicely with #pulseaudio, if that is still used as sound server.
Unfortunately switching to PW for sound is not always possible yet because some mobile-specific packages depend on PA. So if you want to help with camera enablement, please consider helping with issues such as https://source.puri.sm/Librem5/wys/-/issues/13 :)
Before you create a Threads account you should know that you can’t delete it without nuking your entire Instagram account.
Glad I have a Librem 5 phone with hardware kill switches - France Passes New Bill Allowing Police to Remotely Activate Cameras on Citizens' Phones
https://gizmodo.com/france-bill-allows-police-access-phones-camera-gps-1850609772 #purism #librem5 #privacy #security
Intriguing how everyone's aware by now that Threads can't be launched in the EU because it is not compliant with privacy rules, but no one outside the EU takes the clue that Meta keeps sucking every scrap of users' digital footprint and that sensible users (not just the European Commission), should deem this utterly unacceptable and stop using any of Meta's services.
#Threads #Meta @EU_Commission #privacy #GDPR
<extra>
Also, it's not like users never had the power to bypass a distro and it's criteria, and install from a third party repo (AUR, PPA, copr, pip, npm, cargo), or install the pre the package manually, or build from source.
<3/3>
But if a package meets the criteria of a distro, them packaging it or not for a distro depends only of a volunteer distro packager wanting to commit volunteer time to package it for that distro.
It does not depend on some “Central Commitee making arbitrary choices” (my choice of words).
<2/3>
Distros have criteria and characteristics. Some distros may commit to only package Free Software, others might not care. Some might want to be rolling release and others stable. But you know what, none of the distros ever kinda hid those criteria. And distros have the right to make those choices, and users have the right to choose a distro that suits them.
<1/3>
One of the things that is kinda irritating for me, in the "Linux distro model" debate (traditional packages vs immutable+flatpak) is the characterization that some proponents of the latter model make of how stuff gets packaged to "traditional" distros, phrases like:
"The distro grabs all the software they want their users to have access to."
As if distros had some central committee that make those decisions in an arbitrary way. And acted as a middleman that wants to keep control.
I’m cross posting this because I think I stumbled on a good explainer about how the Fediverse works for people who haven’t quite figured it out. Someone on kbin thought they could log in to Mastodon using their kbin account, and were confused about why it didn’t work, so this was my attempt to explain it. #kbin #Mastodon #Fediverse
From: @stopthatgirl7@kbin.social
https://kbin.social/m/fediverse/t/136233/-/comment/531804
🚨 Kolektiva.social SECURITY ALERT 🚨
This is an alert for Kolektiva.social users. Please read this post in its entirety!
In mid-May 2023, the home of one of Kolektiva.social's admins was raided, and all their electronics were seized by the FBI. The raid was part of an investigation into a local protest. Kolektiva was neither a subject nor target of this investigation. Today, that admin was charged in relation to their alleged participation in this protest.
Unfortunately, at the time of the raid, our admin was troubleshooting an issue and working with a backup copy of the Kolektiva.social database. This backup, dated from the first week of May 2023, was in an *unencrypted* state when the raid occurred and it was seized, along with everything else.
The database is the heart of a Mastodon server. A database copy such as the one seized may include any of the following user data, in this case up to date as of early May 2023:
- User account information like the e-mail address associated with your account, your followers and follows, etc.
- All your posts: public, unlisted, followers-only, *and direct ("DMs")*.
- Possibly IP addresses associated with your account - IP addresses on Kolektiva.social are logged for 3 days and then deleted, so IP addresses from any logins in the 3 days prior to the database backup date would be included.
- A hashed ("encrypted") version of your password.
🚨 👉 As a precaution we highly recommend that all users on Kolektiva.social *change their password immediately* to a new, unique, and strong password.
We sincerely apologize to all our users and regret this breach. In hindsight, it was obviously a mistake to leave a copy of the database in an unencrypted state. Unfortunately, what would otherwise have been a small mistake happened to coincide with a raid, due to bad luck and spectacularly bad timing.
We understand that our users and other people on the Fediverse will have a lot of questions. We will try to answer them as best we can, but please be patient and bear in mind that we may be overwhelmed with messages, and may be delayed in responding or unable to provide answers to certain questions for legal or technical reasons. As a security culture reminder, it can be extremely harmful to the individuals charged and to our community to openly speculate on the Internet about alleged criminal activity or about what law enforcement may be able to do with seized data. Our present awareness is that the seized Kolektiva data is unrelated to the federal investigation and prosecution and we are exploring legal avenues to have the seized data returned and copies destroyed.
Thank you for your understanding and solidarity
👇 Please see our replies to this post for additional information (1/?) 👇
Today
* Reddit ends free API access.
* Twitter turns off anonymous reading.
* Youtube is talking about banning ad-blocking users.
The tech industry was living on cheep money and low interest rates, and now they're all afraid to let their precious content get used for AI training.
The walls are going up, the lawful corporate web is collapsing in on itself.
I’ve updated my article on "Killing a Decentralised Network (Such as the #fediverse)" to include a link to the very important mail exchange between Meta and @kev .
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Thanks Kev! You set a precedent where the only and sane way to react is to be open and transparent while they tried to take you in an "off-the-record" meeting.
We have only one weapon and it’s transparency. If we lose that one, we lose everything.