I do appreciate the link to the article and came via HN. I don’t think you can speak for either the audience of people producing software nor for HN.
Another article comparing LGPL and this license sounds good and I am interested in that as well. This article though is a good nudge to start thinking about licensing.
There are some good descriptions and hints, but what the site really needs is examples. Just looking at the code doesn't help me much. The descriptions are also mostly so short, that they could just as well be tooltips on the homepage.
The whole premise of the page is a collection of "web tricks worth remembering" and I can't fathom what bash (e.g. `du -hd 1 . | sort -hr`) is doing there.
fwiw I find `*` a lot easier in regular use than all of `-d 1 .`. It doesn't automatically expand to dotfiles but for regular typing, this advice looks like something you'd do if you're a robot or making an alias
Try ncdu, which kind of does this but better. You can quickly traverse a directory tree recursively sorted by size in a simple ncurses interface and even delete files with instant recalculation.
You’re absolutely right, thanks for the feedback. I initially included live examples (mostly through CodePen), but they were taking too much time to maintain, so I stopped.
The Bash entry was really just a half-finished personal note that I never properly edited. It’s probably out of scope too.
Codepen is an awful experience on mobile (and is slow, as you said). But your page is an html page about html tips. Surely you can just embed them in the page itself?
I get your distaste, but RSS is the more famous wording of the technology. I would frame it as "people who love RSS - but technically these are Atom feeds". RSS is the word that stuck and I think we should keep promoting it and on a technical front I am with you - sure, let's use the Atom format "for RSS feeds".
True. Just based on the reporting we don't know what's going on, but the article makes it sound like those 180+ nodes were unexpected. Of course you would need to set your own limits to alerting and "what is unexpected" and you may still fail to catch something this way.
Not sure that everyone does this anyway. There are some good security postures you can take with Tailscale as well and leaving an auth key lying around is not one of them.
Tailscale lock should have been enabled. For CI/CD purposes the auth key could have set specific tags, which would result in specific ACLs that limit blast radius. The auth key could have a short validity. You could actually use the Tailscale API to generate alerts when a new device joins your Tailnet and ping your phone or something. You could have a complete separate Tailnet for your CI/CD workers.
They might be today but who's to say it won't start firing off fetch calls later perhaps under a new owner if it gets sold.
Unfortunately the browser extension permissions are not granular enough to warn you when fetch is being used in an extension.
As an example, my password manager extension can read and inject content into any page along with communicating with its server to sync my vault. These are the only permissions Firefox shows me:
* Access your data for all websites
* Get data from the clipboard
* Input data to the clipboard
* Display notifications to you
* Access browser tabs
* Access browser activity during navigation
No indication there that it can also communicate with its server.