Recent submissions

Comment · 8 months ago
but i am impressed that gpt was able to decipher the worke.dev url on its own and access it.
Comment · 8 months ago
Comment · 8 months 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 that GPT was accessing the worker directly to bypass the WAF rule son Cloudflare

Comment · 8 months 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
Comment · 8 months ago
serving a zip bomb and after 10 minutes, the traffic from the gpt bot disappeared..
Comment · 8 months ago
will be serving a zip bomb to the bot to see if they stay away from my proxy
Comment · 1 year ago
Jellyfin - an almost direct replacement of plex Emby - IMOO the best replacement if Plex is not viable
Comment · 10 years 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 , moved, removed as needed.

updating the data can also be done remotely

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton