T.C may >>> sailor, and so many years before
nostr:nevent1qqsx2c8tqsrz5l0utrwwpmdhp0zgs2vadqnycmr55r7t40xgryfnctcpzpmhxue69uhkummnw3ezumt0d5hsyg8pljy03cmc0pzc0s3n0a8tjzjxcrqxytzzua7htmz2xafp7v8kygpsgqqqqqqsrdhwql
Don't underestimate the power of the banker spanker
nostr:nevent1qqspwufcjesqwqu2q90r3xuxkjt2dk0drutzdk7yfl8nqzvtsd3dvlcpz9mhxue69uhkummnw3ezuamfdejj7q3qa3um269aaf3u5cy37kuykrrrnsg2pyv7za06pxjduv25lq5sdujsxpqqqqqqznd3fzk
The sovereign stack for communities 🤝
nostr:nevent1qqs8yx32qh7spkggqdhwjhn5ryyckcn76rzhufwv5ddzdlfz8f2lhmqppemhxue69uhkummn9ekx7mp0qgs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qrqsqqqqqp2p6vgf
I remember that nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wf6k2tnrdakj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9usc5pxf had some drive encryption spec for blossom, don't know the state of it rn. But yea is a complex problem
Just reading the spec bud01 there is an optional authorization method: The server may optionally require authorization when retrieving blobs from GET /sha256, returning 401 if not properly authorized
GM!🌞
Last nights I was doing my personal hackathon, wanted to prototype something, something that might be cool even if there is more work ahead, but potentially can improve the ux and security of use nostr keys. I want to share, but also #sec03 is around the corner, should I wait?
It replaces dopamine with zapamine ⚡
nostr:nevent1qqsz8hqlka7uep9elm8v732urs9mnsc8zrzplh39yexzwfwa43a4vvqppemhxue69uhkummn9ekx7mp0qgswc7d4dz775c72vzgltwztp33ecy9qjx0pwhaqnfx7x920s2gx7fgrqsqqqqqp4fjjq3
No idea man, but was following the logs and the pubkey spamming have only two notes I can fetch one from 2021 publishing this video 👀👀 wtf? Its pure gold
https://www.youtube.com/watch?v=olq8mA51_ng
Yes, llms with bigger context window and rag can be feed with all the documentation of whatever software and be much more accurate in problem solving tasks
Ok, after some cleanup, bells, and whistles I've released the note-mixer-relay. Have a look of you want to run one, all feedback is welcome :)
https://github.com/gzuuus/note-mixer-relay
nostr:nevent1qqsxd0mtx9j4lgk5yc8wfmznv5ghamvynceeqpyfgqcs6w3asey6c7gppemhxue69uhkummn9ekx7mp0qgsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5grqsqqqqqpdrfmm8
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt There are some way to set read and write for my relays in amethyst? I cannot find the way to just set a relay to read and avoid to write there
Now imagine that you can create scoped permissions for pubkeys, like event kinds 0 and 3 can just be published if they come from a whitelist pubkey. Same for the rest of kinds... 🤔 retarded or no? #asknostr
nostr:nevent1qqsxd0mtx9j4lgk5yc8wfmznv5ghamvynceeqpyfgqcs6w3asey6c7gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5grqsqqqqqp2ceyww
Short history of a little crazy, and experimental relay: wss://mix.gzuuu.xyz
Last night, I was floating through cyberspace when an idea struck me. A note mixer relay - a simple yet intriguing concept. Essentially, it's a relay that accepts your notes, but instead of store them, it re-signs them with the relay's keys, effectively anonymizing and mixing your notes. This is the npub I'm using for this and where all mixed notes are published nostr:nprofile1qqs80keaa6v84ldnkne66q0qf96rvtf84aj27taw25x3appz83lqspgppemhxue69uhkummn9ekx7mp07t6hp6 .
This idea isn't entirely new, there was some exploration around group of people sharing an nsec. This is the case of nostr:nprofile1qqswgh9y2cz5qu5upzg5yn47m65t7d697k2dtufa9fq54af80dwng5sprpmhxue69uhkummnw3ezucmgv95k6cfwd9hxvme0qyw8wumn8ghj7cn0wd68ytn0wfskuem9wdukuceww3jkx6p0ksrqpx, for example, it was created during sec01.
In summary, this note mixer relay will accept your notes, re-sign them with the relay's keys, and then publish them. Does this idea interest you, or does it make sense? Currently, anyone can publish to the relay, but I plan to implement a whitelist for pubkeys based on my contact list. This could also be integrated with a wot relay, allowing you to mix notes from your friends or entire social graph. Perhaps there are some interesting use cases to explore? 🤔
Just a heads up: be careful not to publish to multiple relays, as this will leak your original note, signed by you.
If you use and share a new nsec you cannot control who has the nsec, it can be shared infinitely, on the other hand by using this relay no one knows the nsec and still be able to publish with it. At least type 1 and 30023 as it is limited now. I am the only one now able to change the profile metadata and publish other kinds with it.
Now imagine that you can create scoped permissions for pubkeys, like event kinds 0 and 3 can just be published if they come from a whitelist pubkey. Same for the rest of kinds... 🤔 retarded or no? #asknostr
nostr:nevent1qqsxd0mtx9j4lgk5yc8wfmznv5ghamvynceeqpyfgqcs6w3asey6c7gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5grqsqqqqqp2ceyww
Yes, a malicious relay can do that, but you can spin up a new ephemeral pubkey and write with it, the result would be the same and you cannot correlate nothing
Cc nostr:nprofile1qqst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshs54zrlx
What you mean? First note ever published or just op notes? But in general, all the notes you sent to the relay gets resigned, only the relay can correlate notes and authors (not in this case) but you always can use a ephemeral key to publish, at least if the mixer relay is public and doesn't have a whitelist
Ok, after some cleanup, bells, and whistles I've released the note-mixer-relay. Have a look of you want to run one, all feedback is welcome :)
https://github.com/gzuuus/note-mixer-relay
nostr:nevent1qqsxd0mtx9j4lgk5yc8wfmznv5ghamvynceeqpyfgqcs6w3asey6c7gppemhxue69uhkummn9ekx7mp0qgsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5grqsqqqqqpdrfmm8
Just follow the instructions, seems that proxisto.re seema that doesn't accept ln, but I remember use it in the past paying in ln, anuway the other link is the one I normally use, it's cheaper, a and it's like a voucher system where you put your account number, pay, and more time gets added to your account
Awesome, have you seen my note mixer relay? That would give you more control over the people that are able to publish by adding them to the whitelisted pubkeys
https://github.com/gzuuus/note-mixer-relay
Thanks juraj! I also bundled a text area to publish directly from the http side of the note mixer relay, allowing you to publish without being in a nostr client. Add a password/nip07 login to protect the textarea should be trivial
Oddbean new post about login | logout
Notes by Gzuuus | export