ultimately, i’m unlikely to be seriously effected by any implementation of global fulltext — almost all my posts are locked to followers only and the ones that aren’t are often already intentionally hashtagged with the relevant tags (for the reasons outlined above)

but i still want to think that we are building a good thing here, and that means supporting better policies even when i’m not personally effected

@effy the same way (insofar as we federate with them, which, for the most part we don’t)

obviously i’m not manually checking the source code for every single instance we interact with, but this is a good baseline rule for any instance which is receiving a large number of our posts, and something to fall back on if we ever encounter any problems

@Lady Interesting

@Lady@glitch.cat.family @effy@social.effy.space

the same way (insofar as we federate with them, which, for the most part we don’t)

@ada @effy right, my point is that the number of non-mastodon instances who actually follow our users is slim (and single-user ones already are exempt)

i have no qualms about silencing large non-mastodon instances with full text search; we believe it to be an antipattern which escalates conflict and results in context collapse

if the instance is small and doesn't follow our users, it is probably beneath our concern

@Lady@glitch.cat.family @effy@social.effy.space I guess this whole dialogue concerns me. I'm a trans woman. I've had my content accessed by bad faith actors when it federated to their instances. My content federated to them, and they were accessing my selfies, still circle jerking with each other as they joked about me killing myself, as they wished me death, calling me a paedophile etc. Most of their comments stayed local to their own instance, so I wasn't even aware of it when it happened, but it still happened. It was still there. And if one person hadn't have replied to me directly and let the post leave their instance I would never have known about it.

Even after we blocked the instance, my content still made its way to them, and some of my posts continued to get comments like that.

And disabling search, even defederating and silencing people doesn't completely stop it from happening.

I'm also a trans woman that is running an instance that has full text search out of the box. There's not even an option to turn it off.

It just strikes me silencing instances that allow full text search isn't going to achieve what you're trying to achieve here. The bad faith actors are still going to go on doing what they're doing, and genuine instances risk getting caught if they raise flags.

I personally think that enabling authorised fetch is the approach to take. It will stop content federating to the bad faith actors at all. Unfortunately, it's reactive, so it doesn't do anything until you block the instance, but still, it stops the content getting to bad faith actors more than this will.

@Chronotope it is my understanding that patches exist in PR #2 and #3 here: https://github.com/VyrCossont/mastodon/pulls

see this previous discussion in glitch-soc (closed without merging) for more interested parties: https://github.com/glitch-soc/mastodon/pull/1502

and of course it has come up various other times in the past as well. i’m trying not to be too harsh on any specific instances for wanting this, while still setting a firm boundary desired by our users.

@Lady Ok, interesting. Good to know. I was just trying to figure out what the concerns were here and understand the changes involved. I see @vyr as the person leading the changes and I think they have some reasonable reasons to do so, but I understand why an instance might want to react the way yours has as well.