TiddlyTweeter, I think for wider apps the widely used system to login using existing > credentials (Google, Twitter, LinkedIn, Facebook etc) for authorisation is > easiest. >
I don't see the whole process yet, but it might be feasible that when logging in with GitHub, the saver would create a Personal Access Token (valid for a day, for example), so the user would only see is that they need to login as GitHub user. https://stackoverflow.com/questions/41879286/get-a-token-by-github-api GitLab offers login by Google, GitHub, Twittwer accounts, and continous integration is much easier to use (you don't need Travis-CI because there is a builtin GitLab-CI), so that platform might be more ideal . The user only registers once with one of his accounts (so no need to memorize a new password) and the saver takes care of the rest. I still have to think about it, but I think it's a viable way. https://gitlab.com/users/sign_in -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f7b41b14-5172-40d3-92cc-05c1116da728%40googlegroups.com.
