Ok. Your point was that you can view Threads content without a Threads account and even if they required an account to view Threads content, users with other fediverse accounts could still see the content because that’s how federation works.
Sorry, i misunderstood your point .
Don’t you have to have an Instagram account to use Threads? Every service on the fediverse makes you create an account. And all of them can put all its content behind that account; nothing in ActivityPub prevents that
Meta can not EEE the fediverse. The worst they can do is create their own distinct fediverse. But anyone who doesn’t want to participate will still be using the open fediverse. They can’t take your instance or force it to update to their standards.
exactly! The end result of EEE is basically the state we’re already in. I also don’t believe that’s what Meta intends. Despite how a lot of ppl here feel about it, the fediverse isn’t worth the effort of EEE. I think its more likely that Meta knows it’s on its last leg and is looking for something to latch on to (see also: their failed metaverse initiative). And the EU’s recent regulatory drive probably makes the fediverse look even more useful for Meta to attach itself to
No it doesn’t because you can’t extinguish a publically available standard when anybody can write their own software. XMPP is the horror story used to warn about EEE, but it still exists. The fediverse is a small network right now. If Meta tried to EEE it, server admins who don’t want to participate in a Meta-controlled network would not implement Meta’s extensions. The network would splinter into a Meta-fediverse and the actual fediverse, which would be smaller than it is now but still exist as a free and open network that could continue to grow.
They can’t turn off our servers, or force us to implement their tech, or stop us from implementing freedom/privacy preserving features.
But if you have to install an extension, how does this differ from current extension that already do this? What could the url scheme do that using http urls couldn’t?
They already have those users. Giving them access to the tiny pool of users in the fediverse isn’t going to give them an appreciable increase in data.
Implementing ActivityPub at their scale costs way more than allowing a drop-in-the-bucket network to go on existing. The fediverse is not really competition for them
You can’t really Embrace, Extend, Extinguish an open standard. Anybody can continue to use the unextended version and that’s exactly what would happen if Meta tried it. They can’t force servers to update or implement meta-specific features
No ActivityPub is explicitly push-based. If you follow someone on a remote server, the remote server pushes their posts to your server. Meta can push content into the fediverse, but like any other user/server they can be blocked if its spammy
Any data they can get from federating, they can get much easier by just scraping it. If your goal is data harvesting, implementing ActivityPub is a huge waste of money
It looks like I was mixing up some facts. The Genius case was denied because genius doesn’t own the copyright to the lyrics they were publishing. I can’t find the case now, but there was a case where a judge said scraping was allowed because it wasn’t a given that the scraper had read a ToS.
They don’t need ActivityPub for that. Nearly everything on the fediverse is public and scrapable. If they want to monetize fediverse data, they already can
Genius (the lyrics company) tried to license the content on their website and a judge said that can’t be legally binding because there’s no guarantee the scraper read it. It seems like the same would apply here.
It’s an explicit goal of ActivityPub, but mastodon implemented its own bespoke API instead of the ActivityPub Client to Server (C2S) API. Apps got developed for mastodon using its API and other services implemented the masto API instead of C2S to get app support.
And anytime you bring up C2S to current projects, they brush it off. So it seems like the grand idea of the fediverse is way far off and not likely to happen soon.
ActivityPub can support tags with spaces, even though no fediverse platform allows you to write tags like that. The name of the tag can be pretty much whatever you want, as long as it has a valid URL.
That wouldn’t make them incompatible with the fediverse. ActivityPub can support tags with spaces, even though no current fediverse platform allows it. A post with a hashtag with spaces would still federate to other services and if that services is robust enough, should still be linked up so that you can click it to see the tag feed.
I wasn’t claiming note was the first term used to refer to them only that it’s been used to refer to them for a long time
I don’t understand why these new services need to reinvent common vocabulary for their services (ie: notes (which is a completely different thing on Twitter), channels, antennas, pages etc)
I don’t know about the rest of the terms, but note is actually the standard term for a microblog post. It was used by services before and contemporaneous to twitter and is the ActivityStream term for these posts.
There is no activity pub team. There is an informal group discussing enhancements at https://socialhub.activitypub.rocks but anybody can join that and submit proposals. Any nobody is required to accept or implement those proposals. I have joined the forum and submitted a proposal myself, but nobody has implemented it or even seems likely to.
Also, not blocking threads doesn’t make your instance a “meta controlled instance”. Meta has no power over any instance other than Threads. Even instances that don’t proactively block Threads can’t be forced to use any hypothetical Meta extensions to AP. And its really unlikely that people who started servers on a minuscule network (most likely for fun or philosophical reasons) are going to follow Meta’s lead just to have access to more people. Everyone who is here and everyone who started a server here knowingly did that on a network that is a tiny fraction of a percent of the size of other social networks; an increased userbase isn’t some big reward for fediverse server admins.