data
data copied to clipboard
uso-archive
meta-data update
When is the meta-data of the userstyle updated? The style has been updated from us.o. But not the date, or the text ("additional info" in my case).
On every 12 hours? https://github.com/33kk/uso-archive/commit/e6b49114de94e6193ec7fc14f50b760a17fb6eb1 https://github.com/33kk/uso-archive/actions/workflows/auto-update.yml
But delete may works diffrent (need manually open own issue and in "The reason given was" (on userstyles.org) add the number issue to authorization & authentication):
- https://github.com/33kk/uso-archive/search?q=158915 - still visible on page with allow Install.
- https://uso.kkx.one/style/158915
I don't think there is an efficient way to get recently deleted styles from USO, currently deleted styles just stay as is.
Marko @.***> در تاریخ دوشنبه ۲۶ ژوئیهٔ ۲۰۲۱ ساعت ۵:۴۱ نوشت:
I don't think there is an efficient way to get recently deleted styles from USO, currently deleted styles just stay as is.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/33kk/uso-archive/issues/34#issuecomment-886299708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT56FG4TQ6P5HIBYRSTVAI3TZSY2TANCNFSM47LLRVNQ .
Unfortunately, we can't see what you wrote irajlalamoot (github ate characters or you sent empty mail/wrote words in wrong place so github mechanism no copied sentence to www page property).
If you can, copy the text from the old email and paste it directly on Github.
@33kk What I meant in this issue is that the meta-data is not updated when the source is updated. The text is of the old version and the "View JSON" button displays the old version. While "Install" gives the lastest version. Even "Updated at" is wrong.
Check https://uso.kkx.one/style/211993
lastest is: 0.5.0
in JSON: 0.4.99
Bug on CDN level?
https://github.com/33kk/uso-archive/blob/dbf6bb5421024bfb14e4bb7507d46468303fffc1/data/uso-styles/211993.json#L32
Oh, there is even the latest version in there.
The bug in that version is because I've used a trick with definable options to activate part of the code. The variable name is placed in the @-moz-document regexp . I've tested it with stylish, stylus (which has a bug now with uso options), and an older version of stylus (without the bug).
I have even tested with stylus by modifing the meta-header and adding @preprocessor uso and options declaration like USOa does. (not with that particular style, but a shorter one)
edit I'm only assuming that the CDN bug is related.
Looks like a CDN caching issue 🤔 Both JSON and CSS are the same version for me
By the way, @33kk , I've played a bit with the @preprocessor uso (local style to try to mimick what USOa does when it import a style with options from USO), is there a way to check the default value in a dropdown? Or is it always the first option?
Both JSON and CSS are the same version for me
Yes, everything got updated for me too.
Another question. Does USOa knows when the description changes on USO, or is an update of the stylesheet necessary ?
Another question. Does USOa knows when the description changes on USO, or is an update of the stylesheet necessary ?
It scrapes recently updated page, any style update causes it to appear there
By the way, @33kk , I've played a bit with the
@preprocessor uso(local style to try to mimick what USOa does when it import a style with options from USO), is there a way to check the default value in a dropdown? Or is it always the first option?Both JSON and CSS are the same version for me
Yes, everything got updated for me too.
iirc stylus allows setting default values with * at the end of label, and iirc I made default entries appear first for xstyle compatibility (probably could remove it, that thing is really broken anyway)
It scrapes recently updated page, any style update causes it to appear there
Good to know.
iirc stylus allows setting default values with * at the end of label, and iirc I made default entries appear first for xstyle compatibility (probably could remove it, that thing is really broken anyway)
Just tried the * trick with a test style. It doesn't seem to change anything. Moving the default value first is definitely better.
I dunno if this is the same issue (maybe not since it seems the inverse of something described above), but I made a few test edits--info/changelog changes, license, and in one case adding a comment to the code, but not changing functionality--to one of my userstyles (one a few days ago that didn't change its update date, and one late last night that did) specifically to see how this mirror would handle them, and it appears that the page for the style and the install page did not update, though the JSON did. 🤔
Ah! I feel so silly! I thought the thing I'd been doing was clearing enough cache that it would be showing me nice fresh info but apparently not--I'd neglected trying to look for it in another browser or even a private window for some reason and just thought to do so around seeing this and it's showing me newer info there, so I guess this is a non-problem in my case. *sheepishly withdraws that note*
That is older...
This is my repo though, and the content of the issue is the same, the second one though happens to have a better title, which is why i kept it. I'm unsure why this matters in the first place