Mario,
I understand the warnings about local storage and someone wishing to have
multi-device, secure date etc... they must take further steps. Lets me
explain why I think it worth making it available but inactive.
But first, GIT savers
I do have a site using a Git based saver, setting it up was not a users
type of task, what If I want to enable saving changes to hundreds of users?
Even in their own sand box?
There is still some room for improvement. At the moment, it's not
> "visually" clear which tiddlers are stored locally in the browser. ... and
> it's not clear, if all local tiddlers are saved to GitHub, if the user
> hit's the save button.
This stands even for the local storage only situation.
Some of my debug sessions showed, that not everything is stored. So I
> needed to do 2 or more saves. ... I couldn't find the problem yet, so more
> research needed.
This sounds like a critical need.
Of importance here is the Local Storage plugin has only being available for
a relatively short time in TWC and I believe application that make use of
it are as yet undeveloped.
- Simple storing of state information and preferences can be very
helpful to user interaction, that can be lost without damage to an
otherwise read only environment.
- Local storage can be used to extend protection for loss in a single
active session, like filling out a survey,
- oops I closed the tab, follow the link again in the same browser
and your prior state will most likely be there
- Without local storage there is no coming back from a tab closure
without a download/server/saver involved
- It is easy to prompt users to export, send save there survey result
before closing the tab.
- I am keen to develop a way to make a json file of changes,
package and allow the user to send an email with this json file
attached
(From a read only wiki)
- Local storage can be helpful when server contact is lost
- I have a Local storage icon underdevelopment to display state, warn
etc... but not complete because the combinations of possibilities are quite
high
- It manages consent and warnings
- If this works well it could be incorporated into the plugin, or
work along side it.
- I am looking at developing a changes only backup process to the local
device (See below)
- Could we get a save changes method to capture changes for each user so
they have their own "copy with Changes"
Changes Only Backup process
Mario with your other backup solutions you may be in a position to help
here. For TiddlyWikis hosted reliably on the internet the ability to make
changes but save only the changes as a difference backup would allow the
restoration of a wiki back to the previous state.
- I wonder if the existing browser backup methods could be reworked to
support this?
- Its an interesting challenge to make this user friendly,
- If local storage was lost, could a read only version detect there were
changes saved on the local device previously?
*In Closing* I do feel strongly that we are yet to scratch the surface of
capabilities of local storage be if the one provided by the plugin *or
other more reliable methods*.
Yes we need to accept the limitations as they stand and find smart ways to
inform and set expectations of its use.
I remain incredulous that even with a user granting the required
permissions, even jumping through hoops to do so, that they can't permit a
given site reliable local storage. This is the security tail waging the
usability dog, personally I speculate this limitation must be overcome.
Perhaps a separate app or executable on all devices that implements
something like Jed's single file saver is our only option, then add a
management tool to sync save and export.
Regards
Tony
--
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/fc2c4ce3-3441-4a2a-a493-405a6f550753%40googlegroups.com.
