Hi Chris, One reason user management workflows aren't built into TiddlyWeb is because > one size won't fit all. >
I imagined the rationale would be something like that. So, taking a look at *socialusers* for TiddlyWeb may prove to be the best approach to not start all from scratch. For example some people prefer not to use Tank because it requires one of a > google, github or facebook account to log in. I > chose that, however, so that Tank has _zero_ knowledge of (or > even interaction with) a user's password. I take it, *tank *implements its own authentication layer / workflow / processes / modules / forms, independent from or extending *socialusers*. So yes, wanting some form of user management sure does not necessarily mean wanting tank... but only those user-management-components when it comes to authentication, and possibly registration ...well, basic user management that works out-of-the-box-ish rather than after develop all of that from scratch. 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.
