1.1.1.2 blocks malware, and archive.today performs DDOS. Where's the false reasoning?
2,878 karma · joined January 30, 2011
my-hn-username-here@monkeyseemonkeydo.lv
I hope you guys eventually find a business idea that is not as antisocial as your current one.
I was thinking about that. Wouldn't you be able to make it so the detonator gets armed by the operator remotely only once in the air and away?
> Blindly translating those centuries of laws into rigid, free enforcement is a terrible idea for everyone.
I understand your point that changing the enforcement changes how the law is "felt" even though on the paper the law has not changed. And I think it makes sense to review and potentially revise the laws when enforcement methods change. But in the specific case of the 55 mph limit, would the consequences really be grave and terrible if the enforcement was enforced by a robot, but the law remained the same?
And doesn't that bother you a little?
If you listen to podcasts, check out this podcast episode: https://www.pushkin.fm/podcasts/cautionary-tales/flying-too-...
It is about Air France 447, but also draws parallels to AI and self-driving cars
Even Hetzner's Robot interface was down.
Edit: https://status.hetzner.com/incident/5e901309-0873-42af-90c5-...
But LLM will figure it out so why not take free speed?
BTW, also if we're getting rid of a web framework and letting the LLM write specialized code for the various CRUD operations, why not also get rid of Postgres/MySQL/Redis and let LLM also write specialized code for reading, writing, and querying the various business objects?
OK, in that case, I think marketing it as "Zero-knowledge" and "end-to-end encryption" is misleading. Oops Backup sees the data, and the client has to trust Oops Backup to handle the data with care.
An example of actual end-to-end encryption would be a cron job doing "pg_dump ... | gpg --encrypt ... | s3cmd put ..." (with some more arguments of course). The database backup is compressed and encrypted on the database host itself, and sent directly to S3.
> 1. Connect your database. Add your database connection string.
^ does this mean client's database must be accessible from public internet, and Oops Backup needs to be given read access to it?
It would be good to have docs going in precise detail of how backups will work. If these docs exist, don't put them behind login wall.
> Each account comes with 2GB of high-speed storage. This is enough for most SaaS databases, blogs, and side projects.
Is this per backup, or total? If total, then with 32-day retention there's only ~60MB per backup, which is tiny.
What is the problem with doing that?
If you use AWS for object storage: https://european-alternatives.eu/category/object-storage-pro...
If you use SES: https://european-alternatives.eu/category/transactional-emai... (but hosting your own is also a viable option)
CDNs: https://european-alternatives.eu/category/cdn-content-delive...
There isn't any single provider that can match each and every AWS service. But for subsets of services there are options.
If there's a specific AWS service that you cannot get anywhere else but do absolutely need, that's vendor lock-in. Would it be fair to blame EU companies for your bad decisions?
Shell scripts can be audited. The average user may not do it due to laziness and/or ignorance, but it is perfectly doable.
On the other hand, how do you make sure your LLM, a non-deterministic black box, will not misinterpret the instructions in some freak accident?
Reminds me a little bit of Sascha Baron Cohen's democracy speech [1] in The Dictator ;-)
Both SQL and CSS have evolved through different versions and vendor specific flavors, and have accumulated warts and different ways to do the same thing. Both feel like a superpower once you have mastered them, but painful to get anything done while learning due to the steep learning curve.