masimatutu

joined 10 months ago
[–] masimatutu@nerdica.net 2 points 8 months ago (1 children)

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

[–] masimatutu@nerdica.net 1 points 8 months ago (3 children)
[–] masimatutu@nerdica.net 2 points 8 months ago (5 children)

No complaints so far. I'm not using many new features, but I really like the new user interface.

168
rule (files.catbox.moe)
submitted 9 months ago* (last edited 9 months ago) by masimatutu@nerdica.net to c/196@lemmy.blahaj.zone
89
rule (files.mastodon.online)
[–] masimatutu@nerdica.net 1 points 9 months ago* (last edited 9 months ago)

No, why? I'm just pointing out that there are a lot of accounts that a lot of people want to follow who are very unlikely to ever move to non-corporate social media.

[–] masimatutu@nerdica.net 4 points 9 months ago (3 children)

Yeah, say that to Biden...

[–] masimatutu@nerdica.net 13 points 9 months ago

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.

[–] masimatutu@nerdica.net 0 points 9 months ago* (last edited 9 months ago) (1 children)

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.

[–] masimatutu@nerdica.net 1 points 9 months ago (3 children)

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.

[–] masimatutu@nerdica.net 2 points 9 months ago

Also,

We are on lemmy.

I'm not ;)

[–] masimatutu@nerdica.net 1 points 9 months ago* (last edited 9 months ago) (5 children)

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.

[–] masimatutu@nerdica.net 1 points 9 months ago (1 children)

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.

 

There's a common false dichotomy about #Threads: cut them off, or leave it to user choice.

I can't speak to other software, but Mastodon offers a third option: limiting Threads. This can be done for all users of a server.

- You can follow Threads accounts after clicking through a warning.

- People who don't follow those same people won't see their posts.

- You have to manually approve followers _from_ Threads.

Basically, it puts Threads in quarantine, without cutting off all connections.

I like that option for our server, social.coop, and it's the one we voted to implement earlier this year.

We know that Threads already hosts bad actors (e.g., LibsOfTikTok). We know some reasonable folks have set up shop there and will continue to flee there from X.

This option makes it clear that Threads is not a safe space, while allowing limited connections.

Every instance will implement the option that makes sense to them, of course.

social.coop/@eloquence/1115888…

 

Default instance blocks should largely replace defederation

Since what content users might want to see is quite unlikely to match which servers the admins tolerate, choosing instance on the Fediverse can be quite complicated, which is inconvenient and off-putting for new users.

For this reason, and simply that the Fediverse is stronger united, I believe defederation should ideally be reserved for illegal content and extreme cases. If Fediverse platforms would allow instances to simply block the rest for users by default, the user experience would be the same, unless they decide otherwise.

@fediverse #fediverse #defederation

281
rule (media.mas.to)
 

Yo Ma-Ma

(I'm so sorry)

392
rule (friendica.myportal.social)
304
browser rule (cdn.catcatnya.com)
view more: next ›