Recent submissions

Comment · 1 month ago
It is bureaucracy BS
Comment · 1 month ago
Just have npm pay the owner of the package. Let the owner handle the money distribution. It doesn't have to be hippie BS all the way down to be better than what we have. You people sometimes.
Comment · 1 month ago
That basically describes the Google shopping ribbon that appears with searches for products. When Google was good, you'd say a website doesn't exist if you can't find it in the 1st page of Google. The shopping ribbon provides offers from websites that aren't on the first page of my search result. Although I don't think you can pay without visiting the seller's website, this means that these are effectively stores that are more visible through the APIs they use to talk to Google's recommender engine. These suggestions are also no doubt personalized.

This also describes adsense, or Amazon or AliExpress, so it is clearly a successful model. If there is much left of other models. The only thing we have to hopeful about is that the interface is standardized so commodified SWE can be used to make your own Amazon or AliExpress.

Comment · 1 month ago
Surely there is an alternative that isn't Signal?
Comment · 1 month ago
Comment · 2 months ago
That results update almost live as you type is impressive, but I also wouldn't mind if it was slow. I just need full-text search with quotes.
Comment · 2 months ago
Comment · 2 months ago
HN's basic search using quotes can be way more useful than google to me
Comment · 2 months ago
*Only works reliably in Germany
Comment · 3 months ago
They literally cost 20 bucks on ebay if not less
Comment · 3 months ago
> Enable custom AuditD rules to watch anything it touches outside of it's sandbox.

Is auditd capitalized like SunnyD for any particular reason?

But really, what should one of these auditd rules look like? I'm imagining something like below, where *lil-agent* is the user for our agent. This would create audit logs if the user messed with any paths outside its home.

  (auditctl) -F path=/ -F path!=/home/lil-agent -F uid=lil-agent
What can this rule tell me though? Since you advise running agents in an isolated machine, that ideally only has the user for the agent, the only paths the agent could mess with are system files if it had an exploit, but at that point it's game over. You'd have to hope it didn't tamper with the audit logs.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton