11,087 karma · joined May 9, 2009
(Granted, from what I can tell, it’s waving away a few details. It was the toise which was based on the seconds pendulum, and then the meter was later defined to roughly fit half a toise.)
In fact, adding exponents here objectively makes it less interesting, because it increases the search space for coincidences.
What makes the case in the post most interesting to me is that it looks at first glance like it must be a coincidence, and then it turns out not to be.
For example, the speed of sound is almost exactly 3/4 cubits per millisecond. Why is it such a nice fraction? The magic disappears if you change units… (of course, I just spammed units at wolfram alpha until I found something mildly interesting).
> If you express this value in any other units, the magic immediately disappears. So, this is no coincidence
Ordinarily, this would be extremely indicative of a coincidence. If you’re looking for a heuristic for non-coincidences, “sticks around when you change units” is the one you want. This is just an unusual case where that heuristic fails.
Meaning that the packets were more or less pure glucose.
It’s one thing you have to look out for in studies on the health effects of a lot of artificial sweeteners, particularly in animals. The doses might look reasonable at first glance, but are often orders of magnitude greater than anyone would actually consume.
(This doesn’t apply to sugar alcohols, mind you, which tend to have a similar or even lesser sweetness to sugar.)
On the plus side, it makes me appreciate how wonderful it is to have modern dev tooling when I’m working on literally anything else.
So that’s one solution, and it’s a big space for biology to play in. The bigger question will probably be whether or not there’s a route where weeds can make incremental progress toward better resistance from where they are right now.
For insects, as someone else pointed out, the easiest route is probably mimicry. But we might also see insects capable of recognizing the laser bots, noticing the chemical signals of burning bugs, etc.
I mean that’s kind, but the whole point of DMCA safe harbor provisions is that they aren’t in the middle of this. They send along the notice, you file a counter notice, and that’s it for their involvement, yeah? If CrowdStrike wants to press the issue, they go after you, not CloudFlare.
Sometimes this can be pretty difficult to even see. If you were a Mac shareware dev depending on VersionTracker and MacUpdate to drive downloads, with no actual marketing budget, you might not have noticed that you were implicitly relying on Apple not creating an App Store which would turn the entire ecosystem upside down.
This is one of the reasons that it’s so tough to make a business work at a small scale. In some ways, you have more flexibility than a big company, but the lack of capital means that certain events that a larger company would shrug off can totally upend everything you’re doing.
And that’s the problem. I’m not shopping with Alexa, because that experience is excruciating. I’m reordering things which I was already going to order through Amazon. They’re not actually generating new sales there; they’re just saving me from having to pull my phone out.
That's not to say that I think that converting to markdown is pointless or particularly harmful. Reducing tokens is useful for other reasons; it reduces cost, makes generation faster, and gives you more room in the context window to cram information into. And markdown is a nice choice because it's more comprehensible to humans, which is a win for debuggability.
I just don't think you can justifiably claim, without specific research to back it up, that markdown is more comprehensible to LLMs than HTML.
So consider this extreme case: suppose we take a large chunk of plaintext and compress it with something like DEFLATE (but in a tokenizer friendly way), so that it uses 500 tokens instead of 2000 tokens. For the sake of argument, say we’ve done our best to train an LLM on these compressed samples.
Is that going to work well? After all, we’ve got the same information in a quarter as many tokens. I think the answer is pretty obviously “no”. Not only are we using a small fraction as much time and space to process the information, but the LLM will be forced to waste a lot of that computation on decompressing the data.
My hunch is that the fact that HTML has explicit matching closing tags makes it a bit easier for an LLM to understand structure, whereas markdown tends to lean heavily on line breaks. That works great when you’re viewing the text as a two dimensional field of pixels, but that’s not how LLMs see the world.
But I think the difference is fairly marginal, and my hunch should be taken with a grain of salt. From experience, all I can say is that I’ve seen stripped down HTML work fine, and I’ve seen markdown work fine. The one place where markdown clearly shines is that it tends to use fewer tokens.
A trick I’ve found seems to work well is leaving some kind of id or coordinate marker on each column, and adding that to each cell. You could probably do that while still having valid markdown if you put the metadata in HTML comments, although it’s hard to say how an LLM will do at understanding that format.
There’s more flexibility with tunable wavelengths, though, since there will often be multiple solutions for what colors and intensities can be combined to create a particular photoreceptor response. By cycling through different solutions, I wonder if you could disrupt the brain’s ability to spot any patterns, so that it’s just a very faint noise that you mostly filter out.