The filter used by ABP and both uBlocks is EasyList, usually they are the ones to blame for these kind of malfunctions.
Not exactly broken, but I don't see a topic for reporting malware links
Basically, there's a trio of malware links that look like they are being inserted into rule34 itself, bypassing NoScript and Ublock.
I have picture evidence if anyone wants it, but for now, here's what pops up with Inspect Element. Tried copying Inner HTML, nothing happened, tried capturing Image Data-URL, got an absolutely massive wall of text. Only copying Outer HTML got me something I could reasonably paste here (I tried breaking it up to prevent any accidental leaks:
<a target="_blank" href=" a rule34 link followed by a massive c.html? link"
<img s r c="ht tps://rul e34.xxx/x/41682-17126170741751500_1_xacd.gif">
</A>
The links pop up once you type something in the search bar and start browsing.
I have picture evidence if anyone wants it, but for now, here's what pops up with Inspect Element. Tried copying Inner HTML, nothing happened, tried capturing Image Data-URL, got an absolutely massive wall of text. Only copying Outer HTML got me something I could reasonably paste here (I tried breaking it up to prevent any accidental leaks:
<a target="_blank" href=" a rule34 link followed by a massive c.html? link"
<img s r c="ht tps://rul e34.xxx/x/41682-17126170741751500_1_xacd.gif">
</A>
The links pop up once you type something in the search bar and start browsing.
RedRover said:
. . .
. . .
add this filter rule in uBlock:
||rule34.xxx/x/*
bipface said:
add this filter rule in uBlock:
||rule34.xxx/x/*
RedRover said:
. . .
. . .
add this filter rule in uBlock:
||rule34.xxx/x/*
This works yeah, do this if you really hate seeing the footer ads.
Also updated our capcha to rechapcha as sweetchapha was pushing malware trough their javascript... pretty sad. Let me know if anything is broken with it.
bipface said:
add this filter rule in uBlock:
||rule34.xxx/x/*
add this filter rule in uBlock:
||rule34.xxx/x/*
Excellent. Thanks.
Plus, I have now learned that UBlock has a really convenient element picker, so double thanks :D
slayerduck said:
This works yeah, do this if you really hate seeing the footer ads.
Also updated our capcha to rechapcha as sweetchapha was pushing malware trough their javascript... pretty sad. Let me know if anything is broken with it.
This works yeah, do this if you really hate seeing the footer ads.
Also updated our capcha to rechapcha as sweetchapha was pushing malware trough their javascript... pretty sad. Let me know if anything is broken with it.
Will do.
Are translations not working at the moment? I hover over it and it doesn't give me the translation
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
PissyBitch said:
Are translations not working at the moment? I hover over it and it doesn't give me the translation
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
Are translations not working at the moment? I hover over it and it doesn't give me the translation
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
try disabling your ad blocker, if you have one installed
bipface said:
try disabling your ad blocker, if you have on installed
PissyBitch said:
Are translations not working at the moment? I hover over it and it doesn't give me the translation
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
Are translations not working at the moment? I hover over it and it doesn't give me the translation
rule34.xxx/index.php?page=post&s=view&id=2287820
This one for example
try disabling your ad blocker, if you have on installed
That worked thank you <3
I can't access this thread:
rule34.xxx/index.php?page=forum&s=view&id=5555
it just redirects be back to the forum index
it was working fine yesterday
rule34.xxx/index.php?page=forum&s=view&id=5555
it just redirects be back to the forum index
it was working fine yesterday
bipface said:
I can't access this thread:
rule34.xxx/index.php?page=forum&s=view&id=5555
it just redirects be back to the forum index
it was working fine yesterday
I can't access this thread:
rule34.xxx/index.php?page=forum&s=view&id=5555
it just redirects be back to the forum index
it was working fine yesterday
Because it's been deleted.
oh; in that case, why was it deleted?
i didn't notice anything out of the ordinary about it
i didn't notice anything out of the ordinary about it
I'd like to know that myself. I didn't do it.
/index.php: charset is declared too late in the document for Firefox's HTML parser ( i.imgur.com/2J2GoL5.png ).
This triggers the blank-messages bug discussed here:
rule34.xxx/index.php?page...id=5564&pid=15#185486
And is probably causing a bunch of extra requests from many browsers.
How to fix:
a) move the <meta http-equiv="content-type" … /> tag earlier in the document
or
b) serve the page with "Content-Type: text/html; charset=UTF-8" in the HTTP headers
This triggers the blank-messages bug discussed here:
rule34.xxx/index.php?page...id=5564&pid=15#185486
And is probably causing a bunch of extra requests from many browsers.
How to fix:
a) move the <meta http-equiv="content-type" … /> tag earlier in the document
or
b) serve the page with "Content-Type: text/html; charset=UTF-8" in the HTTP headers
bipface said:
/index.php: charset is declared too late in the document for Firefox's HTML parser ( i.imgur.com/2J2GoL5.png ).
This triggers the blank-messages bug discussed here:
rule34.xxx/index.php?page...id=5564&pid=15#185486
And is probably causing a bunch of extra requests from many browsers.
How to fix:
a) move the <meta http-equiv="content-type" … /> tag earlier in the document
or
b) serve the page with "Content-Type: text/html; charset=UTF-8" in the HTTP headers
/index.php: charset is declared too late in the document for Firefox's HTML parser ( i.imgur.com/2J2GoL5.png ).
This triggers the blank-messages bug discussed here:
rule34.xxx/index.php?page...id=5564&pid=15#185486
And is probably causing a bunch of extra requests from many browsers.
How to fix:
a) move the <meta http-equiv="content-type" … /> tag earlier in the document
or
b) serve the page with "Content-Type: text/html; charset=UTF-8" in the HTTP headers
Dang bruh, i fixed it
slayerduck said:
Dang bruh, i fixed it
Dang bruh, i fixed it
hooray! thanks