Nostr clients are a bit confusing right now and I'm pretty sure most users do not know these details.
Clients early on could "mention" pubkeys aka others. Now they also can what I would call "reference" others following nip-21. The difference is that the former will trigger a notification to the mentioned while the "reference" should not.
Clients now replace nip-19 bech encoded pubkeys as references or mentions and it's hard to guess which of those it is.
Furthermore mentions do not require to be included in the content of the event, leading at least me to suspect that a brief addition of a mention even though I later remove it from the content might still retain the mention in the tags.
I would want my client to let me edit the "mentions" that go with my message. I want to "mention" people without referencing them and reference them without mentioning them.
Brian Armstrong still hasn't paid #[0] š
https://cointelegraph.com/news/brian-armstrong-owes-me-100-in-bitcoin-here-s-why
Cool story but one issue with LN is that proof of payment isn't as easy as with on-chain transactions. And proof of "no payment" is even harder. Had you shared a Bitcoin address with your video, we could all laugh at Brian for his claim. Now we have to trust you.
Reminds me of that awkward situation in El Salvador with #[2] I think where we pitched Bitcoin to a taxi driver, had him install Chivo of all wallets and ended up paying triple the fare because he didn't see our transactions even though our wallets claimed payment success.
Phoenix wallet shows Payment details and I can copy the payment request and preimage and somewhere buried there probably is a reference to who I did pay but it's not made easy at all.
I just today started my trial of GitHub CoPilot and the first 5 suggestions were wrong and pathetic. Guess if I ever need a `calculateDaysBetweenDates(a, b)` it will shine but until then, ...
It's amazing how GPT can help with tough questions and that will elevate many developers but it will also be a bit of an equalizer. The entry level dev probably profits more from an AI than the veteran developing with his favorite tools.
Survivor bias.
I'm so sick of humans not having figured out food by now. Doing low carb, some doctors agree. Others don't. WTH? Can't professionals agree on something that basic?
Sadly the normies already think that Facebook==internet
HTTP Response Header Field: Carbon-Emissions-Scope-2
Comments ( https://news.ycombinator.com/item?id=35528651 )
https://www.ietf.org/archive/id/draft-martin-http-carbon-emissions-scope-2-00.html
Suppose for a second this is not an April's Fools joke ...
Apart from governments mandating the inclusion of this, basically wiping the internet of 99.9% of its content and limiting it to corporate players, giving governments more control, who could even want this and for what? Which browser would show the user a tally of his last cute cat pix session? What would the client do with this other than throw it away immediately?
Issue tokens on nostr itself. There is not much of a need of a public blockchain for 98% of tokens. Just let the issuer provide a permissioned blockchain.
Ethereum is attractive because it forces all participants to agree on a standard but 98% of these tokens would work better if instead of storing the contract's ID, users would have to store the issuer's API address. Wallets could still know which API to talk to for which token and work seamlessly if the API was standardized.
My client is called nostroid. It's open source, deployable as static html, using svelte. PWA.
is working a slight little bit right now if you have patience as it downloads tens of thousands of events before it's fast and allows you browsing even while offline. Some things are broken. nip-07 used to work but now it doesn't.
We are in a Cambrian explosion of clients and relays. Will is the most prominent of many client developers and he most certainly knows what he's doing. Jack is throwing money at products. Even my client implementation that laid dormant for half a year is getting revived. It's ok to ask for more donations but Will is not the only savior here.
1. As there are so many clients and so little lock-in to one client or the other, there is hardly a case for a subscription model for clients. Supplementary features maybe. nip05, badges, fast relay access, ... but not clients. Sadly. My client has the same problem.
2. In Bitcoin, only mining is a natural business model. Still there are thousands of Bitcoin wallets many of which with no obvious business model. And tons of open source, financed via grants and donations or simply maintained by professionals in the free time.
3. VCs ...?
4. š¤®
But ... most of the buttons do nothing and I can't find any diagram on how this is meant to work. Which part do they plan to do with nostr? How? How compatible is it with git? ...
Thanks.
That's more than a few clicks to undo my post :( Guess I wait for Kieran to add deletion to Snort.
Damn it! I saw nostr:nevent1qqs259cvk8q3rqvh9nrrstem3prqgywq7f58ek8hefqulll5lv2h9rqv065tg earlier and couldn't find it now to show you. We need better search on nostr.
Also a friend just asked about this project that allows you to delete your events ... anybody?
nostr:note14gtsevwpzxqewtxx8qhnhzzxqsgupung0nv00jjpelllf7c4w2xq2wtjjf
How did that note id end up in the replied to event? Gnah. From bad to worse. Snort needs a delete button.
Damn it! I saw nostr:nevent1qqs259cvk8q3rqvh9nrrstem3prqgywq7f58ek8hefqulll5lv2h9rqv065tg earlier and couldn't find it now to show you. We need better search on nostr.
Also a friend just asked about this project that allows you to delete your events ... anybody?
The GitHub replacement on nostr will support that and it will come soon enough. The bounty is 10 BTC.
I see you have your priorities straight :D
#[0] if you want to promote the use of pet names, why not regularly change your name and avatar, not necessarily to those of others with many followers?
It's a lot to develop but I think this should happen rather sooner than later as now a lot of resources is going int defining arbitrary limits leading to good and bad actors working around those limits in a cycle that eats up resources, delaying the inevitable: clients have to pay for what they want to get in return.