Discussion on HN last time: https://news.ycombinator.com/item?id=45326754
Discussion on HN last time: https://news.ycombinator.com/item?id=45326754
Somewhat related, I also have a small homelab running local services and every now and then I try a new technology. occasionally I’ll build a little thing that is neat and could be useful to someone else, but then I worry that I’m just a target for some bot to infiltrate because I’m not sophisticated enough to stop it.
Where do I start?
That's why we use `npm ci` or `--frozen-lockfile` to install the exactly versions as lockfiles. But, by default, the `^` operator and just `install` command will check registry for any new releases and download them.
The primary arguments against pinning versions are missing security updates and increased maintenance overhead. But given the patterns we've seen, the attackers really _hope_ we automatically install new releases
Deleted Comment
It shows you the Hacker News page with ai and llm stories filtered out.
You can change the exclusion terms and save your changes in localStorage.
o3 knocked it out for me in a couple of minutes: https://chatgpt.com/share/68766f42-1ec8-8006-8187-406ef452e0...
Initial prompt was:
Build a web tool that displays the Hacker
News homepage (fetched from the Algolia API)
but filters out specific search terms,
default to "llm, ai" in a box at the top but
the user can change that list, it is stored
in localstorage. Don't use React.
Then four follow-ups: Rename to "Hacker News, filtered" and add a
clear label that shows that the terms will
be excluded
Turn the username into a link to
https://news.ycombinator.com/user?id=xxx -
include the comment count, which is in the
num_comments key
The text "392 comments" should be the link,
do not have a separate thread link
Add a tooltip to "1 day ago" that shows the
full value from created_atOne decision I had to make was whether the site should update in real time or be curated only. Eventually, I chose the latter because my personal goal is not to read every new link, but to read a few and understand them well.
Or copy that repo’s markdown into an llm and ask it to map to the pip ecosystem