Facebook/Meta starts talking about the "Extend" phase of Embrace, Extend, Extinguish as predicted:
"“You could imagine an extension to the protocol eventually — of saying like, ‘I want to support micropayments,’ or … like, ‘hey, feel free to show me ads, if that supports you.’ Kind of like a way for you to self-label or self-opt-in. That would be great,”
Yes, as co-facilitator of #FEP, that is the point. Highly in favor of a bottom-up 3-phase standards process designed to guarantee an open ecosystem and tech landscape. Wrote a bunch about that on #SocialHub:
Some people say that Meta makes Threads federate with Mastodon so it would eventually siphon its users (see #EEE).
That's one of the reasons several Mastodon instance admins decided to preventively block Threads (see #Fedipact).
I think that keeping some Mastodon users from interacting with Threads might on the contrary push them away from their instance and maybe go to Threads instead, what we want to avoid in the first place.
#Threads user with dotted username (an impossibility in vanilla #Mastodon) spotted in the wild federating with a #Misskey instance (namely, Voskey)! So, does this mean Misskey can handle dotted usernames & thus can further do what #Mastodont?
So, this (the dotted usernames that can federate with other #ActivityPub instances but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse. @youronlyone Your thoughts on this again, as we previously discussed it on #Bluesky?
but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse
Is, well, not a fair example because dotted usernames have been in used years before Threads and the Twitter Migration. As I mentioned, site plugins have been using @-domain.tld@domain.tld format.
If dotted usernames are going to be used to build a case of EEE by Meta, then the same argument can be used to accuse all other “plugins” using the same format, like Automattic's AP plugin and Brid.gy fed. ^_~
To clarify, I'm not defending Threads. I just find the issue of dotted usernames being linked to EEE, to build a case against Threads, as inaccurate. ^_^
With a corporate takeover and corporate "values" they shed like fleas, the #EEE will come in form of #Fediverse losing original intent and meaning.
No longer a place of refuge where people build things to the delight of others and in natural interaction foster cultures where humanity can be freely expressed.
Fediverse will be a category name, just like Web and Internet. A place of marketeers and commerce.
And yes, somewhere there.. #fedi still around. That neat hidden place, only to be found!
If this "privacy setting" for #quoteposts is implemented with it enabled by default, the result will be disastrous. :reisensweat: Since there is no other way to enforce this setting other than #defederation, we are going to see Mastodon servers strong-arming those software developers who are "non-compliant" by threatening a #fediblock. :reisensweat: Developers of the -key and -oma families will suddenly have to scramble to make their implementation of #quotetweets compatible with Mastodon's "privacy-friendly" implementation. :satsuki_sadge: This way of "extending" the fediverse is not acceptable, and everyone who has opposed #Facebook joining the fediverse due to #EmbraceExtendExtinguish should also oppose this issue which just eventually leads to the same result.
So according to Eugen, he's been using XMPP during a time when people let their desktop PCs run all the time, which is ideal for XMPP's requirement to maintain an active connection from sender to recipient in order to actually deliver messages.
But when the world transitioned from desktop PCs to mobile phones, XMPP's requirement to stay always on was just not practical, and the world moved on from XMPP and onto other platforms.
The only way people used XMPP was through Facebook and Google Talk, but the mainstream really didn't have a strong appreciation for XMPP.
According to Eugen, Email is still going strong because everyone knows how to work with it
Effectively, embracing, extending, extinguishing is just not a thing for email yet.
L’urlo di Threads fa cagare addosso il Fediverso? EEE… basta
«Noi siamo #Threads, l'esistenza come voi la conoscete è terminata, assimileremo le vostre peculiarità biologiche e tecnologiche alle nostre. La resistenza è inutile.»
In quali modi il Fediverso può reagire all'irruzione di Threads?
Lo scossone per il #Fediverso sarà enorme: guardando alla sproporzione di risorse tra #Meta e l’universo federato, sembra chiaro che tutto ciò porterà a una distruzione del Fediverso per come lo conoscevamo.
Threads federates, you don't subscribe to anyone on the instance. Happy now?
Threads federates, you blacklist the whole instance in your user blacklist. Now happy?
Threads federates, you subscribe to a few people whose writing you like. Happy?
Threads federates. Threads users realize, they can jump ship to another Instance and still talk with and to and about their friends. Threads loses users. Happy!
There is no such thing as "#lawful#access". Encryption is #math. There is no math that the "good guys" can do but which cannot be done by the "bad guys".
Anyone who suggests different is #lying, to #spy on you.
Il y a cette conception naïve que #Threads ne pourrait pas déclasser les publications externes via la fédération ActivityPub comme Facebook le fait déjà via les hyperliens. #EEE
People who use “dark mode” colour schemes on the web; is it preferable to choose it yourself via a setting specifically for the site, or have the site automatically switch based on your system preferences? Is there best practice here? #a11y
I just had a look at #Meta's recent press release about #Threads, and something caught my attention right away.
For the very first time, they're acknowledging another #Fediverse platform alongside #Mastodon. Specifically, they're highlighting that #WordPress can now connect through #ActivityPub.
Now, you know Meta's PR department doesn't say things by accident. So here's why this is a big deal. Last time I checked, WordPress powers a whopping 43% of the Internet. Yeah, you heard that right! If you visit a website, there's a good chance it's using WordPress as its CMS.
Now, if even a fraction of those WordPress sites start federating, it could have a huge impact on the network effect of the Fediverse. Of course, Meta isn't oblivious to this. I've been talking about the potential of WordPress and ActivityPub for quite some time now.
But if you're particularly observant, you might also notice that they mention #Tumblr. We've known for a while that Tumblr is likely to integrate ActivityPub into their platform.
But here's an interesting tidbit: Did you know that one company, Automattic, not only owns Tumblr but is also the driving force behind WordPress?
I don't want to jump to conclusions, but once again, PR departments don't just drop hints randomly. I have a strong feeling that Meta has been having some high-level discussions with Automattic about the future of ActivityPub. It wouldn't surprise me if Meta has some insights into Automattic's upcoming plans for the Fediverse.
There’s been a lot of speculation around what Threads will be and what it means for Mastodon. We’ve put together some of the most common questions and our responses based on what was launched today:
"Embrace, extend, and extinguish" (EEE), also known as "embrace, extend, and exterminate", is a phrase that the US DOJ used to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences in order to strongly disadvantage its competitors.
A year ago if you told me that Instagram would be joining the fediverse, I'd think your crazy.
Let's not forget why they are doing this though, thanks to EU laws they have to make data portable, and with federation support they can portray their monopolistic practices in a different light.
Meta is an advertising company, we are their next market to break into. Remember this.
The former takes people from other domains and makes their posts green text on green background. The colors are manually set and not reflective of any magazine styles or the like, but I have no idea why rgba(20, 45, 20, 1.0) is the color someone chose. I recommend anyone who wants that script edit line#41 to something like GM_addStyle('[data-is-federated-content="true"] { background-color: #EEE; }');, but even then this is a bit annoying to have to do manually.
I think that the bridging solution is the safest and smartest way forward.
For the Federation/DeFederation conversation I really think that both sides have become too personal. Regardless of clandestine meetings or whatever - we need to operate from the position of -
"Hope for the best, make plans for the worst".
Best case scenario - they settle into the Fedi along with others. Sure we can hope for that.
But we need to assume that the potential for harm exists. We have to assume that the potential for bad admins exist. We have to assume the potential for #EEE (though I don't believe it works) will be attempted.
We need to consider these potentials and design accordingly. There is a risk here, and we need to think through things wholly.
You know what, you guise are right: there's no way #Facebook will be good for the #fediverse
me hoping facebook users might get a glimpse of internet outside their cave is naive at best
FB is gonna show up with the carrot of shiny UI and implement all the engagement driving sticky features which average users ask for and Mastodon devs have resisted
I don't think FB sees the fediverse or Mastodon as a competitor tho. I think it views us as a field of unbranded data cows free for the milking
Why do posts that aren’t from kbin show “kbin.social” next to the title?