HN user

JStanton617

315 karma
Posts0
Comments30
View on HN
No posts found.

India (among other countries) have passed so called "hostage-taking laws" that require large social media companies to have in-country employees that can be strong-armed from ways small to large (threats of being convicted of treason and executed).

This is a specific policy to allow them to enforce their censorship laws in other countries.

Payroll is one of the very few (only?) things that "pierces the corporate veil" - that is, the principals / board members are personally liable even in the event of corporate bankruptcy.

You could engage a labor lawyer, but if this was pre-series A and the founder was self-funding, there might not be any personal assets there either.

If you think the folding of the company is in good faith, you might just want to take the loss on this one.

The loss just on the lasers is 100x (i.e. delivered power is 1% of the input energy). Add in a combined cycle effeciency of only 50%, you're looking at needing a 200x improvement to have commercially relevant "net gain"

iPad Pro M2 4 years ago

You need an MDM to manage it remotely. Something like Jamf Now is $2/device/month. Not sure how much the shipping costs, but might be break-even

I was taught basically this same method as the "Princess Bride" plan:

Hello, my name is Inigo Montoya (who I am)

You killed my father (why I'm reaching out)

Prepare to die (my ask / expectation)

For those unfamiliar, the rumor is that Ferrari was somehow detecting the sample rate of the fuel flow sensor (which is a black-box provided by FIA and standard across all the cars), and increasing the flow rate only when the sensor "wasn't looking".

So doing a side-channel attack on the sensor, and designing a pump system to dynamically adjust the rate dozens of times a second. Hacking at its finest

Yes. The code you're running is described as having "random sleeps added to “fix” race conditions, validation functions that just returned true, catastrophic cryptographic vulnerabilities, whole parts of the protocol unimplemented, kernel panics, security bypasses, overflows, random printf statements deep in crypto code, the most spectacular buffer overflows"

This is a kernel RCE just waiting to happen.

There are other ways, but why are they better? He says it out loud, other people can chime in and improve the idea, the Thai gov't sees it without him having to work his way up through a bureaucracy to find someone who can do something about it, etc.

This seems as good a way as any to do it to me.

So Intel tried to shut *BSD out of the process again (like they did for the original Spectre/Meltdown) so they didn't feel they had to respect any embargo?

https://twitter.com/en/tos:

"You understand and agree that the Services are provided to you on an “AS IS” and “AS AVAILABLE” basis."

and

"The Twitter Entities make no warranty or representation and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content;"

Doesn't feel like something you should be conducting international diplomacy with...