4 ms·
This whole thread nastoy has been making the argument that blocked posts are omitted from the thread for all viewers, and circumventing this behavior requires m
by jazzyjackson 2y ago
This whole thread nastoy has been making the argument that blocked posts are omitted from the thread for all viewers, and circumventing this behavior requires modifying the relay (and hence ingesting the firehose) not just the client
You have been arguing that blocked posts still appear in your custom client, which is a different claim than nastoy. As detailed by the GitHub issue that started this disagreement, bluesky relays have introduced thread breaking behavior that one can not get around simply by forking the appview.
- verdverm 2y ago> As detailed by the GitHub issue that started this disagreement, bluesky relays have introduced thread breaking behavior "relay" does not appear in that issue, not sure where this idea that relays have introduced thread breaking behavior is coming from
- jazzyjackson 2y agoI haven't hacked away at the bluesky api but isn't the aforementioned "app.bsky.feed.getPostThread" called against an instance of a bluesky relay hosted at api.bsky.app, as opposed to a PDS or an appview? That being the case, when you want to get posts of a thread, the information of which posts belong to which thread are the responsibility of a relay, which is doing the firehose-level-aggregation of which posts belong to which threads, am I misunderstanding?