ah. great! so this was added in the new version (https://github.com/dskvr/nips/blob/02aaf40f1893434d486a5750c2b86b5dc758edfa/CF.md)? will read up on it…

yeah, which leads me to some problems on how nsites require a pubkey as the domain, because in this case, users can only have one nsite that maps to their pubkey, other nsites they copy would have to use random keys that won't inherit the benefits of this flow as the key is not the one you actually want. or am i missing something?

but it technically is a fork no? because if the original nsite gets updated, the copy won't or does it?

using brave with shields on will cap it at around 28 or so. i'm getting around 170 connections out of 421 relays so it can maybe connect to more than that as some of those are probably not reachable in the first place. i'm getting around 60 relays / 283 authors for my daily outbox usage you can check how many connections your browser will do using https://alphaama.com/ma/ws_test.html

👀

you can see and create them in alphaama as well

sir, your relay is way too sensitive, it can't really handle basic requests without complaining... what's the limit? this req has 60 pubkeys and a since for the last 12h, not even that big. Also, then it keeps disconnecting (or upgrading the connection) which triggers another auth request and more notices. The ok-false message has no id.

https://alphaama.com has been updated today. too many new stuff to list but now it has blossom, nip-17, auth, better feed search, let's you import spells as queries and export queries as a spells, bunch of bugs fixed (probably introduced new ones). will be spending time creating some explainers next week on how to use it for all your nostr needs. if you have used it in the past and have data loaded already, you should reset it using the zzz command. if you find bugs let me know. <3

gm

it's just weird thinking a user needs to keep signing events continuously

why does a relay need an auth every 30s? is this a way to alienate those that use a browser extension without auto-approve?

skills should not be addressable events, they should be simple non-editable events so we can garantee their immutability and not get rug-skilled by adding something that might turn evil later. I know editing is cool but in this case better delete and create a fresh one just to make sure we always have the right skill.