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:
"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.”
This is virtually impossible. The amount of processing power to do that would grind any server with more than a handful of people to a halt.
Best case scenario is hoping Lemmy servers has the same capabilities as other ActivityPub servers. You can make it so Threads can see the server but the server can’t see Threads. In those scenarios, even if they reply to your post, you won’t see it.
In any case, if you want to choose who you federate at a user level, create your own server. You can easily federate with who you want at that point. By being on another server, you give the admins some control. That’s an agreement you made when you joined a server controlled by someone else. There is very little stopping you from your own server. It can cost very little up front and after that, effectively just your own efforts to keep it running. You can be the sole user and make it fairly easily.
They will do 100% like that, that they spread everywhere but the posts on threads are only from threads
It’s not a larger server load, because you’re actually publishing less as users defederate their content. The SQL is actually pretty simple if you have a content field for blacklisting that the user selects when publishing. On the federating front end, you simply don’t publish the content to the instance the user defederated from, as marked in the content field. It’s basically one more line in SQL - essentially would be something like:
where content.blacklist != domainin the select statement.
This is actually already in play to some extent over here at kbin, where @Ernest has made one helluva incredible engine - we’ve got domain level filtering for our feeds, and the search capacity is getting pretty cool. Having that same capacity for what we publish would make for an amazing platform.
You’re confusing blocking and defederation. You can already filter what you see as a user.
No, this is talking about what you publish as a user, and choosing where it appears.
That’s not really how the protocol works though. You’re suggesting a major change to ActivityPub itself.
Edit: and it’s a change that isn’t even necessary. It’s the whole reason you can create your own instance.
It’s not a big change - it’s adding a field, a table, and a filtering line to the outgoing SQL select statement that chooses what a domain accesses when it requests the feed. Access level control has been a thing for content management systems for 20 years - this is not a big ask.
But to be honest, as you’re the third person to have this misconception, I’m getting to the point where I’m almost tempted to crack open the kbin code and see if I can do it myself.
Again, you’re talking about changing the ActivityPub protocol. Objects aren’t published the way you think they are. It’s more like batch processing. This simply can’t be done at scale without massive investment.
Edit: ActivityPub is closer to an RSS Feed than it is to sending out what you publish to each server. It makes it’s lsit available to others (who don’t have this filter you’re talking about) and they grab the whole thing. They don’t scan each item and grab it as they go. And again, that scanning is done by them, not the hosting server. The feed is open by default. There is no real authentication and identity at the level you’d require to transform this into an entirely different product (a CMS).
I’m going to have to dig into it more, as filtering content from an API feed based on the referring domain’s api credentials is something that’s commonplace in the private sector and on other open source projects - in fact, I’ve recently built some reports in Quicksight that do exactly that, and output results on a secure row level basis.
I think it appears more daunting than it is (context I’ve been a web dev, analyst, ecom manager for 20+ years), but I haven’t yet had time to dig into the code. As you’re now the fourth person to make this claim, I’m now inspired to actually go and dig into this and see if I can hack it on my own. If I manage to do it (or it results in total failure), I’ll update my opinions and these posts accordingly. Disclaimer - I am lazy and slow, so this may take a bit.
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.