-
Notifications
You must be signed in to change notification settings - Fork 578
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
getFollows & getFollowers => Add the date of when it happend #2981
Comments
+1 to both this issue and contributing a solution if possible I'm looking to do some quick analysis of how fast follower counts for accounts have gone up over the past week and would like to be able to collected aggregate |
This would be really helpful to me as well. I need to become more familiar with the protocol in order to contribute anything more meaningful but will hopefully be able to soon. |
+1 Would love to have this, too. |
+1 Would also love to see this! |
oh, I see. I wasn't aware that getFollows and getFollowers were public data. So its impossible to secretly follow someone (e.g. show latest content on my timeline) with atproto? |
Yes it's public data
Anyone can go to your pds, and look who you follow, and what are your posts. |
Is your feature request related to a problem? Please describe.
When I go to: https://atproto-browser.vercel.app/at/did:plc:dacfxuonkf2qtqft22sc23tu/app.bsky.graph.follow/3lapxwzhdj72i
I can see that I followed someone at a certain time.
So doing
listRecords
withxrpc
works great.Then I do
I get the information of the subject, but I don't have access to the
createdAt
of theapp.bsky.graph.follow
.For
getFollowers
, I can't access it directly withxrpc
(The collection is not public I guess), so I have no way of knowing when the follow happend.Describe the solution you'd like
Would be great to add a field:
followedAt
for both object.When you retreive the subject, you have the info, so I think it's all good. The issue is that you are sending directly the subject resolved... And it's not directly a subject information... And mixing data is not the best... Breaking the API is also not the best.
Maybe the Option 2 is a good threadoff ?
Additional context
I'll be happy to contribute after agreeing to a good solution. ✌️
Let me know what do you think
The text was updated successfully, but these errors were encountered: