white_viel

3 ms·

1.
by white_viel 7mo ago
but i am impressed that gpt was able to decipher the worke.dev url on its own and access it.
2.
by white_viel 7mo ago
>> interesting. workers.dev domains can be a liability sometimes -- if you've mapped the worker to a real zone, then you probably don't want the workers.dev zone anymore. maybe that is a good idea, prompt a user to disable t
3.
by white_viel 7mo ago
Finally managed to kill the traffic: 1. renamed the worker - the bot was bypassing the route on the domain and using the worker.dev domain 2. add WAF rules to block gptbot in user agent 3. serve zip bomb on request from GPT. interesting tha
4.
by white_viel 8mo ago
update: the bot is back now with a vengeance, sending request at about 1 request per second. ignoring robots.txt and the status code 403
5.
by white_viel 8mo ago
serving a zip bomb and after 10 minutes, the traffic from the gpt bot disappeared..
6.
by white_viel 8mo ago
will be serving a zip bomb to the bot to see if they stay away from my proxy
7.
GPT Bot Ignoring Robots.txt on my cloudflare worker
3 points by white_viel 8mo ago|9 comments
8.
by white_viel 1y ago
Jellyfin - an almost direct replacement of plex Emby - IMOO the best replacement if Plex is not viable
9.
Plex Update: Notice of a potential security incident
34 points by white_viel 1y ago|12 comments
10.
by white_viel 10y ago
what about the bus stop broadcasting a signal with the id, name etc? the system is activated by the proximity..so you can have smthing like approaching station A, leaving station A. it is scalable because the bus-stop transmitters are added