4 ms·

Having to visit the Replies page of user C and try to piece together snippets of conversation - some of which are still unviewable - is not a reasonable solutio

by nastoy 2y ago

Having to visit the Replies page of user C and try to piece together snippets of conversation - some of which are still unviewable - is not a reasonable solution. In particular, posts 7 and 8 are not there and the link between posts 1 and 2 is severed.

verdverm 2y ago
> not a reasonable solution That's your opinion. The vast majority of ATProto users like the enhanced controls over their conversations. If you don't like it, use a different social media platform
- nastoy 2y ago
  That it's unreasonable to expect users to mitigate this by hunting around others' profiles for snippets of conversation is my opinion, yes. That one user blocking another user makes chunks of the conversation disappear for everyone else viewing the thread is verifiable fact. As it is a verifiable fact that this is done server-side via the getPostThread endpoint, by which posts in the parent and replies fields of the response are omitted. This is not "absolutely and provably wrong", as you put it. Maybe do some research yourself before accusing others of intentionally spreading falsehoods?
  - verdverm 2y ago
    You said posts were blocked when what you are actually describing is replies being disconnected from a post on that post. They are still visible within the network It's working as expected You have made multiple other inaccurate statements about Bluesky / ATProto throughout your comments with your new account
    - 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 ago
        I 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?
- llvm-dev 2y ago
  [dead]

by nastoy 2y ago

verdverm 2y ago

> not a reasonable solution That's your opinion. The vast majority of ATProto users like the enhanced controls over their conversations. If you don't like it, use a different social media platform

nastoy 2y ago
That it's unreasonable to expect users to mitigate this by hunting around others' profiles for snippets of conversation is my opinion, yes. That one user blocking another user makes chunks of the conversation disappear for everyone else viewing the thread is verifiable fact. As it is a verifiable fact that this is done server-side via the getPostThread endpoint, by which posts in the parent and replies fields of the response are omitted. This is not "absolutely and provably wrong", as you put it. Maybe do some research yourself before accusing others of intentionally spreading falsehoods?
- verdverm 2y ago
  You said posts were blocked when what you are actually describing is replies being disconnected from a post on that post. They are still visible within the network It's working as expected You have made multiple other inaccurate statements about Bluesky / ATProto throughout your comments with your new account
  - 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 ago
        I 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?
llvm-dev 2y ago
[dead]