If you want to block a possible future Meta instance from your instance, here is the domain to block:

threads.net

(and you might as well block instagram.com and meta.com and facebook.com too, in case they use subdomains from them)

Details from reverse engineering available at https://haqueers.com/@Rairii/110645315091243151

(via @mods )

#Meta #Facebook #Fediverse #Instagram #FediBlock

Rairii (@[email protected])

Attached: 1 image Β· Content warning: facebook meta, reversing threads apk

Mastodon
@feditips Shared for any admins who are interested.
@feditips @mods This is a what if question, but is there a way for individual users to block meta if the server we use doesn't?
@Wolleysegap @feditips @mods
You can block domains if it gets out of hands.
@Wolleysegap @feditips @mods

on Calckey
settings-->other settings---server mute etc

@Wolleysegap @mods

Individuals do have a "domain block" option, but this is slightly different. Individual domain blocks hide accounts from that domain and remove any of your followers from that domain.

The server level blocks are much more powerful, especially if the admin activates "secure mode" (aka "authorized fetch").

@feditips -- CC: @sam, if you haven't seen already
@lmbrjckwharfie @feditips Thanks! Haven’t polled users on here yet but will do so when I get the time.
@feditips @mods a bit curious, has anyone seen any posts coming from there yet?

@vhcrack @mods

No, but apparently Meta briefly published their app and someone looked at the code, which is how they found the threads.net domain name.

@feditips @mods wait, is meta currently on the fedi? What does that block exactly?

@Metamedia @mods

Meta is trying to promote a new microblogging service by federating with some Fedi serviers.

Meta basically want to convince people who fled from Twitter to the Fedi, to flee to Meta instead.

@feditips @mods

It may be advantageous to also preemptively block threads.instagram.com, which I believe they may use as a secondary. Even if they don't, it seems like a modicum of effort for safety's purposes when you're already right there.

@theogrin @mods

If you block instagram.com that will automatically block all subdomains too. Same goes for meta.com, facebook.com etc.

@feditips thank you, exactly what I've been looking for :)

@mods @feditips hi to you. I'm building a VPS to have my own instance (Firefish). I was wondering if it is possible to mute or block an entire TLD (wildcard) ? Exemple : *.jp ... ?

And does the added domain include subdomains ? Example : social.threads.net ?

Thanks

@dominic @mods

A domain block includes all subdomains so it's usually best to just block the main domain instead of trying to guess which subdomains they use.

About TLDs, I am not sure. I have tried asking about this on the github but didn't get a reply.

For what it's worth, on my own server I have blocked some obscure TLDs used by free domain providers as they tended to be spammers, trolls etc, and so far I haven't seen anyone from those TLDs, but that could just be coincidence.

@feditips @dominic @mods What GitHub are you asking on? There's only one official repository for Firefish, and it's on our own Gitlab server. https://git.joinfirefish.org/firefish/firefish.git
firefish / firefish Β· GitLab

A fun, new, open way to experience social media

GitLab

@kainoa @dominic @mods

Ahhhh apologies, I missed the part where they mention it being a Firefish instance. I was asking on the Mastodon github.

@feditips @kainoa @mods many thanks for your replies. Noted for the subdomains. But for TLD, how did you add them on your instance? Just add the TLD like .jp ??

It's ok that you asked in the Mastodon GitHub. I'm testing my own Mastodon and Firefish instances. I don't know for now which one will be my final instance.

@dominic @kainoa @mods

I just put the TLD with no domain name, just like you said, in the form .example

It didn't produce any errors or cause any obvious problems, it's obviously quite difficult to test if it works though.