Well on a brighter note I found my Polaroid camera!!! Lmfao it’s been on the bookcase in the living room in under a teddy bear… no wider I couldn’t find it…

Welp looks like putting in a new toilet might be a little more work then we first thought… gotta do be flooring as the old linoleum tiles are popping up… also appears the original cast iron flange is cracked/ broken… FFS…

example of how ambiguous nip specs are:

it is the expectation of a user that if they mute through the only mute button in a nostr app that it mutes in other apps too

nip-51 contains the option for clients to make this decision for you and not implement the other

this is a fork, if you only implement one mechanism

this is not interoperability

i made a bad boo-boo with my lightning node and had a channel open that was stalled because of a burst of shitcoinery pushing fees up (i should have just waited another day dammit) and i used blockstream green (mistake #2 ) to CFPP on it... twice

gonna check the blockstream wallet actually

but i've also contacted acinq because it was with their node and the sooner i ask about it the better, because their logs should have my node ID in there and be able to tell me about the status of that channel opening

i strongly suspect it's just stuck in HTLC limbo and will return to my address later but i gotta follow this up

yeah, bs green wallet reports the same balance based on my LN node's seed so, other than things unrelated, i can now see a detailed log of my LN node onchain wallet history with it

i hope acinq is nice about this and gives me accurate info, i'm pretty sure by protocol it should be in HTLC limbo waiting for a timeout block height or whatever the things are, been a while since i was deep into the LN protocol voodoo... it is complicated shit, i can't really tell you the details of it except i remember the cascade process of HTLC times ascending through the payment path to ensure that if things go pear shaped the payment balance change reverses

and that is one of the key things that distinguishes lightning from all the other, more primitive shitty L2 designs, like drivechains and parachains and all that other shit... it's resilent

so, i'm sure i will get my sats back under control, i'm just a bit nervous because they are in limbo, i'm sure it will take 5 minutes for acinq's nice techs to inspect the logs and confirm the status for me

never ever again tampering with channel opens, damn, ouch

it is no coincidence that "whores" and "horse" sound the same, almost

most horses will let anyone ride them

untyped, unstructured JSON arrays are the devil

to express them in openapi you have to define them in components and combine them to make them work properly

i am really wasting a lot of time addressing this lunacy in the retention field of nip-11 on this, like, how do i... ok, it's this "oneOf" shit

i am appalled at how unnecessarily complex this is, and the fact that i'm editing the spec on a runtime environment that is executing this lexical analysis and static syntax checking inside an abominably poorly designed interpreter engine instead of a fucking at least bytecode interpreter, it takes it like 7 seconds to parse the grammar of edits i make sometimes

a great example of the #interop failure of #nostr #devstr

i mute a user in jumble

it is still visible in coracle and nostrudel

i mute it also in coracle

it is still visible in nostrudel

i close coracle and nostrudel tabs forevermore, i'm not tolerating this pollution of my computer's memory and my screen's pixels and the waste of CPU and memory (ie, electricity bill and damage to my hardware) that this all entails

because only #jumble actually is respecting me, as a user, with the small exception that #coracle lets me totally hide any notice of the trash i muted and if anyone wants to actually interact with me, they should stop being a twat in-group brainwashed drone, once i mute you, it's pretty much gonna be forever, i'm provoked to unmute people that are in a mode of behaving civilly but honestly, i wish i wasn't, @npub1syj...f6wl please enable fully hiding muted notes, instead of just wasting almost as much space on my screen and wasting my time downloading it

#realy does not send you events at all from users you muted, so long as it has your mute list to consult before returning your results

this should just be standard. no bandwidth, no compute, no memory, and no dfisplay bandwidth wasted on shit you don't care about