All,
WordPress permits OAuth and the standard login process logs the browser in
so I believe login once and at least that browser will have access until
logout, or time out.
Open ID allows you to login with a WordPress, WordPress.com account,
Google, Facebook etc... It is WordPRess that has
All three of those sites have an OAuth flow setup for that. Basically you
get redirected to the login page and then the login page returns a code
back to the client page. Wordpress might just involve using the browser
session, though, I’m not sure.
On Fri, Dec 6, 2019 at 07:58 bimlas wrote:
>
Arlen,
WordPress (that's an interesting but very feasible suggestion), Google, and
> Github all support multi-user editing natively, so each user would have
> their own login credentials.
>
True, but we want to access the API with the saver, so we need a Personal
Access Token. Or is it
WordPress (that's an interesting but very feasible suggestion), Google, and
Github all support multi-user editing natively, so each user would have
their own login credentials.
On Fri, Dec 6, 2019 at 6:54 AM bimlas wrote:
> Jeremy, TonyM,
>
> Another interesting sync adaptor would be one that
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
bimlas wrote:
>
> I think the main problem with "database backends" (Google Sheets,
> Wordpress, PouchDB) is that by default they are not accessible as a web
> page, but everyone has to set up credentials to read and edit the wiki.
>
> A workaround is to add new Personal Access Tokens to
Jeremy, TonyM,
Another interesting sync adaptor would be one that *retrieved *and stored
> tiddlers via the Wordpress API.
I think the main problem with "database backends" (Google Sheets,
Wordpress, PouchDB) is that by default they are not accessible as a web
page, but everyone has to set
Hi,
There has been an idea to use e-mail accounts to store tiddlers using the
IMAP format. e-mail hosting providers are reliable and cheep. You may even
have an account combined with your smart phone contract, but probably not
used.
just a thought
mario
--
You received this message
Jeremy,
we could make use of the sql database that is build to support word press.
However as you say using the api would be more sophisticated.
I have played with building custom post types and would be interested in
creating a tiddler post type. We could also support plugins as JSON
Another interesting sync adaptor would be one that retrieved and stored
tiddlers via the Wordpress API. The attraction is that WordPress hosting is
highly commoditised, being readily available and cheap. It should be possible
to store tiddlers as “Pages”, and to inherit WordPress’s very smooth
I'm just a TW user (not in the computing profession), but if y'all are open to
requests at this early stage here are my 2 cents:
Yay for increased stability (I assume that's what this is about)
1 vote for making this thing a snap or app image or flat pak that an amateur
like me could install
Nice idea. Another option is git instead of a database.
On 28 November 2019 15:59:24 GMT-08:00, Arlen Beiler wrote:
>I have a radical proposal which would take data folders to the next
>level.
>What if instead of the file system adapter we would write a new adapter
>to
>use a database. We could
I have a radical proposal which would take data folders to the next level.
What if instead of the file system adapter we would write a new adapter to
use a database. We could use PouchDB, but I would vote for something much
more widespread like SQLite. We could also write it in a generic way that
13 matches
Mail list logo
