Let's look at this towards the backend of the 10.0.0
Description
Description
Details
Details
- Security
- None
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T150 Write some coding conventions and guidelines on liniting | ||
| Open | None | T152 Release Version 10 (last version not a 'bundle') | ||
| Open | • RhinosF1 | T65 Make wiki_acl wiki specific | ||
| Open | None | T66 Allow wiki specific config for logpage() | ||
| Open | None | T77 Release wikigmnt | ||
| Open | • RhinosF1 | T96 Introduce json plugin loader | ||
| Duplicate | None | T75 Create self-generating plugins | ||
| Resolved | • RhinosF1 | T145 Cache a Session() object in memory for external requests |
Event Timeline
Comment Actions
I was talking to @Operator873 and this conflicts with https://github.com/Operator873/Darkness a bit. I suggest we could use OAUTH for everything but logbot and then the acl could be nearly auto managed. We could grab the user rights from the user info API after tokens are setup and use that for ACL generation. We'd just need to set default config of required rights.
I think we just need to look at securing the tokens in the databse.
Comment Actions
Let's make an effort at this again. I'm not gonna commit it to dev unless we're happy but the code base post the open sub tasks should make this better