Idea: a new method of AUTH on a relay based on Web of Trust/degree of separation. You configure your relay to allow a max degree of separation (say 3). Then when a new user connects to your relay and gets the AUTH message, not only must they sign an AUTH message but so does one other user already on the relay white list (to essentially vouch on your behalf). The person vouching for you must have had their auth message signed by the relay operator/admin or by someone that the admin vouched for directly or someone they vouched for directly up to the degree of separation limit. You can even enforce moderation this way where if someone let's in a bad actor, both the bad actor and the person that vouched for them gets kicked out. If someone you vouched for is kicked out, you get a strike up to a maximum of three (or some other configurable value) #nostr #dev

Lmao GPTo1 is just using the python scripts people built to chain prompts together in the background based on your initial prompt for tasking/agents (I e. Break down the steps, then make each step its own prompt, summarize the result, ask if it matches with original prompt, etc.). This is nothing new.

God I fucking hate JIRA: I get an email about a merge request to review. Click on the link: no info in the MR description but there's a link to a JIRA issue. I click the link: no info but there's a link to a gitlab issue. Click the link: no info but there's a link to a different JIRA issue but I don't have access to it. #dev

I'm trying to understand nostrdb and lmdb better in general. I think I have a good grasp of B+ tree and how they keys in the nodes/leaves are the primary index. But I saw that in nostrdb, there are additional fields of notes that are indexed. How does this work? #asknostr #dev

Any insect specialists, entomologists or just bug boiz able to tell me what these are? Found under a leaf on a tree outside the second story window where I live. #asknostr