


Best password ever, apparently!



Best password ever, apparently!
Most people on lemmy don’t like either Clinton very much, I don’t like the Clintons either.
What’s more important is why you felt the need to make the point that Clinton did racist things, in response to “violent crime dropped between 1990 and 2000”.
Do you believe black people commit more crimes than non-black people? Yes or no?
I get the impression that you believe that black people commit more crimes.
You’re saying there is some kind of connection between Clinton being racist and crimes being reduced. How is that supposed to work?
Being racist somehow reduces crime? Excuse me?
Dems are known for reducing the amount of crime? Very interesting!
Homicide and other serious crimes dropped 40% between 1990 and 2000. That’s because this whole concept of a “nuclear family” is inherently fascist and causes more crime.
It’s a few hundred megabyte llm, not quite the same thing.
Think of a box with 4 particles a, b, c and d. If every particle is on the left side of the box, then there is only 1 way to divide them up. [(a, b, c, d), ()]
If there are 2 particles on the left side of the box and 2 particles on the right side of the box, then there are 6 ways to divide them up:
[(a, b), (c, d)]
[(a, c), (b, d)]
[(a, d), (b, c)]
[(b, c), (a, d)]
[(b, d), (a, c)]
[(c, d), (a, b)]
In total you’ve got 16 possible arrangements, the 2-2 state has the “highest” entropy because you’re more likely to end up with the one that takes up 6/16 arrangements.
Reading between the lines they wrote this because of seeing “I hear you, and you are right to be suspicious — but I only use AI for spell checking, nothing more” one time too many.
Just say nothing. Hitler legally cannot invade if you don’t sign a non-aggression pact with him.


It can only do the impressive numbers after you give it a schema for the data, and the data has to be structured in a way that follows a rigid schema, so it’s not magic.
OpenZL compresses data into a self-describing wire format, any configuration of which can be decompressed by a universal decoder. OpenZL’s design enables rapid development of tailored compressors with minimal code; its universal decoder eliminates deployment lag; and its investment in a well-vetted standard component library minimizes security risks.
The freedom afforded by OpenZL’s graph model is a double-edged sword: the capability it offers comes at the cost of a combinatorial explosion of choices that must be made—namely which components to use and how to compose and configure them. There is no one-size-fits-all compressor
Webassembly for compression or something, but it’s made by the zstd people so maybe it will turn out to be magic eventually.
On one hand the x2.06 ratio for the SAO data is extremely good, zpaq and paq8px are 50x and 10000x slower at encoding and decoding and still can’t even reach that ratio (I didn’t try even more extreme compression, paq8px -8 already took 20 minutes).
On the other hand,
enwik: A Case Study Where OpenZL Performs Poorly
We present this case study to show that OpenZL is not a magic bullet for all use cases. The shortcomings are twofold. First, the standard codec library can achieve good results for many datasets, but is not currently optimized for human text. Second, English text is a highly compressible format for which domain- specific transformations are especially useful. xwrt combines multiple such transformations to achieve its results. With this in mind, we are optimistic that porting text-specific codecs and text parsing will improve the performance of OpenZL compressors in this domain.


Some agent may do 100 queries for 1 user question, but a single scraper bot will do 100 queries every single second of every single day, and costs less to run than the LLM.


The simplest fix is a delay between an update being pushed and the update being deployed everywhere. Several orgs are scanning all popular dependencies for supply chain attacks and they usually catch them quickly, just not quickly enough when there is no delay.


But is it better than ncurses?
Inspect element, surely? See for yourself.
https://en.wikipedia.org/wiki/Roadkill#Eating_roadkill


The incredible thing is this is actually the result of an explicit design decision.
The compiler accepts most GCC flags. Unrecognized flags (e.g., architecture- specific -m flags, unknown -f flags) are silently ignored so ccc can serve as a drop-in GCC replacement in build systems.
They’re so committed to vibing that they’d prefer if the compiler just does random shit to make it easier to shove it haphazardly into a build pipeline.
Maybe there is something wrong with me but the “bad things are actually good because revealed preference” people and similar are the highlights of that site at this point. There is just something fascinating about it.