I have the greatest respect for your work, Mario, and am eternally greatful for your addon. If my posts sounded a little testy, I apologize, but I am quite angry, actually. Not at you personally of course, nor at Jeremy or anyone, but at a situation where I sit here replicating hours of lost work in dozens of tiddlers and thinking about the depressing fact that, in 2018 for crying out loud, the one piece of software that enriched my personal and professional life more than any other tool and which I think is the greatest thing since sliced bread, fails to save my work when I need it saved. Yesterday, I thought -- as I regularly do ever since the FF update last year -- about ditching TW and reverting to the half dozen or so applications which I used to use for stuff that I now do in TW. Because they save my work without, you know, an addon with all the crappy dependencies and unknowns and (your phrasing is ironic really) “edge cases”. Sure, that would feel as bad as reverting to ink and paper, or to chiseling letters on marble slabs, but hey -- my data is safer than in TW. I don’t know what you guys use TW for, but I do professional work with it, precious work not only in terms of invested time, I *think* with it, I produce scholarship. And TW is an integral part of why I love my job, because it elevates me in my professionalism. But that also means I *depend* on TW, I *need* it working. This is why it totally horrifies me when the one single thing the only function of which it is to keep my work safe -- fails. And it totally deflates my faith in TW that there even is a situation where a third party addon has to fulfil that function (yes, I know, this situation has been around since TW2 -- and if I could go back in time knowing how fundamentally broken TW’s dependency on a browser is when it needs a hack to be able to save it, I’d delete the day I stumbled upon TW and had my mind blown just to save myself the heartache of ditching it many years later). You know, I used to recommend TW to colleagues and friends, I created a customized TW2 empty.html to make it easier for them -- not only don’t I do that anymore, I cringe with awkwardness at my own enthusiasm. They all stopped using it, “Zyb, this thing you gave me doesn’t work any more, don’t know what happened.” and I stopped trying to fix it for them, I shrug and say “Yeah, I’m sorry.”, because TW’s problem seems to be unfixable.
Phew. Sorry for the rant. I guess I needed that if none of you guys do. Yes, I’m bitter. Please, also, if you’re tempted: refrain from giving me ‘good advice’. I did look into it: TW Standalone is unusable and don’t even get me started on that server thingy. Zyb Am Freitag, 9. März 2018 10:05:19 UTC+1 schrieb PMario: > > On Thursday, March 8, 2018 at 6:42:24 PM UTC+1, Zyb wrote: >> >> Are you saying that the addon was updated not on browser startup but at >> an arbitrary point in between? >> > > I think, it's a browser background task. ... but there is no description > how updates happen. .. At least I haven't found one ... > > >> How could I have even noticed that? >> > > I will have a look, if there is a possibility to notify users. > > >> Why would it render the wikis unsavable until restart (which means losing >> the work already done)? >> > > As I wrote in the other post, it may be needed to reload the tab after a > plugin update. .. I'll have a look, if a "running tab" can detect plugin > updates. ATM I don't know, if there is any signal from the browser and if > we can *reliably detect it*. > > >> That’s not something that should happen, ever, I think. >> > > You are right. ... But there are always edge cases, a developer didn't > think about. .. > > Testing is hard. As I wrote, to test updates you have to make updates. > > I can test the plugin with windows 10 and an ubuntu system. > I don't have the possibility to test with macOS. ... So I'm 100% dependent > on user feedback. .. If no feedback happens, .. nothing happens. > > Mozilla is switching off the "beta channel > <https://blog.mozilla.org/addons/2018/02/28/discontinuing-support-for-beta-versions/>". > > That's what I had to find out, as I started to have a look, how I can use > it. > > As I wrote in my first post, the plugin should have not been listed and it > should have not been auto-updated. > > At the moment, I try to find out, how to create a signed beta-version, > that can be published at github, without the mozilla store auto-update > thing. > The problem then is. ... What happens if users switch from beta to stable > ... That's a new mechanism, where things can go wrong. ... AND we have to > test it. > > -mario > > -- 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 post to this group, send email to tiddlywiki@googlegroups.com. 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/c83fadfe-d39b-4c64-8121-cc9b81273a56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
