nemothekid

The idea that surveillance undermines high trust societies seems insane to me.

Only because, I'm betting, that you view street surveillance as something that binds others, but not yourself. I doubt you would make this argument for any other kind of surveillance.

If Microsoft were to record everything you did on your PC, would you consider Windows the "high trust" OS community vs Linux? Of if your employer began surveilling all your devices (including personal ones) to ensure you weren't stealing from the company, would you consider your company one of "high trust"?

I don't deny that surveillance can reduce crime, but the idea that surveillance undermines high trust societies is relatively straightforward

I think he's being a little facetious - what he probably means is that if you attempt to get any true scientific rigor of that is going on in biological or chemical systems you end up facing the limits of physics in being able to explain what is going on. So rather and try to have scientific rigor, you just accept things the way they are and memorize the outputs and if anyone asks "why is it like that", your answers are either:

* Because God said so

* Find out yourself and get a nobel prize

Either way, even if you don't know what the answers are, you can still do serious work at a higher level of abstraction.

`Cargo.lock` is a lockfile machine generated by Cargo. It's similar to package-lock.json. In any case, its machine generated the old fashioned way.

There's a dichotomy being presented here where you have to either choose a "style guide" or a programming language feature in order to avoid bugs. The sleight of hand misdirects the reader away from the main way bugs are eliminated: by dedicating engineering resources to it. You're not giving TigerBeetle nearly enough credit.

In a post-Rust world I really don't like the rebuttal for eschewing memory-safety is always "you aren't engineering hard enough". The guys at TigerBeetle are "real engineers" and don't need memory safety. If I'm spending most of my time manually chasing memory errors, I didn't "real engineer" hard enough.

Chasing esoteric memory bugs are the worst kinds of bugs to pin down. They are always non-obvious (because if they were they would be fixed) and almost always non-deterministic. I'm just can't escape feeling like new memory unsafe languages are just hobby projects.

What's the problem if a site is vibecoded?

Typically if a site is well designed, that used to be a signal that a lot of resources had been invested into the project. Now that signal is rather noisy.

Here, is particularly bad, as the main page is just complete slop bullet points. What does 'end-to-end column compression' mean? or 'uniform bytes at every layer'?

It's difficult to understand at a glance now, if this project is going to be abandonware in a week or if someone actually spending time on this. If the creator can't be bothered to read it, why should I?

Personally, I'm also very weary of Claude design-isms. Once you learn them, you see them everywhere.

Off topic: Is there anyone doing any research on how to use Claude/Agents to design websites that don't look so, "Claude"?

People reach for the things you mentioned wayyyyyy before they should.

Most orgs are probably due for a technical reassessment. Scale that I believe would have melted postgres in the past now just runs fine. CPUs got a ton faster and memory got cheaper.

Projects that would have required a complex distributed setup 10 years ago can now be handled by a single machine. For a lot of use cases, CPUs got faster than population growth.

They are already a public company.

My clients will have outgoing connections to whichever co-ordination server I choose.

Then it's no longer p2p? If I wanted to avoid paying cloud egress costs, then I would need a p2p solution.

Tailscale is great for bringing devices/apps into a secure network when I cannot modify them in any way. If I have full access to the source code for everything, the story changes completely.

Naturally, but this thread isn't about Tailscale, its about Iroh. You were the one that claimed Tailscale can already do what Iroh can. But I've pointed out a usecase where Tailscale wouldn't suffice that Iroh can accomplish.

This isn't the same functionality - if I'm shipping a video conferencing application, tsnet would require all my customers be in my tailnet.

The reach of this bug is what makes it serious. Any deployment that points FFmpeg at an attacker-influenced RTSP URL is exposed: media ingest pipelines fetching user-supplied stream URLs, surveillance and CCTV systems pulling RTSP feeds, and transcoding services processing remote AV1-over-RTP sources

Wow this is actually pretty serious - I'm even surprised its being published. There are several services where I can imagine this is exploitable today.

Given that they had originally selected OpenAI for Siri, and that deal fell through, I would guess something about their relationship with OpenAI fell through. Maybe OpenAI wouldn't let Apple run their model on Apple's servers.

Everyone is now dopamine maxxing on smartphones and internet

Childbirth has been collapsing for decades before Mark had launched "thefacebook.com". Japan's TFR cratered in 1960 and never recovered. Did Japan have smartphones in 1960?

The first page of RFC 882 explains outright that the DNS came about in the first place because the mechanisms for updating a HOSTS.TXT file and publishing it to loads of places did not scale.

Great piece of history. The RFC is a bit older than I am so I've never studied it. Looking at it that way, then OP has just re-invented DNS.

Fortunately, we still have /etc/hosts, which we can easily provision

This is the kind of thing you read in a post-mortem and wonder how they designed something so fiendishly wonderful.

At 2:00am our MySQL master failed and failed over successfully to our secondary server. As part of post-failover ops, ansible playbook proceeded to login to 1000 instances to update the hosts file for the new master. This caused traffic amplication which caused our Etcd nodes to believe they were down. As the etcd nodes failed over, our ansible playbook proceeded to then login to 1000 instances to update the hosts file...

Honestly, whatever system you built is justing do the same exact function as DNS just with extra steps. If you squint really hard /etc/hosts is your local dns cache and ansible is your resolver. I think this kind of "simplification fetishization" is dangerously attractive to people who have only managed relatively simply setups. I don't think anyone who has ever had to deal with high-availability failover would consider Ansible a good solution.

