Daniel Supernault
After some careful consideration, I have decided to block threads.net on pixelfed.social and .art by default
However, users will have the ability to unblock the domain
Soon we will be selectively enforcing authorized fetch for accounts with domain blocks so as to provide the best of both worlds.
(I'm also shipping a command for :pixelfed: admins to easily add user domain blocks for all local users)
I'm eager to hear your feedback!
Bèr Kessels 🐝 🚐 🏄 🌱
@dansup will you be reviewing your consideration when you have data?
E.g. the amount of your users that manually unblock. Or amount of interactions with threads? Or when you have a statistical significant amount of "reports" or "flags" over various domains, incl Threads?
Bèr Kessels 🐝 🚐 🏄 🌱
@dansup I can imagine that hard data can strengthen, or sway, your stance on this.
phiofx
This. As an example of the broader collective intelligence and immune system that hopefully will develop organically within the fedi. With developers shaping is software dna and admins, moderators and maybe even new functions being vigilant about what is happening.
Danie van der Merwe
@dansup I've always been pro-choice for users to block or not, but like some others I think it would have been better to have had the default as-is (open) and then users choose to block.Blocking on behalf of everyone seems to veer more towards censorship (my opinion). But OK choice is at least there. I'm keen ton reconnect again with my wife who is not on any alternative social networks.
Tokk :arch:
@dansup Default Blocking of big instances will slowly kill the fediverse. If big companies learn that they are not welcome they won't make efforts any more and let's be honest here: Most Users don't care and won't be in the fediverse in this case.
mateomaui
@dansup looks like the most sane, least fanatical approach I’ve read yet
Healthcarer
@dansup If I understood a word if it I might be alarmed?
phiofx
@berkes I am convinced that if people keep building in line with the #foss human-centric values of the fediverse there is nothing to worry about (no real threats from threads). Adtech based of profiling user behaviors has been an all dominating force not just in social media but almost all personal computing experience, but it has saturated and is end-of-life because thats how capitalism works: no growth = death.
Meta/Threads wants to cannibalize Twitter? Be my guest.
Bèr Kessels 🐝 🚐 🏄 🌱
@phiofx @dansup I think it's important to be vigilant and careful. To err on the safe side when information is lacking.
So I think what @dansup does is good.
But I also believe in science and evidence. That, if Threads proves not to be the threat, or proves its users behave (any instance, really), that then the actual facts and data are at least considered.
Alex Granford
@DavidBHimself @dansup I also think it is wrong to apply blocks on interoperability and freedom of communication - by the very people who stand in the heart of fediverse applications, and in such authoritarian way.
Instead of fixing some of the fundamental gaps of your platform, like inability to set detailed dynamic locations to Pixelfed posts as on Instagram, you have spent time and effort on something taking your community away from other popular authors.
DavidB
Yes, this is a terrible move in so many ways. Especially #PixelFed of all platforms. All users of #Threads are #Instagram users. All of 100 million or so of them. And instead of showing them that there is another way, PixelFed is shutting the door on their face!
I have yet to see a worse way to promote the #Fediverse and the #OpenWeb.
I just can't understand this decision.
When a random instance is preemptively blocking Threads, they're only hurting themselves, but a flagship instance?
They think they're "fighting" Meta, but all they're doing is hurting their users and hurting Threads users, who are our friends and families, the people we want to bring over to the Fediverse.
Just when I was starting to love PixelFed and wanted to start promoting it more, I'm seriously reconsidering now, and will probably leave the thing altogether. What's the point of even changing instance when the flagship and the developers are acting against the Fediverse.
This is really upsetting.
DavidB
@dansup@mastodon.social That's quite disappointing.
Glad we can unblock though, but it should be the other way around.
UkeBLCatboy
@dansup @berkes it makes sense, and is also what threads will do; users will be able to opt in to interacting with mastodon etc. I think it makes sense, 99% doesn't realize they are posting to other platforms and people too otherwise and might not want that.
eduo
@dansup @DavidBHimself @alexgranford
Not only is threads doing the same, setting the tone already, but it's also that IT IS facebook. It pays to err on the side of caution, considering their history.
Everyone who cares and is in these servers will open it up (and will know the other side had to do the same for them).
AndrewFelix 🐀🏴☠️ 🇵🇸
@dansup there are some amazing artists on threads. Personally I don’t think it’s a great idea, and it may limit potential growth.
AndrewFelix 🐀🏴☠️ 🇵🇸
@dansup on the other hand people might not be aware it’s blocked by default.
Seriousity🐺
even though I haven't use pixelfed, atleast they pick the right choice to block meta
Stuart Crabtree
@dansup why?
Esther Payne :bisexual_flag:
@dansup thank you for doing this.
I think it's a very important part of the fediverse to have this attitude. To give an example of community based hosting with a focus on Freedom of association and Consent.
Yes Free speech is also important for our internet. But it can't come at the expense of harms to others.
🎓 Doc Freemo :jpf: 🇳🇱
Well I certainly will be refusing to use pixelfed then, this is uncalled for.
Tim Chambers
@dansup I know you were in a hard place on this decision. While not one I would do - I respect the difficulties in making the call, appreciate you offer the opt in Threads option for users.
clacke
@dansup That's a really cool compromise.
Sean Bala
@dansup It seems like Opt-In might be a nice middle ground between full openness and full blocking. Was there something that prompted you to go down this route? Was it Threads opting for Opt-In?
🇨🇦🇩🇪🇨🇳张殿李🇨🇳🇩🇪🇨🇦
No. It. Shouldn't.
Features, especially those related to privacy and/or security, should *always* be opt-in, not opt-out. Opt-out is the cynical approach crapholes like Google, Meta, and X use to sneak their antisocial features into others' experiences.
I applaud @dansup for doing the principled thing. It's refreshing in the tide of disappointment I'm getting from other fediverse instances.
Bernie The Wordsmith
@tchambers @dansup The speed of this guy implementing. Never seen something like this ✌️
clacke
@freemo It is literally called for.
🎓 Doc Freemo :jpf: 🇳🇱
@clacke I see plenty of reasons in there to block threads, not a single thing to justify software blocking by default.
Debbie Goldsmith 🏳️⚧️🏳️🌈⧖
@dansup Not happy. I will unblock it for my account as soon as that feature is available. Could you please point me at the PR so I can follow it?
🎓 Doc Freemo :jpf: 🇳🇱
The feature which allows an admin block to be overruled is not what I have issue. The fact that the software itself dictates pre-blocked servers is something I am not ok with.
Owl! 🦉
🎓 Doc Freemo :jpf: 🇳🇱
Oh yes, I misread that. My apologies, no issue with the software then afterall. Thanks for pointing that out.
PhilipKing
@dansup I don’t understand this. I see on Threads ordinary people doing ordinary things. Perhaps you’d like to explain what it is you are worried about?
clacke
@kudra It's a tradeoff. Enforcing authorized fetch for public posts means they are no longer part of the public web, they become fediverse-only.
Depending on the author, their purposes and their situation, this may be exactly what they want or it may be the opposite of what they want.
Kudra :maybe_verified:
@jill @dansup I suspect this is because Mastodon doesn't use authorised fetch by default, and only using it with some instances means you allow people to continue to communicate with the instances that don't have it turned on (if I understand correctly, this is a lot of Mastodon). It would be infinitely better if all Mastodon used authorise fetch by default, it is more secure, and many other Fediverse projects do.
jill
@dansup non-technical person here! What does that mean "Soon we will be selectively enforcing authorized fetch for accounts with domain blocks so as to provide the best of both worlds."?
clacke
@solitarywalker The analysis is out in the public, no need to let thr consequences hit your server before you act on it:
solitarywalker
@dansup Unfortunately all you’ve done here is state your decision, without any reasoning behind it. That makes it seem arbitrary and hostile. What harmful/abusive behavior is this instance engaging in which you feel justifies blocking at that level?
clacke
Owl! 🦉
As i read it, @dansup said he will block threads by default on pixelfed.social and pixelfed.art, the instances where he is the admin, and he created a tool to do it. Pixelfed-the-software won't have any blocks by default.
Esther Payne :bisexual_flag:
@dansup you do have a lot going on and it is hard to balance developing, communication and also your own personal needs.
Many folks on here do have friends and family on Facebook and Instagram.
It can be hard to figure these things out and on Fedi there is an quite rightly an expectation of transparency. Which is it's own pressure for a project. Especially with the stage you are at being the developer and the figurehead.
It's an issue for lots of projects.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.