i just remembered the proper word for 99% of all javascript and related web dev error messages:

OBTUSE

adjective

- not quick or alert in perception, feeling, or intellect; not sensitive or observant; dull. Synonyms: unobservant, dim, slow, boorish, gauche, imperceptive, blind, insensitive, tactless, unfeeling

- not sharp, acute, or pointed; blunt in form. (of a leaf, petal, etc.) rounded at the extremity.

- indistinctly felt or perceived, as pain or sound.

it is the exact opposite of "ninja" and "smart" and "sharp" and "precise"

haha #mochi the #catstr is looking a bit under the weather at the moment, more yellow and viscous goop in his drool today, and he has been a bit more sneezy than usual, i guess he's still fighting some kind of sinus infection probably auxilliary to his gingevitis

i probably should take him to the vet for some dentistry but the one in Sao Vicente did not exactly charm me, probably i would go to the one in Santana instead next time

but it was so funny, he really hates me cleaning his drool and weepy eyes, and he totally got wind of what i was doing and did some acrobatics and shot outside

what was funny was i was just saying to him "why don't you want to go outside?" haha

ok, done.

i made a boo-boo with my channels, the fee rate was too low and a burst of high fee transactions came in and delayed opening for half the day

i used CPFP to boost the fee rate on the tx but alby hub doesn't recognise this and it still thinks the transaction is unconfirmed

i'm guessing that what will happen is the other side saw it open, but then my node didn't talk about the channel, and eventually it will get force closed

i tried to close it but it's not associating with the opening TX so it won't work

my guess is i just have to wait?

in times of mass stupidity of people storing tiny JPG files on chain due to some retardation campaign to milk retail, this can happen, so it would be useful to add a fee bump interface i think, or alternatively, have the front end recognise a CPFP and change this... or is the back end happy and just not presenting what the node is seeing?

according to the debug tools the transaction on the channel has zero confirmations

i assume that it will just get force closed because it looks like the node hasn't recognised the updated opening TX and the other end probably also maybe didn't see it so it has a close at some point i guess...

i have #wireguard VPN on my #android phone (android version 13, blackview BV4800) and i set it to the "always-on" mode and was dismayed for some time that the stupid thing seemed to disconnect randomly

for whatever reason, making it "always on VPN" doesn't do two other necessary settings, inside App Info:

- Battery usage - set to unrestricted - it needs to be always on, duh Optimized does not keep it on or turn it on on demand as you would expect

- Unused app settings - Pause app activity if unused - disable this, because it should always be in use, even if you don't open its' UI

since changing these settings on it, it now stays connected as it was expected to when set as Always On VPN

fuck you google, and the whores you rode in on