the relay owner could still delete what ever they want, might serve an archival purpose but doesn't really add censorship resistance
I switched my VPN address and everything started working again 🤷♀️
kinda wish I didn't do that... Now when I went to reconnect the wallet I get this contact support 
I also just disconnected the wallet connect... All other receiving wallets I try offer me an lnbc link... But damus seems to have an issue still fetching the invoice from an alby reciver
yeah In damus my sending wallet is wallet connect with alby, no zeus involved. I'm still experiencing the error fetch with #[2] with #[4] & yourself.
I come here for people, I go to a rss reader for news from sources I like. Mixing becomes something close to the mess of an email inbox.
ok I'm new to coding, I found the code in telegram/invoice.go I have an idea to create a variable to hold the message text... unless you say else wise, I'll wait to figure out botfather and get a test done before submitting.
in 1.4 builds it still says “error fetching ln invoice” but at least will let me get to the pop up screen. Glad it works else where tho.
Damus, 1.5(4) & 1.5(3) still same issue the morn... I'm tipping out of my alby wallet just fine, but zaps to #[4] & #[2] accounts won't even generate a temporary zap. I did try on snort just now, and that did work so 🤷♀️ maybe not an alby issue. Brb gonna check a 1.4 build.
maybe even a pfp search, just color detection... I would go to a profile I think follows that red guy and then limit it to just pfp with red in them? or maybe have a pfp alt text metadata like aim, world, pepe, cat
I'd really love to search a following list, id really love to have a “conversations” shortcut to see what @soandso has tagged/replied to me in.
same, I've been meaning to do that, designing and printing out cashu mints is really up my ally
nostr:note1ujjqcm730mctlzwvmhplyvjghtwz9n6yas0ffmh0u3c3ctk2jvgsdmga8m
on lntipbot the one thing I would change is for the notification “this was a zap on nostr to be truncated into the you received message so it's not technically two notifications... #[0] 🙏
I like their extension first to support nostr, maybe its one point of failure but easier to trust a signing extension that has a financial reputation to uphold & I'm successfully zapping out and splitting to client devs. I use #[4]‘s lntipbot as my receiving wallet and really enjoy that.
won't let me zap #[2] but also won't let me zap #[1] themselves... Other zaps are leaving alby and showing to other receiving addy’s
having issue one tap zapping to profiles receiving with #[0]
it was dumb as a game controller... But a sub lacks windows and needs a periscope. 
The end user should be informed about the expected outcome, and an impartial source should be able to verify whether the expectation is being met. Algorithms on nostr need to be at least as open sourced as twitter.
Personally, I value having control over who enters my home. I don't want anyone else's rankings, whether they are from my friends or based on how a client, server, or centralized service ranks individuals, to influence who can enter my home. I believe there should be filters available for both inside and outside my home, and I prefer these filters to be specific and concrete. When I'm told that I'm viewing my entire house, I expect to see the complete view without any omissions (this should include looking at what relays my followees are on and getting their content from there).
I'm not interested in knowing what occurred at a bar last night if I wasn't present there. It would be strange for me to spend my time at the bar tonight catching up on events from the previous night. Besides, when it comes to web sockets, I want to engage in live gameplay, not compete against .io bots.
can change that... if you on damus it's a purple :Pepe: btw 