[ACL] Guest users, unowned bags, and other ACL details
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authorization
Research direction
Review the referenced issues #63, #20, #54, and #47 together with the current ACL, anonymous-permission, wiki, and configuration behavior. The work is complete only when the agreed 0.1 behavior is defined and implemented for unowned bags, anonymous permissions, wiki loading or caching, and the configuration setting.
Written by the indexing model from the issue text.
Description
I'm combining these here because they all relate to a single feature.
- #63 - This one required me explaining that both the bag and the recipe needed to have at least one ACL entry, otherwise the bag ACL would inherit the recipe ACL's default allow policy. So I'm setting it to default deny all that way people can safely forget to set it properly. This was already the case with owned bags and recipes, but now it will also be for unowned.
- #20 - This one is a bug in how the anon default permissions are defined. I've removed them from the code for the moment and will be adding them back in 0.1.
- #54 - I'm not sure what to do with this. These wikis should really be loaded from TiddlyWiki, not stored in the database, because if the user updates TiddlyWiki we would want that to be reflected in the wiki. It should probably just export them as single-file wikis and store them in the cache.
- #47 - This will be a config setting in 0.1.
- Dominant language
- TypeScript
- Stars
- 60
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from TiddlyWiki/MultiWikiServer
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
TiddlyWiki/MultiWikiServer#140 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#139 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#138 ·
-
User creation fails with 500 error when email field is left blank - missing frontend validationOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#136 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
TiddlyWiki/MultiWikiServer#135 · 1 comment ·
All issues in TiddlyWiki/MultiWikiServer
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
siyuan-note/siyuan#20517 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NaturalIntelligence/fast-xml-parser#890 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zsviczian/obsidian-excalidraw-plugin#3000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pnpm/get.pnpm.io#68 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nuxt-modules/better-auth#578 · 2 comments ·
Maintainers usually reply within 1 day