Yeah, well, you know, that's just like, your opinion, man.
It's a bridge that looks like it's made from stone. It looks slightly different from other bridges. It's not bad. There are probably many eyesores in the surrounding towns that look much worse.
Yes, cookies are not the most healthy thing, but there are better and worse ones. It is not just even about it containing some sugar. Why replace the spices that made a traditional cookie special, with more sugar? What is distinctive about sugar?
There is a good reason for that. Even traditional speculaas (not Lotus or other mass produced speculoos/biscoff) contains less and less speculaas spices the further you move away from Amsterdam. Because the spices arrived there, they were cheapest there. The further away (in this case south) you moved, the more expensive they were. This leads to bakers, especially commercial ones, to use less in their recipes.
> For me, having to maintain and secure it was too much work. A vps may have been easier in some ways, but harder in others.
For security you simply setup Tailscale and only allow private network to access your VPS -> 1h max to setup
Maintenance is running upgrades once a week/month -> 10mn
Depending on how critical your data is, you can rely on the provider's backup policy or setting up something as simple as a cron rsync on an external provider -> 2h to setup
I was also shocked reading OP's post, but after thinking about it a bit I came to the conclusion that they didn't meant "100km daily" but more like "having less than 100km range is not an issue because she never drive that much any day of the year".
Having to recharge the car during a single trip being seen as an issue by OP.
As someone having to fight Meta's bots everyday to keep websites accessible to actual customers, I'm not surprised to read that it can be seen as something positive on the other side of the fence.
The end game will be that either your site is fully open to bots and humans alike, or your site is open to humans only(×) and requires Airport security style identity verification.
My own approach is to put the API key in the MCP server, apply principle of least privilege there, and firewall access to MCP with agents being on same private network with Tailscale.
Not only giving an API key to an agent can leak to the model because of harness issues or too broad reading rights, but also most providers don't give the ability to apply principle of least privilege to an API key.
I don't want to give an agent full R/W access to any of my services/accounts.
They tried to make it look "natural" with the rock tiles but there's absolutely nothing natural about it.
A plain concrete bridge would have been less of an eyesore.
reply