Why am I here and not on #Bluesky or #Threads? Because here I am on my own instance, hosted in the EU, and not on a centralised service from the US (which both Bluesky and Threads are) where soon a Trump government is installed that can easily force both Bluesky and Threads to hand over full access to all my data. That's my personal risk calculation. Yours might be very different. And that's perfectly fine!
And yes, I still treat every single post and message here as ultimately being stored and analysed by adversaries because the for me the Pub in ActivtyPub means public. My private communication happens via Signal or old fashioned pen and paper. Or, even more often, by direct communication over a coffee, beer or a walk outside :)
Another reason for staying here is metadata. Trust me, not many organisations out there really care about the content of your posts. They focus far more on the connections and frequency of data on likes, boost, follow/unfollow etc. In a centralised service that metadata is, ohm, centralised too and easy to access. In a federated network that isn't that easy, especially when, like me, you live on your own instance and not a big one like mastodon.social. Decentralisation makes abuse expensive.
@knezi Try it :) You can see the difficulties already in your daily experience here when you notice that not all replies to a post show up in your timeline. Building the complete social graph of all interactions in the Fediverse is an exponentially bigger problem than doing that on a centralised service like Bluesky or Threads.
@knezi@jwildeboer Quite a lot of the metadata isn't really. They can scrape obvious interactions like if you respond do a post, but not much else. Most instances don't let anyone but the poster see who actually clicked "favorite" for example. They'll see boosts, but that's about it.
More importantly, they can't see the other, less obvious stuff. For example, Facebook and Twitter know if you click to open a post, but Mastodon won't tell third parties about that.
@knezi@jwildeboer As a side note, Mastodon offers a few useful features like automatic post deletions and hiding more profile stuff. This does not by any means guarantee third parties can't scrape or see any of this, but at the same time, it does limit them a lot more. For example, unless they're scraping constantly, they're not going to see older automatically deleted posts.
A lot of instances will block those who spam too many requests I imagine.
Like you said, the data is already public on ActivityPub. Whatever adversaries interested in building the social graph or analyzing metadata can do so, regardless of your instance location or who is power.
Seems pretty easy. Already several other PDSes out there e.g., letting people make custom feeds using hashtags, LLMs, whatever to drive a bespoke algorithm.
I’ve been comparing services (been here for a couple years) for about a week. There are pros and cons to both.
@raphael They’d have to check/scrape *all* ActivityPub instances all the time to get a complete social graph of the Fediverse. While at a centralised service that social graph is part of the architecture. That’s a huge difference.
@raphael Or to explain my argument in more simple ways: Twitter has the Firehose, where you can access all traffic at once. In a federated network such as firehose doesn’t exist and trying to build it is an exponentially bigger problem that IMHO cannot be solved.
Oh, please... I was toying with the idea of making a search engine for the Fediverse last year. It took me less than a week to scrape and index 8 million ActivityPub accounts last year, with all of the users posts, including those that had enabled authorized fetch.
@jwildeboer This has the potential to be very disruptive because how can you compel people to earn a living if they choose poverty? How can you sustain a civilisation if people refuse to reproduce? How can economic empires thrive if individuals no longer wish to work for large corporations? When this behavior will be recognized as disruptive, the absence of positive signals will be seen as a negative sign.
@jwildeboer Come to think of it, this is going to be even more important, because society is experiencing a "passive revolution". Young generations simply do not want to work for "the system". And, contrary to popular belief, a sizable proportion of them is not on mainstream social networks.
@jwildeboer All these work because the burden of the proof is put on you. That is the opposite of a fair judicial system, but we are talking of unfair regimes.
@jwildeboer If you want a job, employers want to see your Linkedin and FB account. It may not be always legal, but it is hard to prove you did not get the job because of lack of access or lack or a suitable track record. In some dating circles, people who do not have the right pictures to show on their phones are suspicious. Online shopping sites make it more difficult for new customers and will extra check them. It is easier if you have a track record of purchases.
@jwildeboer That is already a reality today. If you need a US visa, you need to tell them about your social accounts. Be prepared to have to explain why you don't use FB. If you need credit, you need a record of your credit usage. Problem if you pay most in cash. In countries where most people pay by card, be prepared to explain what you do with your money if you are controlled by the tax authorities. They will have access to your bank accounts and see cash withdrawals.
@jwildeboer It is good that someone posts about the importance of metadata.
However, in a surveillance state, the absence of signal is a signal in itself. If you do not have a continuous track of metadata on social networks, if you do not show a record of your life as a "good citizen", that is enough of a signal to light a warning. And that is a lot more difficult to escape.
Capital-P "privacy" is absolutely incompatible with publishing networks. Telling people that Mastodon is any better in this regard is at best wishful thinking and at worst irresponsible.
We *might* make it work with AP if we have better C2S implementations where end users control the keys and allow for E2EE, but if your threat model involves 3LAs and corporations building your profile, the best solution is to avoid any social network and stick with Signal/Matrix/XMPP.
@raphael I specifically pointed at that in the second toot on my thread: „I still treat every single post and message here as ultimately being stored and analysed by adversaries because for me the Pub in ActivityPub means public.“
Okay, cool. My objection though is to the first post. It doesn't matter whether we are here, Threads, Bluesky or Twitter. When it comes to social media, the only winning move for those concerned about state actors and large corporations is not to play.
@heaths To identify yourself in the Bluesky network, you need an identifier. The layer that manages and provides these is the PLC. And, guess, who runs the only PLC that is used in the Bluesky network?@pravee_n
@jwildeboer@pravee_n my understanding was that anyone *could* run a relay, but even their docs admit it’s a ton of bandwidth and implies there’s not much incentive to do so. So maybe they are practically running all the relays and that makes them practically centralized.
Still, it seems to solve for the problem of the Mastodon effect where sites are getting DOS’d by instances requesting data for thumbnails.
Personally, I see pros and cons. To each their own, though.
To clarify: not trying to push anyone anywhere. 🙂 This just seems like a great exploration of the protocol. I skimmed the docs earlier - I’m really liking the Labeler functionality - but this thread has convinced me to read more thoroughly.