That was me, WoS doesn’t support NIP-57 yet so you won’t see the payment attached to your posts.
Zapped you 1k sats. No indicators on the Damus side though. Who is your lnurl provider?
No worries. You might just want to stick with your strike.army address for your nostr lnurl provider for now.
They don’t appear to render on the timeline view by default. Probably an expensive operation on a per post basis. Try opening a recent post from Will, you’ll see them in the note view.
brb.io exposes their relay content in a restful interface which is really nice. #[2] are the endpoints part of the relay or a separate layer over the db?
Nice! Hopefully now that the NIP has been officially merged we’ll see even more rapid adoption. Will mentioned there will be some big ones but couldn’t elaborate.
#[0] how did you get your zap to Will to include a message? Tried adding a note to my lighting payment and it didn’t get included.
You can send using any lightning wallet. To receive you need an LNURL provider with support for NIP-57. Currently that means strike via strike.army, but word is Wallet of Satoshi is not far behind.
You’re ignoring the long term implications of this model. The more BS you generate with your signature attached the easier it is for the rest of the network to filter out. Trust accumulates, and payments are secondary. You typically only pay people you trust first.
Right, been testing other relays isolated in global this way. While Red/Yellow is a good indicator I’ve also observed that Green does not always mean the relay is returning data - just that you can connect.
How are you profiling/debugging the connection issue for your wine npub endpoint? I just signed up yesterday and assume it’s working but there’s nothing within Damus that would indicate otherwise.
How about people who are perpetually late? Them too? 😄
When it comes to content filters people should use algorithms, not consume algorithms. There is a massive difference.
👍 seeing this in global which I have filtered only using eden right now. I think it might still be struggling with latency. I have to force kill Damus every so often to get it to load global (otherwise it says no messages)
Signed up for eden. Payment is pending….
You are still bullish on the fediment aka Uncle Jim model though right? Realistically it will never be 1-to-1 with custody, having a heuristic for being adequately decentralized is difficult but necessary for us to answer “have we made it?”
Right, so continuing to pull at this thread ephemeral events are just suggestions as well. I guess I’m worried every developer will spend time learning about these event types only to realize it’s only reliable if you have full control over the client and relay. There are hidden assumptions.
There is a NIP for opentimestamp integration but I’ve yet to hear of anyone using it.
Timestamps are embedded in the event payload which is great as it’s tamper proof - this is assuming you trust the pubkey, which in the case of user metadata is not a big risk.
It’s currently hardcoded in the app but Will mentioned he’s converting it to a dynamic config pulled at runtime. Prior to December the damus.io relay was the only default.
https://github.com/damus-io/damus/blob/master/damus/ContentView.swift#L12