json turns young boys minds into whores

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

Since no one asked we've finally delivered: a full-blown FUSE filesystem for all Nostr events and metadata.

nak fs /mnt

cd /mnt/hodlbod@coracle.social

I was going to make a shiny video of this but the result was too bad, so please someone make one and post it here.

In the meantime I have these amazing screenshots of the most beautiful file explorer I could find on my computer:

nak fs --sec 'bunker://...' /mnt

cd /mnt/@me/notes

echo 'goodbye stranger' > new

cd /mnt/@me/articles

mkdir whatever

cd whatever

vim content.md # write a very thoughtful article

vim title # write a very thoughtful title

touch publish

I always try to cable as many devices as possible apart from the phones and some wireless only devices. I have one extended AP but it is wired back to the main switch

GM

I’m by the seaside

today i am learning how to actually write a full, proper #http server using the #golang standard library for handlers and multiplexer (router)

looking at all these silly things, gorillamux, go-ch, and i just wasn't even considering gin and all the rest idgaf i want to learn the base of this, i already have code that does this shit but i need to integrate this generated openapi 3 API i've designed correctly

i'm doing it for #realy first, but next week i literally have to do this exact same thing for my #fiatmine job, so i'm killing two birds with one stone today, once i figure out how to plug in this generated code, then clients can be built from the same spec via code generators, which massively reduces adoption friction - i mean, this is why REST dominates the industry now, and it's really needed to eliminate adoption friction for #nostr because the way it stands right now, the SDKs that exist are awful, inconsistent, inefficient, and usually buggy NDK i a bastard piece of shit, so i'm told, and my colleagues have forked it and are superseding it with WASM based C++ generated code

what i'm building here will be a huge icebreaker for nostr apps to integrate with web 2.0

i'm not so much concerned about the lefts running their own relays, idgaf about what those drones are doing, but what i am concerned about is leveraging the eventbus/pubsub architecture of nostr to facilitate real world deployments and have people paying nostr devs to build this stuff, instead of begging from bitcoin whales

It's not a CPU, it's not a GPU, it's a _ _ _ !!???

Driver done 🫡🌿

A house in the jungle where grown men gather shirtless to play with each other’s buttholes and post videos of themselves paying local fruit merchants with bitcoin.

Stop pretending the Primal House isn’t gay as fuck.

This week I received these two devices.

Do you know what they are for?

Nós vamos abrasileirar esse português europeu do nosso amigo aqui 🤣. Por sinal, ainda não encontrei ninguém de Portugal no Nostr, você conhece alguém?

asked google to translate and... WTF???

É claro que você deve se sentir bem! Com todo o respeito ao legado de Portugal e aos meus colegas lusófonos de todos os países do mundo, mas se você vai se dar ao trabalho de aprender português em 2025… 🇧🇷 it is! 😁