The problem that so many people hit with DNS isn't specific to DNS the protocol - it's the problem of service discovery. This architecture doesn't eliminate service discovery, it just moves it to a far more brittle configuration.

What does E2EE mean here? If I send an email to someone using rootshell from gmail, doesn't rootshell get the email in plaintext?

One funny thing I've discovered as a result of certificate transparency logs is that the second your host gets given an SSL cert, you are immediately blasted with ai crawlers.

I put a project online - it was online for a month, and the second I added an SSL cert it went from 0 traffic to 1000 requests/min.

While I have had my time fighting the OOM killer, I believe overcommit would have always won. To torture the metaphor a bit more, airlines have OOF mechanism - they just eject the overcommitted passengers before the plane takes off.

A passenger buying a ticket is malloc(), but passengers don't always utilize the seat (use the memory). Normally this works out fine, but occasionally, there are too many passengers. Thankfully though instead of executing a couple passengers they give you a voucher.

1. If postgres shutsdowns uncleanly, your entire table is truncated; you lose everything.

2. You should check if your backup method backs up unlogged tables. For example, RDS Snapshots on AWS do not backup unlogged tables.

These 2 are a double whammy where if you aren't aware of these tradeoffs you can find that a bad restart has deleted all your data, plus your unlogged tables were never backed up.

There are so many unfortunate footguns with unlogged tables, that I'd argue that the goroutine route is preferable.

add [skip ci] to your commit message

Your question just kicks the can down the road. The problem with the article, to me, is the author doesn't want to accept a certain amount of complexity and has erected arbitrary road blocks.

To you, a "whole damn event loop system" is too high a price to pay, but try/catch is not. The complexity of exceptions is invisible to you. However there are certain environments (e.g. FFI) where I dont want "the whole damn exception runtime".

That only applies to Javascript, which, is mostly only red functions anyways (there are no blocking apis in javascript). Javascript doesn't have the coloring problem in the way Python or Rust has it.

In Python, you can wrap the call with asyncio.to_thread, in rust with tokio::spawn_blocking.

Java's checked exceptions fit the 5 criteria:

1. It either `throws` or it doesn't

2. If the function `throws` you have to wrap it in try/catch, or make your function `throws`

3. Your function is `red` if it `throws` the same exception.

4. see (2)

5. See the FileReader class in core.

Now, C++ exceptions might not satisfy all of these, but the problems CheckedExceptions were meant to solve still exist in C++ and as a result some style guides forbid them entirely. Like async, the biggest problem with exceptions were the ergonomics.

Am I reading this right?

SpaceX TAM - "Enterprise AI Applications" is 6T. The other 22T enterprise AI. This is a rocket company pretending it's a frontier AI lab.

On the other hand i can’t remember when there was a serious outage on GCP

They had a really bad global outage a year ago. At least with AWS outages are contained to a single region.

Yeah, I clearly prefer non-hamfisted regulation under the guise of "protect the children". Half-assed attempts like this are worse than useless.

Just like with GDPR, the tech giants will put their foot on the scale and continue to operate how they fit, and the smaller guys will die under a thousand paper cuts. I'd rather not add more regulation that cements Meta as the sole media platform of the internet.

I think you are just reflexively trying to argue your point without even thinking about it.

30 million tiktoks are posted by day. What do you mean your are going to allow "users to filter". This "regulation" will be trivially defeated by TikTok-Videos LLC uploading videos and TikTok-DataScience, providing the most popular filtering algo.

At the end of the day, many children will simply default to using the best algorithm, and all this regulation helps no one.

I don't for a second believe that tiktok (or facebook or any of the others) employs a primitive algorithm

Is your contention that whatever future law have some mechanism to decide the complexity of the algorithm? How would you design a law such that the reddit ranking algorithm is primitive, but tiktok's algorithim is "advanced".

I don't know of anyone saying you should buy an F1 car for your family, do you?

It's a metaphor. Your clients telling you they need you to deploy on AWS are the kind of people I believe are telling you to buy an F1 car to daily drive to whole foods. You said it yourself: "AWS is being pushed on everyone".

I do see people in this very thread with very different ideas of when AWS makes sense for you.

Naturally. However, 99% of, what I believe are illegitimate complaints of AWS (AWS has tons of legitimate complaints), are from people who were probably better served by a using a simple VPS provider than a cloud provider. A VPS provider is simpler, easier to understand wrt to pricing, and cheaper. Most of the complexity in AWS comes from the fact that AWS itself is a very complex tool targeted to large organizations and deployments where people aren't using EC2 instances, or are using 100s of them. The complaint that the UI doesn't have enough affordances when trying to create a single EC2 instance is kind of ridiculous when you consider it's a tool designed for people launching 100s of instances. Nobody is reasonably launching 100 instances through the dashboard. Furthermore, if vendor lock-in is a concern you have AWS is the wrong tool.

Likewise for IAM. People complain a lot about IAM. But AWS has thousand different user types, and a 1000 different services. I've written my fair share of permission systems with a fraction of the amount of permutations. They always become complex due to the combinatorial nature. GCP manages to somehow be even worse. But you wouldn't need to deal with something like IAM if you just stuck with a VPS.