Hi Tony > On 26 Feb 2019, at 05:01, TonyM <[email protected]> wrote: > > Further feedback > > Perhaps a setting in the local storage plugin, or a seperate session storage > plugin to use session only storage > > Session storage is per-origin-per-window-or-tab and is limited to the > lifetime of the window. Session storage is intended to allow separate > instances of the same web application to run in different windows without > interfering with each other, a use case that's not well supported by cookies
I’m not keen to support session storage because it makes things more complicated without addressing any new use cases. > I am struggling a little with the workflow to configure and deploy Wikis with > Local storage since once activated it starts using local storage. You might find it helpful to set up a filter for which tiddlers are saved to local storage. A useful variant is to set $:/config/BrowserStorage/SaveFilter to [prefix[$:/state/]] and thus to only save state tiddlers. Best wishes Jeremy. > > Regards > Tony > > On Wednesday, February 20, 2019 at 4:49:24 PM UTC+11, TonyM wrote: > Another use case; > > We can request a username be given, and saved in the browser session. That > username will be there on return. > > Local storage permits the saving of new tiddlers such as comments. If we get > the user to provide their user name all their created tiddlers can be > exported easily and such a package can be forwarded as a submission to the > website and imported by or applied by the wiki owner with update access. > > Regards > Tony > > On Wednesday, 20 February 2019 13:22:58 UTC+11, TonyM wrote: > Mark, > > I am experimenting with local storage over here > <http://tiddlywiki.psat.com.au/tiddlywiki5.1.20PreRelease.html?param#>. > Anyone can use this as a platform to test Local storage and play with the > pre-release as at 2019-02-20 so have a look. > > I have no doubt it will have a number of great use cases. > One is simply permitting trivial search and settings the visitor uses to be > saved for your return > In this case it is trivial if the settings are lost on return > Local storage saved Pallets, themes, toolbar settings etc... make the > experience much better. > Remember it only saves the changes from the loaded version so it needs only > the space required to store these changes > Imagine if I had a "Home Loan Calculator", the user details are small in > volume. > The Result of the computation could be printed so the result is captured by > the user, > If the local storage goes (by my calculation very unlikely) they can enter it > again (if you do not promise they will not expect it) > At any time the user can save the wiki in totality - they are in charge of > their own risk aversion. > Issues Encountered > If I export an updated wiki to file, then upload and replace the online copy > with those changes, when I return to the URL it is still showing the local > storage items which are now redundant > I need to find a way to purge these > I Found a Way to purge this > It is all good showing there are unsaved changes, but this would be > unnecessarily confusing to casual users. I have thus hidden this in the > DOcument Info tiddler. > Regards > Tony > > On Sunday, 10 February 2019 06:04:50 UTC+11, Mark S. wrote: > Actually I'm puzzled what the use case might be. If you can't trust your data > in it for long, and if there is no synchronization, then what are the use > cases? Mostly I could see it in an environment where every other save > technique is disallowed and where you don't mind if the data could be > exposed. Perhaps a system where your only connection to the outside world is > via email. Perhaps a mechanism for using TW for collating and processing > information, that then gets copied and pasted elsewhere. What else .... > although your data isn't secure, if you've ever rifled through your FF > profile for information (like I did with NoteSelf), it's definitely obscure. > Obscure may be good enough when all you want is to not leave a trail of files > behind. > > Other ideas? > > -- Mark > > There's another product, Laverna, that uses local and/or indexed storage as > well. They tout that they have an emphasis on privacy, because your data > isn't on the web. > > On Friday, February 8, 2019 at 6:11:17 AM UTC-8, @TiddlyTweeter wrote: > PMario wrote: > Some more info about the storage limits > <https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Browser_storage_limits_and_eviction_criteria>. > If you take your time an read this stuff, you'll see that the behaviour is > completely unpredictable. > > And in my opinion way to fragile for our usecases. ... > > I agree. > > I think there are a limited set of use cases where it could work usefully. > But for longer-term saving of a wiki it is not a good strategy IMO. > > FYI, when NoteSelf first appeared I looked into it and found understanding > browser storage very difficult. NoteSelf is a really great tool, but I'd > never use it without a CouchDB remote database its constantly syncing with. > > My two cents > Josiah > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/af265d40-69fe-461d-8fee-2b358bf4c85b%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/af265d40-69fe-461d-8fee-2b358bf4c85b%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8BF2FF44-8974-488C-854E-508CFE3B9043%40gmail.com. For more options, visit https://groups.google.com/d/optout.
