/top/
/new/
/best/
/ask/
/show/
/job/
^
slacker news
login
about
←back to thread
Bypassing Google's big anti-adblock update
(0x44.xyz)
1034 points
deryilz
| 1 comments |
12 Jul 25 19:06 UTC
|
HN request time: 0.206s
|
source
Show context
SuperShibe
◴[
12 Jul 25 20:20 UTC
]
No.
44544826
[source]
▶
>>44544266 (OP)
#
[flagged]
replies(6):
>>44544855
#
>>44545234
#
>>44546507
#
>>44546656
#
>>44546983
#
>>44547982
#
4gotunameagain
◴[
12 Jul 25 20:23 UTC
]
No.
44544855
[source]
▶
>>44544826
#
Well, in his defense it would have been patched immediately after the first adblocker used it, and he would have gotten nothing at all out of it.
Oh wait he got nothing at all anyway ;)
replies(2):
>>44544888
#
>>44545091
#
m4rtink
◴[
12 Jul 25 20:56 UTC
]
No.
44545091
[source]
▶
>>44544855
#
Would be quite different if they patched it and broke important extensions, possibly facing serieous outcry and bad publicity.
replies(3):
>>44545271
#
>>44545323
#
>>44545582
#
deryilz
◴[
12 Jul 25 22:03 UTC
]
No.
44545582
[source]
▶
>>44545091
#
I agree that would change things but I can't picture an open-source extension with millions of users pivoting to rely on something that's clearly a bug.
replies(1):
>>44547361
#
1.
userbinator
◴[
13 Jul 25 03:57 UTC
]
No.
44547361
[source]
▶
>>44545582
#
At that point it's a feature, not a bug.
Having millions of users on your side is great ammunition.
ID:
GO
↑