dadrian

The pricelist was a marketing stunt.

While the result is impressive, this blog post is extremely disappointing.

- It does not show an example of the new best solution, nor explain why they couldn't show an example (e.g. if the proof was not constructive)

- It does not even explain the previous best solution. The diagram of the rescaled unit grid doesn't indicate what the "points" are beyond the normal non-scaled unit grid. I have no idea what to take away from it.

- It's description of the new proof just cites some terms of art with no effort made to actually explain the result.

If this post were not on the OpenAI blog, I would assume it was slop. I understand advanced pure mathematics is complicated, but it is entirely possible to explain complicated topics to non-experts.

There's something ironic about vibe-coding an anti-YC site. They're why OpenAI exists!

The Internet in 1999 was not good at all. Browsers barely worked, computers crashed constantly, the ability to actually search for useful things was limited, and many things we take for granted as being online (news, people, documentation) were not.

The mid-to-late 2000s are perhaps closer to what the author is looking for.

I dunno, they'll let anybody get on the Internet and start a podcast.

I will bring this up at the next meeting of the secret cryptographer cabal where we decide what information to reveal to non-cryptographers.

Except for the part where it's constantly having quality and reliability issues, even independent of the server-side infrastructure (OOMs on long running tasks, etc).

As opposed to Pip, which is obviously free and sustainable forever.

The person with the most HN karma of anyone on this site, currently thinks djb's actions are wrong.

For someone to come in and buy Bluesky and then hold everyone’s data hostage, then Bluesky would actually have to have enough value that someone would want to buy it.

RMS has, at minimum, showed that he swayed by parrots, spider plants, and free plane tickets and guest lodgings.

SAML is arguably the worst cryptographic standard ever created

The PGP packet has entered the chat.

GOT ‘EM

Some of them also aren't really dead.

The 90-day disclosure window is an arbitrary courtesy, not a binding contract about the behavior of either party. They probably had other things to do.

Taken both in name and role, more or less.

PE didn’t kill housing. Private equity owns 2-3% of homes.

It's not red! You're just colorblind.

Network DLP is also not bulletproof so I'm not sure what the argument is there. These things are all best effort.

if you have DLP at work, open the integrated browser in VS Code and notice how you can send protected test strings without anything chirping you.

I recognize it's not instrumented, but how are protected strings getting there in the first place?

That is not true, you can run DLP on an endpoint directly and inside a browser directly (e.g. via an extension or direct integration hooks).

You can also try to stop the situation where the CC numbers are in the clear anywhere in the first place, so that you can't copy/paste them around. What happens if someone writes the CC number down on a piece of paper?

This is good advice, and there's good people on the signature list, but why is this is an open letter? This feels navel-gazey and straight out of 2017.

A MITM could replace the redirect with malicious content, as described in the blog.

Yes, it started that way, but complaining about the current auto-update behavior of the software (not the ACME protocol), is completely unrelated to Let's Encrypt and is instead an arbitrary design decision by someone at EFF.

Add a /, e.g. `shortname/`

Let's Encrypt does not write or maintain certbot

Non-unique hostnames, which are RFC 1918 space, single-label hostnames, and addresses assigned to mDNS (.local).

Chrome has shown the HTTP warning in Incognito mode for about a year, and has shown the warning if you're in Advanced Protection mode for about 2-3 years.

Web browsers and operating systems are full of memory safety bugs, and are not written by engineers in crunch these days.

Not clear to me there's a correlation between hours worked and number of memory safety vulnerabilities

I like Zig, although the Bun Github tracker is full of segfaults in Zig that are presumably quite exploitable. Unclear what to draw from this, though.

[1] https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...