I am not open to your ahistorical take on Google Chat and XMPP.

Google didn't do anything wrong by using an open standard.

They didn't do anything wrong by building a good interface that people liked to use.

And they didn't do anything wrong by disconnecting from the network when the spam and harassment outweighed the benefit to their users.

We, the XMPP community, failed to capitalize on success by diversifying the network. It's our own fault not enough nodes were there.

If you'd like to draw some conclusions about ActivityPub from this, it should not be that a network should disallow supernodes, but that we have to counterbalance them with a wide diversity of other nodes of different sizes with different value propositions.
That huge audience of GChat users was an immense asset, and we fumbled it.
Note for my subtooter: there's not a recipe for this. Sometimes a group of independent Open Source developers and advocates manage to change the world. Other times, they don't. I think one big success factor is having people whose full-time job is expanding the network and making it healthy, unrelated to their own node or implementation. But not always. If I knew how it works and could replicate it consistently, the Internet would be a lot different.

@evan The SPAM increases BECAUSE OF google. Large reach with little effort, that's the recipe for spam.

Small nodes are overwhelmed by a big node and stop working.

The growth of a decentralized Network is slow and has to be protected.

@pifa You might note that none of these things are true for fedi.
@pifa @evan Actually, the spam fighting part was not taken as a high priority enough by us the XMPP developer community. We were not quick enough to provide tools to fight spam.

@mremond @pifa @evan when for profit interests enter a free space its THEIR responsibility to provide support and ideas to solve that problem

meta nor google will ever do that unless they absolutely have to and if they do it will push the protocol in directions meta and alphabet want not the people

@castironflower @pifa @evan well, I remember from that time that the people working on Google chat were involved and responsive.
@castironflower @pifa @evan we had workshops with them at Google. We worked together on specs and had protocol discussions.

@evan

What makes any network “work” or not is a balance of features and humans.

I am amazed that all the new apps or platforms [threads] are not taking the time to be more creative and sociotechnical about the features with a recognition to NOT recreate the past. Whether fediverse or owned.

@evan
Once communication services get to a certain size there ought to be regulations that enforce opening up to standard protocols. Think of the phone systems, email systems and terrestrial TV.

@evan the should have worked with Google to fix the issue.

I've already seen a lot of people quick to push Threads off the fedi rather than deal with the issues it might create

@anclement @evan "Supernodes" are okay if they are not predators with a track record like meta. We know how meta runs its social networks and we ran away from its playforms for something different.

@dilmandila @evan but Meta brings eyeballs and users to the the fediverse. It also brings brands to the fediverse. I know a lot of people may not like those things.

But rather than block and run away, shouldn't we try and address the issues in the standard?

@anclement @dilmandila human beings aren't eyeballs.

Participation in the social web is a human right.

We will not be changing the ActivityPub spec to keep people trapped in walled gardens and out of the social web.

@anclement @dilmandila nobody should ever have to interact with anyone they don't want to on the social web. EVER. That is fundamental, and I will fight tooth and nail against any structure that doesn't let people shape their own social space.

But that is part of the protocol already. Blocking accounts and defederation already work, as well as blocking words. We need better support for Bayesian filtering, but I think that will come.

@evan @anclement @dilmandila

> Participation in the social web is a human right.

Really? https://www.un.org/en/about-us/universal-declaration-of-human-rights

No, it is not a violation of "human rights" if, say, my instance or all instances choose not to federate with Threads.

That you bring "human rights" into the issue is a measure of the poverty of your actual argument. And I might add that Facebook has complete disregard for human rights.

Universal Declaration of Human Rights | United Nations

A milestone document in the history of human rights, the Universal Declaration of Human Rights set out, for the first time, fundamental human rights to be universally protected. It has been translated into over 500 languages.

United Nations

@TomSwirly @anclement @dilmandila

Article 19: "Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receive and impart information and ideas through any media and regardless of frontiers."

Article 27: "Everyone has the right freely to participate in the cultural life of the community, to enjoy the arts and to share in scientific advancement and its benefits."

@TomSwirly @anclement @dilmandila you have a right to decide who you interact with. I 100% support that and I will fight to make sure you can always exercise it. But all people have a right to be on the fediverse, even if they can't have a conversation with Tom Swirly.

@evan @anclement @dilmandila

> all people have a right to be on the fediverse,

And indeed, anyone can get a free Mastodon account, or browse anonymously, so this problem is completely solved.

But you're going much further. You are saying is that people have a "right" to see Threads threads on Mastodon. This does not follow.

