Read-only channels
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I am working on a Microsub server that, apart from the conventional 'feeds in a channel'-model, also uses channels to output filtered posts. For example: I have one channel that returns the most liked posts. The feeds that are used as input for this channel are in different channels.
A 'read-only channel' would be just like a normal channel, except:
- You cannot delete it. (But renaming seems fine to me.)
- You cannot follow anyone in it. (For the posts come from different channels.)
- You cannot unfollow anyone in it.
- You cannot get a list of followers.
In a way, the `notifications` channel is already such a channel, although it's never mentioned you cannot follow people in it. (Should you be able to?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Microsub channel and notifications-channel rules referenced by this issue. Resolve whether read-only channels, including notifications, should prohibit deletion, following, unfollowing, and follower listing, then document the decided behavior in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100