Currently, the only proper way to follow new releases of specific networks/channels/actors is to create one alarm per entity.
Like Favorites, having a hard-coded 'Following' stash that gets populated by a "Follow" button may be useful.
Favorites differ from Following in that non-favorites may still be worth following.
By following, Traxxx could just setup a new alarm that connects to a 'Feed' stash, unfollowing deletes that alarm (probably needs some metadata so Traxxx can find the correct alarm).
Notifications just work implicitly
The 'Feed' stash could maybe be shown on a dedicated /feed page, that is user-only (or maybe even configured to replace the landing page?)
Currently, the only proper way to follow new releases of specific networks/channels/actors is to create one alarm per entity.
Like Favorites, having a hard-coded 'Following' stash that gets populated by a "Follow" button may be useful.
Favorites differ from Following in that non-favorites may still be worth following.
By following, Traxxx could just setup a new alarm that connects to a 'Feed' stash, unfollowing deletes that alarm (probably needs some metadata so Traxxx can find the correct alarm).
- Notifications just work implicitly
- The 'Feed' stash could maybe be shown on a dedicated /feed page, that is user-only (or maybe even configured to replace the landing page?)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently, the only proper way to follow new releases of specific networks/channels/actors is to create one alarm per entity.
Like Favorites, having a hard-coded 'Following' stash that gets populated by a "Follow" button may be useful.
Favorites differ from Following in that non-favorites may still be worth following.
By following, Traxxx could just setup a new alarm that connects to a 'Feed' stash, unfollowing deletes that alarm (probably needs some metadata so Traxxx can find the correct alarm).
Alternatively, maybe when Following an actor, the destination stash could be configured.