i've never been able to get it working with brave

it's like parasitic organisms taking over their hosts.

just give the baby fluoride, and then the nonces in the school will take it from there. thanks.

it's almost like someone knows that the best way to make a child into a psychopath is to make them drink fluoride. really, that's what it looks like. this is psychos reproducing.

man, wireguard is driving me bonkers tonight

easy, making fixed IP nodes form a mesh

seemingly impossible to get a client to connect to one, or all of them.

so, i get the mesh working, great, over SSH, all three nodes ping each other on configured addresses

then i try to add the servers to my local wireguard peer and add the peer of my local to the remotes, ded. lose ssh connection. the end. game over. try again.

4 times later i'm ... not so inclined to try again

i guess i gotta read some more shit. man, i used to read good. i don't read so good these days. i gotta handle this.

i'm lovin' it

nostr memes are the best non sequiturs i've ever seen in my life.

they have been doing this for at least like 15 years, it's completely fucking deranged

instant follow, my spidey sense never fails me and i see the pattern here

i am a #ragecoder and i write code to fuck these cunts shit up

i strongly suspect that more than a few of the assholes i hate in the rockstar brigade are in a conspiracy. this just shows how far back it goes

also, here is my surprised face, what a piece of shit

by which i mean, that motherfucker is a vampire

a malicious insider. spooks and their ghouls are everywhere.

also, he is probably the absolute best javascript programmer in all nostrland. hzrd149 is good but he's just got that japanese minimalism down pat

nah, it's high grade japanese steel.

i think you need to consider trying jumble.social or something. i don't even see this.

i don't think it's gonna be anything specifically malicious. it's just plain old domain squatting. "oh it's a different name, but maybe they will pay us to transfer it to them"

malicious in the sense that they are making a calculated guess that a unique name that isn't registered that has some registered might be rich and then they will not care to spend $500 to nail down this one which isn't as ideal but ok.

the monopoly on TLD is the suck. you sholud be seedsigner. as in like www.seedsigner.

this is only 9 months away for me

yeah, i got intp when i was younger but now i fairly consistently get INTJ so it obviously changes with age. i figure "wisdom" makes you more quick to decide

marathons are overrated. sore knees come from doing high impact exercise like running or skateboarding

but joint problems are a sign of autoimmune problems as well, though also from scarring. i have both, and i'm 49.

i think it's other genetics in this case tho

except i have this in common and also only just started to look a bit old in the last 3 years

it's an essential part of survival. you use what you got.

i'm so far beyond 30 but everywhere my youth was advantage before then now has been replaced with wisdom and flexibility.

that's why old bastards are grumpy

i hardly didn't even notice until i hit 40 that i was slowing down haha. then i ground to a halt at 45, because i got very sick. i'm coming out of it now, and experience substitutes a lot for strength. and you can still be flexible, that's something i find easier to keep than strength also, since it isn't so much bound to hormone levels.

well, i think that it's not really useful for one-off stuff like relay configurations but for distributing them it might make sense, as it saves some on bandwidth. but i'm not seeing a strong case for this. events are not that big in data size, especially not when encoded as raw binary. typically follow lists are like 1/4 or less the size of the json

i've been thinking about this and it can be a privileged event that only the relay and the author can read, and using bloom filters to designate the list so even if the list is leaked you can only check it one by one to see which npubs are included

routing on networks uses lists, it's lists all the way down.

local relays definitely are a thing. especially they should have little crons that fetch from other relays. and also there is a great need for inbound routing so users can also have their frens write straight to their relay.

some of these obstacles are systemic issues on the internet that bias against p2p, and most p2p protocols are quite deficient, but largely because of the restriction of routing.

other lists have to be supported by the client, that's a major problem.

also, it doesn't have to be public, mute lists have a private section now too.

the main problem really is just that primal pretty much administers the God List and they are extremely biased about who gets on it. the real challenge is a good client to onboard people to. coracle probably could do the job, and even he made it so it can be whitelabeled. the other thing is outreach to other social networks where there might be interest.

it's sold at most garden stores as "dusting sulfur" and other than that you need to collect guano and powder up charcoal. voila, black powder.

i describe it as the eastern switzerland. probably i would rate it higher than switzerland these days, also. technically my oma was swiss.

trieste is a pretty little town. i remember the park there, big pretty park.

