Show newer

@montag supposing you have a two-column CSV of english and spanish words (en-es.csv), a program that selects a random line from a csv (randline), and a program which displays the first of two values and prompts for the second (prompttest), the first case is

cat en-es.csv | randline | prompttest

“flipping the cards over” is in fact fairly trivial and natural to do in this case

cat en-es.csv | randline | awk -F, '{ print $2 "," $1 }' | prompttest

i’m not saying this just to be contrarian. but i think your original point is a bit wrong in treating arbitrary or emergent manipulation as something that needs to be “programmed in”. in contrast, i think in many cases it has been deliberately programmed OUT

we do have (very old) techniques and paradigms for manipulating data in computer systems in much the same way as one might manipulate a physical object. these techniques have, in many cases, deliberately not been used in modern applications, because the developers of those applications have found it undesirable to give users that kind of power

Copyright held by
the Los Angeles Airport
Police Department

@asterisk i worry that i made my point too subtly so to be more explicit: i think it’s entirely okay to consider oneself a “trans lesbian” and not a “transbian”. those are not necessarily equivalent terms. but i want to acknowledge that this also goes the other way, and there are people for whom the latter term is the one they identify the most strongly with. when they are talking about their communities and culture, they don’t have to be talking about you

@asterisk it is important to remember that many young trans women have not had good exposure to real (queer) lesbian spaces and that their most significant encounters with cis lesbians have probably been witnessing vocal TERFs. transbianism is a form of lesbianism which is explicitly not cis. that is why the term gets used

@asterisk as i have seen it used, “transbian” usually signifies that the people the transbian finds attractive are significantly (altho not necessarily exclusively) also trans. it often appears in the plural; e·g “transbian couple” = couple of t4t lesbians

“trans lesbian”, in contrast, makes no claim as to the cis/transness of the desired partner. in fact i think a large part of the popularity of “transbian” as a term is to counter the (TERF) assumption that trans women are only interested in cis women partners

so yes, the terms are not equivalent. but not in a malicious way, i don’t think

remember the 2000s? 

when romance was still alive?

re: floating point arithmetic 

@aescling i'm so impatient for github.com/tc39/proposal-decim to get standardized but it’s only in Stage 1

@coriander i haven’t yet obtained the ability to take pictures so they’re all i have

art take 

technical skill is cool and all but it isn’t the part of the thing that makes the art the art

Show thread

art take (in caps) 

ART IS JUST MAKING MARKS ON AN OBJECT IN A WAY THAT EVOKES A RESPONSE

Guantánamo Bay 

« Conditions at Guantánamo Are Cruel and Inhuman, U.N. Investigation Finds » honestly not sure we needed a U.N. investigation to tell us that

@jamey the closest to an actual implementation of this i have is e.g. u2764.com/NFIC/ (view the source!)

idk if you speak XSLT, but in case you do, line 64 here is the bit that handles the feed archiving: git.ladys.computer/U2764/blob/

i don't presently have any system which uses raw atom for the page contents themselves, but the idea of having just a feed (with stable archives) and being able to pass that through one or multiple static site generators (minimally, an XSLT file) to generate a browsable webpage is conceptually appealing to me

it means any user can create their own custom themed version of the entire site from just the feed

@jamey RFC5005 is a practical necessity to using atom feeds as the source documents for a static site generator and i love it for this reason

tech communities 

i mean i do :—

const getDataViewBuffer =
Object.getOwnPropertyDescriptor(
DataView.prototype,
"buffer",
).get;

// later…

const buffer = Reflect.apply(
getDataViewBuffer,
myDataView,
[],
);

—: and that’s not even a weird edge case really that’s just a normal feature of the language

but i feel like most developers would look at that, say “it is not obvious to me what is happening here”, and move on rather than try learning

Show thread

tech communities 

the other problem is that while i try not to make my code incomprehensible to people who are willing to learn about niche uses for edge cases in the ecmascript spec, it definitely is incomprehensible to the sort of person who has no interest in ever learning stuff like that

Show thread

tech communities 

no shade against applications programming or ui/ux dev but most of my nonprofessional work is extremely not that and i don’t have anyone i can say “hey check out this datatype implementation isn’t it cool” to rn

Show thread

tech communities 

i really need a hangout which is very into lisps and data witchery and not just one which is into tangible user interfaces lmao

Show older
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.