barsonme

Well, it's not just individuals with their savings. It's businesses, too.

I don't disagree, but fwiw it's only about one month's payroll for 25 people if each employee makes around $200k per year.

Canada tried this like 20 something years ago. It, uh, didn’t work.

I’m sure the US military is smart enough to put their toys away before the balloon they’ve been watching for a week floats overhead.

Ha, thanks! I’m planning on adding fixed point decimals soon. That’s actually why I made the package in the first place.

Have got you covered there… https://github.com/ericlagergren/lwcrypto/tree/main/ascon

The maphash package from the blog post provides routines that call into Go's runtime to hash arbitrary types.

The maphash package in the standard library (hash/maphash) provides routines that hash string and []byte.

The builtin map type is a hash table.

> At the very least by authorities with a perma warrant looking for "CP" or "terrorist" material.

I mean, unlike perceptive hashing, cryptographic hashes do not lie.

Given that modifying just a single bit in an image results in a wildly different hash digest, I think the risk is a little overblown. There are probably easier ways for authoritarian governments to figure out who's sending illegal content, like just taking somebody's device and looking at their messages.

> Then all someone has to do is generate images that collide

If the hashes are cryptographic, then this is impossible (given today's technology).

> with the ones in the CSAM hash database

The CSAM hash database isn't public AFAIK.

> I remember someone posting about a year ago a bunch of strange looking images that produced those collisions.

You're probably thinking about their proposed 'perceptive hash', which has since been scrapped.

Yeah, there is an easement for the trail.

This already happens with public utilities and whatnot.

I own a number of acres with a public walking trail through part of it. I don’t particularly like having random people being able to walk though my property, but honestly it’s such a minor inconvenience. And people use it much less than you’d think, especially in sparsely populated places like Wyoming.

> Under one interpretation of federal law, the public wouldn’t have to corner-cross at all to get to landlocked land: If the only way to reach public land is through private land, people can just take the most direct route “right through the middle.”

This sounds entirely reasonable to me. It’s silly that you can own something (the public owning public land) but can legally prevented from accessing it.

Also, as a hunter and somebody that enjoys being outdoors, I didn’t know about OnX! Super cool.

Because of Blackstone’s ratio.

I may be misunderstanding, but from the linked article:

> “We’ve returned close to $1 trillion to the Treasury over the last 10 years. We did not keep that revenue in the Fed,” St. Louis Fed President James Bullard told reporters last month.

I think manual three-way comparisons are very clear. But so is strings.Compare. For better or worse, copying code is a pretty normal thing to do in Go. See "A little copying is better than a little dependency." [0]

[0]: https://www.youtube.com/watch?v=PAAkCSZUG1c&t=9m28s&themeRef...

Go doesn't have many features of other languages. There are several competing goals, including keeping the language small, not hiding complexity, etc.

Manually writing the three-way comparison fits in with these goals. If slices were comparable then I'd wager that bytes.Compare would not exist.

Or, you could use cryptography.

That would only work if the original was uploaded to GitHub before the copies. Like, somebody could copy from GitLab or BitBucket. And git histories don’t always help if they’re not copied over.

Also because we’ll pay that much :)

He’s doing SQLite too, and SQLite uses TCL extensively in its tooling.

ZK proofs let you (the prover) prove a fact to somebody else (the verifier).

FWIW the linked paper on nuclear warheads is fairly accessible. You don’t need to understand nuclear physics to grok the algorithm.

ZK proofs only demonstrate knowledge of some fact. So, you could prove that you know the way through the maze, but then immediately forget it afterward.

Maybe the nuclear inspectors inspect the warheads frequently enough that rearming them would be detected? Or perhaps there is just some level of trust and you have to rely on the country to play by the rules.

The “magic door in a cave” game might’ve been a better example of interactivity.

Ehhhh, I’ve been writing Go for ~10 years and I’ve never had this make it into prod. Many times in local development and testing, though.

What hourly rate do you think is fair for them to pay their employees? $20-$30/hour is ~130%-180% of the median income for Allegheny County, where the company is located.

I honestly don't know what's fair for the jobs the company is hiring for. Maybe they're woefully underpaying! But at first blush it does not appear terrible.

A totally not in-depth look at machinist hourly rates (in Seattle) looks fairly similar to what they're offering.

I’m not sure what to make of your reply. You don’t offer any evidence that it’s not subjective. And I don’t even know what you mean by

> Case closed, apologist anecdata will not be considered.

Not sure this is your call to make?

I haven’t ever bought a lightening cable. Every device that uses one (iPhone, Magic Mouse, whatever) has come with one. And lightening cables don’t require unique chargers or converters.

I don’t think it’s some great positive, but I also don’t think it is “clearly detrimental” to the user experience, either.

> even when it's clearly detrimental to the user's experience

This is entirely subjective. Personally, I’ve never been bothered by the different port type. I’ve also never really known it to be a problem for friends and family.

That doesn’t mean I wouldn’t prefer USB-C for the iPhone. Just that for me it’s not been “clearly detrimental.”

So the choices are (a) convince the EU Commission to adopt another charging port, or (b) manufacture devices with multiple charging ports?