@FASA_Andrew_1879 I believe it's 2 servers. Gab.com is the main one, and it's possibly another one which I can't remember right now :D

@maloki @FASA_Andrew_1879 Gab.ai, I hear

@cj on it – we'll be adding anti-fascist language to our CoC this weekend.

@gingerrroot Those two are the ones we know of right now

@maloki and update: i also saw someone saying they have an .io but i haven’t checked that yet

@gingerrroot .io doesn't resolve for me, I think maybe they said it because I said ai or io

@sara It's atleast gab.com and then maybe another gab.ai or io? something like that. I don't remember.

@maloki @sara Deleted my earlier message to say I just came across this list: https://efdn.club/@norikawa/102300879956456736

@sara @maloki They don’t exist yet. Be on the lookout for further posting when it actually happens.

@riking They have publicly announced that they are making gab.com into an instance it's probably not going to be another domain, and if it is we still have 2 weeks to find out. . @sara

@SelfsameSynonym Well, it's a step one. And Florence does have a chance to add features on here. If people submit the PRs we'll accept them especially in regards to this.

@maloki suspending their instances is definitely something to do.

Are privacy tools like domain blocking not already in the backlog?

@SelfsameSynonym I'm not sure what you mean.

You can read the issues in the repo of you want more details right this moment.

I'm in bed, and about to fall asleep, because medicine.
I'll get back to you tomorrow.

@SelfsameSynonym @maloki oh. That explains the behaviour we've seen.

@phessler @SelfsameSynonym yeah

@SelfsameSynonym @maloki and it would work the same in any other federated system without authentication basically

@charlag @maloki I’m sorry, I was yawning. What irrelevant excuse were you making for Eugen’s terrible design?

@SelfsameSynonym @maloki it's not an excuse. It's just what is public is public for everyone. Another possibility is share with specific groups. Tell me how I'm wrong please.

@charlag You're not wrong, and I don't think we should engage with infighting, we are on the same side here.
Let's focus on what we can do, and see where that'll lead us
@SelfsameSynonym

@charlag @maloki If I block you, you can’t see my public toots. That’s not how it works at the instance level. Here’s how that works:
-Admin A on server A sees that Nazis set up server B.
-Admin A suspends server B
-Server A deletes all data from B in its database, doesn’t write new data
-Server B still connects directly to server A, delivers A’s data directly to Nazis on B
-Nazis on B can @ and interact with statuses on A

I’m fucking sick of “you can’t do anything about it because it’s P U B L I C and F E D E R A T E D” when it would be trivially easy for instance suspension to reduce the access a suspended instance has by simply rejecting direct requests from the suspended instance.

If it worked that way and enough instances suspended the Nazi instance, they’d be actually cut off from the greater fediverse the same way herd immunity keeps a disease from infecting people who aren’t vaccinated.

Instead, the Nazis can directly connect to the instances that have suspended them and see and interact with the users. Those users won’t see that Nazis are stalking and organizing against them because their instances won’t deliver the notifications (most of the time).

It’s a trash design that doesn’t provide any safety at all and I have no confidence that anyone with the ability and resources to fix it is the slightest bit interested in doing so.

@SelfsameSynonym you're not wrong about this, and I'm trying to start some constructive conversations about this over with Florence.

@charlag

@SelfsameSynonym @maloki well, I understand how it works, thanks. Would it be better if Nazi instance saw that they're blocked and fetched statuses some other way?
Maybe it could be harder for, I can't tell for sure but it complicates a lot of things, kills relaying of statuses and you can still open that instance and read everything?

@charlag From all anti-abuse reports and stuff I've read, making it harder for them is actually _beneficial_ to countering a lot of the shit they do.

Out of sight out of mind kinda deal.
@SelfsameSynonym

@charlag From all anti-abuse reports and stuff I've read, making it harder for them is actually _beneficial_ to countering a lot of the shit they do.

Out of sight out of mind kinda deal.
@SelfsameSynonym

@charlag @SelfsameSynonym @maloki Its gab were talking about, if they could code and work around such issues they wouldnt have given up on their own site. It probably wont take much to stop them from interacting with people. Like you did with blocking them from using your app, which is good.

We can probably do similar things with mastodon itself or at least throw up more roadblocks for them to trip over.

@bclindner @maloki thanks for the notice. I've already blocked the gab.com and gab.ai domains but if there are others, let me know so I can block them too 👍 I'll be working on adding explicit anti-fascist language to our Code of Conduct this weekend.

@ashfurrow @maloki I think we've also identified gab.io. It would be ideal to somehow block *.gab.* but I don't know if that's possible on your end.

@bclindner @maloki Sadly, the domain blocks aren't compatible with wildcards.

@ashfurrow @maloki Figures. If any other problematic instances show up I'm sure we'll know shortly.

@gudenau @ashfurrow @bclindner RoR

@gudenau I know it's ruby at least.

I think rails are involved, but right now my mind is totally spacing on if it's actually true.

@ashfurrow @bclindner

@maloki @gudenau @bclindner Yeah it is RoR but the structure of the code might make domain blocks with wildcards difficult. If the check is running often, turning a string comparison into a Regex check might have performance implications, for example.

@gudenau @maloki @bclindner I mentioned performance as one possible consideration. As usual with Matodon (and indeed, all OSS projects), the real impediment to implementing this change is getting it merged by maintainers. The best start would be opening a new issue with a proposed solution – let me know if I can help.

@ashfurrow @gudenau @bclindner I think we started discussing it in an issue on Florence. Care to contribute to the conversation there?

@maloki @gudenau @bclindner Do you have a link? I searched the GitHub issues but it looks like discussion of Mastodon development is now split between different places.

@gudenau @ashfurrow @bclindner

Repo: https://github.com/florence-social/mastodon-fork

Let's see if I can find the actual issue I'm thinking about too.

Mainluy the discussions here:
https://github.com/florence-social/mastodon-fork/issues/108

but also this issue that doesn't have a lot of discussion yet.
https://github.com/florence-social/mastodon-fork/issues/110

@maloki @gudenau @bclindner Ah gotcha. I'm not even up to date with the various forks of Mastodon anymore, huh.

@ashfurrow @gudenau @bclindner

#Florence is #ForkTogether :) We evolved, changed names, and had our first Pre-release this week.

https://write.as/florence-development/this-florence-pre-release-0-1-the-fork-is-alive-flomodev

@gudenau @bclindner @maloki @ashfurrow You could just cache the state of the already 'known' domains, and have the regex check only run on the first request from an 'unknown' one. And have changing the domain block list purge the cache. That should be enough to keep performance good, especially after a bit of time for the cache to warm up.

@rick_777 preemptively blocked

@chr
Thanks!

@chr @rick_777 😍❤️🙏