Currently, the follow endpoint ignores the additional parameters for renotes, post notifications & languages. The latter is expected, as we've not implemented note languages yet. The other two are missing, and the endpoint not working as expected may be confusing for users.
Original issue title
it appears that timeline filters don't apply to the streaming API? was created by samuel
Original issue description
So I'm actually having trouble tracking down exactly what's going on here. In Mona, when I select a user and turn off reposts, reposts only seem to be turned off when I leave the app and come back to it. When the app is open and loading posts in realtime, the reposts from users show even when I'd turned them off. This doesn't seem to be a problem at all in Enafore. I'm not nearly as familiar with activity pub as I could be, so if anyone knows how I can better track this down to provide more useful information, please let me know.
i don't want to be that guy but
well actually
{width=70%}
the endpoint is /api/v1/accounts/:id/follow
So interestingly, when I turn off someone's reposts in Mona, they are also turned off in Enafore. Do we know how Mona and Enafore would be communicating about this, if it's not part of the official API? The issue is that Enafore always respects the filter, even when I leave the Enafore app open. Mona does not, for any new posts that come in while I have the app open on my phone. @jeder I'm using a screen reader, and your images had no alt-text, so sorry if your image stated something already relevant to this question.
Oh hold on, did I implement this and then forget about it, one moment.
these screenshots show that there is an endpoint for this in mastodon api
I did not, it would seem. 
Alright, apologies for the confusion. I'll go and check it out.
@fastfinge, hmm. I'm not sure how it would be communicating this since the follow endpoint doesn't currently support customizing follow relations. I'll have a look at how enafore handles this.
As expected, it sends a follow with the parameter that's not implemented. On my end, when pressing the "hide boosts from user" button & reload the page, the state of the button resets to boosts being shown, which is expected given there's no backend code to handle this yet.
I wonder if it could have something to do with the markers API? Maybe Mona is marking those posts as read, so then when I go back to Enafore, I'm not seeing them or not noticing them or something? Sorry, I'm just guessing randomly now; I'll let the experts figure it out. :-)
Yup, the same thing happens here. Maybe I'm dreaming about this working in Enafore? I'm officially confused. Sorry!
No worries, I've updated the issue title & description to match the request & added another bit that is related, and will tackle it when I have time. Thanks for the report!
+1 on this, it'd be nice to have the ability to disable boosts like other fedi software
This is scheduled for the next beta release, so unless something happens that prevents me from implementing this, it'll be available soon :)
YAAAAY! This is the only missing feature left for iceshrimp.net to be fully equal to Mastodon for my use-case.
Heya! To my knowledge, the filters in question are handled client-side in Mona. I don’t know how it’s meant to work, last I checked Mona doesn’t have an option to load posts in real time, only supporting manual refresh of timelines.
Mona uses the Mastodon client API to talk with the backend, and as far as I know there is no way to request reposts of a specific user to be hidden via that API. Once we add support for this feature to the backend, there will be a way to set this up, but it will have to be done via the web UI, as we don’t control the Mastodon API specification and there’s no equivalent action we could implement.