Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reposts in feeds do not contain enough unique data #1811

Open
csuhta opened this issue Nov 3, 2023 · 0 comments
Open

Reposts in feeds do not contain enough unique data #1811

csuhta opened this issue Nov 3, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@csuhta
Copy link

csuhta commented Nov 3, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant