Luke Wren

@wren6991@types.pl

Cursed computer architecture enthusiast.

Engineer at Raspberry Pi. 日本語下手。 He/him

Replying to an earlier post

re: aipol

@whitequark After burying my head in arxiv for a while I've decided LLMs themselves are interesting (but don't exist in a vacuum). When people call them fancy autocomplete, or make a big deal about non-determinism, I think they're directionally correct in noticing the stank around LLMs and avoiding them, but it still comes from a place of either wilful ignorance or uncritically repeating things they heard on the internet. I don't look up to that or aspire to be like that.

To make a more specific point, I'd like people to stop interpreting everything that comes out of a softmax() as a probability density function just because it's non-negative and sums to 1. Next-token prediction is a useful objective for pre-training because it's a way to kickstart the model to learn higher-level representations unsupervised, but the reason it's called pre-training is you *keep going after that.*

If it wasn't for:

* the data theft,
* the vandalism of public internet infrastructure,
* the environmental damage,
* the widespread copyright laundering and "clean room" re-implementation of code that is in the training data,
* the erosion of social norms around contributing to open source,
* their ability to one-shot intelligent people into believing bullshit,
* their corrosive effect on your intellectual abilities,
* the concentration of the means to write code in a handful of US companies,
* the impending financial crisis,

...then I'd support their use. I don't see most of these changing though. The only actually-open-recipe-open-data models I'm aware of are Nemotron, and they underperform given their size and architecture, so perhaps the secret ingredient is crime.

Replying to @wren6991@types.pl

Ok, side quest over. I can store a novel in a mere 74 MB, and it works on both stock and open firmware (using XTEINK's weird custom bitplaned image archive format: gist.github.com/bdeshi/f605499)

Special shout out to MuPDF for implementing about 30% of a browser layout engine in C + Python, but unfortunately I need the remaining 70% too. This was a good PoC though.

Japanese text rendered with anti-aliasing on a smol e-ink device.
ALT
A dithered 2bpp image above some anti-aliased text (which is not dithered).
ALT

Replying to @wren6991@types.pl

crosspoint-reader's default CJK font support leaves something to be desired 🤔

crosspoint-reader-cjk looked promising, but on closer inspection is a vibecoded slopfork that has broken font rendering (unreadable) for English text in the UI, crashes when opening any of my epubs, and has a broken recovery menu. Uninstalling was an adventure. Not going to link it for obvious reasons

All of the characters are just "missing character" question marks
ALT

Replying to @wren6991@types.pl

Open firmware here: github.com/crosspoint-reader/c

The 1-bit font rendering is a bit cromchy, I wonder if I can do anything to improve that. It renders images with what looks like 2-bit grayscale?

Firmware for the Xteink X3 and X4 e-readers. Contribute to crosspoint-reader/crosspoint-reader development by creating an account on GitHub.GitHubGitHub - crosspoint-reader/crosspoint-reader: Firmware for the Xteink X3 and X4 e-readersFirmware for the Xteink X3 and X4 e-readers. Contribute to crosspoint-reader/crosspoint-reader development by creating an account on GitHub.