UPDATE:
UnifontEX has now received a JSTF table, a process that fixed compatibility with some programs. It also has been given a vector DFONT and a better WOFF1 in terms of bandwith. PLEASE redownload.
I use Firefox as my primary browser, so I know about that issue because I've experienced it myself. Also, I'm someone who is always worried about how people see me because I'm so used to people treating me terribly for having autism (among other things). So, like, I tend to always say "please don't hate me" at the end of certain messages, because I've had pedantic people completely tear into me for the littlest of reasons, such as semantics. As such, I've found it best to add that to my messages. Anyways, 4096x65536 1bpp indexed color PNG is definitely a corner case. No wonder many viewers choke up.
As for why I brought up the 3DO: It's because the TTF2PNG version is just the right size (1MiB, thanks to the 3DO's precedent) to be a retro Unicode font ROM in various old computers and devices. I've even thought about making a version of FreeDOS modeled after DOS/V (a version of MS-DOS made to display Japanese and Korean characters on VGA DOS machines) using it, and I call it "DOS/U" (Unicode DOS). I've also planned on using it in an open-source fantasy retro computer I make as the video chip's internal font, and the audio chip is something else I have planned out too.
I did do the Markdown image embed into the README, as well as a repo link and image in the body of the post, but regrettably Lemmy isn't making the actual post image work.
I would imagine that nonbinary versions of the Nidoran family would be somewhat in-between both canon sides, yet also deviating significantly from either, while also having SOME elements of both. Also, the symbol in the species name for such a Nidoran would be 🜬 (Unicode character for Sublimate of Antimony, which was repurposed by the nonbinary community as a gender symbol for nonbinary.)
Also, Pokemon has some interesting things regarding gender: Firstly, there are trans Pokemon. In some older gens, Azurill has a different gender ratio than its evolutions. This manifests in those games as a female Azurill turning into a male Marill after evolution. Also in Sword and Shield, there is a glitch in which a male Salandit can evolve into a female Salazzle. Salandits normally can ONLY evolve into a Salazzle if they are female. So, in Pokemon, there are examples of unintentional transfem and transmasc Pokemon.
On the topic of Pokemon gender glitches: It turns out that various glitch Pokemon have gender ratios that do not match those of any conventional Pokemon. Now, those glitches don't produce nonbinary Pokemon. Those require a Gender Code of 0xFF. If I had to pick a nonbinary Pokemon, I think that the best example would be Mew.
Here is some documentation of the program's format: http://justsolve.archiveteam.org/wiki/BWTC32Key
Also, it ended up on WikiData (essentially a subsidiary of Wikipedia): https://www.wikidata.org/wiki/Q105859280
Also, the program is FOSS. It's an open standard.
I'm a nonbinary techie who has a certificate in cybersecurity, HTML, and CSS, and an Associate's Degree in networking (and is still in college going for another IT bachelor's degree), and I've been doing technology projects for over a decade. I'm also in the video game modding community, and I also make virtual instruments, electronic music, and do digital art (including 3D printed art, which I've been doing since I was 11. I'm 21 now.) My career goal is to be a technical writer. I've used Linux for 10 years, and I've known how to work a VM since 2011. I've also dabbled in typography and animation. I put effort into my projects, often spending years on them. I even have made plans and libre blobs for ASICs I want to get manufactured. I consider myself a techie of all trades.
Oh, and just as both gender identity and AGAB are not binary, computers are also not exclusively binary. In the olden days of computing, (most often happening in the country where Tetris was invented), there were computers that used ternary rather than binary, so there was on (1) and off (0) like a binary computer, and an in-between of sorts (2 or negative one or 0.5 depending on implementation) using a form of leakage current. In such a system, gender input forms aren't like setting values to 0 or 1 corresponding to binary gender. The 3rd part of the trit (ternary equivalent to bit) would in those simplistic systems (Pokemon Crystal caught data OT gender, plus ALL Pokemon games since) would be outside male or female. Now, ternary computers went obsolete decades ago, but there are still companies out there making ternary architecture. Samsung decided to jump into it to improve computing technology, and people have been saying it will come back into play. And it looks like that WILL happen. A lot of the quantum computing being worked on is based around ternary, because there's more states a value can be.
If ternary isn't outside the binary enough, it's important to note that the first computer (the Babbage Analytical Engine from the 1800s, which was all planned out but never built, yet Ada Lovelace decided to devise programs for it beyond Babbage's original intent for the device) used decimal entirely rather than binary. Mind you, the device was mechanical, and was meant to deal in numbers. HOWEVER, its input system was in the form of punched cards, so not all of the machine was strictly decimal. But it mostly was.
If decimal isn't outside the binary enough, there IS a number base that DEFINITELY is. Base32768, which is great at making binary data no longer binary. Base32768 is special in that 15 bits of data are stored per Unicode Plane 0 (Basic Multilingual Plane, whose characters in UTF-16 take up exactly 16 bits) code point. The resulting efficiency assuming no compression is involved is an efficiency of 93.75% (15/16ths), which is FAR more efficient than Base64 could ever do, which, when you combine it with heavy compression like my program BWTC32Key (http://b3k.sourceforge.io) does (it also uses AES256-CTR after the compression but before the Base32768), it can justifiably be an archive format when stored as UTF-16. BWTC32Key's files use a .B3K file extension. These files are special in that their base is NOT binary. Their base is actually Base32768, not the Base 2 of binary. Also, some programs consider text documents already to be non-binary files. .B3K files are literally just UTF-16BE text documents that store data. BWTC32Key is something I wrote in 2019 after 4 years of effort and I spent 4 more years updating and adding features to it. So even modern computers that aren't quantum can escape the binary.
So yes, computers aren't only binary, even now. Database admins, web designers, and other developers should do well to remember not to have gender, or birth sex (something that should not be asked for willy-nilly), be a boolean value in their code. I mean, BWTC32Key is written in JavaScript and is quite literally a form, except there is no server involved, and everything in it is inline. But it's still a form. I've seen my fair share of forms that are not inclusive to intersex and nonbinary people, among other issues, and as someone who has written code using form elements, I can say that those forms have significant problems in their design in addition to being exclusionary. If you are a developer, don't replicate that code. Also, ask LGBTQ+ people what they feel is a good form design, and also include a write-in box so people can put what they want in. Oh, and by the way, please support Unicode passwords. BWTC32Key is really good at making them in all their secure glory, but nothing supports them yet, even as 4090s are cracking 8-character ASCII passwords in 48 minutes. Web designers and programmers in general need to be more inclusive of both security and diversity.
TL;DR: Computers aren't binary either.
My fursonas are what I am.
Thanks!
I have a template at http://stgiga.github.io/gigaware/5box.png which has more boxes for more reactions.
My experiences with the medical establishment in general have been questionable.