I neglected to stress that I intended my my Joplin comments to be "on thread" since it can auto-sync as frequently as every 5 minutes. That would limit any loss of date to a relatively short time frame.
On Friday, January 28, 2022 at 11:58:48 AM UTC-5 Hans Wobbe wrote: > I have used Joplin enough that I am comfortable with its Offline & Synch > capabilities. Some points that appeal to me: > > 1. Its Open Source and extensively used. > 2. It has reasonable support for Tags and Folders and flexible SORTing. > 3. The Documentation is more than adequate to get you well started. > 4. You can Share ( with trusted Pals ) > 5. On Apple IOs its speech recognition is excellent. > 1. better than on Android, > 2. good enough that I can WalkAndTalk > <#m_540315287181718850_WalkAndTalk> > 6. It has Mermaid Markup support and a webClipper capability > > ItsNoTiddlyWiki <#m_540315287181718850_ItsNoTiddlyWiki>, but IsA > <#m_540315287181718850_IsA> good adjunct to TW @ https://joplinapp.org/ > > On Tuesday, January 25, 2022 at 11:33:10 AM UTC-5 [email protected] wrote: > >> 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: >> >>> [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ca88b9d8-6b11-4f4f-a4af-9cb96edcc576n%40googlegroups.com.
