I dislike servers
Another thing I added was the ability to set the price dynamically in the query string:
So that the shopify template email can pass this to adjust for shipping, etc
Just updated lnlink.org with usd support. This makes it a bit easier to integrate into stores like shopify:
These are like stripe payment links but they require no server, only a c-lightning node. All the data in the page is contained in the URL, so you can put these in a shopify “pay now” invoice email and it just works.
(just trying to get nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s to implement the muted words feature)
It’s working
I vehemently reject the idea that nostr clients have to keep implementing the “next great idea” so that it keeps working. Bcash mentality.
kinda agree, imagine if we could use enclaves :(
Not like we want to encourage sharing bitcoin and nostr keys anyways
It means you follow them. If it doesn’t have it they are not in your web of trust.
Scammer alert… nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:note17usnvu34h9s9l69zf545atedl9gxa9kjhrdnrepzm0sufcz7hles5kmmqt
this is why we check that little purple icon next to the name right!?😅
Yes to me that NIP is more a signal that the client uses the gossip model than anything else. Doesn’t add anything otherwise.
going in a different direction. not all clients have to follow. Users will migrate to the clients that work best for their needs.
drivechains might drive me over the edge to finally implement the muted word feature.
problem with nip65 is that its not just a relay list spec, it prescribes a specific way to pull data from these relays which damus isn’t really setup to do (yet).
yes but its worse now because there even more ways to store relay lists
Ignoring contact list corruption and overwriting isn’t really a solution to the problem
Damus has been storing relays in the same way relays have been stored since the beginning of clients. Damus doesn’t implement the gossip model and does not implement nip65. I can only use damus on my account, most other clients don’t work and are unreliable. I’m going to keep going with what works instead of what people say “is better”.
just growing pains. All of these things are fixable. Im just pointing it out so people know what the problems are so we can work on fixing them.
its brittle because it is strict and is detecting bad stuff. Other clients accepting silent data corruption isn’t very good either.
I was diagnosed with IBS when I was a kid. None of the doctors gave me any useful advice. At the end of the day it was just because i was drinking too much sugar and not enough water.
I think best thing to have is to detect corruption like this and heal it automatically so the user doesn’t have to think about it
As long as im not generating broken data i can sleep at night
What do you mean converting to binary format? thats what nostrdb uses for all stored data (flatbuffers + something custom for notes). No json is stored.
gn nostr 😴 
nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 why isn’t this working? I’m #zapping but my wallet is still only taking 100 sats out
Help 🙏 please! 
Support is disabled until the end of the month! Sorry :(
Adding urls to statuses so you can click them them
Doesn’t need to be Apple Music. Any software can update your playing music status! nostr:note1q5pc3elkyy7v6duwfzd4pka9rphd2c26usfrpg5zj3dau7nr4zyqmyt3vc
I didn’t force anything though with the zaps spec. I iterated on it with nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 who made the spec a lot better. This narrative that I forced it through was ridiculous, and the feedback I got back from you was just not good, sorry.
Noone has suggested substantial changes to make it “better”, including you. If its so bad than suggest an improvement.
Honestly this constant hostility from you is offputting and doesn’t really make me interested in working with the zbd-and-fiatjaf-centralized and cliquey nip repo at this point. nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is starting a spec for publishing NIPs on nostr so I will be putting more energy into that.
clearly he thinks damus is a threat like this because he removed me from the nips repo. Ironic since he’s working on a competing nostr client. The whole nips repo is becoming not that useful, lots of bad specs and people trying to bully others to adopt these bad ideas. People have already changed my zap spec which is now incompatible with the damus implementation without an ACK from me. It’s honestly becoming a joke. How do protocols die? Look at how the nips repo is run and you’ll get an idea. Maybe there is a better way but I’m not sure yet.
the “Replying to …” order of names is currently really confusing.
Would love to have the person that I’m replying to as the first one on that list
nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 
Fixing now
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s wdyt? Add an option to filter nudity out?
Should definitely be an option
Thanks! Haven’t seen anyone close a channel on me yet.
Matrix glitch going from viewing someones profile to global. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
1.6(10)
iOS 16.6 https://nostr.build/av/044e1decb269145a8b0dd309d06922abf71f7f3d4e06f8be6f95672838b65c68.mov https://nostr.build/av/b5189d681361ce4be6aefc6e0a38f81848e5f7b045db04c3284be4df2212d97f.mov
nostr:npub1h50pnxqw9jg7dhr906fvy4mze2yzawf895jhnc3p7qmljdugm6gsrurqev showed me this the other day. Its never happened to me but looks cool
I spent 3 days trying to fix it thinking it was a bug i introduced during the nostrdb refactor, only to realize it wasn’t caused by me. I’m hoping apple fixes it in the next beta build
I don’t know what this is. Not every client is expected to render every note type. Damus will never implement moderated communities.
Not seeing any of the nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk daily reports on the Damus TestFlight versions pushed yesterday. If I roll back to v1.6(7) then I can see them again. Our other posts still show up, but I don’t see the daily reports. Any ideas? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
Here’s the note ID for yesterday’s. It still shows in other clients, and we tried rebroadcasting.
nostr:note17ucj4343pzehza8ehsgxzgzaum8nl6gsy5ql4t8ct0nu3ekl4ynshyap2a
Ill debug, thx
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s I still have disappearing text bug on iOS 17 even though it said it was fixed
Example note
nostr:note1jn33nlfhdv8t7x747h7njxfz4q8nj4edj82d4pddvkysphwl0tqqlgyn47
Had to revert it because it was causing thread glitches
Haha its crazy this isn’t done yet. Ill add a reminder so i actually do this
Why does this note appear in Damus with the “naddr” address, and nobody visually tagged in note, but it shows that I’m tagging you, Gigi, and Pablo when I open a reply?
Cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 
Damus doesn’t support those yet, and you can be tagged without it being in the body
