Arg, I mean the plug-in is opt-in and opt-out for all tiddlers defined by
the filter. By default, the plug-in itself can be set to either on or off
by the author for all viewers. Maybe the setting to turn the plug-in
on/off could be one of the tiddlers that can get saved to local storage to
The glaring difference is the plug-in is opt-in, by default, to local
storage of everything intended for local storage by the TiddlyWiki author.
Opt-out is manual and is opt-out of everything intended for local storage.
What I am doing is opt-out by default, and opt-in local storage for only
Arg. Now I have "Cloudy with a chance of meatballs" stuck in my head...
On Friday, March 11, 2022 at 1:17:27 PM UTC-4 Charlie Veniot wrote:
> Well, more so a wiggling target than moving. Or gently swaying ...
>
> On Friday, March 11, 2022 at 1:14:52 PM UTC-4 Charlie Veniot wrote:
>
>> Then
Well, more so a wiggling target than moving. Or gently swaying ...
On Friday, March 11, 2022 at 1:14:52 PM UTC-4 Charlie Veniot wrote:
> Then that will be the glaring difference between my work and the plugin.
>
> Well, the plugin is really for the benefit of a TiddlyWiki's owner. What
> I
Hi Charlie,
> Then that will be the glaring difference between my work and the plugin.
I still don’t understand what you meant. What is the glaring difference?
> Well, the plugin is really for the benefit of a TiddlyWiki's owner. What I
> am doing is for the benefit of the TiddlyWiki
Then that will be the glaring difference between my work and the plugin.
Well, the plugin is really for the benefit of a TiddlyWiki's owner. What
I am doing is for the benefit of the TiddlyWiki viewers.
Something like that. It is a moving target ...
On Friday, March 11, 2022 at 1:09:03 PM
> Oh, I mean somebody else's TiddlyWiki putting things in my local storage
> without my "yes, I agree" (i.e. "yes, I opt-in") consent.
That's hard to prevent in general: HTML pages don't need user permission to
write to local storage.
In the case of the browser-storage plugin, steps are
Oh, I mean somebody else's TiddlyWiki putting things in my local storage
without my "yes, I agree" (i.e. "yes, I opt-in") consent.
On Friday, March 11, 2022 at 1:02:55 PM UTC-4 jeremy...@gmail.com wrote:
> Hi Charlie
>
> Quite awesome, except for one thing: it is opt-in by default, right?
>
>
Hi Charlie
> Quite awesome, except for one thing: it is opt-in by default, right?
I'm not sure what you mean. If you referring to the fact that on the demo that
I linked the browser-storage plugin is activated by default, it is possible to
leave it set disabled, and expose a checkbox or
Quite awesome, except for one thing: it is opt-in by default, right?
Within the boundaries of the filter, it is an all-in / all-out option, by
default all-in for the viewer of that TiddlyWiki ?
I cannot stand "opt-in" by default, leaving the user with the manual effort
of opting out,
Out of the box, the browser-storage plugin saves $:/state/ tiddlers (apart from
$:/state/temp/ tiddlers) and thus most of the UI state. There’s no
configuration beyond installing the plugin and restarting.
To make it save all configuration such as which toolbar buttons are hidden
would require
Charlie's post on browser storage
(https://groups.google.com/g/tiddlywiki/c/l-1YLy0xpJo/m/mreI115qAgAJ) prompted
me to post a reminder about the official browser-storage plugin. Charlie is
exploring many interesting use cases for browser storage, but that particular
post covers the same
12 matches
Mail list logo
