I continue to be squeezed by both sides of the threads situation. I am operating on the premise that people who think I’m a terrible person and this is a terrible instance for allowing any interaction with threads have left and/or blocked, those remaining seem to want to either have nothing to do with threads at all and are mainly concerned with their data, and those who want to seamlessly interact with threads. I have threads limited/silenced on Infosec.exchange, but that isn’t seamless, and it’s also not fully blocking. So, here’s my proposal:
I remove the limit from threads, and run a job to domain block threads for each account. Any account who chooses can undo the block (or ask me to do it) and then they can seamlessly interact with threads, and those who want nothing to do with them get their way.

Thoughts?

(Note: this was only intended for Infosec.exchange/.town, and fedia.social)
@jerry Just wanted to say I don’t care what you decide either way. I love this server and will stick around whatever happens. Also, all this drama is a good reminder it’s been about a year since my last donation to cover server costs, going to change that shortly.
I said it was an idea, not a good idea

@jerry

I wasn’t hurt’n anyone…

@jerry we’re all trying our best here
@jerry not on your instance but I like the current method you're using
@jerry A lot of folks I've talked to about moderation on the fedi note that we need more granular tools. This sounds like a step in that direction. I'd be curious to see how it goes!
@jerry seems reasonable to me. How will new accounts be handled?
@jerry I really appreciate your continued effort running these instances. I have been able to maintain some semblance of a social media connection after my departure from far shittier places. I have no opinion toward this issue, however I wish for you that complaints were behind a paywall. Thank you, genuinely. And good luck.
@jerry i think everyone can choose to run their own instance and control their own destiny.
@jerry otherwise. accept that you may disagree with your instance admin.

@jerry I appreciate you going through all the extra effort to keep all these people happy. Most of which don't contribute financially or even post anything of interest outside of reposted news articles from hackernews. I don't think this is a problem that should be tackled from the top. Everything I've read shows its blockable on user end. The beauty of this platform is people can move if they don't like it.

Jerry, you don't owe anyone anything. Don't allow yourself to be misled of swayed by these crybabies.

@jerry I suspect that most people aren't deeply invested in it either way. It's not like their posts will make it here on their own without follows or boosts from someone followed. If Threads is blocked but someone is following a discussion that includes a Threads user would it just show up with gaps here? Not sure that's ideal.

I'd maybe consider things more on Lemmy/kbin instances that present more like Usenet.

Overall I'd say don't stress too much about a tempest in a teapot, and thanks for running all this.

@jerry personally I think their slack moderation justifies an instance block at this point, but I also understand that it is very much a judgment call given the nature of these instances

@RandomDamage @jerry “wait, Threads has a Slack?"

(i’m with you now, it just took me a second there)

@jerry I don’t have strong opinions on this but appreciate what you’re doing to make everyone happy here.

I do find the idea of keeping anyone “out” is kind of weird to me in this space since it’s all able to be scraped with RSS anyways. The privacy violations continue anyways - they’ll just use more domains/IPs than can be blocked if they want to scrape content.

At any rate: you’re doing great and I’m happy to be here.

Hey, @jerry I appreciate the effort you put in maintaining and running these services very much. I am firmly in the I-don't-want-any-interaction-with-threads camp, but I also understand that you don't owe me anything. You have given much already. I am currently happy here. If that ever changes, I will leave without hard feelings and drama.
@jerry this is, I think, the most reasonable approach I've heard suggested yet.
@jerry Removing the block but assisting users to block individually that want to is an interesting choice. Appreciate your thoughtfulness here as an admin, and your commitment to an open social web as well.

@jerry Sorry that you have to take all this flak.

Apparently we're not mature enough to simply block or allow ourselves so we might have to let daddy do it. (It's not you Jerry, but all the whingeing barstewards that cannot decide/act for themselves).

And I'm worried about the total garbage that is Meta too, but for freedom of choice and if they're federating, they're federating...

@jerry the problem I see is you might get gripes from new accounts that don’t get that block.

I am personally fine with Threads for now and will probably unblock for my account so I can interact with people I may know there.

@jerry probably worth putting together simple steps for editing that domain block and sticking it in a server sticky note.

Might even solve the problem a lot of people have, if they know how to do it.

@jerry Sorry for the grief this is causing you.

It will never cease to amaze me that someone would come after you rather than just clicking the vertical ellipses on a post from an instance they have an issue with and then -in this case- selecting "block domain threads.net"... it may technically not be the least they can do, but it's only a couple of clicks and it's so much easier than being an unpleasant guest

@jerry that sounds very reasonable as long as users have a way to know what's happening. If the setting applies to new users, you'll need a very obvious post or be ready to handle “Where are my Threads-buddies?" questions.

I'd say ANY solution ideally needs an opt-in/opt-out switch somewhere. And, as you noted, see how it goes and follow the established processes for dealing with problematic instances, should that become and issue.

MANY thanks for all you do! Running a small country ain't easy…

