Hello, I found TiddlyWiki at the beginning of last year and I am amazed by the thinking in its design - everything can be served from an HTML file and all the data is stored and presented in a nice way.
Now I come with a challenge of access control. I want our users to use Tiddlywiki in parallel with one of our application. Our application is using Oauth2 for single sign-on. So I want my users to sign in SSO then access to my Tiddlywiki HTML file. I also want them to have read access to all the text tiddlers but have write access to only a group of tiddlers based on their login. I guess the challenges here are: - Use Oauth2 to manage the access to the Tiddlywiki HTML file - only using a (macro) tiddler but not using a server. I found resources about how to add Oauth to tiddlywiki, e.g. in tiddlyweb. But my idea (might be not feasible) is to only use tiddlers to control the access. So I can still keep everything in one HTML file. - Access to a group of tiddlers. I saw this has been discussed and mentioned in Google groups and some server options like BOB. But I haven't seen a practical way to do so. I think this is not just a post about finding answers but also seeking the opinions about if this is worth doing and if this is a Tiddlywiki way of thinking. BTW, I watched the video "Intertwingling the Tiddlywiki" at CodeMesh and glad more people are hearing the beautiful idea! Thanks, Chun -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1e19db5f-1076-4ccd-9a69-15142490116f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
