Leave it to the communities.

Are Nitter links okay?

I’m fine with it.

I think this should be implemented on a community level and not on an instance level. As much as I don’t like twitter/x myself, it doesn’t mean we should be censoring everyone else.

Why I’m voting yes:

1. Twitter links are unusable these days without an account and we shouldn’t encourage people to maintain non-federated social media accounts.
2. It’s a breeding ground for hatred, bigotry, and since Musk took the reins Nazism.
3. I just sincerely hate the site and hope it dies.
4. No one posts links to there anyways.

Instance level action is a last resort option. There is no reason to do anything about X at an instance level. Rules are primarily a community level thing.

Do it https://lemmy.dbzer0.com/post/36484194

I think it should be up the communities. Not everyone hates twitter/x.

As others have done the best solution seem to be blocking twitter links but still allowing screens, this way you preserve the content but don’t give them any clicks.

The only value posting something that requires a login is when a bypass to that login is being provided.

Personally I would go so far as to ban links to any social media site that requires a login to even view the content linked.

But yes, banning Twitter links has plenty of other good reasons for it too.

I don’t think an instance-level ban is necessary at this stage, ever since thinking more about it after a similar discussion on a .ml post.

What I’d much prefer to see is a move on the part of users to use alternate methods for sharing Twitter content: links to reputable archive services or alternate frontends for Twitter (I lack a lot of knowledge in this area, but xcancel stuff, whatever libredirect does, etc.), or screenshots. In this order. Sometimes something comes up in the Twitterverse that is worthy of sharing, where pointing to the source is important for verification. But there are steps that can satisfy that without necessarily direct linking to Twitter, or that being presented as the only access medium to other users.

I’d think about this more at the level of courtesy (or good sh.it.iquette, if you will) than a hard rule. Won’t get your comment/post deleted if there’s no community rule but will have someone jump in with a not-direct-to-Twitter link/pic and some light (I’d hope) ribbing.

I support any community that makes it a hard rule at the community level, though. And if it came to pass at the instance level it’s not like I’d leave sh.itjust.works over it - I can’t see Twitter posts anyway, just a log in screen.

While I generally think such things should be community level as default, I’m fine with it if it happens.

I haven’t run across an x link in over a year that was worth clicking on. It’s a shitty site/service that’s turned into a festering pit of nastiness. It’s not something I feel strongly enough about to campaign for it being instance banned, but it’s already something I avoid.

Let’s do it!

I like this idea. Two things to clarify, although they may seem obvious.

• it should only apply to posts, not comments
• screenshots are fine

Otherwise it sounds good to me.

I don’t think it needs banned, but I would be completely unfussed if it got banned. And I wholeheartedly support just downvoting the beans out of anything sourced from there in the meantime.