Hacker News Reader

Comment by kovek | Hacker News Reader

This looks like it is presented as geared towards mastodon consumers who want to control what they see on their timeline. I think a mastodon client would be a better choice for an entity that supports these features than a mastodon instance. Why did you chose to design such an instance instead of a client with filtering capabilities? This instance looks like a great tool for moderators instead of mastodon consumers.

View on HN

Not my project, but why bother writing a whole client and maintaining it when all you want to do is build some better filters?

Get filtering happening on the server, then it works for everyone on that server regardless of whether they're using the default web app or an app on their phone.

Some Mastodon admins share their patches for things outside the scope of what gets approved by the project lead so if they decide it's a good thing then maybe they'll add this feature to their own instance; the 'source code' link at the bottom leads to the git repo that is presumably their live code.

If you have a preferred client or multiple clients across devices, this means that you don't need to worry about differences in features or preferences. It guarantees a consistent experience.

This will be useful to consumers too since they can filter out angry posts from users they don't follow. I agree that, in practice, this might be more useful to moderators. Another use case is to automatically move posts to folders based on text/URLs in them.

Correct me if I'm wrong, but if an instance wants to comply with the recent EU laws about copyrights, GDRP, anti-hate speech, etc, filtering on the server is mandatory anyway.

As I understand it, "qualifiers" give the same filtering power to the user too.

I guess people could simply send encrypted tweets to the instance, and decrypt them on the client side to escape the filter.

Reply on news.ycombinator.com