Pinned post.
I wonder when that'll come along #nostr
Basically, under ones npubs:
Pinned="noteid"
Or
Pinned="noteid,noteid,noteid"
For multiple.
Aaand my VR quest 2 broke =/
(Tracking dying / died)
No more VR / VRChat until I manage to get a new one (I should have had a new one, a Pico 4 Pro, but Turkey have most likely destroyed it (actually). $900 down the drain).
Don't know when I'll get a new VR headset, but it'll be either a Quest 3 or Pico 4 regular (probably this one).
I'm not going to say never, but.... x3
Had fun redesigning the first page:
Introducing...
NOSTR URL shortener
A free URL shortener service enabled by the NOSTR protocol, that is fast and fuss-free, stripped of all bells and whistles and gimmicks.
It just works!
https://nostr-url-shortener.vercel.app/
What I need help with:
- community to decide a short domain name
- a sponsor for the domain
- designs and logo
- just test it
Open source GitHub repo:
Ye! I saw nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z 's post utilizing different kinds for different file types and had a website ip and running on nostr. Everything is perfect and I'm super hyped about it. All that was left was to solve the ICANN problem =3
To your points:
1. First come first claim. Others can take the same name, but they can't take when the first person who took it is.
2. The NPUB in the Blockchain is the owner of the name and controls the rexords. Transfer of ownership is recorded in the chain.
A) I'm not an expert on this so I can't answer this properly, but I'd imagine a software specified in this would be developed to search for these specific transactions and categorize them for fast searching (if you're running a node with umbrel for example, you'd download that software and use it).
B) That's a... Well, that's an issue with Bitcoin and nostr all together then? x3
That's just a responsibility with the individual that they have to have, like in those 2 protocols, and take the appropriate security measures.
Oh, is everyone getting tagged in each reply? Sorry too! x3
I guess this should prompt nostr clients to include 2 things later:
1. Mute Post Thread (from the perspective of the person getting tagged along in replies).
2. (Reply to: @ @ //@ @ //@ ) from the perspective of a person replying and wanting only reply to specific tagged individuals.
.
B + last paragraph)
Aren't most Bitcoin users (and I'm not even talking about Binance and similar custodial users) are trusting third parties with their transactions as they aren't running their own node? As long as things can be verified by the user themselves, like how it is with Bitcoin and everyone's kind of fine with it, then I don't think this is that big of an issue. What can also be done is provide the user with the power to change who's providing them the node data, like how it is with Blue Wallet for example, and even allowing adding multiple ones and cross checking the end result to decrease the chance of fowl play.
This is an interesting concept.
It seems to be a simple way to take a name "key" and attach a npub to it ( "value" ) on the bitcoin blockchain.
Then presumably a client would look up the name ( "key" ) on the blockchain ( most likely through a server that's keeping track of these ) and get the npub ( "value" ).
Then it could query various relays for a kind 38300 event and extract the JSON record out of the "content"
A few thoughts.
1. Whats stopping me from just creating a new bitcoin transaction with the same name as someone before?
2. If the data is stored in nostr whats the points of putting the npub on the blockchain? is it just a way to publicly associate a name with an npub?
I think there are a few fundamental issues with an approach like this.
Firstly the bitcoin blockchain is not easily searchable, it might be easy to write data to it but without a centralized server that keeps track of all data written to the chain its almost impossible to search for something
Which makes it pretty useless if your trying to quickly look up a name in a self sovereign way
Second issue. I don't trust nsec keys. They work well for social media and posting on nostr but I would not want to put anything else behind them.
Not because they are insecure, but because if they get leaked then it wont be just my social media account that gets compromised
current list of 38300 events: https://nostrdebug.com/query?base64=eyJraW5kcyI6WzM4MzAwXX0%3D
Ye! I saw nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z 's post utilizing different kinds for different file types and had a website ip and running on nostr. Everything is perfect and I'm super hyped about it. All that was left was to solve the ICANN problem =3
To your points:
1. First come first claim. Others can take the same name, but they can't take when the first person who took it is.
2. The NPUB in the Blockchain is the owner of the name and controls the rexords. Transfer of ownership is recorded in the chain.
A) I'm not an expert on this so I can't answer this properly, but I'd imagine a software specified in this would be developed to search for these specific transactions and categorize them for fast searching (if you're running a node with umbrel for example, you'd download that software and use it).
B) That's a... Well, that's an issue with Bitcoin and nostr all together then? x3
That's just a responsibility with the individual that they have to have, like in those 2 protocols, and take the appropriate security measures.
What do you guys think of Nomen by nostr:npub19pw5egjuhcsfsv42zkjtjs6nhpm69lnv8w2dacdyez7rvacrqnds6xjtwk ?
(A #Bitcoin + #Nostr solution to the NIP-05 problem / ICANN problem)
Gist from my POV:
Register/record a name in Bitcoin along with who owns it (nostr npub), and have records handled by Nostr.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
(and other nostr / bitcoin dev I didn't mention/know about #asknostr)
It seems like this solves 3 problems: ICANN, NIP-05's reliance on ICANN, and having Bitcoin human-readable addresses.
(sorry for the poke if it was annoying)
Check out Bionic Bay, a fast-paced adventure puzzle platformer, with its demo up on its Steam page.
Post:
#gaming #indiedev #gamedev #indiegame
https://cdn.nostr.build/i/62209e99ff4d7929da7979bc333b80db317639d8e9b0b66befb3811241a20544.webp
This was pretty fun to play =3
nostr:note10ly6947d4aeauhzqmu2vrq7j38m2vpsl0mpjuyh5y7lpjk5mkv5qn02t59
Regarding the zap goals feature on #zapstream , it would be nice to have these improvements:
1. a create zap goal button that's already there without the prerequisite of having someone/yourself zapping the stream.
2. an edit button to change the zap goal to another (changing the zap event)
2.1. creating a zap goal would lead to 3 fields: goal title, zap amount, (or), zap event.
why do I want 2/2.1? continue the goal campaign from one stream to a new one mainly, and if the goal is achieved, then I'd just change it without having to make a new stream.
off the top of my head:
the weird @'' quote things when you try to mention someone
anytime you do a : it bugs out and can't get out of it / press space unless i ctrl+a then ctrl+v then it removes the lock in
no categorization of the notifications page (tabs to see only reactions, zaps, replies, quote replies, etc)
off the top of my head:
slow performance.
no quote repost.
too damn simple (post card and site bg blend too much).
post button too far away (the circle pen in the bottom right corner of the screen).
at first I was maining snort, now maining primal (all on desktop. mobile I'm imagining plebstr then amethyst at the moment).
It seems like #Nomen is the best solution out there to solve the ICANN (website domains / DNS / human-readable address/ID) problem.
It's an open protocol that combines #Bitcoin and #Nostr together to register/record names (on Bitcoin) and has records attached to them (on Nostr), and the owner is a Nostr user/keypair.
Really hoping that NIP-05 gets adjusted or replaced with a new NIP to have Nomen as the ID/handle solution. Already registered my name 👍
Another thing that's pretty awesome about #nostr is how easy it is, as a user, to switch from one client (app/site) to another competing one, in the blink of an eye.
No loyalty. No friction. The best client wins.
And what's the best thing to do as a user in such a space?
Brutal honesty.
Sting the devs/designers with your words (respectfully) as you light a burning barrel under them so that they'd make a better client for you so that you'd come back.
"I started using A-Client instead of B, as it has X better, and has Y that's not available in B"
I can design and was part of a failed revolution, what's up?
At first, I kind of enjoined how nice zbd is, years ago, but as more time passes, it's became more and more of what I had left initially. How they're hadling nostr is no surprise to me.
nostr:note1cllxfajr7sc7hp9vskkne9mmxk02zwd2qtr76xm7tvf8dwkenh4sn9c03z
Free The NIPs! 🤣
But on a serious note though, there is a big bounty to make a github replacement on nostr, so it's only a matter of time until we get it =3