control-panel-for-twitter VS Mastodon

Control Panel for Twitter [1] can automatically hide boosted blue replies for you

…although if an account is big enough, you're safer looking at the Quote Tweets instead for actual comments (it also restores the old direct link to those in the focused Tweet), e.g. you're lucky to get more than a handful of non-blue replies under an Elon Musk tweet among the engagement farmers before you hit the maximum number of replies Twitter will load

[1] https://jbscript.dev/control-panel-for-twitter

In terms of a browser extension for Twitter, I highly recommend Control Panel for Twitter. It works as a browser extension as well as on some mobile browsers. It is highly customizable to filter out who/what you don't want to see and is fully open source if you feel the need to tweak.

It's updated regularly and the creator is highly active on Twitter to provide updates and answer questions - @ControlPanelFT

If you decide to use it, drop the guy a donation, they work hard on it!

https://github.com/insin/control-panel-for-twitter

Aye sorry I should have linked. Here you go: https://github.com/insin/control-panel-for-twitter/releases/tag/v3.21.4

Control Panel for Twitter can already put them back [1] * *

[1] https://github.com/insin/control-panel-for-twitter/releases/...

* while Twitter continues to put the headline in the aria-label on the link, given there's no accessibility team left to protect it

* unless you're using Firefox, as Firefox Add-ons now takes ~4 days to review new versions

> Prioritising the replies of people who pay money for it was a body blow

A Twitter reply thread will only load around 200 Tweets in total, so on Tweets which have a lot of engagement, it's more likely that your reply will never be seen even if you paid, which defeats their whole purpose for ruining reply threads as a selling point. Just an incredibly short-sighted change.

My browser extension for Twitter [0] can hide replies from "verified" users - if you look at any Elon Musk tweet with this feature enabled, you'll be lucky if you see more than 1 reply.

Quote Tweets are where it's at now if you want to find comments on busy tweets which aren't Twitter Blue user posting multiple cry-laugh emojis, and they've recently made those take multiple clicks to access, from one of 2 different menus (my extension also restores the old Quote Tweets link).

[0] https://jbscript.dev/control-panel-for-twitter

While I realize this does nothing for mobile (RIP third-party clients), Control Panel for Twitter [1] has been nice for me to use as a browserscript. Defaults/hides "For You" and tweaks a bunch of other stuff (hideable trends, etc).

[1]: https://github.com/insin/control-panel-for-twitter

On desktop, the extension "Control Panel for Twitter" will let you "Replace X branding changes", it's great.

https://jbscript.dev/control-panel-for-twitter

You can also hide the idiots with the BlueLiteBlocker extension

https://github.com/BlueLiteBlocker/BlueLiteBlocker

Makes Twitter a bit more like it was before idiot in chief took over

Idk for mobile, but for desktop - one such example.

Oh, TIL about https://mastodon.social/ (https://joinmastodon.org/)

Looks like what you describe, doesn't it?

> Social networking that's not for sale.

Interestingly there is some discussion for Mastodon with people asking the limit to be smaller, which raises the question as to the purpose of alt text, and how to properly handle larger text lengths in screen reader programs.

https://github.com/mastodon/mastodon/issues/12268

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Mastodon DMs have absolutely no privacy: https://github.com/mastodon/mastodon/issues/18079

For a decentralized protocol doing things right is much more important than doing things fast, it is very difficult (and in a lot of cases impossible) to break backwards compatibility.

Postmortem on what happened here: https://news.ycombinator.com/edit?id=39305884

The v1 API of Mastodon limits the size of the tree that it will expand for users who are not logged into the server: https://github.com/mastodon/mastodon/blob/main/app/controllers/api/v1/statuses_controller.rb . I am guessing that this or some similar limit applies to threads being returned to unauthenticated users of the web UI. It just arbitrarily stops expanding the replies at some point, including the main thread from the OP.

If a thread is truncated, users expect it to expand automatically and autoscroll when you hit the bottom. In my desktop browser, that does not occur, and there is no indication that there is more to see. This is the situation of the web interface as of Mastodon version 4.2.5.

The issue is very sensitive to observer conditions. If you are logged into the server, the behavior is different. If you use a Mastodon app instead of the web, the behavior might be different. As the tree expands, the cutoffs become different. If you look at the thread on a different Mastodon server, the tree is different because every server has its own view of the Fediverse.

HN needs a best practice for linking to Mastodon threads in a way that provides a consistent experience to HN readers. The average Mastodon server would be crushed by hundreds of HN readers grabbing the entirety of a huge thread all at once, so this might involve some thread-unroll-and-cache service. I tried https://mastoreader.io/ but it did not solve the problem.

Alternately, we push changes into the Mastodon web UI to warn users when they need to click to see more and assume that people will get used to the navigation.

Suggestions?

Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5

>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Mastodon is free and open-source. Go ahead and add the flag:

https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....