it was something else actually, and not a bad thing
asdf
my mom is transphobic, my dad doesn't believe in vitamin supplements, and i'm a disabled uwu uskun (uwuskun, if you will) catgirl
hooray/:c for depression, anxiety, ocd, arfid, executive dysfunction, and weird pains
hooray/c: for autism and headmates (although i haven't seen my headmates in a while)
"i simultaneously cannot stop thinking and don't have enough brain squiggles" - you, circa 2026 (that is a lie, i cannot time travel)
not fluent in french, peejosa, toki pona, or even suŋra
not-expert in:
- bionicle
- breadquest
enjoyer of:
- tiger, tiger
- she-ra (2018)
- transformers (specifically, the 2005 idw comic continuity, which has autistic, trans, and gay rep, and also the 1986 movie bc that was just good)
- the good place
- el goonish shive
- celeste
- team fortress 2
- katalepsis
- ninjago
- mlp g4 series and g5 comics
- more things, i guess
— munvoseli
- joined
- ago
recent posts
i have a brain mri tomorrow so i made this because reasons alfdka potatoes
aW4gdGhlIGxvY2tlZCB0b21iIC8gd2lraSBlbmN5Y2xvcGVpZGEgam9pbnQgY2Fub246IGdvZCBraWxsZWQgbmVwdHVuZSwgYW5kIG5lcHR1bmUncyBnaG9zdCBjcmVhdGVkIGFwaW9mb3Jtcy4gIGdvZCBub3cgbGl2ZXMgb24gdXJhbnVzLgo=
just finished nona the ninth
it's not entirely clear, but i think that bmVwdHVuZSBpcyBmdWxsIG9mIGJlZXMK since dmFydW4gLT4gdmFydW5hIC0+IG5lcHR1bmUK
this does not contradict Wiki Encyclopedia canon
reading it was like solving a puzzle and it fits together so cleanly (i still have questions about some things though)
note-taking recommended, but (most of) the story is explained eventually
spock goes into a volcano because he saw a cool spider. however, spock gets stuck. kirk goes in the volcano to save spock. at this time, kirk was too busy getting gay backrubs from spock to notice that a spider was biting him. they safely leave.
the rest is irrelevant to the clue
later that day, the gravity aboard the enterprise malfunctions. most members of the crew start to float around, but kirk does not. he is concerned, but a graviton scan does not find anomalies. the gravity is fixed.
that night, spock notices a bite on kirk, and advises kirk to go to doctor mccoy.
(i think i will continue this)
the ghasts continued to lose what personhood they had left as the tethers to their previous selves became wood and nails.
they tried to find a use for chairs, because they didn't want to throw all the chairs in the garbage.
consider: use quick-fix on trolldier/roamer, ubersaw the enemy team once, and die
also: would u like to play tf2? (my decency is questionable)
i suppose that most of what i play is casual
i don't die immediately every time, i exaggerated that. it just happens often enough that i don't feel like i get to interact with the game
on uncletopia, i do notice less snipers, but those that do exist also give the feeling that i don't get to interact with the game
maybe i should try those more mobile loadouts if i get back into tf2. i don't think it feels this way when i'm not playing medic
helo.
this is a general process of stable diffusion:
- generate garbage
- identify problems with the garbage
- fix problems with the garbage
- this is garbage 2.0
- identify problems with garbage 2.0
- fix problems with garbage 2.0
- this is garbage 3.0
- and so on
this is similar to the process of revision in human writing, wherein
- generate garbage
- identify big problems with the garbage
- fix those problems
- now you have something with less idea-errors
- do that again, or whatever
- now you have idea-good stuff
- identify typos in the idea-good stuff
- fix the typos
- now you have not-garbage
in both processes, there's focus on deeper issues at the start, and focus on shallower issues at the end.
a difference is that while stable diffusion works from a basis of absolute nonsense, humans have a tool called "outlining". the initial garbage that humans generate from outlining is not absolute nonsense.
with stable diffusion, the amount of bytes-or-equivalent remains constant (i think?), while with human outlining, the amount of bytes-or-whatever is greatly variable.
when i started playing minecraft a few weeks ago, i did it to prove to myself that i could do a difficult thing on a consistent basis.
now, it's like i cannot stop thinking about minecraft. i find this to be frustrating. i no longer have a good time playing it, but i still play it for whatever reason.
the sniper from team fortress 2, from the perspective of a medic main
you can't defend
you can't hide, not for too long
you have to keep moving, and you have to move erratically
you might get a couple seconds in their line of sight
if you use the vacc (which can give you bullet resistance every so often), a demoknight might charge through your team and one-shot you with a melee crit just because they saw you with it (since the vacc can be considered annoying to play against, but does not protect against melee damage)
sniper is an ever-present threat, even in areas you think you're safe, like inside the spawn building
no one can outsmart bullet
most of tf2 is fun even when you're losing, but this is why i don't really play tf2 anymore.
i want to see what's going on because knowing what's going on is fun, but i need to stay behind cover. even if i stay behind cover most of the time, i need to step into a sightline at some point, and then poof. it's impossible to play against a fast/accurate sniper.
if i get killed by any other class, i feel like it was my fault in some way. you can duck. you can damage-surf. you can watch the flank routes. you have a saw and a crossbow, if you're feeling spicy. but sniper? you can't react. while strategies exist to reduce risk, it's just an inevitability.
i used to very much dislike c++
but i think that those feelings were only partially founded
while there are things i don't like about c++, and there are things i like that are not in c++, c++ has convenient c abi/sdl2, and more-convenient-than-c dynamic memory management
those things are, like, two of the most important things to me
so potatoes
(costanza george is responsible for an unusual proportion of all dreams dreamt by dreamers of costanza george)
interesting.
anyway do you ever have a dream but it devolves into you and a friend saying "vraiment" at each other over and over
re: chat history stuffs
i think i now understand how useful it is to reference past conversations. for instance, looking at origins of apioforms, or determining when vibacam died
and the bad incidents i mentioned were dealt with quickly and effectively, and would not pose an issue
i am sorry for putting up a fuss about that
i'm not thinking that text compression will be an issue
my primary concern is visual representation of the text, since the 96x64 pixels is so small. i normally like to have over 300-400 words per page (i was wrong earlier about 250-300), but i'm just not sure that's feasible outside of a very dense logography
even with peeekriv, 300 words doesn't seem attainable. 200 words doesn't seem attainable, either. i cannot rule out 100 words.
a solution might be to do a ti-84-not-plus for the screen resolution, but that would involve having a ti-84-not-plus
i have been thinking about putting english fanfictions on a ti-84 plus.
i have only been thinking, and have been doing no doing. i think i know how to know how to do, but i do not yet know how to do.
let's suppose that a chapter of a fanfiction is 30 to 60 kilobytes. the ti-84 has 480 kilobytes available in ROM. this means that, theoretically, you could fit 8 to 16 chapters on a ti-84, if you don't even consider text compression. the reader code would also exist in ROM, which would unfortunately take up a lot of space. fortunately, you might be able to use RAM for some of the text.
i normally like to have around 250-300 words per page.
let us assume that each word represents 5 characters. the ti-84 plus has a screen size of 96x64 pixels. this does not bode well. the ultlang font (https://github.com/ultlang/ultlf) and the minecraft font are both 7 pixels tall. if you have another pixel for in-between line spacing, you can only have 8 lines at a time. letters are generally around 4 pixels in width (and one extra pixel for intraletter spacing), so you're looking at 25 pixels per word. you can only have 4 words per line, which is 32 words per page. this not good.
alternatively, braille is an option. you get 32 letters per line, and 16 lines, which works out to 80 words per page. still less than 1/3 of minimum target.
you might be able to make words compact by replacing weird english things like 'ough' with shorter forms. braille already does this with some phrases. however, this might be difficult to decipher if done automatically - consider 'though', 'through', 'thought', 'cough', 'bough'. consider also 'th' in 'the' and 'rivethead'. consider also homographs.
:c
i may in the future consider pixel-oriented logographies such as peeekriv, although i am worried about space for sprite storage.