With Meta starting to actually implement ActivityPub, I think it would be a good idea to remind everyone of what they are most likely going to do.
You must log in or # to comment.
Man, I’m not gonna relitigate this but no, Google Talk didn’t kill XMPP. XMPP is not, in fact, dead. WhatsApp killed Google Talk and pretty much every other competitor and XMPP would have been in that boat with or without Google Talk.
This is gonna keep coming up, it’s gonna keep being wrong and I’m really not gonna bother picking this fight each and every single time.
This needs to be higher for visibility. The story of Google killing XMPP is a good one but it’s utterly bullshit. XMPP was a mess, Google didn’t kill it, it killed itself by having fucked ecosystem that didn’t do anything better than numerous proprietary standards at the time.
It’s not like XMPP was EVER dominant, nor was Google talk - even man messenger was more popular at the time and that’s also dead.
Yeah I kept thinking these people must be incredibly young if they think this is what happened. As if Google Talk was anyone’s problem (in the big picture), nevermind XMPP’s.
Well, people like to think that the fediverse is a genuine threat to Meta. And they like to feel they’re doing important work defending it from Meta. So this will indeed pop up again, and again, and again.
They do? I mean, a few times I did have to point out that Meta has multiple products breaking 2 billion active users, so the “fediverse” is a drop in the ocean, but not many people seem to stick with that argument after a quick bout of googling.
deleted by creator
Do you REALLY think that will be their end game?
deleted by creator
Why can’t it be both? It’s useful now for that reason and if it does grow they are in a position to kill it or absorb it.
And Reddit killed phpBB (kind of).
And phpBB killed the newsgroups.
Etc.You are right. Convenience killed the previous “protocol”.
You saying that XMPP is not dead?
Name 10 active generalist servers.
No, really, it would be good to know. I haven’t been able to find active XMPP communities since ca. 2015.Hah. Alright, it’s not deader than it would have been had Google not stepped in and then stepped out. We’re grading “dead” late 2000s instant messaging apps on a bit of a curve here.
Server 1, server 2, server 3, server 4
Both you and the writer claim to have been there back then, but have wildly different ideas for what happened… Were you a dev on XMPP too?
An XMPP developer would likely have been delusional about the protocol he himself developed. But at the time I can assure you XMPP was completely irrelevant. AIM/ICQ/MSN/Yahoo! and maybe IRC were the tools of the day back then.
Because of actual competition (which XMPP had absolutely no part in) multi protocol messengers had their golden age then.
As a newb techie back then. Using 4 of the ones you listed.
I never heard of XMPP and still don’t know what it was …
Oh, absolutely not. Let me be clear, I do not question that the author was involved in the project and interacted with Google. I do not question any of the factual details in the article and my argument is not that he’s lying. Total respect for him, his work at the time and even his opinions on how annoying and frustrating it was working with Google around.
What I’m saying is his perspective on the alleged failure of XMPP is specifically biased by his insider experience, that many of the examples he gives do not apply to AP, that the process he describes there is not EEE, that it’s not the reason XMPP and Google Talk failed and that, as he admits throughout the piece, XMPP didn’t in fact disappear or “die” after Talk’s failure or because of their intervention.
Did you bother to read the article or did you only decide to write this argument w/o any substantial basis?
Oh, I read it when it came out back in June. Many times, as it kept being shared as an explanation of the first Threads backlash.
It’s full of incorrect assessments and false equivalences.
Threads doesn’t really have the volume (yet) to subsume ActivityPub. The process it describes for standards drifting towards the corporate actor doesn’t apply to ActivityPub, which is engineered from the ground up to support multiple apps with differnent functionality (hence me writing this in Kbin and others reading it in Lemmy and being able to link it and follow it from Mastodon), the article only acknowledges that XMPP survived and kept on going at the very end as a throwaway and doesn’t justify how it “never recovered” and, like I said, it doesn’t acknowledge the real reasons Talk and every Google successor to Talk struggled and collapsed.
So yes, I read it. Past the headline and everything. I just didn’t take it at face value. This piece keeps getting shared because XMPP wasn’t ever that big to begin with, so this sounds erudite and informed while the similar arguments being made at the time about SMTP and RSS were more obviously identifiable as being wrong for the same reasons.
which is engineered from the ground up to support multiple apps with differnent functionality (hence me writing this in Kbin and others reading it in Lemmy and being able to link it and follow it from Mastodon)
I mean that’s basically what every protocol is. ActivityPub abstracts concepts, that apps implement in their own way (for example the concept of group). If you manage to deliver changes, even improvements, to the protocol, apps need to keep up and comply with it. This is what means “drifting towards the corporate actor”. I propose changes to the protocol to a rate that only me (the corporate actor) can keep up with. This way only my users will have certain features and eventually some apps will become incompatible with the recent version(s) of the protocol.
That is already how ActivityPub apps work.
It’s also not what happened to XMPP and, interestingly, not what the article claims happened to XMPP, even. You’ll note in the postmortem about it the recollection is that Google was too slow to adopt features and fix bugs, not the other way around.
I guess once you get enough confirmation bias in play you can embrace, expand and extinguish both by doing that and the opposite of that.
You’ll note in the postmortem about it the recollection is that Google was too slow to adopt features and fix bugs, not the other way around.
You still fall behind on compatibility with the original protocol. Doesn’t matter if you pull up or down, it still breaks compatibilty.
It absolutely matters under ActivityPub because, as I said earlier, it comes down to the client to manage the incoming packets. If Meta is out of date with the protocol but the rest of the federation is not (and retains backwards compatibility at all), then everybody else gets nicely formatted but feature-limited Meta content and they get garbled stuff.
It’s only relevant if we get garbled stuff and they get nicely formatted content. Which should be entirely avoidable if they “pull down”.
So no, not the same. And crucially people are still misquoting the article and the article is still misrepresenting the so-called “EEE” strategy.
The difference here is that, one, people are more aware now than they were back then (privacy wasn’t as big an issue then as it is now, thus people are more aware and are on the Fediverse for a reason), two, now the Fediverse has the upper hand (because of Mastodon mostly… they are somewhat of a player in the social media market), three, devs won’t allign with Meta’s moral compass just because it’s Meta (like it was with Google back then… people actually believed that company’s slogan back then).
So, what might have worked back then, probably won’t now, but it’s still good to approach Meta with caution.
This is a core problem of distributed systems though. Signal even cites this as their reason to not federate with anyone.
Once you get decentralization going you need everyone to stay kind of up to date or stuff will just not work.
It is not. Discord’s protocol has been tailormade to suit Discord and the developers will not give a single thought about keeping it stable because only the Discord server&client are meant to use it.
This misses the point in my opinion. The point of a protocol is to establish a set of rules that need to be followed, that’s it. After this, it can be managed in many ways, it can be open or it can be closed, etc. The fact that ActivityPub is “engineered from the ground up to support multiple apps with different functionality” it’s because ActivityPub is an open protocol. Every protocol is designed to support whoever implements it. This doesn’t have any inherent “the protocol (changes) will suit everyone” or “everyone will be able to keep up with it” property, though. If changes to a protocol happen very fast, apps that are compatible today - and can be compatible tomorrow too - still need to implemented those changes, or at some point they will not be compliant anymore. This is not because the protocol loses the property of supporting multiple apps, but because a protocol still needs to be implemented, which is responsibility of the consumers, which requires time.
So my point was to challenge OC perspective that since ActivityPub is designed to support multiple apps, then there is no risk that it gets messed up and breaks compatibility with those apps (because it’s generic) due to - in this case -Threads influence. This is just nonsense, in my opinion.
fwiw, XMPP/Slack/Discord/etc basically solve the same problem that IRC already solved. Software Engineers just reinvent the wheel again and again as everyone loves a green field.
That said, Meta cannot be trusted. They’re going to do a year or two of embrace and extend, pretending to be good citizens. Then they will invent some crisis that causes them to want to de-federate, likely that content on other servers is not moderated to their standards or that convoluted features of their extended protocol are not being met. This take seems pretty spot on to me.
Then they will invent some crisis that causes them to want to de-federate
Easy to predict.
Zucc-bot saw titties on Lemmy, something something think about the children outrage. “Better follow our advertisers happy friendship rules or we defederate and all your users will miss there normie friends. Not our rules, bro.”
Wouldn’t that just isolate their instance much like heaxbear? Or are you saying that the threads instance will be larger than Lemmy.world, or kbin?
Meta out scales the entire project. Google says 141 million users. Its the scale of pissing into the ocean.
Not too familiar with the back end stuff, but would federation data from Meta just DDOS a server not worth millions?
Meta does, but I’m not sure threads does.
I know people on facebook, but I don’t know anyone on threads, even if it is owned by meta.
I expect activitypub to be relatively scalable. As long as meta isn’t doing something stupid like trying to federate everything to everyone, the traffic should be limited to the users that have connected to each other. There are already absolutely gargantuan instances out there with millions of users that federate just fine with tiny instances.
I mean, that would be the initial fear, but I’m not sure how that would matter. Threads can defederate from Lemmy.nsfw but lemmy.world can still federate both.
Maybe I dont understand something
I don’t see this as a genuine, good faith move from Meta. We’re potential future competition to them. They can’t buy us so I think there going to try to shit up the pace over years and hope we come groveling back. It’s a make or break moment for the protocol against a titan.
They absolutely CAN buy you though, they can buy individual instance owners. Maybe not the Lynch pins like .World but many others and cheaply.
It’ll quickly turn into shit storm, and the average casual use will give up and go back to Reddit or move to Threads, which is what they want
I don’t think they fear the two hundred thousand people using fediverse compared to their hundreds of millions to billions of users.
We’re as much competition to them as a food truck is a threat to taco bell.
force them to defederate as fast as possible
Software Engineers just reinvent the wheel again and again as everyone loves a green field.
While somewhat true, this is also a dumb take. Not everyone working at Slack/Discord/etc can work on IRC. They’re making competing businesses, not just wanting to re-solve the same problem but wanting to do it with a new code base.
I suppose that applies more to XMPP, but not everything has to be a business, and you don’t have to be an ass about it.
You’re the one being an ass about it, saying developers always want a greenfield project. Tons of people contribute where they can, but we still need a job. So if somebody wants to make a business making a new chat client so they can make enough money to feed their family, well, that’s the capitalistic hellhole we’ve found ourselves in.
And those developers get told what to do. The wheel also gets reinvented by PMs and entrepreneurs who think they can do it better. Sounds like someone is salty about their software maintenance job.
I’m talking about the new company phase, not the established phase with management. Every company starts somewhere.
I don’t even know what you’re on about, I don’t know how you could see that as salty about anything with my job lol
No.
- I want to send messages to people who are not currently online (having a server stay online for you is a desparate hack and not a solution)
- I want to send media other than text
- I want my messages to be e2ee
- I want presence - e.g. know if someone is available, busy, away
- I want voice/video calls
and many more…
None of these were solved by IRC but by the others you mentioned.
Sure, but all of those things could have been done by extending the existing protocol.
Also, fwiw, it has had media sends, presence and support for encryption for a very long time. The rest could be added. All of those things could have very well been an IRC client with a couple of extra features and a server upgrade to queue messages.
Nothing good will come of federating with meta, the fediverse should simply stay out of their reach and realize whatever potential it may have.
I think there might be another way to hurt it though that this article doesn’t seem to mention. Funnily enough, it’s also a theme of an asterix and obelix comic book, which the introduction referenced. This way would be monetization. Threads might try to “help” the fediverse by feeding the bigger instances money, therefore the hosts of the instances would be more open to negotiations with meta and accepting of their policies.
I will compare this to YouTube which started paying all it’s big creators until they became dependent on the platform for a living and then started slowly implementing more and more rules that limit their freedom of expression. Remember how much PewDiePie used to swear in his getting over it videos? In another “pew news” or whatever it was called video I happened to watch he directly mentioned that he censors himself because he isn’t going to put his job on the line just to say “fuck”. Profit invites creators to comply with YouTube’s regulations even if they aren’t enforced violently always.
The same pattern was used in the asterix comic I mention above. Ceasar decides to open a building complex almost next to the problematic for him village and so the residents flood the markets and are shocked at the low prices compared to Rome. As a result, the villagers start increasing prices and advertising their goods and services, neglecting their previous morals and ethos. In the end, however, the Romans lose again after (panoramix, I think?) makes them realize how much separation this has caused them, living only for their business. As a result they kick the Romans out of their village, once again united, and Caesar’s plans fail.
I think both these stories could serve as a potential warning to anyone who might consider selling themselves out if meta adopts such a policy.
The year is 2023. The whole Internet is under the control of the GAFAM empire. All of it? Well, not entirely. Because a few small villages are resisting the oppression.
European detected.
Hey, that’s us!!
California has privacy laws but they are weak
So Google used Microsoft’s “Embrace, Extend, Extinguish” strategy and looks like Facebook is aiming to use ut as well
Every corp is aiming at that. It’s a strategy that worked very well for MS (and the CIA).
To be fair, Microsoft didn’t invent this, they only showed that it could be implemented in the tech industry. To some extent, basically every big tech company does this now.
These days, we just call it “the stages of enshitification”. And basically every large tech company is doing something like that
“Enshitification is when our preferred open social web standard gets adopted by a major corporation.”
Wat.
No, that article is full of bull shit.
For mastodon if it can help:
-
Open your favorite text editor and write threads.net
-
Save it as csv
-
On your profile on Mastodon, click “edit profile” and scroll to “import/export”.
-
Choose “import”, it will open a menu.
-
In this menu be sure to click on “Following list” and choose “Domain blocking list”.
-
Browse and select your CSV
-
Click upload
deleted by creator
Absolutely no problem!
By chance, the instances (for or protecting minorities) I’m on are all defederated of threads.
-
This is a fascinating read and very relevant given that Meta is moving closer to connecting Threads (per OP). The article gives a good example with How Google killed XMPP
The article lacks some details that are inconvenient to the point it makes. What was the state of XMPP before being adopted by tech giants and after they dropped it / walled it off? What could be done to prevent it?
I just remember that Google used to be able to talk to Facebook and it was awesome.
Before that I used Trillian which had to log in to all the networks. There was one beautiful moment in time where you could just use an XMPP client and you were able to reach most of the people you know
What was the state of XMPP before being adopted by tech giants and after they dropped it / walled it off?
It was slowly gaining a user base. It was a good alternative to MSN Messenger and other big corp messaging protocols (Yahoo Talk or whatever it was called).
Yes, it was a good alternative, and it remains good alternative now although Matrix seems way more popular these days. Nothing really changed regardless of adopting XMPP because with a hindsight we know that for tech giants it’s the platform and not protocol that captures mainstream popularity:
That is true. Discord - gaming, Messenger - FB. Google just couldn’t tie it with any social network, so it flopped… and their numerous attempts at creating one.
That’s a good point. That would be helpful context
This time I don’t think it is an extenguish scenario. I think this is more of a preventative move to one-up the EU on interoperability. They want to be able to say “look how good we are, we already were interoperable for x time!”. But of course this could also not be the case and they might just want to kill the network, but I even find that unlikely. Xmpp isn’t dead in fact I use it every day as my phone number for texts and calls and I quite like it. Super robust, I basically never saw any federation weirdness like you could see on mastodon or Lemmy. So in my eyes xmpp didn’t get killed, they got beat by someone who had ressources and made a better product. And it’s not that I don’t think meta can make a great product that users like, but I kind of think that, especially when the competition exists (xwixxer) compared to basically none for Facebook and Instagram
Yup. This is pretty much right on the money.
BlueSky and Threads are looking at interoperable protocols because they a) have engineers at home that think it’s cool, and b) see the writing on the wall about upcoming regulation and want to preempt it. This is probably good for other networks already based on interoperability, but there are definitely a ton of open questions.
The article is 100% revisionist history written backwards to justify a knee-jerk conclusion and XMPP is indeed not dead. Or not any deader than anybody else that got washed away by WhatsApp winning the messaging wars over the 2010s.
EDIT: Re-reading my own post, it’s too harsh. The article isn’t “100%” revisionist history, so much as a biased insider account. The revisionist history is largely coming from both the misattribution of what happened to a deliberate move from Google and the fact that it’s being misread and misquoted when people react to it.
The article is 100% revisionist history written backwards to justify a knee-jerk conclusion and XMPP is indeed not dead. Or not any deader than anybody else that got washed away by WhatsApp winning the messaging wars over the 2010s.
Importantly, the article fails to establish how the current XMPP usage numbers show it’s “dead” compared to back in the Google Talk days. Especially in the context of the entirely changed langscape of text messaging. So the very premise is weak from the get-go.
Yeah, it does acknowledge that it still exists and has a solid community at the very bottom.
I do excuse it, it’s an article from an insider with an axe to grind that is bummed out that the Google integration didn’t make them win the IM wars and that Google was bad at supporting a secondary app, as they do. That’s legit.
But as a breakdown for a mallicious plan from Meta to “EEE” ActivityPub… well, it’s not even pretending to be that.
I think this is more of a preventative move to one-up the EU on interoperability
And it’s not even difficult to figure out.
As if Meta has any interest in actually being federated. This is like Google paying Mozilla to keep Firefox alive. As long as it’s not “serious competition”, it’s useful. You can point to it as a “Look! Free market! No monopoly here! We’re not stifling competition, we are actively funding it!!!”. And Meta gets to promote how they’re actively engaged in interoperability, supporting federation and all that.
I think it’s even slightly different in that Firefox has some dependence on Google (a scary level, actual, if Google ends that deal Mozilla is pretty much fucked) that the fediverse doesn’t - the people on the fediverse right now are enough to keep Fedi alive and moving, and I’d find it really, really hard to argue that they aren’t there deliberately to avoid being subject to the whims of Meta/Twitter/Reddit, etc. Like, in a lot of ways, it’s a sacrifice to be on these services because the bulk of content still exists in the proprietary silos. Because the actual protocols and main developers are also intrinsically motivated by the this separation, it’s hard to picture how they could even try to extend/extinguish here.
Like, if Threads fully federates, I’d guess that quite a lot of people block their instance just to keep their hands clean. Those that interact with Threads via Fedi probably fall into the boat that I would. I want some particular content or to follow some people, just not shoveled at me however Meta decides it should be, and not in a way that they can profit from showing me ads. If Meta pulls some bullshit, it’s likely the Fedi would more or less just block them entirely then give up and start a Threads account. And I have a hard time seeing a world where they go to Eugen or basically any of the other driving forces in the Fedi and are like “we need you to change Mastodon so we can [do some typical Facebook bullshit” and Eugen are like “yeah cool with me.”
I think its more likely that Threads users are eventually going to see fedi users dropping a long comment or some post that is about how it’s nice to have a clean ad-free feed and move clients if not over to the fedi in general. It won’t be enough to really matter for Meta other than to say “see we don’t have a monopoly!” and hey, if the fedi gets a little bigger it’s all good for the rest of us.
Super robust, I basically never saw any federation weirdness like you could see on mastodon or Lemmy.
Because the protocol is more or less a finished product.
And of course, there is also the fact that ActivityPub is not meant to be used as 1 on 1 talk protocol. When you have to sync with posts on other servers, that does take a toll.
Random question, but is your avatar a Windows 95 icon file?
I think so, I had it in my downloads file for like a year or two and I just found it
Meta does not give a shit to absorb the fedi. We are like a thousandth of their size, just a blip on their radar. I have no idea where people get this idea of self importance that Meta cares about their 10 user server.
If they didn’t why would they develop tools to federate? It’s obvious that the threads project was sped up significantly following musk’s obliteration of Twitter, so they wouldn’t go out of their way to implement such a feature if they didn’t have a very specific reason for it.
A company’s goal is maximization of profit, so don’t assume they intend anything else. The activitypub userbase is too small to be a significant addition to their userbase but in this way they can destroy it before it escapes their control. They don’t take risks. Mastodon could seriously compete with threads and it’s gaining popularity. If one more big boom happens it might be too late to stop the fediverse from competing with meta in the most cost efficient way possible. Do not be lured in by the false sense of security, meta wants us to help maximize their profit. We aren’t doing that right now so Meta wants to stop us (or limit us, whatever they deem more profitable)
They don’t take risks.
Quibble: Meta took a huge write off because their metaverse didn’t get the reception they hoped.
I think they take risks, just calculated ones. And sometimes… A founders ambition.
It is as you say, but look at the difference. Allowing metaverse to grow is only going to hurt them, while the potential profits from the metaverse could be massive. They deemed it a risk worth taking because of the potential success. Meta won’t leave the fate of lemmy up to chance, because they decided we are not very likely to disappear in time.
The metaverse (that game) was released before it was done in any way for the marketing hype, but they are still working on the VR headsets. Once those are ready for mass adoption, the metaverse will have a comeback, and a hard one. People love sucking on marketing titties, and that won’t be any different.
Roblox metaverse best metaverse for now
Meta’s involvement is to “poison pill” fediverse if it really starts to take off. Or just outright buy the bigger/best parts and leave the rest wither…
I bet XMPP users were saying the same thing about google talk, maybe try reading the article?
The whole two of them? What good XMPP client is there again?
whatever supports the calyx xmpp/jabber server
Might be because of Threads, and Meta seeking to use ActivityPub themselves.
I don’t disagree with you though; I don’t think the fedi is big enough at the moment to register as more than a blip on their radar, as you said.
Microsoft was using Embrace Extend, and Destroy against Linux 25 yrs ago when it was a blip compared to MS.
This tactic is designed to be used against potential opponents before they become a real threat.
It costs peanuts to eliminate a weed in your yard when it first sprouts.
It also gets the jump on your neighbours who might be interested in this little weed as well.
Also you can’t have unmonetized weeds popping up everywhere they might inject colour and variety into your barren add riddled hellscape.
If something killed XMPP for me - it was Matrix. On open source replacement that is not only more popular, but has more active development and it’s easier to use. No big company required. And since XMPP is still alive for its niche user base and EU is probably the reason for Threads federation - I don’t think this is the right hill to die on.
Also Matrix can bridge to XMPP, of course you wouldn’t because nobody uses XMPP.
calyx institute keeps xmpp slightly alive for non xmpp mega fans
Is there anyway to implement (without spinning up your own private instance) the ability for individual users to opt out of federation of their content to certain instances, or would that introduce too much overhead and complication?
This is a commonly requested feature, and is likely to appear in a future version of Lemmy. In the interim, several of the mobile apps have this feature.
Given new EU legislation, it is likely that in the future, they may be forced to correctly implement ActivityPub, and to federate with instances not violating their content policies.
Well, if met
ha decides to interop, activity pub can launch some propaganda to make users “just switch”, I guess. I mean it’s somewhat different from the situation with xmpp and google as most sane ppl already know fb’s crap isn’t good for your data… So maybe smth like “remember that cool shiny thingy people were leaving xitter for? Guess what, now you can talk there with your grandma without subjecting yourself to fb’s shady practices” could work given interop works good enough.P.S. that specification under a EULA actually sounds like a good idea if you put it a bit differently: whatever implements this specification should be published under one of $insert_a_set_of_licenses. Then whatever proprietary garbage creator that decides to join will be forced to do this via bridges, and others can tell them to fix their crap 😁
most sane ppl already know fb’s crap isn’t good for your data
Bold of you to assume they care enough to do something about it. It took half a second for more than half of my friends to jump onto threads when it launched. None of them ever considered the fediverse before that. People just flock to whatever the big companies do.
Sure, but, on the other hand, when crapple rolled out their “are you OK with zuck watching you sleep” switches, ppl suddenly declined that generous offer… So I’m inclined to think they kinda care, but convenience is more valued.
Well, okay then, depending on how that interop is implemented, it may be possible to make some kind of one click-ish data importing, idk. Not messages, but at least friends, communities and similar stuff. Just speculating, tho
We already talked about XMPP a few months ago, if anyone is interested in reading about some experiences with XMPP for more context.
No. There was nothing to extend and extinguish with XMPP. It was a dead on arrival protocol that nobody ever used seriously. I’ve been to the internet at that time and what people actually used was: AIM, ICQ, MSN and possibly even Yahoo!. (IRC for the nerds and Counter-Strike)
It was exactly the other way around. Nobody ever used XMPP, then Google opened federation on their first chat and suddenly someone was actually reachable via XMPP which was a cool thing for some nerds that were into XML then, but when Google noticed that it only imports problems with nothing to gain from the XMPP network they just shut it off.
At the time nobody cared because the people accidentally using XMPP didn’t give a shit about it because they used Google not XMPP in the first place.
Some governments I think and the BBC are already using mastodon, and honestly, those big organisations used things like tweetdeck before instead of mainstream twitter apps. I can feasibly see big organisations like governments, politicians and media sites not wanting to use threads, and instead using their own instances to interact with threads users.
XMPP still works great btw. It was hard to convince everyone to get an address, but now 95% of my messages are over XMPP. To me compatibility with internet standards is a hard requirement.
