It was only yesterday that I clicked on a Translate button to read a Japanese post. Today I see a Chinese post with English translation right below. Beautiful stuff.
Any conversation
I have something that usually builds, tests, and deploys under five minutes. It has been over two hours and forty eight minutes and it is still going on today... 🫣
It’s using the
/firehose endpoint. It’s an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since it’s heavily rate-limited — up to 3 conns under the same network, but I can’t control how clients decide to use it so.. ¯\_(ツ)_/¯I hate crawlers that don’t advertise they’re crawlers. ’n badly written. They don’t respect the canonical URLs so they keep getting themselves into a loop instead of actually crawling the site properly. They make the logs really hard to read. Can’t block them they’re distributed.
I am curious what an actual solution to this problem could be. Everything I've read about it feels like a bandaid — from robots.txt to cloudflare turnstile — there has to be a better way!
It would require permaban on IPs which would require permalogging of IPs in order to track them, and we are currently obfuscating them before hitting the DB with daily rotating salt so an anonymous user can’t be tracked. So we’d have to give up privacy/security :/
How do you define slop in relation to ? For me, it is how quickly you get to an unmaintainable state- the acceleration into something that becomes difficult to work. I talk more about it here: hellodavid.dev/blog/slop
Sharing a great read today:
Some of the takes are on the extreme end, but like most IT decisions, you can dial the pain to exactly what you want.
^C
textlog runs on a 2.5€/mo vps 1 core/2gb ram, using just one instance of Bun with its embedded SQLite. Works perfect and I run a few other apps as well on that machine.