Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mute clients #8271

Open
1 task done
hackertours opened this issue Aug 18, 2018 · 6 comments
Open
1 task done

Mute clients #8271

hackertours opened this issue Aug 18, 2018 · 6 comments
Labels
suggestion Feature suggestion

Comments

@hackertours
Copy link

Feature Requests: Mute/Filter specific clients. This would enable us to keep our timeline free from crossposters and other very specific clients.

image


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
@trwnh
Copy link
Member

trwnh commented Jan 2, 2019

One current problem is that the source app is not federated between servers, so currently it is only visible on local statuses. I do agree that this would be an extremely useful feature, and I enjoy having it in Subway Tooter on my phone.

@Gargron
Copy link
Member

Gargron commented Jan 2, 2019

Apps do not have the same ID between servers, and some don't even have the same ID between users on the same server. This is because app registration must be automated and anonymous, because a single developer cannot pre-register on every potential Mastodon server. So, I don't know how this is supposed to be accomplished.

@trwnh
Copy link
Member

trwnh commented Jan 2, 2019

Federating the application should be enough, shouldn't it? Name-based filtering would probably be enough, and there wouldn't be a real need for ID-based filtering. Yes, this probably opens up avenues of name spoofing, but this can already be done right now and also isn't very significant. The current Mastodon API response contains e.g. the following:

"application": {
    "name":"Tusky",
    "website":"https://tuskyapp.github.io/"
}

Either this can be exposed in the ActivityPub representation (perhaps within the mastodon namespace), or the web app can fetch the information via the Mastodon API (less compatible but works right now, e.g. from truncating the ActivityPub id and querying it against the remote instance's /api/v1/statuses).

@nightpool
Copy link
Member

nightpool commented Jan 2, 2019 via email

@trwnh
Copy link
Member

trwnh commented Feb 24, 2019

#8476 is still a blocker on this

@lorenlepton
Copy link

im just wondering about this a bit more, since there has been a stupid influx of new users coming to mastodon but still crossposting & obviously the stress the servers have more than likely taken for everyone on here & other servers

it would be lovely to have such a feature, because, in all honesty, its fucking shite having that drek come over at such a fevered rate. even more so now

I love the work being done though & fully appreciate the time & effort put into the project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion Feature suggestion
Projects
None yet
Development

No branches or pull requests

5 participants