Optional authorization model / not require explicit authorization of feeds
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
It would be great if hyperdbs could replicate freely without the need of a power dynamic where the db creator has implicit control over access. We've seen in practice that this is sometimes not desirable (e.g. in cabal, where we employ a connection stream hack to auto-authorize).
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
The issue names no files, tests, or entry points. Start by tracing where feed replication currently requires authorization, then compare that flow with the connection-stream approach mentioned for Cabal. Done should be a decided, documented design for optional authorization and its expected replication behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100