Skip to main content

I think I found the domain name of #threads, #Meta's new #Fedi-enabled service, also codenamed #Project92, #P92, and #Barcelona.

URL: threads.net
IPv4: 157.240.22.63
IPv6: 2a03:2880:f231:c5:face:b00c:0:43fe (note "face:b00c")

Looking up threads.net returns #Instagram's logo, the title "Barcelona" and "this page isn't available" (probably because it's not open yet).

I'd recommend every #MastoAdmin #FediAdmin in the #FediPact to #FediBlock them before they go live on the #Fediverse!

Screenshot showing threads.net's HTML <title> tag is "Barcelona" and it also returns the Instagram logo, a minimalist white camera icon on a gradient yellow-pink-blue background.
Screenshot of text from threads.net reading "Sorry, this page isn't available. The link you followed may be broken, or the page may have been removed. Go back to Threads."
Screenshot of threads.net's Cloudflare DNS records, showing an A (IPv4) record 157.24.22.63, and an AAAA (IPv6) record 2a03:2880:231:c5:face:b00c:0:43fe. Both have the Facebook logo presented to the left of them.

Barcelona

threads.net
#mastoadmin #fediverse #Barcelona #Meta #fediblock #instagram #fedi #threads #P92 #fediadmin #project92 #FediPact
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •
In addition, threads.net also uses Facebook's name servers and there's references to fbcdn.net, a Facebook content delivery network, in the website's source code:
Screenshot of threads.net's information on https://www.whois.com/whois/threads.net. Registrat is GoDaddy.com, LLC. It was originally registered on May 28, 1997, but has been updated on June 8, 2023 and expires on May 26, 2024. Statuses include clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, and clientUpdateProhibited. In particular there are four name servers a, b, c, d, as subdomains of "ns.facebook.com", further proving this domain is owned by Meta and Facebook.
Screenshot of the <head> block of threads.net highlighting Barcelona in the <title> block and 29 calls to static.xx.fbcdn.net.
Screenshot of "Threads, an Instagram" app on Apple's iOS app store, out on July 6, 2023. Screenshots are shown below, showing it has a similar interface to Instagram.
Screenshot of Threads.net's app privacy settings, showing it will link the following data to app users' identities. They include: Health and Fitness. Purchases. Financial Info. Location. Contact Info. Contacts. User Content. Search History. Browsing History. Identifiers. Usage Data. Sensitive Info. Diagnostics. Other Data.
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Here's how to #FediBlock threads.net on #Mastodon 4.1.0 and above (I'm unsure about how to do this on other #Fediverse #servers, sorry:

FOR USERS:

1. Create a txt document
2. Type "threads.net" (without quote marks)
3. Save as "blocked_domains.csv"
4. On Mastodon, go to Preferences > Import and Export > Import.
5. For input type select "Domain blocking list".
6. Upload blocked_domains.csv.
7. Click "Merge" so threads.net is added to your block list. Do NOT click "Overwrite"!
8. Click "Upload"!

Screenshot showing Mastodon's CSV import menu with "blocked_domains.csv" uploaded as a domain blocking list with "merge" selected.
#mastodon #fediverse #fediblock #servers

Mother Bones reshared this.

in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Here's how to #FediBlock your entire server from threads.net on #Mastodon 4.1.0 and above (I'm unsure about how to do this on other #Fediverse #servers, sorry:

FOR MODS AND ADMINS:

1. On Mastodon, go to Preferences > Moderation > Federation.
2. Click "Add new domain block".
3. Type "threads.net" (no quotes).
4. Set severity to "Suspend".
5. Click "Create block".

Screenshot of the domain blocking menu in the Federation tab of the Moderators tab in Mastodon's preferences menu, only available to Mastodon moderators and admins.
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

If you're an admin using Mastodon 4.0.2 or below, the menu described before won't exist and you will need to access your Mastodon server's #PostgreSQL #production #database (assuming you're using PostgreSQL) and paste the following #SQL code to block threads.net:

INSERT INTO domain_blocks (domain, created_at, updated_at, severity, reject_media, reject_reports) VALUES ('threads.net', now(), now(), 1, 't', 't');

