-
Notifications
You must be signed in to change notification settings - Fork 34
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
AP: reject incoming DMs #886
Comments
You'll also need to check how Fediverse software behaves if it receives that error. To my knowledge, Mastodon happily returns a Not saying that you shouldn't send a |
True! Mastodon and most other fediverse servers generally check signatures synchronously during inbox delivery requests, and then return 202 and do all other processing async, so sending servers don't see failures there. The idea here would be to return eg 501 synchronously, but you're right, I have no idea whether/how different servers would surface that to users, if at all. |
The more sophisticated approach here might be to send a DM back saying, "sorry, DMs aren't supported, feel free to send them that message another way." |
Subsumed by #966 etc |
Bridgy Fed only handles fully public data, so it doesn't bridge DMs. It happily accepts them though, and then ignores them, which isn't great, since it means people can DM bridged users and have no idea their DMs didn't go through. We should return HTTP 501 Not Implemented or something similar to inbox deliveries of DMs.
The text was updated successfully, but these errors were encountered: