after this point, all who quote twatter are doxxed.
you may now laugh at them.
Engagement was always a horrible metric. Attention was always a horrible currency.
My thesis remains unchanged: #bitcoin and #nostr fixes this, if we get the #value4value part right.

https://dergigi.com/2022/12/18/a-vision-for-a-value-enabled-web/
or in other words, eliminate the fiat spigot, since the arbitrary firehosing of new tokens leads to elaborate and sensless games.
paul is a name that in its many variants illustrates one of the most hilarious things about european languages.
there's paul, pablo, and pavel/pavla
they all are from the same origin, yet the U, V and B are mixed up.
when you look at all of the different languages, including the cyrillic ones, you can see that the U, V and B are mixed up, in some languages the B is pronounced as V, in some, the B is pronounced as F if the next consonant is unvoiced also (eg, AVTO in russian and bulgarian, written АВТО).
the weirdest thing about it is that it seems like this mess originates from attempting to pronounce latin *script* in a non-latin tongue. like the spoken form was not how it traveled to some places.
similar kinds of transcription and pronunciation errors can be seen as the source of the phonetic rules and spelling rules between languages. many latin languages use a V where we use B in english, and use a B where we use a U in english. eg Pablo = paul.
it's not just the inspection though, because very often timeouts are too short to tolerate the general slowdown of having compiled it to be debugged.
doesn't work in a sub-100ms timescale.
when someone makes a debugger that makes this kind of state inspection post mortem i'll be using it. it's simply impractical for especially low latency network protocols, the debugger assumes linearity and single threaded execution. even the Go debugger, delve is like this, despite most Go code being highly concurrent and parallel and time sensitive.
i admire the skill of a good needle operator. i'm pretty handy myself but sometimes veins are extremely stubborn and wriggly and small.
first time doing something is always a mess. i was removing the stupid factory plastic wrapping on one of the light fittings in my apartment that nobody had tried to remove, because both of them had ugly half torn off product information labels still on them.
the first one i wound up messing up the three part layer of glitzy paper underneath the metal frame with the retarded scratch-protection plastic wrapper layer, and then eventually in the wind one evening the paper flaps off and gets half burned on the bulb.
the other one is perfect, and i cleaned it up in like 1/10th of the time.
#gm
today i finish signr at long last.
expect an announcement later on.
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
what do you think about this hot take of how I see supporting personal relays? the accepting of events that have been accepted previously may have compute limits but it also is far under the threshold for having relays of 100s of members if you expanded to a regional relay or local relay.
coracle runs a relay locally, that's why it still gives a rendering when it's offline.
being led along for a long time while putting out an extraordinary amount of effort about getting compensation and then having the rug pulled after a month of endurance.
just happened to me recently.
debugging concurrent code with microsecond intervals between events makes debuggers worthless. printing logs is the only way to get something to post mortem this kind of code.
when i write code it's either too short if it's linear and too parallel, concurrent and time-dependent if it's not linear.
concurrent solutions can do a lot of things that you can't do with long winded single threads. number one thing is extremely low latency responses. parallel throughput tends to just be simple single threads and usually barely needs debugging.
nostr:npub1mlekuhhxqq6p8w9x5fs469cjk3fu9zw7uptujr55zmpuhhj48u3qnwx3q5 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m nostr:npub1dld9hn3gsgtkh7atl26s8gd49qfjjkpdw8ztap9mk4n7vhq60y0satfd8s Way to get the point wrong! I actually **like** Nostr for many of the reasons you listed.
But maybe one reason why I don't like Nostr is that in most interactions I've had people just project on my words whatever bugaboo they think they are fighting instead of spending a minute reading what I wrote.
you aren't compelled to see it either. nor do i have to waste my time with your vascillation.
irony is a nostr user posting from damus about how cultish the majority of bitcoin/lightning/paleo/christian/traditional values nostr users are
get over yourself, everyone has an opinion, and other organs too.
oh, that takes one extra step:
use that quote item, then grab the nevent string that appears, and then go back to your reply, like so:
as usual i have got to the very last bit of a section of work, and i have insufficient brain remaining left to complete the task before retiring to the horizontal.
well, actually, probably need to do a refactor after that to push the functionality into the library section but the CLI part is done.
tomorrow i should achieve signr v1.1.0 and be able to move to gitr and put them nsig's into Git repositories in place of gpg/ssh signatures.
nobody made nsig's yet, we have keys but no generic signature made with them, only nip protocols. soon you will be able to enable people to verify your files and git commits with your npub
and on that note, GN nostrians.
i miss my speakers and gaming rig and fast ssd but i survived and may just yet make the leap across the abyss thanks to having kon mari'd them.
i travelled up and down the east coast of australia with a big backpack at first and then by half way through it was just one little shoulder satchel.
the japanese art of minimalism is GFY.

