Hacker Newsnew | past | comments | ask | show | jobs | submit | sk5t's commentslogin

Notes was simple enough to allow folks with no computer science background or even sympathy for the machine to build teetering, badly-performing things.

However, even with a mind towards efficiency and minimalism, performance at roughly hundreds of thousands of documents was extremely elusive.


Yes, it very closely parallels the “one weird trick” bait from a decade ago.


I’ve seen it use “one weird trick” multiple times in its end of response baiting. Literally those words.


Simply require per-use parental consent for fopen.


Is this a serious question? Whom do you imagine would offer such a guarantee?

Moreover, finding a more effective way to revoke a non-controlled key seems a tall order.


If there’s a delay between jets being posted and disabled they would still be usable no?


To the best of my knowledge, Redis has never blocked for replication, although you can configure healthy replication state as a prerequisite to accept writes.


How does one concretely prepare for socio-economic collapse, beyond taking a long position in canned goods?


There are a lot of ways one can prepare for such a collapse, the most impactful way is to develop skills and preserve knowledge of history, production, and other important information that is being suppressed or pigeonholed to only industry in foreign countries; to a greater or lesser degree.

Preserve the dependencies that promote critical thinking, rational thought, and measured reason.

Aside from that, figure out what you need for survival beyond the basics in a non-permissive environment without a rule of law; and build a community of people that have these skills. The lone wolf always dies, the pack survives.

Austere Medicine, Food Preservation, Guns/Self Defense, Information Recon, etc... Map dependencies, costs, and yields (information that is largely kept confidential these days).

Learn how to make stuff from scratch, and learn what areas you can leapfrog given knowledge of the development of such the technologies in such industries.

Most of the materials we rely on today would not be available because we rely on knowledge of chemistry which few have.

The actual factors that determine the Wealth of Nations are based in the ability of the individual citizen to be self sufficient and produce necessities from scratch that will last without excessive recurring cost. Through a distribution of labor. The book from Adam Smith covers these factors in great detail, and while LTV is now defunct/refuted, the cost portion implicit in the making of intermediate goods resulting from such valuation/economics is not, and remains valid.

Debt-based money-printing on the otherhand is all about distorting the market allowing nationalized industry to outcompete legitimate companies through slave labor under financial engineering. The debasement stolen from everyone holding the currency is in fact slave labor. A runaway positive feedback system that destroys everything it touches (eventually), tainted by Ahriman.


I'll put my hoping energy into a new Portishead album instead.


She's a solo artist now, right?


New band albums are rumored and hinted-at, from time to time, by Geoff Barrow, though it seems hard to say if there will be another.

Bear in mind Beth made "Out of Season" apart from Portishead several years before the release of "Third." I wouldn't think her recent solo work indicates a split.


Decent article, with some technical misunderstandings about MULTI/EXEC, perhaps unnecessary skepticism about Lua, though I certainly do wish Redis had richer built-in functions for CAS and the like.


Agree, there seems to be a lot of skepticism. Maybe this is a cop-out but most people probably don't even need some perfectly implemented rate limiter and having a basic, efficient, easy solution that solves most of the problem isn't horrible, it's just pragmatic. I don't think anyone is running around claiming Redis is the end-all solution to rate-limiting.


> ...unnecessary skepticism...

The URL suggests they might have a product to offer to solve the problem.


Yes - not only is Slack search underpowered, but also records management folks are likely to configure pruning of Slack content older than a couple years or so. This is IME less likely to be a problem with wiki pages.



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: