Recent submissions

Comment · 5 months ago
There might be multiple methods and heuristics, but one way that I have encountered was based on packet TTL.

Android and Linux use 64 by default - the block could be circumvented by setting the laptop to use 65 TTL.

Comment · 6 months ago
What do you think the minimum pad clearance is for the clay?

You can dead bug an LQFP if you absolutely have to…

Comment · 8 months ago
This assumption has unfortunately led to countless security issues, at least in the past. The nosniff header (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...), was created because of this and should be added.

While this probably works, you should also add a restrictive CSP (using the sandbox directive).

Forcing the download (via Content-Disposition header) would likely be even better, but it is annoying for users.

Comment · 2 years ago
It's still available, just hidden in the search tools.
Comment · 9 years ago
Not sure what you're getting at, apart from the loss the same disadvantages also apply if the cable is superconducting.

Even worse, maintenance and running costs of superconducting cables are likely much higher due to the cooling (high temperature superconductors are "high temperature" in comparison to other superconductors - there's still lots of cooling needed).

Comment · 9 years ago
That would be a best case scenario and I doubt that's what's happening.

And instead of bringing those services back locally, nearshoring will probably be considered first.

Comment · 9 years ago
Obviously they're fucked. Luckily we are still in the hardware design phase, otherwise we'd be even more pissed.

I don't think anyone built a product with enough volume that Intel would reconsider the discontinuation.

Long-term component availability is a major issue for hardware products. Discontinuing a product basically over-night is not a nice move from Intel and I hope people will remember this when Intel launches their next IoT/robotics product.

Comment · 9 years ago
There are virustotal clones that don't send back results to the vendors. This is specifically done to prevent that kind of problem.
Comment · 9 years ago
Same here, no problems anymore for more than two weeks now.
Comment · 9 years ago
You cannot skip FCC certification, you can just go through the "simpler" unintentional radiator testing when using pre-certified modules. That's still around 1.5k USD.

Also you can't use custom firmware on a pre-certified module, otherwise you'll still have to do the intentional radiator testing. You control those modules with an external MCU, which is cheap though.

TIs WiFi offering is horribly expensive compared to any ESP8266 based modules, still like 13$ @ 1k units on DigiKey. That's the main reason the latter got so famous.

You need to sell a few hundreds just to get those fixed costs down to a reasonable amount per unit. And then you still have to pay the engineers... Maybe 80-100$ per unit would be more appropriate, but then again I doubt they sell in huge numbers.

Comment · 9 years ago
I agree it's overpriced.

However don't forget that when selling a product, lots of other costs arise. E.g. you'd need FCC certification (around 10k USD for intentional radiators) and make sure that no other standards are violated (mainly regarding mains voltage). The plastic case mold is another 3-5k. Then some margin for returns, marketing, etc.. It's a niche product, so the fixed costs make up a big part.

If it's popular someone will sell a simple DIY kit for 20$ and an open-source server. But I doubt there's much demand.

Comment · 9 years ago
I doubt their "signal processing" involves anything more than a microphone and a peak detector.

A more practical side channel attack would probably be through radiated emissions over the mains power. However if you're willing to go that far, a laser microphone is much more effective and simpler.

Comment · 9 years ago
Don't worry, they thought about that:

Guests' privacy is always protected. Our patent pending technology ensures that no content is recorded

It's patented, so it must be good.

Sarcasm aside, I really wonder what's in that patent... I mean it must (should) exist, otherwise it should be "pending".

Comment · 10 years ago
Just checked again, we're still seeing issues. I can reproduce, simply by using my personal account in a private window, it randomly fails in at least one of our environments (e.g. prod, staging, localhost).

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton