GKaszewski/movies-diary
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: shared/collaborative watchlists with federated users #11

New Issue
Open
opened 2026-07-10 03:54:22 +00:00 by GKaszewski · 0 comments
GKaszewski commented 2026-07-10 03:54:22 +00:00
Owner
Copy Link

Allow users to create shared watchlists that federated users can collaborate on — a "movies to watch together" list.

User story:

  • Create a named watchlist and invite remote actors to it
  • Invited users can add/remove movies from the shared list
  • Changes sync via ActivityPub (Add/Remove activities on a shared Collection)

Open questions:

  • Ownership model: single owner with collaborators, or symmetric?
  • Visibility: private (invite-only) vs public (anyone can follow/view)?
  • How to handle conflicts (e.g., someone removes a movie another person added)?
  • AP representation: shared Collection with multiple attributedTo, or a custom object type?
  • UI: separate "Shared Watchlists" section vs tabs on existing watchlist page?

Scope:
This is a significant feature touching domain models, federation protocol, and UI across both classic HTML and SPA. Likely best broken into phases:

  1. Local shared watchlists (multi-user, no federation)
  2. Federation sync for shared lists
Allow users to create shared watchlists that federated users can collaborate on — a "movies to watch together" list. **User story:** - Create a named watchlist and invite remote actors to it - Invited users can add/remove movies from the shared list - Changes sync via ActivityPub (Add/Remove activities on a shared Collection) **Open questions:** - Ownership model: single owner with collaborators, or symmetric? - Visibility: private (invite-only) vs public (anyone can follow/view)? - How to handle conflicts (e.g., someone removes a movie another person added)? - AP representation: shared Collection with multiple attributedTo, or a custom object type? - UI: separate "Shared Watchlists" section vs tabs on existing watchlist page? **Scope:** This is a significant feature touching domain models, federation protocol, and UI across both classic HTML and SPA. Likely best broken into phases: 1. Local shared watchlists (multi-user, no federation) 2. Federation sync for shared lists
GKaszewski added the backendfeaturefederation labels 2026-07-10 20:17:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Rust backend / domain / adapters
 big
Large scope / multi-sprint effort
 bug
Something isn't working
 feature
New functionality
 federation
ActivityPub / social federation
 spa
React SPA frontend
 ux
User experience / design
No Label backend feature federation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GKaszewski
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GKaszewski/movies-diary#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?