Remote

Lain(e/o/a) Taffin Altman

@pthariensflame@social.treehouse.systems

mastodon 4.6.4+glitch-th

I’m Laine, Laino, or Laina (they’re all equivalent)! I love computers and math and computer math and math computers and math math and computer computers—interests include linguistics, type theory, programming language theory, constructive foundations, and the wide array of GSSRMNM topics (gender, sex, sexuality, romance, multiplicity/plurality, neurodivergence) and anything else in the generalized “queer” space.
Gray ace/bi | aro | NB | plural | AuDHD

0 Followers

0 Following

10 Posts

Joined November 14, 2022

Age:

Above 30, Below 60

Pronouns [EN]:

they/them

Pronombres [ES]:

elle/elles/nosotres

GitHub:

https://github.com/pthariensflame

Bluesky:

@pthariensflame.bsky.social

Tumblr:

https://www.tumblr.com/blog/pthariensflame

Posts

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · May 09, 2026

Replying to @viq@social.hackerspace.pl

@viq@social.hackerspace.pl @caroline@chaosfem.tw At that point, by virtue of it being all of the objects and therefore belonging all of the places, it is automatically already put away where it is.

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · May 09, 2026

Replying to @SRLevine@neuromatch.social

@SRLevine@neuromatch.social @caroline@chaosfem.tw What matters for cleaning is surface area, though, so it’s still an improvement.

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Apr 07, 2026

Replying to @gracie@mk.absturztau.be

CW: snuggle RP Hover or focus to reveal Sensitive

@gracie ‹gently wraps you up in our fuzzy wings›

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 19, 2025

Replying to @Mara@hachyderm.io

@Mara@hachyderm.io Idea: doc alias?

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 04, 2023

Replying to @pthariensflame@social.treehouse.systems

@wizzwizz4@fosstodon.org @atax1a@infosec.exchange Actually, would either (or both) of you want to participate in some of the design process? I'd be very happy to get some more ideas than just mine! I've started typing up the document properly and I'd like to be able to discuss things in this architecture, both specific concrete elements and broad design principles, in closer to real time. Let me know if there's a platform you prefer for that! I'm on both Discord and Matrix, and I'm sure I can adapt to whatever else is out there! 😃

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 04, 2023

Replying to @wizzwizz4@fosstodon.org

@wizzwizz4@fosstodon.org I haven’t! This may actually be the first time I’ve talked about it anywhere at all. I’ve been encouraged to keep going though, so I’ll let you and @atax1a@infosec.exchange know when a preliminary spec document is ready! Expect it to have decent coverage of the ISA design but no parts of the binary form locked down yet.

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 03, 2023

Replying to @datenwolf@chaos.social

@datenwolf@chaos.social @thephd@pony.social memset_explicit exists now, at least!

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 03, 2023

Replying to @ids1024@fosstodon.org

@ids1024@fosstodon.org @thephd@pony.social I think the requirement for “nontrivial” makes this answer immediately “none”, for one simple reason: minimum implementation limits. A nontrivial C program, even if otherwise strictly spec-compliant, is definitely going to blow past limits on function name length and source code size and number of variables in a file and so on.

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 03, 2023

Replying to @atax1a@infosec.exchange

@atax1a@infosec.exchange @thephd@pony.social I should really write this up and publish it even as a very rough draft!

Lain(e/o/a) Taffin Altman @pthariensflame@social.treehouse.systems · Nov 03, 2023

Replying to @atax1a@infosec.exchange

@atax1a@infosec.exchange @thephd@pony.social Yeah, this and many other such things means there is no language at all that lets you “fully control the hardware”, since the lowest-level control you get (ISA and/or programmable microcode) is still a heavily abstracted interface. And that’s why I’m developing an architecture spec that has linear statically-typed values behind a large number of available references (“forwards”) as the only directly accessible form of memory. Down with (architectural) registers, down with byte-addressed memory, down with transparent pointers, and down with the executable form of an ISA having to be the same as its stable form!

Lain(e/o/a) Taffin Altman

Posts

Remote instance