Restrict pages to identified clients
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 31
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
As a site owner
I want to restrict pages to clients that identify themselves
So that I can host content that is not public
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
No files or tests are named. Start by reading the HTTP request handling and how clients are identified over the Reticulum Network; determine where page access is decided. Done means identified clients can access restricted pages while unidentified clients cannot, with the behavior covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100