a/gitea
Archived
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Notes about federated starring

Browse source
This commit is contained in:
Anthony Wang 2022-04-24 13:41:16 -05:00
parent 1b9a9df5ec
commit 9b763c2f0e
Signed by: a
GPG key ID: BC96B00AEC5F2D76
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
notes.md
View file

@ -61,6 +61,7 @@ How the federated following flow will work:
Sorry, ignore the above. I'm reading the ForgeFed spec and it's pretty clear we will have to go with the second option and actually render remote users and repos. Well this is going to be a lot more UI work than I'm comfortable with... (I'm a backend person, OK?)
### TODO
- Code cleanup and error handling (needs a lot of work)
@ -71,3 +72,19 @@ Sorry, ignore the above. I'm reading the ForgeFed spec and it's pretty clear we
- Implement functions from fetching followers/following using GetUserFollowers/GetUserFollowing
- Render remote user in UI
- Popup box in UI for redirecting to your instance
## Federated starring
Federated starring is very similar to federated following but requires the database to store remote repos in some way. It uses the ActivityPub `Like` activity and the `liked` collection.
### TODO
In addition to the federated following stuff:
- Handle remote repos in the database
- Create actor endpoint for repos (similar to what we have right now for users)
- Add table for `liked` collection
- API endpoints for returning `liked` collection
- Implement function for fetching `liked` items and returing a collection
- Function for handling `Like` activities for the inbox