🧵1/3 Tested for you: If I #block an #instance or people privately, I can no longer interact with them after a short wait, even though I can still see the profile. But I have tried this with #Threads and it does NOT work!
Regardless of whether I block the whole domain or just one account (test with Insta-Boss), I can still interact and comment (he probably, too?). So I will have to move to another instance with #blockThreads ▶️ https://fedipact.online/#privacy#dataSecurity#GDPR@Gargron
@NatureMC@Gargron your post isn't clear to me: are you saying that if I (individually, on mastodon) block a Threads account, that Threads users can still see and interact with my posts?
And is the situation the same if I block the whole threads instance?
@deborahh I could interact after blocking the instance AND the account (Screenshot 1). But I learnt that individual "blocks" are in reality only filters: https://docs.joinmastodon.org/user/moderating/#block
It's different to a block made by an instance.
You can try it yourself because it can be different on other instances. Some already blocked Thr. See links in my 🧵 and here: https://fedipact.online/
@NatureMC this is ehat I want clarified: when you say "I could interact" I assume you mean using your mastodon account, correct?
That doesn't worry me so much, as I can choose not to interact. ¯_(ツ)_/¯
I hope I notice in time to not interact 🤦♀️
But what worries me: if I (individually) block an account (or all of threads) can they still interact with my posts? I REALLY do not want Threads trolls on my feed, in my replies.
@deborahh For the function please read the link doc - it explains everything.
Yes, my screenshots work with my instance - instances may be very different.
I couldn't test if the blocked boss of Insta can interact with me.😉
My problem is not so much trolling, it's a question of security because Meta grabs all content for AI etc. The Fediverse was free of that problem and after a full federation (not yet existent) they must formulate how they want to protect us against data collecting by Meta.
@deborahh EU: If you put your photo in a system that has the rules "we can grab everything", they'll do it and you can only stay away. If it's a system with the rule: We never grab anything" and they do it, it's completely illegal. If someone grabs your photo from outside an system (f.e. on Google) without asking you, it's illegal. It's a very complicated legal matter (also depending what is an creation!).
We still have no good regulations for AI-training yet. But laws for collecting datas and
@deborahh No, a written post is not automatically a creation/art. (If it is completely public, Media can eg embed it by code without asking. May not if it is not public.) But Mastodon says: We don't grab it for AI. Meta does!
Photos have a copyright and Meta especially grabs art from artists. It's a big debate at the moment how artists can protect their art or sue AI companies.
Or if you post a photo of your baby: Meta uses it to train AI. If you join FB or Insta, it's in the GTAC. Not here.
@deborahh Meta was often sued in the EU.
Please excuse me that I can't explain all this satisfactory, I'm neither a lawyer nor an IT specialist.
Therefore, I count on clear general terms and conditions. And if Mastodon wants that federation they have to formulate them not in a moment when it's already too late.
@deborahh To your question 1: If you block a whole instance, it should filter all accounts on that instance. I you block only one account, only this account will be filtered.
And you can choose how to post. "Followers only" makes your posts only visible to followers, "unlisted" also to others (ex: by boosts) and "public" brings you even into the Live Feeds of your instance and other instances that are federated with your instance.
Blocking prevents the other user or server fetching and seeing your posts. But since #threads isn't fetching your data right now, blocking #threads makes no difference in that regard.
Blocking also means that it does not actively show you content of blocked users.
But it does not prevent you from seeing them. That's natural because you can always access any content of users you have blocked by using a different server or logging out.
@folkerschamel@Gargron So please don't call it a block. I can even INTERACT with the blocked users. Even if they don't see this, it is just a filter not a real block. The question of complying with EU laws remains open.
Thank you for explaining that, so the only alternative for me is to move to an instance which doesn't federate with Threads. https://fedipact.online/
(BTW, even the block of shitter was better.)
How sure are you that this is not the case for you? If not, this sounds like a serious bug. Can you report that bug so that it will be fixed as soon as possible?
Usually directly approaching a open source developer does not have much effect. Especially lead developers like @Gargron get plenty of messages directly directed to him, they won't read all of them. Open source projects work differently.
That's exactly the reason why commercial software like #threads is usually much more successful, because far most people prefer convenience over nerdy technical stuff.
@folkerschamel I'll say it again in a friendly way: I don't need mansplaining. I don't need your arrogance about my knowledges.
Some people just want a network that is compliant with EU laws and Meta is not that. There are no statements about how compliant the new federation will be and that worries people. Full stop. End of debate.
@NatureMC My understanding is that the delay of the #eu launch is exactly because #meta needed the time to make #threads#eu law compliant.
Anyway, I didn't want to criticise your knowledge. Open source software development just is a nerdy thing.🙂 But I admit I wanted to encourage you a little bit to contribute to it by reporting the issue you have encountered.
#mastodon, as every open source projects, lives from people giving back and contributing to it.
🧵 2/3 I understand if people love #Threads and federations with big #corporate platforms but I want to have a real choice. @Gargron
I didn't leave the big platforms to get them back without any protection. I could post for followers only, yes, of course, but this takes me my reach.
If it stayed that way (described above), I could go straight back to large platforms.
@NatureMC@Gargron Hmm, following and waiting for some clarity about this. There is a lot I don’t understand, but I agree with your bottom line: I found happiness by abandoning corporate social media and coming here and I would hate to see it ruined. Letting users opt in or opt out seems reasonable. If that doesn’t work, I’m going to have to migrate. Sigh.
This poses legal problems (EU privacy and digital laws) and the problem that Thread collects everything in its system for AI and other reasons. I want to be sure that it can't if I decide it. Otherwise, I don't need mastodon.online - then I could change to Insta.😉
@NatureMC You are absolutely correct to be concerned. I can confirm that this behavior is replicated on my instance. As you discovered, this is not a bug but a feature of Mastodon. Even if you reported it on GitHub, it would likely go unanswered like most requests over the years. Eugen does not share the same philosophy as most of the developers in the Fediverse. He has a growth mindset rather than a privacy one. This is his right and I support your decision to leave the large unsafe instances!
@NatureMC from a practical point of view, blocking is enoughbto make you invisible to that specific user and viceversa. I don't really understand so much paranoia regarding threads' federation.
Add comment