Will @jb55 - 1y
I will continue to support damus iOS for the forseeable future, but to do things such as zapraisers and zap-to-unlock, i will need a different platform to build on. This is why I started an alternative, cross-platform client back in december that works on linux+mac desktop, android and web. This should also be the fastest client, it uses rust and low level graphics apis. Building a client like like this is much more difficult, but will be worth it in the long run. Damus iOS will continue to be where I spend most of my time, and we plan on making it the best iOS onboarding experience for nostr, but if we’re going to build a new circular economy for bitcoin in cyberspace, the apple appstore isn’t the place for this.
Derek Ross @Derek Ross - 1y
linux? check. android? check? web? check
omg! this has all of my wants and my needs. thank you!
Michael Matulef @Michael Matulef - 1y
👀 nostr:note1adrtltyhpwf3mavmcplruvawymxca8lxs408v5wyqunr089m97lsn9yrzv
Will used to have a new web client somewhere on the Damus domain but I forgot the URL. I wanted to see if that was it and if it was active 🥹
Hmm I 5K zapped your above response. The sats are gone from my wallet but don't show up on the note. ¯\_(ツ)_/¯
No, it was different than that. It had v3 in the name I believe.
pukka @jared - 1y
Thank you nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s for all that you to do! I’m here to support anyway I can as a #pleb 🤙🏼💜 When corporations controls the money you spend to communicate, it controls the quantity, quality, and topics of speech that can be heard in the public arena. If that’s not a Freedom of Speech issue, I don’t know what is. #nostr #plebchain
corndalorian @corndalorian - 1y
Oh ok. Don’t think I ever saw that one.
oh it was just https://damus.io/webv3/
yeah it was just a prototype though, not even close to a usable nostr client yet. But I got this same code working on android, web and desktop. So its doable.
The: Daniel⚡️ @The: Daniel⚡️ - 1y
If Damus comes to Android that would probably inform my next choice of phone.
i assume this is the one since you can add different columns
awesome. thank you again for all of your hard work. i am extremely excited for this upcoming client.
c80b5 - 1y
You da man, Will! Really glad to hear this.
river @river - 1y
https://nostr.build/i/bc65cd19fb98a8b02554a534cea0b07a649899d35142856db55758513978cc16.jpg
This is with no optimization’s 😅
damien @damien - 1y
💜
Pextar @Pextar - 1y
💜🫂
gino @gino - 1y
What about Damus as a PWA?
Vitor Pamplona @Vitor Pamplona - 1y
Please do Gossip from the start. We should get rid of the style of apps (with fixed relay lists) we helped create.
e0339 - 1y
This. Fixed relay list clients are simpler and work well on a small network but don’t scale as Nostr expands and you have find notes on relays you’ve never heard of.
Have the relay list specs in Nostr ossified? Where does one look to find the “home” relay and/or a relay list for a gossip implementation? I remember it seemed to be under debate a few months ago
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c can probably describe better, but I think by Gossip Model we generally mean that the app figures out where to get posts based on the author's write relay list. The amount of connected relays changes significantly over time. That initial description could be expanded to using any relays that are declared in the event kind you are looking for. Public Chats, for instance, should be based on the preferred relay of the channel metadata + relays from your follow lists (so you never miss a follow's chat post even if it's not in the main relay of the channel).
Right, but aren’t there like 3 kinds that can store relay information associated with an npub? Or do you specifically mean the version of relay lists that allows read/write specification?
Ahhh is it nip-65? I think this may be different than the relay lists I am familiar with. https://github.com/nostr-protocol/nips/commits/master/65.md
You can use both. No need to be shy :)