This is added in 2.0.3.
shazbot
joined 2 years ago
There is no server load, I am talking about the equivalent to cookies: sessionStorage and localStorage. Albeit small, the performance drag comes from parsing a growing list of IDs, and the fact that 5MB is shared across the entire browser for all scripts and applications, and the aforementioned security consideration. When I said "we have to store," I was talking about the localStorage method. Also, KES should never callback to a remote server to store settings, we are against that.
I've been thinking about this. I think I would say: hide posts for the duration of the browser session and localized only to that tab, yes, eminently doable, and they won't return while you browse around until you exit the browser. But for permanent storage, we have to store the ID of each post in perpetuity, and this will necessarily grow to epic proportions over time as you hide stuff, but there is a small upper bound (5MB) on how much can be retained persistently across all apps. In addition, you'd be carrying around the ID of every post you've blocked before and it would be visible to other tabs in your browser, which is a small security concern insofar as it vaguely indicates your preferences. So there is a security and performance negative to this. I don't think we should retain any such information, only generic information such as on/off states, etc. Hope this is clear.
Ah, okay, so it works on mobile Safari, but with the caveat that you can't save it as a pseudo app to your home screen. This seems pretty good overall, we can mention that in the documentation. A few other users reported trying to create PWAs with some special apps (not Userscripts) and reported the same outcome. It's because they essentially blacklist extra dependencies.
Overall, I'd say this is a positive indication that it's working, yes? This is the outcome we were hoping for, as Userscripts closely resembles GreaseMonkey's API, so once we added support for the latter, it was all but guaranteed to work on the former.
Yes, I think there are additional sandboxing/security considerations when using a PWA, which may block pulling in additional script dependencies needed. If I understood you correctly, it works on Safari on a desktop, but when you add it as a mobile home screen app, it doesn't? Can you still use it on mobile some other way?
Permanent hide?
OK, just wanted to isolate the scope of the problem. Seems to still be isolated to iOS.
Make sure you are on 2.0.2 at the minimum. A small hotfix was needed.
Consider it done, boss. Will be added in next update/hotfix.
Alright, if you have additional debug output from the dev tools console, that would be helpful. Unfortunately, we don't have easy access to an iOS test bench at the moment, but I'll try to read through the Userscripts documentation to see why it might behave differently.
The short answer is that the auto-update functionality is kind of half-baked in all of the script managers, usually they default to 24 hours, it doesn't always work, and apparently GM discourages it. I'd suggest using the update button provided inside KES (shown in the event that your version mismatches), which opens a link to the script and your extension manager will then prompt you to install it or override the current version you have.
Alright, looked into it some more and I think we can do this using GreaseMonkey's internal storage, which is private to an atomic script and not accessible elsewhere. I'll work up a prototype. It will probably work best with infinite scrolling on the thread index enabled.