Aurynn Shawso I've started seeing Mastodon apps fetch posts in threads from other servers directly, bypassing server blocks.
This is ... this is deeply concerning to me.
Mike Bell@aurynn I see no replies to this post, because I'm on a small instance and it doesn't receive replies along with boosted posts.
Therefore, my normal flow when I think I might want to reply to a post is to open it on the original server, so I can see the rest of the conversation first.
I understand the block concern, but the normal usage of many users bypasses that anyway because they are trained to open the original page, so does this really change much?
@aurynn Obviously it would be better if the user's own server was able to provide the context that they should actually see, blocks included.
I'm not sure, but I assume https://github.com/mastodon/mastodon/issues/18150 should do this? But given that issue #34 is pretty similar, it seems unlikely that's going to get a huge amount of priority :(
@aurynn Ah - I see that in fact it is the solution described in the issue linked above which is causing the concerning app behaviour.
I've added a note to the bottom of that issue mentioning the concern and suggesting a way this could potentially be fixed without stopping clients from being able trigger fetching of context (which for me at least, would be a really useful feature!)
@mike The solution is a gossip protocol being added to AP