#postgresql #database #production #SQL
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Here's the #iptables and #ip6tables commands to block #IPv4 and #IPv6 packets directed to/from threads.net:

iptables -A INPUT -s 157.240.22.63 -j DROP
iptables -A OUTPUT -s 157.240.22.63 -j DROP
ip6tables -A INPUT -s 2a03:2880:f231:c5:face:b00c:0:43fe -j DROP
ip6tables -A OUTPUT -s 2a03:2880:f231:c5:face:b00c:0:43fe -j DROP

@revengeday has a list of 1000+ domains owned by Facebook / Meta you can save as "blocked_domains.csv" and import as a blocking list in your server: datakra.sh/assets/lizard.txt

Screenshot showing mastodon.moule.world has suspended threads.net.
Screenshot showing that threads.net's IPv6 address has been blocked on mastodon.moule.world in the OUTPUT chain.
Screenshot showing that threads.net's IPv6 address has been blocked on mastodon.moule.world in the INPUT chain.
Screenshot showing threads.net's IPv4 address is blocked in mastodon.moule.world's firewall in both the INPUT and OUTPUT chains.
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Here's a list of #iptables and #ip6tables commands for admins can copy and paste into their #Fediverse server's command line to bulk-block all packets to and from IPv4 and IPv6 addresses owned by #Meta (source: asnlookup.com/ipv4/31.13.24.0/):

drive.google.com/file/d/1-Mnvj…

iptables Commands to Block Meta's IP Addresses

Google Docs
#fediverse #Meta #iptables #ip6tables

Mastodon Migration reshared this.

in reply to MOULE (Snow Way out Dec 6th!)

Laru
Laru
• •

i made this earlier this week, it might help making things a bit more dynamic (requires you to already have an empty chain set up, also this was made for my server specifically which has only ipv4 so this script doesnt handle ipv6, should be easy to add tho)

as argument it takes a text file containing a list of ips/networks to add to the blocklist, separated by newlines

in reply to Laru

Laru
Laru
• •
PS: heres a list of all their ip ranges, including those that arent registered but are likely to be used by them in the future (adjacent subnets have been merged)
its compatible with my script (but it includes ipv6 networks)
in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

I've read that some users are vowing to leave the #Fediverse because they are on a server that has agreed to federate with #Meta's #Threads app, or they're on a server that has not made their position clear on whether they'll federate with Meta.

I' recommend reading fedipact.online to find 418 servers that have pledged to block Meta you can migrate to, though not all are open for registration. Among the biggest are pixelfed.social, mastodon.nl, mastodon.art, pixelfed.de, and others!

🖤 ANTI-META FEDI PACT 🖤

fedipact.online
#fediverse #Meta #threads

reshared this

in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Apparently, federating with Meta will no longer be automatic and you can now opt-in to have your server federate with them with "financial incentives" if your server is "big enough":
beach.city/@vantablack/1105941…

Still though, it's worth blocking their domains and IPs anyway just in case they change their mind and federate openly (and to stop their data-mining of your servers without you or your users' consent!)

MOVED vantablack@cyberpunk.lol

2023-06-23 14:59:21


oh, here's some JUICY rumored details about meta's plans for the fediverse

tl;dr "Meta will only federate with select larger instances from the beginning. There will be contracts which also provide for financial compensation for the instance owners."

can't entirely verify their validity but it's still worth posting just in case

#FediPact #barcelona #project92 #p92 #meta #facebook #fediverse #fediblockmeta #FediAdmin #MastoAdmin #threads

Louis @louis@emacs.ch You make some strong arguments here. It's great to see you laying out your reasoning in detail and with passion. theart: That's the spirit. What | have learned, however, is that Meta will only federate with select larger instances from the beginning. There will be contracts which also provide for financial compensation for the instance owners. Meta positions itself as a “savior’, because especially the big instances have a very strong financial pressure. Users take it for granted that someone else is paying for everything. In these contracts, Meta also specifies the rules regarding the moderation. Instances will have the option of allowing ads from Meta or not (with the benefit of additional compensation). Smaller instances will have the possibility to register for a federation with Meta in a second step, but there will be no financial compensation and Meta decides if they will grant access based on their reputation.
Regarding Meta, I'm in the industry for 25 years and have a few friends who worked at Meta from the early years until recently. One s stil there. Regarding UFol, | was part of the disussion at the time, we held a vote at Emacs.ch P R S But don' take this at face value, obvisouly these admins have to sign harsh NDAS. But it sounded very credible and | could not imagine it going any ther way. Examples of big instances (from Japan | believe?) show that the long-term burdens are simply unbearable and operators just wait for the right moment to e 1donot critizise Meta for their attempt to use the favor of the hour to their ‘advantage. As a public corporation its theijob to make proft. As I said, its not them who will decide the fate of the Fediverse. ‘Overworked/stressed out admins, high costs for infrastructure, ongoing disputes ‘and moderation challenges are what threaten the Fediverse. It was not meant to ‘9row o fast before we find common solutions for these issues. What do you think?

