Andrey Meshkov
Andrey Meshkov
Debug it via browser console, make it a valid JS function call: ``` var scriptlet = function() { console.log('test'); } scriptlet('trusted-replace-node-text', 'script', 'ダウンロード', '/(window\.[0-9A-z]+[\S\s]+ele\.outerHTML;\})/', '$1;document.addEventListener("DOMContentLoaded", (async function(){const t="undefined"!=typeof dl_link?Object.values(dl_link):null,e=document.querySelector("a.dl_button[href*=\"?\"]");if(!t||!e)return;const n=e.getAttribute("href");let...
Duplicates #1364, please upvote it if you need it.
Instead of blocking app traffic, we'd better find out what URLs did they use. Is there any info about it?
We'd better check how many people have already upgraded to v2.8, as this rule will be quite problematic for v2.7 users.
This is actually so bad, A LOT of people are still using the old versions. It seems that the only viable solution would be to simply disable the old API...
It's unbelievable how many users are still on v2.7 and older versions.
Serving different filters might be a solution. I don't really understand what prevents users from updating the app. Maybe we're doing something wrong? What if instead of the current simple...
Yeah, I guess so. @Alex-302 could you plz take a look?
Tbh, I'd still prefer blocking domains and not apps, this would help in the case if some package names are missing from that list.
Currently, we're using an "universal" APK build where the app detects in runtime whether this is a TV or a mobile device. Apparently, it does not work correctly for Station...