Redlib (redlib.nadeko.net) has broken layout and text

[jarsealer]

Any instance running Redlib (a reddit frontend) like https://redlib.nadeko.net or https://rl.bloat.cat doesn't render correctly with Pale Moon (and Basilisk), and has text and images all over the place.

Code: Select all

Invalid URI. Load of media resource  failed.

[Moonchild]

Looks like it wants CSS pseudo :has()
Issue #2473 (UXP)

[Mæstro]

I suffered this same problem a year ago and was offered a workaround.

[jarsealer]

I suffered this same problem a year ago and was offered a workaround.

The HTTP response filter actually works, site is readable but becomes very slow when scrolling posts with pictures. Good workaround tho.

[Mæstro]

Since a year ago, I have lost interest in accessing Reddit at all, through proxies or otherwise, but when I used Libreddit, I never suffered any such lag. My best guess is some scripting weirdness which I never noticed, for I block scripts by default. µBlock Origin can manage this, much like the more complex ηMatrix or malign NoScript.

[jarsealer]

I'd say the best way to access (view) Reddit without JS would be https://old.reddit.com and allowing the essential scripts in eMatrix, as it probably isn't as JS heavy as the newer Reddit UI. Though I'd prefer to use front-ends if available. Also, eMatrix is superior in managing scripts (1st-party and 3rd-party, which specific ones from which domains, etc,.) and other types of requests by the browser than uBlock Origin. Might take time to learn the way to configure it, but once you get the hang of it, you'll find it to be really useful.

[Mæstro]

Teddit was my preferred Reddit frontend until the API changes two years ago broke it. I never understood why Libreddit survived across several instances while Teddit perished, just like how most, but not all, Nitter instances died about the same time. I have tried ηMatrix, but I find it too much headache. µBlock was already there and ready to assume NoScript’s various posts, including XSS and frame filtering, so I draw on my own experience in suggesting it for anybody seeking to replace it. µBlock can cope with 1^st/3^rd-party distinctions, inline scripting, CSS/SVG blocking, indeed anything ηMatrix filters but cookies, for which Cookie Masters serves.

Off-topic:
The only ways I should like to change µBlock are cosmetic. (I was reluctant to part with NoScript for the longest time on strictly aesthetic grounds.) Traditional XUL menus, like RequestPolicy, NoScript and Adblock Latitude, for the dashboard and a NoScript-style tooltip menu and interface for the rest would be lovely. If I had my own µBlock reskin like this, I could think of no better name than Ægis.

[moonbat]

Also, eMatrix is superior in managing scripts (1st-party and 3rd-party, which specific ones from which domains, etc,.) and other types of requests by the browser than uBlock Origin.

Both serve different purposes; eMatrix is an overall content blocker that works as a whitelist and doesn't have resolution beyond the domain of the resource in question. uBlock Origin gives more fine-grained control in cases where both ad and main content are served from the same domain or you want to get rid of non ad nuisances like cookie notices and newsletter subscription nags. I've been using both.

µBlock can cope with 1st/3rd-party distinctions, inline scripting, CSS/SVG blocking, indeed anything ηMatrix filters but cookies, for which Cookie Masters serves.

There's a difference - ηMatrix prevents previously set cookies from being read on a different domain. So you might have signed into Google and kept its cookies to avoid repeat sign ins, but you wouldn't want a third party Google script reading a Google cookie on some other site you're surfing. No other extension offers this, and Cookie Masters serves as a complement to ηMatrix.

[jarsealer]

I find the built-in cookie manager in PM to be sufficient for managing cookies. Never understood why there's extensions for that, most of their capability is covered by the browser. I'm pretty sure it's similar for Firefox too with some minor differences.

[Mæstro]

Cookie Masters’ interface is almost identical to SeaMonkey’s cookie manager. This is common Mozilla heritage. I could achieve the same results without extensions by opening about:permissions over and over, but I need to manage cookie permissions site by site often enough that it is far easier to go about it this way. Meanwhile, ηMatrix treats cookies uniquely, as Moonbat described.