in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

I should mention that the importable blocklist of :Meta: Meta's domain names was written at a time when "threads.net" was not confirmed to be the domain name of :Threads: Threads, but I still think it's good to import it, as it will also block other #Meta domains like threads.instagram.com and any they decide to integrate with #ActivityPub in the near future.

I'm noticing a lot of sites (#WordPress, #Tumblr, and now #Threads) are embracing the decentralisation trend and integrating ActivityPub!

#wordpress #ActivityPub #Meta #tumblr #threads
in reply to MOULE (Snow Way out Dec 6th!)

Chris Alemany🇺🇦🇨🇦🇪🇸
Chris Alemany🇺🇦🇨🇦🇪🇸
• •
Domain is definitely owned by Facebook Inc according to mxtools
mxtoolbox.com/SuperTool.aspx?a…
screenshot from mxtools

Network Tools: DNS,IP,Email

DNS and Network troubleshooting and diagnostic tools integrated into one sweet interface.
MxToolbox
in reply to Chris Alemany🇺🇦🇨🇦🇪🇸

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Yep! And threads.net references fbcdn.net several times too, which is a content delivery network from Facebook: mastodon.moule.world/@MOULE/11…

MOULE (Snow Way out Dec 6th!)

2023-06-22 05:29:12


In addition, threads.net also uses Facebook's name servers and there's references to fbcdn.net, a Facebook content delivery network, in the website's source code:
Screenshot of threads.net's information on https://www.whois.com/whois/threads.net. Registrat is GoDaddy.com, LLC. It was originally registered on May 28, 1997, but has been updated on June 8, 2023 and expires on May 26, 2024. Statuses include clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, and clientUpdateProhibited. In particular there are four name servers a, b, c, d, as subdomains of "ns.facebook.com", further proving this domain is owned by Meta and Facebook.
Screenshot of the <head> block of threads.net highlighting Barcelona in the <title> block and 29 calls to static.xx.fbcdn.net.
Screenshot of "Threads, an Instagram" app on Apple's iOS app store, out on July 6, 2023. Screenshots are shown below, showing it has a similar interface to Instagram.
Screenshot of Threads.net's app privacy settings, showing it will link the following data to app users' identities. They include: Health and Fitness. Purchases. Financial Info. Location. Contact Info. Contacts. User Content. Search History. Browsing History. Identifiers. Usage Data. Sensitive Info. Diagnostics. Other Data.

in reply to Chris Alemany🇺🇦🇨🇦🇪🇸

jessel
jessel
• •
this setting only prevents p92 content from showing up on your server. i think you want another setting to prevent your server content from being read by p92 (which seems to be the more concerning flow)
in reply to jessel

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Admins of Fediverse instances can use iptables and ip6tables in their command line to drop data packets going to and from servers like those owned by Meta: mastodon.moule.world/@MOULE/11…

They have a lot of domain names (and thus IP addresses) to fediblock: asnlookup.com/ipv4/31.13.24.0/

MOULE (Snow Way out Dec 6th!)

2023-06-22 06:39:09


Here's the #iptables and #ip6tables commands to block #IPv4 and #IPv6 packets directed to/from threads.net:

iptables -A INPUT -s 157.240.22.63 -j DROP
iptables -A OUTPUT -s 157.240.22.63 -j DROP
ip6tables -A INPUT -s 2a03:2880:f231:c5:face:b00c:0:43fe -j DROP
ip6tables -A OUTPUT -s 2a03:2880:f231:c5:face:b00c:0:43fe -j DROP

