this post was submitted on 01 Aug 2025
769 points (96.4% liked)

Programmer Humor

25425 readers
1034 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
769
We don't talk about IPv5 (infosec.pub)
submitted 1 day ago by qaz@lemmy.world to c/programmer_humor@programming.dev
140 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] needanke@feddit.org 4 points 13 hours ago (1 children)

What is stoping Google from just blocking your entire IP-Block?

[โ€“] domi@lemmy.secnd.me 4 points 9 hours ago

Mostly, I'm not big enough to trigger anything there.

Also, since ISPs usually only get a single humongous IPv6 block, it's actually pretty hard to know what is okay to block. Somebody might be on a /48, /56 or /64 network but they might also just have a single IPv6 address. Since you're blocking quintillions of IP addresses with each /64 net, the risk of hitting innocent IPs is high.

Also also, I'm not sure if Google is actually prepared for such a case. Since all the requests coming from Invidious just seem like legit unauthenticated requests, it's hard to flag them on IPv6 when the IPs are fully randomized.

Still, Google is moving towards requiring a login for everything. So I assume that method won't work for much longer.