It's like claiming there's a "right" to see New York Post articles in the New York Times.

No such right exists, and you don't make a case why it should.

@TomSwirly @evan @anclement @dilmandila You're heading down a very dark alley in which lurks a Fediverse where "we don't federate with user_count > 400, we don't federate with gay owners, we don't federate with marxists, we don't federate with socialists, we don't federare with pro-Israel, we don't federate with pro-Palestine," and so on becomes the norm.

A splintered network. And all that because some people don't understand that pub/sub is user to user, not instance to instance, and want to punish other users while telling their users what they can subscribe and what they can publish.

@mikka @evan @anclement @dilmandila

> You're heading down a very dark alley

In a world where children are being killed right as we speak, this is hyperbolic. A sense of perspective goes far.

> A splintered network.

Yes, it's a federated system, that's the whole point of it. If you don't like it there are a zillion other social networks. Or you can have accounts on two instances.

> want to punish other users

Get a grip.

@evan @anclement @dilmandila Yes, I did in fact read the link I sent you.

These rights in no way translate into a right to see Threads threads on Mastodon, anymore than I have a right to see RT shows on the BBC.

Anyone can see Threads. Anyone can see Mastodon. No human rights are impaired to the slightest degree if Threads threads do not appear on Mastodon.

@anclement Which "issues in the standard" does Facebook think there are?

@anclement @evan

Can you provide an example of Facebook dealing with problems it has already caused?

Here's one of many it hasn't:

https://www.amnesty.org/en/latest/news/2022/09/myanmar-facebooks-systems-promoted-violence-against-rohingya-meta-owes-reparations-new-report/

Facebook is a company of proven dishonesty and rapacity. They lost the benefit of the doubt a decade ago.

Myanmar: Facebook’s systems promoted violence against Rohingya; Meta owes reparations – new report

Amnesty International
@evan Absolutely, if anything it should always be an opportunity to learn and grow the platforms that we create, build, manage.
@evan I want to do this, I want my own server, and contribute to decentralization.
I recently joined infosec's relay and it's filling up my HD and slowing down my server. That is only one relay, a portion of the , if I wanted to federate with Threads, that is bigger than 35x the  it's not technically possible.
@Andres c'mon. This is an off-topic reply. Start your own thread; there are good solutions to your problem.
@evan I think people also feel burned by the RSS / Google Reader story. In many ways, that felt more significant than XMPP. I am fascinated to see if RSS reader developers can leverage AP to recreate something like Google Reader. Inoreader already offers the same features and more, but it's a walled garden.
I’d expect so, from many different directions. I’m working on something like this - and open source app that listens to both ActivityPub and RSS (and hopefully more to come). The future will be bridged 🤞 @charlesroper @evan

@benpate @charlesroper @evan Ideally, a client or server that bridged AP and RSS/Atom would not, in fact, poll for individual feeds but would instead exploit WebSub (nee: PubSubHubbub) as a means to share feed polling between systems.

See WebSub Spec at W3C: https://www.w3.org/TR/websub/

WebSub

WebSub provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content to subscribers when it becomes available. WebSub was previously known as PubSubHubbub.

Yes. And #WebMentions, too. We may need to make another thread to discuss #Emissary but it already supports those. #ActivityPub is actually the sticking point right now, because it’s orders of magnitude more complex. @bobwyman @charlesroper @evan

@evan

That sounds like an interesting theory.