@revengeday has a list of 1000+ domains owned by Facebook / Meta you can save as "blocked_domains.csv" and import as a blocking list in your server: datakra.sh/assets/lizard.txt

Screenshot showing mastodon.moule.world has suspended threads.net.
Screenshot showing that threads.net's IPv6 address has been blocked on mastodon.moule.world in the OUTPUT chain.
Screenshot showing that threads.net's IPv6 address has been blocked on mastodon.moule.world in the INPUT chain.
Screenshot showing threads.net's IPv4 address is blocked in mastodon.moule.world's firewall in both the INPUT and OUTPUT chains.

in reply to MOULE (Snow Way out Dec 6th!)

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

Here's some iptables and ip6tables commands to bulk-block traffic to and from Meta: mastodon.moule.world/@MOULE/11…

MOULE (Snow Way out Dec 6th!)

2023-06-22 06:55:41


Here's a list of #iptables and #ip6tables commands for admins can copy and paste into their #Fediverse server's command line to bulk-block all packets to and from IPv4 and IPv6 addresses owned by #Meta (source: asnlookup.com/ipv4/31.13.24.0/):

drive.google.com/file/d/1-Mnvj…


iptables Commands to Block Meta's IP Addresses

Google Docs

Unknown parent

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •

No worries! I also made this so Meta shouldn't be able to send or receive data packets to and from Fediverse instances: mastodon.moule.world/@MOULE/11…

MOULE (Snow Way out Dec 6th!)

2023-06-22 06:55:41


Here's a list of #iptables and #ip6tables commands for admins can copy and paste into their #Fediverse server's command line to bulk-block all packets to and from IPv4 and IPv6 addresses owned by #Meta (source: asnlookup.com/ipv4/31.13.24.0/):

drive.google.com/file/d/1-Mnvj…


iptables Commands to Block Meta's IP Addresses

Google Docs

in reply to MOULE (Snow Way out Dec 6th!)

Many Colors, Many Forms, Many Flavors, Maybe More
Many Colors, Many Forms, Many Flavors, Maybe More
• •
(CW added midthread) the future of fedi, Facebook, fediblock

It looks like it has many, many more IP addresses than just these two. Probably all of them should be blocked.
gladtech.social/@cuchaz/110571…codeberg.org/cuchazinteractive…

Jeff Martin

2023-06-19 14:39:12


Shields up, folks! :blobcatgooglytrash:

Facebook is joining the Fediverse and you know what that means. Adtech, surveillance, privacy-invasion-as-a-business-model, and all that. It's what they do. It's what they've always done. We don't expect this time to turn out any differently. :blobcatfacepalm2:

The most effective way (that I know of) to fight back is to completely block any Facebook-related IPs at the firewall level. This will prevent Facebook instances from federating with your instance. It will also prevent Facebook scrapers from trying to harvest information from your instance's users, which Mastodon's defederation tool can't do.

I made some simple tools to help make blocking Facebook easy for instance admins:

codeberg.org/cuchazinteractive…

In this repo, you'll find the ASNs known to be used by Facebook and lists of current IP address ranges for those ASNs. There's also a python script to turn those IP address ranges into firewall rules for iptables, the firewall used by the Mastodon instance setup instructions. And there's a short readme to explain how to use the script and download the IP address ranges.

I've confirmed that these IP address ranges will block threads.net, and threads.instagram.com, which are domains currently known to be used by Facebook/Instagram instances.

Happy blocking, folks! Stay safe out there.



iptables-asn-block

Tools for blocking ASNs using iptables
Codeberg.org

in reply to Many Colors, Many Forms, Many Flavors, Maybe More

MOULE (Snow Way out Dec 6th!)
MOULE (Snow Way out Dec 6th!)
• •
(CW added midthread) the future of fedi, Facebook, fediblock

Yep! Well into the hundreds of thousands of IPv4 addresses, and well into the nonillions of IPv6 addresses.

I’ve compiled a list of as many of #Meta’s #IPAddress ranges here for #Fediverse #Instance admins to import as iptables commands: drive.google.com/file/d/1lipuA…

MetaBlock (25 June 2023).txt

Google Docs
⇧