@jerry think of it as opsec, would you be leaking ANY data to threads for any users who don’t explicitly opt in? I think they’re going to be able to scrape the user data anyway if it gets leaked through other instances who choose to federate with them so anything other than complete isolation will allow them to gather and monetize data from all fedi users eventually.
@jerry I still believe for users who really want to interact with threads, just join threads. You dont gain anything by having a fedi account and then interact with users on threads, you are effectively giving threads all your user data so why not just join threads? Whats the point of Mastodon if not to explicitly opt out of being tracked and monetized by those guys?
@CaptMorgan You know that your posts and boosts are not private, ja? It's all publicly available at the "https://freeradical.zone/@CaptMorgan" URL for anyone who wants to scrape that data.
@adfporter good point, so threads can scrape any data they want regardless of uf they ate allowed to federate
@jerry Only thought is "thank you for dealing with the situation". (And people who are worried about threads reading what they post in a public place are silly)
@jerry This seems like a lot of work for you as an admin to appease the vocal minority.

@jerry I appreciate you trying to find a technical solution, but I still think Threads is an openly fascist instance and merely tolerating them is causing harm.

Ideally this should be dealt with at the legal level, with Zuck thrown in prison for life and all his companies burned to the ground. But as long as that's not happening, I will advocate for blocking Threads at every possible level everywhere.

@jerry thank you for being so generous with your time and effort. 💚 Please try to allow yourself rest from this kerfuffle and do something that brings you joy. I don’t think people who have never ran a forum or a BBS understand the amount of complaints in any possible direction that a “sysop” will be confronted with and how that takes a toll on an individual who actually does this stuff out of the goodness in their hearts. So take care of yourself in all this.
@jerry That seems like a good compromise to me.

@jerry I trust your technical opinion more than mine.

I would consider that many non techies/normies will end up using threads over other fedi instances.

Other than that, is interfacing with threads significantly costly? I don't mind limiting Threads should it save you from overbearing costs.

Regardless I will be staying here and love it no matter what you choose. Thanks so much for giving us this online home 🏠 ❤️

@jerry "those remaining seem to want to either have nothing to do with threads at all and are mainly concerned with their data, and those who want to seamlessly interact with threads."

This is not true, some of us just don't care about the whole threads situation.

@jerry I’ve joked about federation with Threads because I get the ambivalence, but overall I'd support it - anything that entices more journalists and official accounts on the platform i think is a good thing.

Thank you for all the great work you do, and communicating the quandaries does great service for all the other fedi admins.

@jerry People will never leave you alone if you start implementing bespoke solutions, and you've enough to be doing just keeping the servers alive without trying to be the conscience of everyone. Any solution that increases the workload on yourself I think is unfair.
@jerry I greatly appreciate this idea and want to be able to interact with Threads..
@jerry you have far too much patience.
@jerry opt in is best. Domain block by default is elegant and clever. You’re a good llama… errr… admin! Don’t let those who wallow in anger ruin your day.

@jerry

A default to blocked, button to unlock would be good.

I would also love a one way option, where you can read, but they can't read you.

But otherwise I don't care that much. I do however think that if people are too permissive with threads this ends like Gmail and email.

@jerry Just seeing this.

Do what
you feel is right, because there's plainly no solution that's going to stop people from being miserable, self-righteous sealions about this.

Any by the way, if you're calling Jerry a bad person for
carefully considering this from many sides, go look in the mirror.
@jerry I get confused by this. Can we not block threads for own own accounts? Or am I missing something?
@jerry
Sounds like a brilliant way to deal with the issue. Allow people to opt in. Can you set a default user level block on new accounts? And can you group message @*@infosec.exchange?
@jerry The data concern doesn’t make any sense to me. This is a public instance. If Facebook really wanted to, they could monitor everyone on here all the time.
@jerry I am ok with threads personally. I'd be more concerned with you and instance's ability to handle any significant scaling/load, which might include more drama.
@jerry personally I like the way you've already approached it by muting the domain.
@jerry can you refer to a good source on the implications of this, in terms of the data privacy/ownership?
Just want to better understand the issue :)
@jerry do you think the absolutists understand that ActivityPub is an open API and that all of their posts are already publicly available? My preference is for limit/silence by the admin and let users nuke the domain if they want, this seems the most flexible approach to me.
@jerry how many storage you will need if "syncing" with Threads? Will this be a big problem for many instances?
@disaster I don’t actually know - it’ll more be a function of how many people here follow how many people there, and the amount of interaction. The site is close to 7 years old and has ~1TB of media and ~200GB database. The current setup can handle about 10x that without and changes.
@jerry I sit in the camp that there are accounts on threads I would like to follow, and I don't understand why Facebook would go through this trouble just to scrape data they can already get via an RSS feed. So as long as there are steps I can take to follow a threads account if/when I want, I vote for whatever makes your life easiest.

@jerry sounds great to me honestly, I would unblock it.

Thanks for dealing with this mess, I know I wouldn't want to.

@jerry I feel bad for every Mastodon admin. It's like trying to cater to single-issue voters, but the issue changes every week and who's on which side is randomized at every reset
@jerry You thereby let a known bad actor into your ecosystem...and absolve yourself of blame, putting it on your users.