Re:Wikimedia narrows down the app sendin 90M requests to a p...
by walrus01 on Thursday February 11, 2021 @12:50PM
(#26104755)
the hard part about this, if it were not wikimedia but some individual person's server, is that the traditional method of using something like an apache rewrite rule to replace the jpg/png with goatse wouldn't work, because the image isn't even being displayed.
[ Parent
| on HN ]
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by msla on Thursday February 11, 2021 @12:53PM
(#26104791)
Even worse: You might be seen as an easy way to Goatse people. Just give the yahoos the URL of an image you're rewriting to be the infamous gape. The traffic would only grow once you came to be known for Goatse as a Service.
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by stickfigure on Thursday February 11, 2021 @01:09PM
(#26105031)
> Goatse as a Service (YC S21)
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by walrus01 on Thursday February 11, 2021 @01:10PM
(#26105050)
Implemented via several dozen geographically distributed 1U servers with 10 or 100GbE network interfaces, and anycast DNS. You could do it pretty much the same as anycast DNS recursive resolvers, but all sharing the same hostname, IP and TLS keys.
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by densone on Thursday February 11, 2021 @02:02PM
(#26105688)
We need goatse anycast address
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by walrus01 on Thursday February 11, 2021 @03:56PM
(#26107036)
You can totally get your own asn, acquire a /24 of ipv4 space, and announce as anycast your netblock containing the goatse httpd from multiple geographic locations.
Re:Wikimedia narrows down the app sendin 90M requests to a p...
by mywittyname on Thursday February 11, 2021 @02:00PM
(#26105674)
Help us solve the problem of hotlinking.