#nostr is not #Bitcoin there is nothing original in the design and specification yet, that isn't served best already by cloud architecture. the resource requirements for relays will grow beyond reasonable home server and small VPS operator capacity. without a mechanism for funding relay operators, and sharding the data they handle is designed, it's on a highway to centralised hell. even the minimal feature to allow users to specify an expiry date isn't there. the format is JSON which is a very bulky data encoding. it uses HTTP websockets, which are very heavy in the negotiation phase and thus not well suited to gossip heavy traffic, required to make relays peers not just servers. all associated media in notes are currently served already on a very small number of cloud based CDNs. none of the people involved in making the specification or allowing proposals in have shown any interest or understanding of any of these requirements. nostr has a chance, over the next year, to get serious about centralisation resistance and after that it's just gonna be another buzzword used to sell the same old shit.

teh word "repository" is awesome. it is from the word "repose" "he sitteth in a most languid repose" it basically means "chilling out".

this afternoon i am working on a deployment of the #strfry codebase and as i wait close to 8 minutes for it to build (C++) i'm reminded of why Ken Thompson, Rob Pike and Robert Griesemer developed the Go language. and also this xkcd: as i sit here idling shitposting on nostr.

i'm not exceptionally intelligent i just don't let my brain get filled with bullshit, so i have more storage available.