Hacker Newsnew | past | comments | ask | show | jobs | submit | im3w1l-alt's commentslogin

A large company is guaranteed to have been analyzed very carefully by skilled analysts. If you have a small sum to invest, a big risk appetite and you are willing to do your homework then you are better off trying your luck with understudied companies in inefficient markets.

It follows from the theory of comparative advantage. The big players can extract a lot more than you can from big companies but only a little more from the small ones.


If mastodon had a security hole they could all be owned at the same time. Fediverse servers on different software would be unaffected unless the hole is in a library used by both.


The Twitter account takeover was an inside job.

To be fair, the article is just part of a challenge to write 100 blog posts in 100 days. Nothing wrong with writing whatever you want, although the title of the post is still terrible. The question is, why did anyone think this article was worth submitting to HN?


Yes I'm aware. An inside job against mastodon would be harder. A few people may be able to deliberately insert malicious code but that goes for any open source project.


Google was willing to pay the most. This means it was more confident than anyone else of being able to scale the products.


The higher performance is not free. Fear makes you accept a higher risk of injury.


Indeed. Cases where the golgi reflex[1] is suppressed are some of the most vivid examples.

[1] https://en.m.wikipedia.org/wiki/Golgi_tendon_reflex


The nyquist limit is based on recovering a general signal. If you have a-priori knowledge about the signal you can do much better.


Are vacation apartments included? And if they are not how can officials know whether someone visits a few weeks a year? Or will this target company owned apt complexes?


From the article:

> For the properties to be eligible for forced purchase, they must have no tenant contract for two years and no record of recent power or utilities use, meaning that occasionally-used second homes do not appear on the list.


That reminds me of the one annoyance of the very cool Softice debugger. The clock would stop while active.


It's like the halting problem. It's hard to decide whether a given switch works in the general case. But it's possible to design an obviously correct breaker.

Edit: the gnarly thing might be ensuring it doesn't harvest power through data wires or store power in covert capacitors or batteries.


It's not only about the mathematical factor. It's about which usecases are possible.


If you let the number of objects to sort go to infinity while keeping size of objects in bits capped, then they will behave like integers.


I thought more of being able to do bit manipulation or hashing etc on your keys. Those things don't necessarily require a fixed key length. (And in some languages, even integers don't have a fixed length.)

You are right in some sense, but you'd still have trouble implementing something like bucket sort in your setting, if all you have are comparisons.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: