is there a nostr nip-07 keychain extension that lets you keep multiple nostr identities and doesn't involve email like alby?

#asknostr

putin is WEF simp just like the rest

ah yep, but note that in alby these accounts are tied to an email address...

yeah, i saw the password has a prefix that looks generated

alby only handles one identity currently also

but yes, ssh has many, there is a key name which you set in the config to associate with a URL

oh i see, looking at my keepassxc yes indeed i stored a password for it

it seems very redundant

is the signup flow include this? i didn't realise it did, i thought it was just based on nostr cryptography?

i don't have a password for my nostr.build, i use NIP-07 and alby nostr keychain and i pay in sats

we have had EC PKI for over a decade now, it is time to move on, i agree

a keychain like this literally only has to be a few keys which you segregate for purposes or alts

there is already public registries of these keys but honestly the state of PKI is still pretty bad, and you would have to be silly to have me believe that pgp is fine, if it was then explain why it's becoming very common to use SSH for git repo auth?

i wouldn't say it's a symptom of a broken system so much as a failure of tech companies to care about security, which should be considered to be suspicious

that's worse than broken, that's corrupt

yeah, ah ok, so maybe i will stick with badger then, the only thing that irks me about badger is i see by its imports it pulls in opencensus.io dependencies and i don't like the sound of that, sounds like telemetry

range scans? on badger or? what is a range scan exactly anyway? surely it's still some kind of key iteration?

badger definitely can do range scans if you implement the keys correctly, it can even keep the key table in memory so those scans are extremely fast, it's just a matter of defining a key format

i'm kinda focused right now on hitting a milestone target in the next two weeks on the project i'm building with this but in two weeks i think i can be confident enough to pop it out by itself, since if it reaches that target it covers everything required for a paid relay with arbitrary storage back end interfaces

i haven't developed any other than the badger driver for the database but i intend to build one for another k/v store: https://github.com/akrylysov/pogreb

the rationale for using this one is that it is very fast at retrieval, way faster than anything else, and my intended use case of the database in my relay is for caching front end for a distributed data store backend, so most of the workload is actually read side, and that's something i know because i watch the activity of clients using my relay and they pull soooo much data over and over again, and pogreb gives fast speed without as high a memory use cost for the use case

on nostr there is no spoon feeding

my only other media intake is occasionally i scan through zerohedge and sometimes one or two articles look interesting enough to read but it's so repetitive mostly and to me, with my current understanding of the state of the world and the historical context, redundant and/or incomplete and/or pessimistic

i see no need for using a general purpose json parser for a very specific protocol, as a general purpose implementation, if it's not generated code, it's going to be slower due to reflect and if it's generated code the complexity of the generated code will account for cases that are not present in the actual use case

the json parsing i have inside the event, envelopes and filters are custom made for the task and are as lazy as possible so they are fast, and the code is easier to debug

i wrote a cut down version of bytes.Buffer that has special elements for recognising and cutting out strings, escaping that is specified in NIP-01, and it can scan through a whole object inside an envelope without parsing just looking for the bounds of the object and pass it to a more detailed process

it's already got that, and i haven't had to make a change in that part of the code for maybe a week... change that was required was in the ok envelope i didn't account for there being whitespace between the commas and the true/false value being by itself, now it skips whitespace...

the json parsing i have written is deliberately minimal and lazy as possible, so there may be other ways that existing relay and client implementations may break it, this is one of the reasons why i'm saying it's not ready yet, but it's one change i've made in the json in a week period, the least so far, hoping that i won't encounter any more than that

the most recent big changes i made to the library were in the relay client code which had a nasty concurrency bug that i created a patch for go-nostr but fiatjaf isn't happy about how i talked about it here on nostr but he can go fuck himself and apply the patch and be happy

it's a work in progress but https://github.com/Hubmakerlabs/replicatr/tree/main/pkg/nostr

i am still working through things in it, like i just added NIP-44 from the terribly written golang reference version which was criticised by the security report for its handling of byte slices quite rightly

most of it won't change much more going forward, the relay is fully functional but i'm not satisfied that it's past early beta grade quality yet as it occasionally still does things wrong

probably in a month or so i'm going to pop it out independent to the parent repository but for now it's too likely to change to be manageable to keep two repositories in sync when the relay has such tight dependencies on it, every time you have two repos in Go where one depends on the other, getting them to sync together is a two step process that is best avoided until one of the parts is stable and doesn't need any further changes

it also needs documentation

i mean, by all means you might want to do whatever you like with it, and it is working pretty well already, but it's not finished yet by my standards

linux GUI on WSL is all based on wayland weston compositor and it doesn't respect CSD and looks pig ugly like windows 7 without aero

can be done though, it just is a poor second best to actually running linux

you'll eventually realise you are being spoon fed

*what you think you want

yeah, there's some big problems with this all because the system is so corrupted