nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm all the relays in `getRelays` call seem to be down? Causing issues for some people, why can't we modify this list?
Certainly the plugin should give the user such feedback at some point. Warn if less than 3 healthy relays are configured.
A real troll is immune to shame or other feelings that would stop others from keeping at it. Do not feed them. Mute makes that easier.
I find it outrageous that payment providers ask my banking password so I always search for alternatives. Now I appear to not have alternatives. WTF? Their cert was issued three days ago and they claim to be endorsed by government agencies. My bank apparently did endorse on their website that payment provider but WTF are banks doing to allow their business partners ask their clients for their credentials??? It's 2023!!
nostr:note1zfrrzfrpaywue2u8ucekz3v8y5mvgrupef3dfjgj0vsrfx4z859qewez2uIt's not a done deal yet, right?
I like it. Apart from populist ideas still being on the table and likely imposed on people unnecessarily it would fix so many things. But it's so far off what people even consider. Who would vote for that?
Democracy: You get to vote who governs you, not how you get governed or if you should be governed at all. And the people who stand to be voted into positions of power are either Machiavellian psychopaths or don't make it to the top.
NostrPostr was my rookie attempt at doing this while getting to know nostr and I gave up when I ran into some concurrency issues. It worked locally when testing but not when it got hammered by multiple clients. But for a local process on your phone, maybe that's not even an immediate issue. Fingers crossed.
Most people don't remember that email used to work offline. You would go online to send your outbox and receive to your inbox and after five minutes or whatever it takes to sync thee immense 5kB you cut this expensive line again. Then you can read through stuff and reply offline.
Yes, nostr should at least optionally work like that and it makes a lot of sense to split the relay (store and forward) part from the client. A client shouldn't have to care about storage or networking for that matter.
with l,year,2023 you couldn't query for movies from 2023.
Thanks for the reply. I'll try to come up with a patch for the nip so others don't have to struggle there.
So the following are kind-1985 events observed in the wild:
A)
e,fd87c3863a9044a60f507b952eb0391524f89d941acfec0830b233cab3c0568c
L,#t
l,Nostrasia,#t
B)
L,#t
e,0f2c0dfb2c5a67422999e26b68fe8ae326b9c4cb50cfbfce82056101ba30b917
l,#bitcoinlegal #Bitcoin #imagazine #strefabitcoina,#t
C)
L,#t
e,13a4d33bc1396b1e2e537b77b763d107d06d5f3b37e5cf817ed8870c0d784c87
l,philosophy,#t
l,epistemology,#t
l,defeater,#t
D)
L,#t
l,nostr-beginner,#t
r,httpsXXXnostr.Xhow/en/what-is-nostr
E)
L,#e
l,question/summary,#e
e,1e49a2b5415c1949030c8f3de113f10d31a16501a1220e0445ab3a3500b2fdc8
F)
nonce,37551,15
t,tt2906216
r,tt2906216
l,nostr-movie/rating,tt2906216,{"quality": 0.7}
r,ImdbId,tt2906216
r,tmdbId,493529
r,name,Dungeons & Dragons: Honor Among Thieves
l,year,2023
l,postRatingId,true
My guess of the intended use is:
A) Assign hashtag Nostrasia to event fd...
B) Assign multiple hashtags to event 0f...
C) Assign multiple hashtags to event 13... the right way?
D) Assign hashtag "nostr-beginner" to ... a url referenced using an r-tag
E) Assign label "question/summary" to event 1e...
F) WHAT? Lack of L-tag is against nip-32. Somehow if there was additional tags like L,year, l,year,2023 could make sense as l,2023,year, right?
So my confusion is why would one use L,#t and another L,#e and how can we help whoever is trying to mirror IMDB on relays?
I'm trying to implement a thing and struggle to make sense of NIP32 "Labeling". nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1z7e7ml8kevdfdala8k0cthfhcvfhmxf8mt27qzc83pc8ay0m3zdqlgw4fh nostr:npub1veeqt66jt2j209y9nv4a90w3dej074lavqygq5q0c57dharkgw0qk738wt authored this. Anybody willing to clear some doubts?
The nip mentions:
`e`, `p`, `a`, `r`, or `t` tags. This allows for labeling of events, people, relays, or topics respectively.
So e and a are events.
p is pubkeys, some of which represent people.
r being relays is as of nip01 explicitly not universal (e.g. an `"r"` tag may have a meaning in an event of kind 1 and an entirely different meaning in an event of kind 10002) so I wonder how do r-tags work. I found some 1985 events using r-tags for non-relay stuff.
t are topics? How do these work? In the wild I see events using t tags to reference IMDB movies by their ID.
Who wants to help me clarify the nip a bit?
I'm trying to implement a thing and struggle to make sense of NIP32 "Labeling". nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1z7e7ml8kevdfdala8k0cthfhcvfhmxf8mt27qzc83pc8ay0m3zdqlgw4fh nostr:npub1veeqt66jt2j209y9nv4a90w3dej074lavqygq5q0c57dharkgw0qk738wt authored this. Anybody willing to clear some doubts?
Problem with mail is that the other end almost always is one of the big data silos.
I’m excited to announce Grow - the first referral program for Nostr: https://makeprisms.com/grow
- Easily create referral bonuses to share with friends 🫂
- Choose any amount and share the link 🤝
- Recipients instantly receive the bonus after joining Nostr 🤑
#grow #grownostr $boost
What? Without wallet connect installed, I'm not getting far with this one. Have a video to show how it works?
I'm not sure we are talking about the same thing. My use-case is wallet reviews. The subject of the label thus would be no a or e tag. I'm talking about the review itself being a long-form post. As nip32 is not explicit about the content supporting markdown, should I create long-form posts where markdown would be expected and link those from the content of my nip32 events or should I just go with long form in my nip32 event?
I'm thinking of Raspberry as the prime example of successful open hardware. Everybody is stoked to learn the next release's specifications but dozens of companies build cheap replicas. Many still buy the more expensive brand while other brands establish as more or less reliable. A fascinating market.
This is very laudable! You can still provide your own branding and set quality standards while allowing or even encouraging "cheap knockoffs" to sell "your" design.
'. Due to copyright, some vendors’ code cannot be made public, and we have removed some of the code from the source code. Therefore this open source code cannot be compiled. However, we can share this part of code under an NDA if you want to fully verify the code and reproduce it.'
#walletscrutiny links to it's own issue about the wallet, where it explains the problem. this issue also links to https://github.com/KeystoneHQ/Keystone-system where keystone writes what I quoted above. nosource seems to be a valid verdict.
NIP32 is not prescriptive about the content-field's content. On the other hand, label's were deliberately not made replaceable.
If in my application, the reasoning for a label was rather a long-form reason than what the examples in the nip showcase, should I link a NIP23 long-form article with a nostr:naddr, use markdown in a long-form style article or something else?
#askNostr