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.
Bento has auto-update baked in. It checks for signed updates in a manifest, downloads it, rewrite the file structure with the new and reloads with the new file.
Is „frontier“ overused? I thought frontier models were the best-of-the-best such as Fable right now. I assume you can’t host these models yourself since you would need many GB of RAM and expensive GPU of is my thinking of „frontier models“ wrong?
I was confused too, but I believe that it refers to the Pareto Frontier: the best set of solutions to a multi-objective problem.
Look it up, it’s a bit difficult to explain concisely in words but it is intuitive visually.
If we are thinking of intelligence and price, a model will be in the Pareto Frontier if there’s no cheaper model of the same or higher intelligence. Or if there’s no more intelligent model for that price or lower.
So for example DeepSeek V4 Pro can be considered a frontier model because there's no cheaper model that is as intelligent.
For any solution in the Pareto Frontier, there no "no-brainer" alternative, in the sense that there's no other option that is better in some way without giving up something else. It's the best of its "weight-class".
There are two frontier labs - OpenAI and Anthropic, and maybe 4 frontier models currently. That term refers to model capacity and in general represents a model’s capability relative to the rest of the industry irrespective of price. That’s why even the Qwen announcement carries language about it being ‘near frontier’. Same with Kimi.
Whether a model is frontier or not has everything to do with capability and nothing to do with price.
That’s a good visualization, although I am a bit mistrustful of Arena’s scores. It does get around the fact that models are getting trained for the benchmarks, but the methodology of letting random people compare outputs side-by-side is a very shallow judgement method in my opinion.
EDIT: Indeed looking at the overall rankings for text again, the list is rather strange, a lot more about writing style than intelligence.
They supposedly have a style control system, but I doubt it's perfect. I wish there was a parento view like this for agentic systems(using a standard harness)
I don't know that I agree with this specific use of frontier because it is confusable as you say.
But (off on a tangent) I do think that there are multiple frontiers generally — and I also think the open weights, small local model frontier is by far the most important and exciting one.
I keep mucking about with what Gemma 4 12B can do and every time I do I find myself thinking that all the energies in the AI world are going in entirely the wrong direction, because it is small, clever, efficient and remarkable.
If all of that research money were to be spent on improving AI models that fit inside a 16GB RAM machine with unified memory, I think really important progress could be made.
I enjoy using the Qwen 3.6 models (and BottleCap's new fine tune of the 27B) but the small Gemma 4 models are impressive in a way that I think is going quite unreported.
So while I don't think this website should use the word "frontier" here, even referring to Qwen 3.6 27B which is weirdly close, I think it could.
I’ve got a 32 gig m1 MacBook Pro. how would I go about trying Gemma like you mentioned? Would it run at an acceptable speed, and what could I do? Coding?
I figure it might be quite a competent general coding teacher for more, er, consumer programming languages, for want of a better word — python, PHP, JS. Seems to be pretty solid on WP knowledge too.
And I find it curiously interesting when talking about photography. I've been finding it intriguing to ask it about my own photos and make suggestions about other images to research. I just showed it three of my own photos, and asked it to analyse them and recommend photographers I should research. It recommended someone amazing I have never heard of before. But it also recommended a 19th century British photographer who happens to be my lifelong photographic hero — someone whose broad characteristics inform what I do without me slavishly copying them. Bit of a jaw-dropping moment for it to have picked up their influence in subject matter that they would never have approached.
I'm still suggesting it more to people for them to see what the small-model future might look like, because it's so much more capable than one might expect.
On an M1 Max I have been using either Unsloth Studio (which is basically a web app) or LM Studio (nicer app on the Mac). You can use the Google AI Edge Gallery to play with the smaller Gemma models (but at the moment the QAT variants don't seem to be there unless I am missing something).
I think it's likely the 26B QAT model won't fit in your machine — you may be able to fit one of the UD_Q3 or UD_Q2 variants but whether you'll be able to run other things you want at the same time, I don't know.
(The QAT models are "quantization aware training" — AIUI the model weights have been assigned during training to survive four-bit quantization with less loss.)
(I don't think the M1 really gets much benefit from MLX, in case you were wondering, though I could be wrong)
My interest in this model is largely to really get to grips with what small models can actually do, especially with tool calling, because I think it helps comprehend what the value proposition of the cloud models is.
I have been very surprised by the quality and clarity of its answers. It's also helped me understand that much of a typical harness system prompt is likely to be unnecessary now; Gemma 4 seems to be pretty sensible out of the box.
You're absolutely not going to be able to get it to go off and build whole apps from a long prompt; it is not that good, but it does tool calling and thinking, and you should be able to explore pointing a coding harness at it if you turn on LM Studio or Unsloth Studio's API server. You could also use the Llama system tray app (formerly LlamaBarn) or just use llama-server from the llama.cpp distribution.
Probably Pi is going to be a better harness because it can have a minimal system prompt, though I've not tested it with Pi myself.
It seems to know PHP and SQL to a fairly decent depth (and I suspect JS and Python). It also has a unified vision model (it doesn't need a separate mmproj sidecar thingy) that is fairly fast, and it is quite impressive at image analysis.
So you could probably use it to generate image descriptions and tags, summarise text, generate wordpress snippets, that sort of thing.
It can capably answer questions like "Can you characterise this image and suggest further similar images I might like?" — I am currently using this to provoke me to take photos again.
Have a play with the E4B edge model, too — again, much more interesting than I expected.
The frontier is a multidimensional space defined by the “best” combination of traits a model can have in multiple dimensions: parameter size [smaller is better], various task metrics, and relative token generation speed on like hardware [faster is better], and active memory requirements [smaller is better] are all possible dimensions, and a model on the frontier of the current options space is one where getting better on one of those measures cannot be done without getting worse on at least one of the others.
That's not what people are normally referring to when they say "frontier models". It means the most capable models full stop. Not the most capable that you can run locally.
Had the same though. The gap between open-source and the frontier is closing in, especially with Kimi K3, but that is like >2T parameters. The Gemma 4 and other models you can actually run on an average Mac, is not in the same league.
It might be overused elsewhere but I don't think its use here is inappropriate given it's qualified: it doesn't say "frontier models", it says "frontier open models".
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.
reply