Lemmy.world Support

3236 readers

3 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket

You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

founded 1 year ago

MODERATORS

[email protected]

To the admins- will lemmy.world block Facebook's Threads or are you open to federating with them in the future? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

176 comments fedilink hide all child comments

https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

Many of us do not trust Facebook and anything it is associated with or swallows up.

EDIT:

https://techcrunch.com/2023/07/05/adam-mosseri-says-metas-threads-app-wont-have-activitypub-support-at-launch/

"Instagram head Adam Mosseri said "

““Soon, you’ll be able to follow and interact with people on other fediverse platforms, such as Mastodon. They can also find people on Threads using full usernames, such as @[email protected].””

“We’re committed to building support for ActivityPub, the protocol behind Mastodon, into this app. We weren’t able to finish it for launch given a number of complications that come along with a decentralized network, but it’s coming,” he said.

“If you’re wondering why this matters, here’s a reason: you may one day end up leaving Threads, or, hopefully not, end up de-platformed. If that ever happens, you should be able to take your audience with you to another server. Being open can enable that.”

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (2 children)

Yeah, you can filter your feed. No one is arguing that. But you can't filter the feed to someone else. That's not how it works. I also don't understand why you have to keep throwing around your supposed credentials when you haven't been able to understand a simple web api concept. If you want Threads not to see you, they need to defederate your server. You don't honestly think this server is posting to information to every other server individually, do you? Those servers grab information and that information is the same for every server that grabs it. It does not publish individual feeds to individual servers. That's ludicrous when you consider the minimum specs for a server.

Your credentials don't mean much when you can't provide any hint of skill to make it mean much.

[–] [email protected] 1 points 1 year ago

FFS. Filter by domain referrer when the call is made to the API from the instance that wants to publish your work. It's not that fucking hard. How do you think IP filtering works?

[–] [email protected] 1 points 1 year ago

Sigh. You people are fucking exhausting. #5 of saying "you can't do that" and giving nothing more than "server can't handle it" as a reason, which is why I stated my credentials, because I'm sick of people talking out of their asses.

When the instance that wants to publish your work makes a call to the api, they have a domain referrer value. Being able to filter on that value is already in place through the process of defederation.

Filtering the output on that domain referrer value is neither some complex process, nor will it increase server load as you're reducing the amount of content the API is producing.

How do you think IP filtering works? Every public facing web service does it. This is the exactly the same thing, except that rather than blocking the entire site, you're blocking a small part of it. It's even easier than blocking a specific page to an IP, because you only have to block a subset of data coming out of the feed on the api.