@vertigo An appliance is physical, with hard constraints. The barriers between programs are conventions and tradition. Only in rare cases due to best practices.
Failure to discern between the simulacrum of something real and the real thing is not a problem of actually-existing technology that actually works, it's an ontological problem imposed by force of an epistemic consensus.
The problem at the root of all evils of the anglosphere is the idea that you can make your own reality just by wishing it hard enough.
Meet Sci-Hub's Alexandra Elbakyan, the mastermind behind the liberation of 50 million journal articles that I refuse to call "stolen", shattering the $10 billion-per-year paywall of academic publishers.
@djsundog@vertigo A square of 64 x 64 RGB pixels holds 12288 bytes of data, uncompressed. That's way more than the usual toot can hold as text, and it's better than using some complex metadata embedding mechanism.
@bob For example, the output of 'ls -al > ls.xtxt' could be an extended text file, with not only the readable text output, but also the metadata for each file listed, in a stream separate from the text/plain output.
So this is not only relevant to the semantic "web", but all the semantic things.
@bob I have some code I wrote some months ago. It's really trivial.
The only problem with multiplexed text files is that they're not text/plain but text/extended, so they don't play very well with standard unix tools. So I started to write a few equivalent tools to test the concept. (muxt, demuxt, and muxcat)
Eventually those can be made simple drop-in replacements for the normal unix tools.
@bob Unfortunately multiplexed text means that some new tooling is needed. But it's so trivial to implement that I think that may be a sound trade-off.
@jjg@clacke I feel the need to stand on a soap-box here. :)
We need to remember that RISC-V is an instruction set architecture. It's a specification, and therefore, has nothing to say about whether or not instructions are speculatively executed, in what order they're executed (within reason, of course), etc.
Specific implementations may or may not be affected. KCP53000, my own RV64I CPU, is not affected. Reports today confirm neither are cores built around Rocket. BOOM remains uncertain.
@ghost I would argue that the distraction economy is actually more beneficial to those who don't make very good things. The makers of good things are busy making things good, not polishing their sales pitches, so they're at disadvantage compared to those who don't have to invest the time making things better. They only have to make the pitch better.
@ghost You're absolutely right, and it's sad but most people rarely get past the marketing pitch. Part of the problem with the distraction economy, people have too many distracting things targeting their heads and it's hard to tell what's useful or convenient without making a conscious effort to find out. So even people who make good things need to shout louder if they want to get an audience, even if it's deserved attention.
@h definitely... i was just saying earlier how tedious it is that we have to sell accessibility features as beneficial to everyone— like to get the tech bros to care about audiobooks we gotta market them as something they can listen to at the gym or in the car— but it’s true. people in general benefit from accessing info in different formats. i used to LOVE audiobooks when i was driving a lot. now i like them because i don’t have concentration to read.
@bob@ajroach42 Hehehe, it's ironic, yes the keyboard was terrible. A friend had an Atari 800XL which had a great keyboard, but where I lived the ZX Spectrum reigned supreme in terms of community and software availability. The Sinclair QL, and the +3 were only marginally better.
But definitely my intuitive longing is, and has been for about 10 years, for something semantic-y, in the sense of a 'giant linked space of data in which I can store and retrieve really fine-grained facts that reference each other'
@natecull @ajroach42 @enkiv2 Almost two decades on I think it's possible to safely conclude that the semantic web as conceived by TBL and implemented in RDF was a failure.