Hi Mario, > I pointed to my console > <https://dev.tweb.at/console.html#host:https://dev.tweb.at/api>, where > you can see, that managing recipes, bags and policies is easy. ... but > creating a generic and simple to manage access concept for the basic > recipes (TiddlyWikis) and the r/w structure is hard. >
When I look at that "good old commander" console I am entirely convinced that one thing we need to get collaboration going is a (TiddlyWiki based) ui to manage TiddlyWeb, including authentication and registration workflows. Two things I notice looking at the above are: 1. it's not a TiddlyWiki 2. I can't seem to even authenticate / log-in, even if I wanted to Also, setting up recipes without using lists and checkboxes seems error-prone / too complicated. Doing this within TiddlyWiki should eventually simplify the process. However, any server interaction involving login / registration appears to require more components than TiddlyWeb on the server-side, e.g. some (login) forms / email workflows / adding a new / temporaty user, discarding it after x-days non-activated, registration tokens, email validation, all that jazz. Not knowing how "socialuser" works, I think it's a bit of a problem / challenge to fiddle these things out every time you wish to implement TiddlyWeb... while sounding simply, user management / authentication / registration workflows have their challenges that do require some well designed workflows / components / processes. Best wishes, Tobias. -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
