I've been scratching my head trying to think how to package assets for my #lispGameJam project, I really REALLY wanted to be able to inline assets as raw hex code, like I normally do for uxn projects, not have to read binary files, so I added a special form with square brackets that lets me to just that! This is the first sprite(a little arrow) I was able to store in my source code.
and I think most people experience it as like flat triangles and squares in a biology textbook where it's like you know there's an arrow between like this triangle and this triangle is just like doesn't make any conceptual sense and is like confusing and annoying
Um but nobody has done research on the positive side of these heuristics. And so, I think that's a bias on the part of the decision bias researchers that they're only looking at the down arrow. How do these heuristics get us in trouble? And they're not looking at the strength of these heuristics.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.