masimatutu
Stay tuned for more useless language facts!
- 3 Posts
- 17 Comments
2·11 months agoNo complaints so far. I’m not using many new features, but I really like the new user interface.
For some weird reason in the implementation of the AP protocol, lemmy posts are seems as just a link on mastodon, the replies are complete though.
ActivityPub allows two post formats, Notes and Articles. Articles support titles and therefore posts on Lemmy and threads on /kbin use them, while notes do not and are therefore used for microblogging and commenting. Currently Mastodon’s article federation only goes so far as linking the post for content, and to be honest I’m doubtful whether Threads will federate Articles at all given their carefulness with federation.
You’re confusing defederation with Lemmy’s instance blocking. Defederation means that none of a server’s content is federated. Lemmy’s new instance blocking feature, however, only blocks communities and not users.
That’s not how federation works. If you’re on an instance that doesn’t allow Threads, you won’t see them at all, even when viewing posts coming from other instances.
Also,
We are on lemmy.
I’m not ;)
You know that if you actively blocked the instances that are federated with Threads you wouldn’t have seen this post, right (lemmy.world/instances)? I’m also only active on instances that block Threads, but blocking those who don’t is an excessive measure.
The thing is, you don’t really see anything from the Microblogging Fediverse around here at all, do you, so why would you from Threads? And Meta will only explicitly collect your data if you follow one of their accounts, which is impossible from Lemmy. So in a Lemmy context it is quite irrelevant.
But they won’t. Seeing how little even the relatively federation-conscious Mastodonians interact with Lemmy, from Threads it will be close to zero (especially since the devs are very “careful” with federation and probably won’t display article-formatted posts anytime soon).
No, that’s just Lemmy. On Masto it blocks all interactions from users (including prohibiting them from following you and therefore fetching your posts).
I’m just saying that even on federated instances the users can choose to block Threads, and that that gives the same result for them. There’s no need to force the hand of the user; there are more than enough corpo-critical people on Fedi for it not to be taken over by Meta.
Edit: And I understand that allowing interaction with Meta is very risky business. Which is why I like the approach of instances like social.coop which restrict interaction from Threads but still give the user a choice.
It really depends on the instance. There are many cozy, non-mainstream corners on the Fediverse. For instance, beehaw.org is as pleasant as can be.
By all means, fuck Meta to the moon and back, but for goodness’ sake, users on federated servers can choose to block the domain with the same result, not to mention that admins can simply restrict it (see social.coop/@eloquence/1115888…). It just isn’t so black and white as people are making it seem.
Federation with a bigger platform is realistically the only way for Fedi to become mainstream, and at the moment Meta seems at least to be trying to be communicative. And with their quite unvaluable userbase they really don’t have enough leverage against the privacy-concious Fediverse to turn AP into MetaPub. For now.
Thing about the Fediverse is that software is just software; what you should care about is the instances. There are a whole bunch of Mastodon instances that have already defederated long ago. A few big ones include mas.to, mstdn.social and troet.cafe; you can find the rest here: fedipact.veganism.social/.
@clgoh They haven’t even embraced yet and they’re extending already. Nice.
Yes, but they only see the title and a link to the original post in place of a body.
Yeah unfortunately I can’t because I’m on Friendica and Lemmy is annoying in that it treats images differently from the rest of the Fediverse.
This link should work: files.catbox.moe/stvn1w.jpg