Salta al contenuto principale


Is #Threads even still trying to federate?

βœ… They changed their .net domain to .com: mastodon.social/@madeindex/115…

βœ… They have not continued federating, it's still a one way road of
Fediverse traffic moving to Threads:
mastodon.social/@madeindex/112…

βœ… There haven't been any changes since I can remember & it's always been in "Beta".

βœ… The only "change" I have noticed is a spam notification before every! post "Continue sharing to the #Fediverse?"

@JBrickelt963 πŸ’™

#Facebook #Meta #Tech #IT #Mastodon


Marky Mark still hasn't updated the old Threads.net domain in the #Fediverse to the new Threads.com

Guess his superintelligence wasn't up to the challenge πŸ€–

On a side note: If #Meta wants a product to be "cool", @zuck should not wear it! 😎

❌ #Demeta now: reddit.com/r/DeMeta

#threads #ai #facebook #it #humor #mastodon #markzuckerberg #profile #joke #threadsnet #threadscom #tech #socialmedia #domain #online #internet #it #update #funny #superintelligence #zuck #artificialintelligence #ki


Questa voce Γ¨ stata modificata (2 ore fa)

reshared this

in reply to MadeInDex πŸ“°πŸŒŽ

indeed I followed all the points mentioned here but that you Fediverse point of view since I do not have an account on their platform.

I understand from the publication you are referring to regarding the domain name that it had not been updated in certain documents.

I don't know if the complexity of transferring usernames is related because the identifier is pseudo@domaine.xxx is written hard in messages.

in reply to JBrickelt963 ✊(Ο†)🚩

Good ❀ Personally I also don't use it, just for this project (it's pretty bad, so you are not missing anything ❀)

It might be complex, but if they wanted to I'm sure they could easily solve it, wouldn't even cost them 73 billion like the Metaverse (which never got solved tbh) hehe

in reply to MadeInDex πŸ“°πŸŒŽ

I am sure of it and certainly too. I had the same thought. They would have ample means to create a port between two domain names (similar to 2 instances). Since technically nothing in ActivityPub prohibits it, but is just a choice in the implementation of Mastodon and their API. Between 2 instances managed by the same person and resources such as billions of dollars it's not very complicated.
in reply to MadeInDex πŸ“°πŸŒŽ

Laurens @ ConnectedPlaces explored this topic a bit in Fediverse Report 147 - I couldn't read the article he's linking to, because it's paywalled, but he quotes Conner Hayes (head of Threads) saying:

"It’s something that we’re supporting, it’s something that we’re maintaining, but it’s not the thing that we’re talking about that’s gonna help the app break out".

Must say Metas commitment to the fediverse always felt kind of halfbaked, because afaik, you had to enable the fediverse connection from Threads manually, which was/is not going to help adoption

connectedplaces.online/reports…

in reply to MadeInDex πŸ“°πŸŒŽ

Yes that was actually very clever marketing and strategizing
"Hey look, we're doing this new-fangled thing and btw. we're open now..."

@JBrickelt963 Exactly πŸ˜€ I actually didn't expect Threads to still exist by now, I'd expect it to be re-integrated into Facebook, like they're doing with the Messenger service.

in reply to Simon Justesen

@simonjust
I think they can't for now, because it's their "super fast growing social media start up" now, they probably still need it for stock price reasons ;)
@JBrickelt963
in reply to Simon Justesen

@simonjust yes, I must have seen words reported like which in essence gave the impression that it was something that he was committed to keeping (link between Fedi and Thread) but that it was not an absolute priority. It gives the terms: half-hearted.

@madeindex

⇧