• they/them • θΔ

scrunkly little yinglet / bat / avali /
nondescript flappy critter

does the computer
(among other things)

debilitatingly gay
in an open poly relationship

frequently NSFW 🔞 no minors pls

@trashbyte on discord

askbox is open!
ᅟ—

this user is shorter than averageno binary? no problemreject humanity
this website is gaytake back the webamiga friendly
blendercrouton.net88x31 collection


cool critters and comics:

zatzhing.mekobold60.com
pont.coolwww.runawaytothestars.com

🌎 web zone
bytebat.zone/
🐘 mastodon
chitter.xyz/@byte
You must log in to comment.

in reply to @mynotaurus's post:

it feels off to make me tag every single post i do, forever, even when its a 5 second shitpost, when the mute button is one, maybe two clicks

theres only like what, 20 to 30 yinglets on cohost. i usually post more than that in a day lol

you spent more time writing all of this and the tags on the post than you would have tagging it with #yingletspeak so how hard is it really? the mute button is easier but that means i will never see your posts, even if maybe you'd post something easily readable that i am interested in! is that really a good solution? i don't think so.

the tagging system exists so anyone can muffle posts for whatever reason they want. you're supposed to tag every little thing. even this. it's not that weird at all.

yeah but all my posts are in yingletspeak. if it hurts to read, theres no benefit to not muting me

thats the real reason why we built so many translation tools, so if you want to keep me on your timeline but it hurts to read, you can set it up in baaasically all browsers now (i think theres a chance safari might not support extensions in PWAs which. ugh whyyy)

(also im notoriously bad at remembering to tag my posts already and i only use like. 4 rn lol, i doubt id be able to catch most of my posts with it)

Safari

I remember a long time ago, I was complaining to the dev of a website that the way he coded his graphs caused it to not display properly for me, and he was like 'yeah I'm not gonna bother figuring out what's causing that bug because I'm pretty sure you're literally our only user using safari'