Well, there never was any law that required robots.txt to be honored. Big players like Google do, but I am not aware of any consequences if they wouldnt (of course UNTIL it is then regulated).
I don't think there's anything special; I very often get new-reddit results with no 'site:' qualifier. I can't think of a specific query offhand, but it happens multiple times daily for me.
I mean for async assigns specifically. I did something like this in the past and had some troubles with render_click returning the html before the async update completes.
Engineer working on Deno KV here. Building on FDB is mostly a pleasant experience since it solves the hard part of the problem for us (concurrency control and persisting mutations).
We sometimes run into its limitations - the way we are using FDB is a bit beyond what it was originally designed for. But when it works, it works great.
I'd suggest rethinking "5 automated flows with unlimited emails" on the free plan.
Sending a few emails is very cheap, but sending a lot of email is not.
Inevitably somebody will sign up for the free plan and send far more email than you expect. It will either end up costing you money, impacting the experience for your other users, or both.
Where are you connecting from, out of curiosity? 200ms is poor!
Fly apps get anycast IPs, so it's basically bgp getting you to our "nearest" edge proxy, then we connect you to the closest vm from there.
https://debug.fly.dev will show you which region you hit first (the fly-region request header).
--edit--
I snooped on your HN profile and found Australia. We don't have an instance of this app up in AU, but we could. You're likely connecting to us in Sydney, and LAX is most likely the fastest over our backhaul from there.
I'm not sure if this is in the realms of what Fly could do easily but I love the idea that for this kind of Liveview app you could monitor where your users actually are dynamically set up a close node to reduce latency.
Bonus points if you could bring the node down again when usage drops.
From Finland: Through LTE I get served via 'fra' with ~60ms (as one might expect). However if I switch to Wifi I get 'hkg' with ~260ms?? Not exactly next-door :)
Would you mind emailing me with your IP address and a screenshot of what you see at https://debug.fly.io when you're on wifi? Finland to hkg is not what we want to be doing.
(not op) Is that link wrong? I'm getting ERR_NAME_NOT_RESOLVED. I tried with Vodafone mobile (UK), Openreach Wifi (UK), and a few other countries over a VPN (Canada, Australia, ...) in Firefox and Chrome.
Those spikes are hilarious, they're probably from a liveview DoS. People are fond of using the debug console to "click" hundreds of times per second and there's no rate limiting in the app.
