Yeah, I almost wrote "never for longterm/safe storage", but I like to leave 
myself some wiggle room in case there are any kinds of improvements I'm not 
aware of.  Not something I've ever had time to keep up with.

Well, security-wise, I'm a "no way no how" for certain bits/kinds of data.  
Keeping an eye out for anything that could change my mind, but I'm crusty 
curmudgeon about it.

All kinds of useful articles on the web for reading.  Loads of hits with a 
"browser 
local storage use cases 
<https://www.google.com/search?q=browser+local+storage+use+cases&rlz=1CABRFU_enCA980&sxsrf=AOaemvLDoYZ7qQqkd3Llne-vdQky8Hl_Wg:1643126992641&ei=0CDwYae7JtaYptQPjYCO4A4&start=0&sa=N&ved=2ahUKEwin492Fpc31AhVWjIkEHQ2AA-w4ChDy0wN6BAgBEDc&biw=1745&bih=830&dpr=1.1>"
 
search.

I'm interested in the standard uses cases and how they could be used with 
TiddlyWiki, but way more interested in the not-so-much-thought-of 
possibilities.

In the realm of standard use cases:

   - a public TiddlyWiki hosted on some site, and using browser local 
   storage to save a user's preferences for using that TiddlyWiki (themes 
   etc.), searches, default tiddlers on startup, yadda yadda
      - same kind of thing with nodejs TiddlyWiki instances on some server
   
On the unorthodox side, not sure yet.  Definitely the thought of a 
communication mechanism for TiddlyWiki instances in the same domain.

Hmmm, communication mechanism between a TiddlyWiki instance and something 
else in the same domain.  A way for a suite of favourite tools to interface 
with each other.

Yup, I may look like the hamster is dead, but the wheels are spinning ...

On Tuesday, January 25, 2022 at 8:58:01 AM UTC-4 TiddlyTweeter wrote:

> cj.v...@gmail.com wrote: Not sure I'd trust this for longterm/safe 
> storage of anything, but I am intrigued by the possibilities.  
>
> Quick comment on how I have used it. I think it is robust enough for, for 
> instance, garnering responses immediately. But I would not trust it between 
> sessions. It is also browser specific. So, yes, additive utility, for 
> clearly defined scenarios. But, no, for a persistent system.
>
> Just a comment
> TT
>

-- 
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/85aeb0cc-91fd-4826-ac0c-aca3f4fbb3a3n%40googlegroups.com.

Reply via email to