- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
cross-posted from: https://sopuli.xyz/post/19842291
You must log in or register to comment.
I signed the pledge to not ever federate with them, and unlike the DARE pledges they made us sign in school, I’m taking this one seriously.
The advantage of the Fediverse is exactly that, that each instance can decide if they federate or not. The thing that I’m wary of is a renewal of Embrace, extend, and extinguish. I’d like to think that Zuckerberg isn’t going to try playing dirty tricks, but we’ll see what happens if and when Threads ever becomes really successful.
EEE would require existing Mastodon users moving to threads which I can’t see happening
EEE would require existing Mastodon users moving to threads
It would not.
Meta could implement ActivityPub in Facebook, and there’s your majority population. Imagine a Facebook user “friending” your mastodon account. You follow them back because it’s your mom, and so does basically everyone. Next, Facebook implements Pages to round off the concept of “communities.” Then, Facebook introduces a genuinely useful extension - marketplace. Once a decent clip of people set up shop, trim off any instances that don’t adopt the FriendlyPub fork.
Bam, EEE.
Once a decent clip of people set up shop, trim off any instances that don’t adopt the FriendlyPub fork.
And you’ll be back at square one, as if Facebook hadn’t federated in the first place. Which is essentially how the Fediverse is right now.
There’s a lot of shitty things they can do. They could push for changes to ActivityPub that nobody sane wants, confusing everybody that says “We support ActivityPub”, and spread FUD about anyone that doesn’t move to their new shitty version. Similar to how Google pushes through changes to web standards that benefit them, forcing Firefox to implement them too.
Then it’s up to Mastodon not to bow to the changes. The worst thing that can happen is that we lose federation with Threads again.
Threads uses can now “follow” fediverse accounts but “only if they’ve interacted with a post on Threads” and the posts “wont appear in your feeds.”
Well played, Zuck. Hilarious.
I don’t see how anything has changed. I don’t use threads, but this URL doesn’t work:
https://www.threads.net/@georgetakei@universeodon.com
And the post from the article just shows his account as plain text:
Because their link is different, it’s https://www.threads.net/fediverse_profile/georgetakei@universeodon.com
Interesting. Can’t tell if that worked because it wants me to log in. Wonder why they don’t just allow appending the instance at the end like the rest of the fediverse does. Does that post show the username as plain text for you as well? It’s still showing that way for me.
It’s clickable for me, however on some accounts mentions render as plain text, idk why, is this one clickable for you?
Nope, those are all not clickable. Probably requires logging in or something. Does not inspire confidence in them being a long-term team player, but we’ll see what happens I guess 🤷
True, you’re right, we’ll see, they still say that the “Fediverse sharing” is in beta so things can change
Instagram has long maintained a login wall, so I’m not surprised to see one on Threads. That means they hate the open web, not necessarily federation.
I do assume bad faith when it comes to Meta, and I suspect their middling, slow implementation of ActivityPub here is mostly intended to discourage antitrust actions against them.
hey look, threads can do something Lemmy can’t! shame it’s the only good thing they can do
A lot of effort to be blocked by most everyone from the fediverse. I don’t want the ads or to be tracked. I also don’t need dumb ass lib takes that come from contributions to capitalist social media. I’ll get the best ones from screenshots here or mastodon tvm.
Remember: it takes two to tango. Threads might want to federate, but a lot of Fediverse instances want nothing to do with Facebook.
