@dansup I don't think it's necessarily easy to say you're blocking Threads. Some portion of your fedi community is going to disagree with that decision, if your server serves more than a handful of people. And beyond that, clearly most of our friends and family also disagree, otherwise they wouldn't be using Facebook products. Blocking Threads is a brave and difficult stance that only sounds popular in a weird bubble.
It's also not easy to organize a community, no matter your stance on Threads.
@dansup I think our best collaborative effort so far is all the tooling and infrastructure IFTAS is bringing to the table. They're sponsoring the development of some really powerful stuff that could help a lot of communities, and providing severely needed resources, too.
That, plus FIRES / whatever else @thisismissem is building, plus efforts like FediSeer and Oliphant and The Bad Space, kind of start to build a comprehensive picture of what's possible with Trust & Safety here.
@usagi@dansup@deadsuperhero generally you don't need to because your admin has normally taken care of it. But at the moment you only option would be to go block by block, or maybe the import/export feature
@usagi@dansup@deadsuperhero so you as a user can import a domain blocking file, but really, these files are often the worst of the worst, and if your admin hasn't done that, then the entire server is likely to be at high-risk (since hosting providers tend to have zero tolerance when it comes to stuff like CSAM)
You can import a domain blocking file, but you really shouldn't have to. Go to settings->imports and you'll be able to import one from there if you really think you need it
Generally the focus is on admins / operators because they have the most power when it comes to the servers they operate.
That said though, better tools for admins also means better data, so a project like FIRES can bring intelligence into user profiles, surfacing advisories against given servers (this was originally proposed in the FSEP paper)
@thisismissem@usagi@deadsuperhero@dansup I’d say it is not entirely out of scope and one that would benefit admins/mods and devs. A user needs assessment would be great!
Ha, last night I finished up the pull request that should give Pixelfed some baseline compatibility with IFTAS FediCheck — though this work was out of my own pocket, as IFTAS can't sponsor open source (due to IRS restrictions)
IFTAS is the perfect org that could eventually maintain FediDB, as much as I'd love to continue maintaining FediDB, its growing increasingly important to the fedi and an org like that could manage it long term better than I might be able to.
@dansup@deadsuperhero I'd probably not say IFTAS is the correct home for FediDB, but instead a generic Fediverse non-profit (this was floated at FediForum)
@dansup I value the right of individuals to decide if they want to follow or block (instances). Having a choice is why we should be here. A walled garden decides everything for individuals, and leaves them no choices. Many of us wanted to get away from that.
@dansup what does upset mean in this context though? Like, if you run a Mastodon instance, and someone goes: if you don't block Threads, I'm moving instances
You go: I won't block Threads
They go: alright, I'm moving
Is that upset? Because I see that as perfectly reasonable; this kind of freedom is what makes the Fediverse awesome
If people start harassing instance admins, that's a whole different story—anyone who does that doesn't belong on the Fediverse to begin with
@mohab@dansup I find I’m the inverse of this. I want Threads, and would be aggrieved by having to move instances because my instance decided for me that they wanted to block the platform. I chose my instance based on geography, and there’s only so many Canadian instances.
@dansup People have a good reason to be upset, because those open protocols have no proper tools for users to feel themselves safe in the case of collaboration with some big-tech corpos being well known for lying many times to users. Such things should be developed in the first place, before someone even began thinking on opening, collaboration, federation etc. Before, not after the fact. The order plays an important role here. Doing the opposite will only produce horribly disastrous results.
Add comment