Are you saying that "#supernodes" (like #Threads?) are o.k., but there need to be more "standard" #Fediverse instances to counterbalance their huge number of users?

@HistoPol yes. Lots of different nodes, lots of sizes.
@HistoPol and diverse. Not just all account servers; different kinds of services.

@evan when Galactica, flagship of the Colonial Fleet but with strict defederation policies, encountered the more powerful Battlestar Pegasus it was important to both collaborate with the Pegasus against a common enemy, but also maintain autonomy as the the interests of the Pegasus were not always aligned with the fleet.

The Galactica, despite being outmatched by the Pegasus, remained crucial to the fleet as a focal point and a strategic asset in a role that smaller ships could not have played.

@evan This times a million. Thank you for saying it.

@evan If this is the conclusion we should draw, is there any case of an open protocol where it has played out this way? Where a flourishing ecosystem of small nodes successfully counter-balanced the big ones and everyone is still free to spin up new nodes and enter the ecosystem? Genuinely curious, because I haven't found a auch a case, but I'm not around that long.

@marcelweiss

@cmw @evan Email & Podcasts

@marcelweiss We've already discussed at length, that it's currently not possible to just spin up an email server and operate on eye level with the big ones. You have at length explained that this is for spam protection, reinforcing the point that email is not a valid example here.

PodCasts, contrary to popular belief, do not constitute a protocol, nor a network. It's simply a format of entertainment. @evan

@cmw @evan Podcasts are based on RSS. The robust eco system on top made sure that Spotify couldn't take over the space. It's not the only reason but still a pretty good example of what we're talking about here.

The debate that email is not open anymore is even more deranged than the xmpp one.

@marcelweiss Granted, RSS, like many other file formats is alive and well. Podcasts also may use it, true. Or may not, that largely depends on the player. Like file formats, entertainment formats are not protocols.

Your opinion on discussions of open protocols and how they interact with the corporate world is duly noted.

Let's get back to the actual question that I posed towards @evan: Is there an example where the above mentioned strategy worked out as I described?

@cmw @evan @marcelweiss I would say the best case for this is the word wide web itself.
@liaizon @evan @marcelweiss that's a good point. It is a collection of protocols rather than one and a number of them have in turn been somewhat oligopolized, but as long as you play by the rules of the established players, you can participate.
@evan Yes, we must have "nodes ... with different value propositions." Today, too much attention is focused on the one problem of shaping audiences (i.e. blocking/moderation/censorship) while all the implementations look pretty much the same.

Ideally, we'll see innovation in the user experience. Chemists, economists, gamers, photographers, or journalists could probably all identify domain-specific features that would serve their specific niche better than the general systems we see today...
@evan This, it's not like we can STOP meta from using ActivityPub. It's an open protocol, and that means sometimes people you don't like will use it. We have to adapt. If Facebook is to not dick around with the protocol, they have to have good reasons: counterbalancing forces that they're afraid to mess with. Governmental, or other entities that demand that they play nice. Big enough that they NEED to stay interoperable, not just do it out of the goodness of their cold, black hearts.

@evan Google didn't disconnect from the network, the network disconnected from Google, because they refused to implement TLS on s2s connections.

How's that for an ahistorical take?

@pettter @evan If I read this thread correctly I'd call that excuses for not having enough nodes diversity. (I'm not making any claims over the funding XMPP projects had at this moment because I wasn't there.)
@evan Thank you for this take..
@evan Why stop at XMPP? The same thing happened to SIP. The prospect of an open interconnection was obliterated by spam and fraud. The lack of a path to innovation was why I ultimately got out of telecom.

@timoj @evan I'm not sure I'd call SIP a failure. Maybe the average user doesn't interact with it very much, but vast numbers of people use it everyday. Callcenter operations, corporate PBXs, private LTE systems, follow-me numbers, and lots of telecon services use SIP in some way or another.

The major exception is Microsoft, naturally. Although even Teams—which uses Skype-derived protocols, supposedly—can interoperate with SIP endpoints.
#telecom #SIP

@kadin @evan I’m not saying that parts of it aren’t used. I’m saying that the archipelago of incompatible islands undermined the original intent of developing a flattened, confederated communication system. It didn’t displace the PSTN or PBXes… it was coopted by 3GPP and telecom manufacturers and broken in such a way that it ultimately became a closed intranetworking protocol, not what we originally intended when we went to replace H.323.

@timoj @evan True. Though that's a pretty ambitious goal. The telcos have always been seemingly uncomfortable with the "internet way" of doing things. (Honestly, I think we're still probably 20 years from getting to a single consensus and standards body.)

Do you think SIP would have been better if 3GPP hadn't adopted it into the IMS standard? That always looked like a win to me, finally building on an IETF standard rather than in parallel to it.

@kadin @evan Sadly, no. At the end of it, it ended up being developed and deployed by people and companies that had no interest in a functioning, open standard.
@kadin @evan Then again, I used to ask a rather pointed, uncomfortable question about LTE and beyond that never came with a decent answer: if we’d known about the iPhone, would we have built modern mobile networks this way? IMHO decidedly not.

@timoj @[email protected] Really good question. And I think up through WCDMA, the answer is "definitely no". With LTE, the feeling I get is "we shouldn't have bothered wasting time on XYZ", where that might be any number of legacy-ish LTE features like circuit-switched voice and data, baroque encapsulation formats, and the whole idea of terminating a subscriber's data traffic anywhere but at the closest possible point.

Definitively separate control vs. data planes is not a bad idea, though.