Think anything that has to be always on is just harder, most people dont have always on devices
Yeah I dont have enough Bitcoin
Congrats, enjoy
Are there any implementations of NIP46 (Nostr connect)? I think I saw one somwhere.
He does love his domains
Yeah agree here, when I saw that website I didn't go through with it.
Wow been awhile since I looked at the damus github, alot of activity
#[0]
I'm discussing Roblox with a child I don't understand it's doing chores what part is fun.
#[0] can you fix the shutdown problem of the cln plugins? useful info is here: https://github.com/ElementsProject/lightning/issues/6040 that would make it more easy to update the plugins or even restart them from the cli
Thank you this is helpful should be able to get it done tomorrow. On my raspiblitz node it seems to shutdown. but I will add handling the shutdown explicitly.
Weird brag... Jk🫂
Can use https://github.com/0xtrr/nostr-tool. I thought you could use damus.io/key but doesnt seem to be working at the moment might be only for keys not ids, not sure. Im sure there is another web one somehere but none i can name.
the note1... is the bech32 enchoding of the the id. https://github.com/nostr-protocol/nips/blob/master/19.md
I really should not be using a client without spell check
the note1... is the bech32 enchoding of the the id. https://github.com/nostr-protocol/nips/blob/master/19.md
Can you post it? I bet one is the hex and one is the bech32
https://twitter.com/VickerySec/status/1375130578660433924
sorry its twitter
How anyone keeps up with anything in telegram is beyond me.
Was listening to the #[0] video this morning with #[1] this morning about being able admit or deny users to a relay via an API. Seemed like a cool idea to do it over nostr so threw this togather where a relay admin can allow or deny users by publishing a note. There is no NIP at the moment just made up the format, will formalize if there is interest. It is a gRPC extension for the nostr-rs-relay. Will add an http api to it as well.
https://github.com/thesimplekid/manage-relay-users
Can use this to publish notes for now:
https://github.com/thesimplekid/nostr-tool/tree/manage_relay_users
Added HTTP API
#[0]
I'll catch you up on the topic of us president. Nobody good.
"The familial relationship between Alice and Bob is "second cousins once removed."
Here's why:
Bob's father is a cousin of Alice's father, which means that Bob's father and Alice's father are first cousins. That makes Bob and Alice second cousins to each other.
However, Bob is not in the same generation as Alice, because he is the child of one of Alice's second cousins (Bob's father). This means that there is a generational difference of one between Bob and Alice.
When there is a generational difference between two relatives, it is called a "removed" relationship. So, Bob is "once removed" from Alice in terms of their second cousin relationship. Therefore, the full familial relationship between Alice and Bob is "second cousins once removed."
Was listening to the #[0] video this morning with #[1] this morning about being able admit or deny users to a relay via an API. Seemed like a cool idea to do it over nostr so threw this togather where a relay admin can allow or deny users by publishing a note. There is no NIP at the moment just made up the format, will formalize if there is interest. It is a gRPC extension for the nostr-rs-relay. Will add an http api to it as well.
https://github.com/thesimplekid/manage-relay-users
Can use this to publish notes for now:
https://github.com/thesimplekid/nostr-tool/tree/manage_relay_users
The other issue with it is if I see your note on a relay you've blased to but are not reading from and comment on that relay you'll never see it. So clients will have to get smarter about figuring out what relays people are writing to and reading from. Gossip does some work around this
Sort of you have to trust blastr to actually send your events and not censor. Though it's open source so if more people run blasters it's less of an issue.
Nice. Ill throw this here for anyone on CLN
#[0]
This is definitely part of it. The user base of twitter compared to facebook and insta is much smaller.
i tried to comment but looks like i failed
#[0]
I think its a bit of a chicken and egg, right now a good portion of the content is people talking about nostr and devs. No complaint from me but thats not the content most people want. But this will change as people join. This take is also skewed by my follow list and i don't look at gloabl so i could be totally off. Related to this is discovery of other accounts, without looking at global its tough to find related accounts that you may be interested in.
I'll look into it thanks
I think it's a specific event kind, although not sure why it's not listed here: https://github.com/nostr-protocol/nips#event-kinds
I think it was removed
But from others you can? I think the issue was that i had my clnurl misconfigured with the wrong zapper pubkey and I dont think amethyst is checking this #[0]?, whitch is what I was testing with but damus does. This may get cached somewhere and take a bit to clear. This would also explain why your fix fixed the issue for you but not for me, if it is the case its working for you?
Damus people can't you see zaps on this note?