maybe that is a good idea, prompt a user to disable the worker.dev domain. however, having the worker.dev domain open for me is more of a backup way to access the worker as the mapped domain is more for a hobby project.
> Interesting. workers.dev domains can be a liability sometimes
what about allowing the specific worker.dev to serve a robots.txt on its own that can be used to disable the AI bots?
i.e https://XXXXXXXXXXX.username.workers.dev/robots.txt should be allowed to be configure on a worker level. not sure how that affects the design of the infra, but it would be a good idea
interesting that GPT was accessing the worker directly to bypass the WAF rule son Cloudflare
TLDR: GPT Bot is systematically accessing my private ubuntu mirror, ignoring the robots.txtToday in the morning I woke up to the following message from Cloudflare about my quota usage on Cloudflare workers>> Your account has reached 75% of its daily requests limit for Cloudflare Workers and/or Pages FunctionsThis is unusual as only have one worker on my Cloudflare account that proxies my...
Dear Plex User, We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure.What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained...
it is scalable because the bus-stop transmitters are added , moved, removed as needed.
updating the data can also be done remotely