Mark S., 

Right. I think the oomph of that post is that we kinda get into trust 
issues on cloud dependencies not in a TW fold. I think that may get worse 
over time.

The problem is becoming the "supplicant daughter" who has to accept poor 
information, rather than a robust proven protected TW nest.

The issue of how external storing dependencies work matters I think.

Thoughts
TT


On Friday, 6 March 2020 17:06:02 UTC+1, Mark S. wrote:
>
> As an aside, how are people using Google drive now?
>
> The link for google drive on TiddlyWiki.com leads to a 404 page.
>
> The link on tiddly toolmap leads to a chrome store. The problem there is 
> that the reference site 
> (http://lordratte.info/tiddlydrive/) leads to two warnings from ublock 
> including one for badware. When 
> I push on through, I get popup advising me that by agreeing to "accept" I 
> will have the chance to change to a "safer"
> search on Firefox. I don't like this. This seems dowdy, scam-y  and 
> possibly dangerous. 
>
> So, what do we know about the provider of the google drive extension? Or 
> is there some other undocumented approach people are using?
>
> On Friday, March 6, 2020 at 6:21:37 AM UTC-8, Mario Public wrote:
>>
>> Dear All
>>
>> I wish to to have my TiddlyWiki online for easy access from every 
>> device/location.
>> I am the only user of the TiddlyWiki.
>> I am using the google drive extension and it works but I would prefer not 
>> to host personal files there. Nothing particularly sensible, just personal.
>> What is the easiest and most private way?
>> I have my own domain and I tried to host the wiki there by uploading it 
>> and using store.php but I got errors and it did not worked.
>> Is dropbox a better option?
>> Thanks
>> Mario
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/004259ae-2d84-4387-9bed-652e80460345%40googlegroups.com.

Reply via email to