so, it was slovenia. i never went to rostijl in slovenia. i had burek tho. i couldn't say that slovenian burek was better than serbian burek tho. same same. the best burek, much better than turkish.

i'm debugging a http SSE subscription mechanism at the moment. almost got it working. events are now being delivered and all, just not sure about whether it's properly removing listeners

so i've been posting events to wss://test.mleku.dev to trigger subscription deliveries. i had to add a new "whitelist" feature to the relay because omg the amount of clients sending events and then not responding to auth, it was a constant stream of bullshit i couldn't see any of the messages i was sending to it.

man, so glad i fixed the weird race condition bug with the spider on #orly

now i'm watching the logs of my test and prod deployments and not seeing anything that bothers me, and also giving me a small smug sense of satisfaction that people are already using them both extensively.

my first formal position of employment involved working with a government IT department, specifically accounting. the number of things they did with excel was hilarious.i didn't do much work with excel in my role but i learned quite a lot about writing excel scripts at that time.

funniest thing about excel spreadsheet scripting is that it seems to be something that women are particularly good at. there was a lot of women in the office i worked in. it left me with a vague impression in general that women were good bookkeepers, and later encounters with book keepers confirmed this. it's beautiful tho.

not saying in all cases women are not capable of really inventing things but they sure as hell are good at operating calendars and ledgers.

i cite the case of Mileva Maric, wife of Einstein, for this. i'm pretty sure what the women of yugoslavia say about her is correct: that she was the actual inventor of relativity theory. so, don't misread me by thinking that women are not capable of invention. to the contrary, i think they are very capable as a class of human in the process of invention. probably they originally invented math and calendars. the motivations for which should be clear, since the first big insight about these two topics logically would have likely emerged from those who are most subject to biological clocks. ie, fertility.

not even scientific papers lack an abstract at the top that summarises the text.

i was feeling this urge to feed it to an LLM to write one for me but then i thought better of doing that because of the lack of credibility of the user who dropped the link.

i couldn't tell what the stupid text was even trying to propose.

and it is so friggin long there's no way i'm reading it without a bit of newspaper style journalistic structure.

i can't see myself using it personally but it will be fun to see them being used. probably could be quite useful for things like deciding on venues and activities for meetups.

took a while to dig around and find the problem. it's partly related to the fact that the event and tag unmarshaler doesn't copy memory (which makes it faster) but this also makes concurrency cause funny problems.

what was literally happening was that an event was being decoded, and then the buffer holding the memory where an event was sliced out of, was then overwritten by the next incoming event from the relay the client was connecting to, and by the time the event was being saved to the database it had already been mangled. i think also the event ID, signature and pubkeys were being overwritten as well, because those also are zero copy operations.

lesson learned: zero copy codecs must be paired with fresh buffers from the network transport. otherwise you get data races.

now, i'm getting more in the frame of mind to think straight, and this is because i had a can of red bull. which in combination with the allergy messing with my brain suggests that eliminating the allergens will help me quit these bad habits. probably nicotine is also suppressing allergy symptoms on my brain. my brain is literally swelling and this is messing with my thinking, reducing my IQ dramatically.

glutens are the worst, second is caseins and especially caseins that have been ultrapasteurised, most likely unpasteurised natural milk would not do this. but it's what did it to me today. my brain has felt like mush.

so anyhow, next, i guess, to figure out how i need to write this publisher implementation for the single-listener design i have come up with. and then, with that, i think i can call the HTTP API an MVP. there is other methods i could optionally add, but i just want to put it to bed with a feature complete - compared to the websocket API, set of methods. import and export are orthogonal to this, but are essential features for administration. the event publish, filter search and subscription mechanisms make basic nip-01 feature parity.

i kinda promised myself that by the end of this month i would be starting on the job hunt for real. so, hopefully i can get this subscription system done in the next three days. preferably today, but with a mushy brain i'm probably not gonna get there that soon.

very nice, well done nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl and nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z 👏👏👏

so, i think i have found it. it's a buffer being reused in the client library, this is why it didn't appear before, it's been some time since i was using the websocket client library.

the fix was simple: just stop reusing the buffer, make a new one for every received message. the end.

it was particularly affecting follow lists. it was also causing a race condition because the buffer was being used concurrently. with this one tiny change, allocating a new buffer for each message, the race condition has gone away and so has the mangled tags.