You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using https://bsky.social/xrpc/app.bsky.feed.getAuthorFeed
When I fetch an author's feed, repost objects are the same as regular post objects, except the repost object also contains a reason object. The reason object doesn't contain its own at:// URI, it only contains a by object and an indexedAt field.
If I was storing these posts in a database or otherwise operating on them on a per-user basis, it is very hard to differentiate reposts across accounts.
As an example:
User A's authorFeed:
Post 2
Post 1 (Repost)
Post 1
User B's authorFeed:
Post 1 (Repost)
Post 3
In this example, there is only one unique at:// URI for Post 1 across all three versions of it, but I may want to keep track of the repost-posts separately for particular users. I would have to invent my own ID somehow for that.
In other social media systems, a repost is a skinny "wrapper" post with its own ID that references the original post. How am I supposed to operate on individual repost objects? Shouldn't a repost have its own URI or unique identifier?
The text was updated successfully, but these errors were encountered:
I am using
https://bsky.social/xrpc/app.bsky.feed.getAuthorFeed
When I fetch an author's feed, repost objects are the same as regular post objects, except the repost object also contains a
reason
object. The reason object doesn't contain its ownat://
URI, it only contains aby
object and anindexedAt
field.If I was storing these posts in a database or otherwise operating on them on a per-user basis, it is very hard to differentiate reposts across accounts.
As an example:
User A's authorFeed:
Post 2
Post 1 (Repost)
Post 1
User B's authorFeed:
Post 1 (Repost)
Post 3
In this example, there is only one unique
at://
URI for Post 1 across all three versions of it, but I may want to keep track of the repost-posts separately for particular users. I would have to invent my own ID somehow for that.In other social media systems, a repost is a skinny "wrapper" post with its own ID that references the original post. How am I supposed to operate on individual repost objects? Shouldn't a repost have its own URI or unique identifier?
The text was updated successfully, but these errors were encountered: