🚀 New Damus TestFlight is live — and it’s a banger.

🔍 Web of Trust just got smarter (reply guy filter in threads = activated)

👥 Follow Packs are here — find your crowd

💸 Wallet UX upgrades

🛠️ Plus a bunch of behind-the-scenes magic

Big shoutout to our Purple Subscribers for being the first to test the chaos — and to our unstoppable open source devs. You’re building the future and killing it!

Join the TestFlight here: https://damus.io/purple/login/

Full Changelog:

### Added

- Added send feature to the wallet view (Daniel D’Aquino)

- Added popover tips to DMs and Notifications toolbars on Trusted Network button (Terry Yiu)

- Added tip in threads to inform users what trusted network means (Terry Yiu)

- Added web of trust reply sorting in threads to mitigate spam (Terry Yiu)

- Added follow list kind 39089 (ericholguin)

- Added follow pack preview (ericholguin)

- Added follow pack timeline to Universe View (ericholguin)

- Added NIP-05 favicon to profile names and NIP-05 web of trust feed (Terry Yiu)

- Display uploading indicator in post view (Swift Coder)

### Changed

- Removed media from regular link previews if media is already being shown (Terry Yiu)

- Renamed Friends of Friends to Trusted Network (Terry Yiu)

- Added privacy-based redaction to nsec in key settings view (Terry Yiu)

- Added privacy-based redaction to wallet view (Terry Yiu)

- Renamed Bitcoin Beach wallet to Blink (Terry Yiu)

### Fixed

- Fixed note rendering to include regular link previews with media removed when media previews are disabled (Terry Yiu)

- Improve error handling on wallet send feature (Daniel D’Aquino)

- Fixed issue where the text "??" would appear on the balance while loading (Daniel D’Aquino)

- Hide end previewables when hashtags are present (Terry Yiu)

- Fixed wallet transactions to always show profile display name unless there is no pubkey (Terry Yiu)

- Fixed quotes view header alignment (Terry Yiu)

### Removed

- Removed hashtags in Universe View (ericholguin)

Reply to this note

Please Login to reply.

Discussion

Def is a banger tho

Can I join TestFlight somehow?

Arg. The link is in your note 🤦‍♂️

Let us know if you run into any issues!

how about 'activate mark down feed mode' ? 🤔

nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5

Where?

When?

What job does markdown help you accomplish on a short form nostr app like Damus?

i just thinking about 'Notes' on nostr

markdown is more function version of note 😅🙏

Nip-01 doesnt specify markdown, and jt has critical mass/adoption.

For longform markdown you can add feedback here: https://github.com/nostrability/nostrability/issues/146

markdown is enabled in longform notes! damus just doesn't compose those yet

get in touch with inner grammar nazi and strict hot librarian chick and PRIORITIZE... markdown is the true hot add on an app based on text bruh

- thanks for the work you do.

😉

very unhinged comment but i'll allow it

Curious why the follower count number not being cached? Is that efficient to just restore number from previous cache?

to get an accurate follower count you would need to download the contact list of everyone who follows you. let's say you had 20,000 followers, that would be 800MB, assuming 50kB contact list size which is typical.

we could in theory do this, but would be a waste of bandwidth, and there are bots that spam follows.

there is no such thing as follow counts on a decentralized protocol

I mean if you look into Twitter/X API there’s “followes_count: 99” objects, why the client not save the contact number count locally, just the total number not the entire list?

So by default it will not download entire followers list, but when user do, it will cache that (only the number), so next time user will see the approximate last time follower number

because nostr is not an api, and there is no follows_count. If you want to propose that as a protocol extension then by all means, but most nostr devs already find kind3 contact lists problematic so it’s unlikely to happen.

as for caching counts when you download lists, yes thats the best you can do. but considering it is so easy to fake follow counts i don’t think its worth it or meaningful.

A more meaningful metric in a decentralized network is eigencentrality (like pagerank but for web of trust)

primal.net did caching btw despite its on the back end.

I mean its such annoying that everytime I load someone profile in Damus it must load all followers from 0.

yes but primal is not a nostr client. I am building a nostr client.

*feedback rejected*

not rejected, just giving my feedback to your feedback. I have been thinking about this for 3+ years

clients are not meant to trust relays in any way, i don’t see how you could even trust follow counts from relays in the outbox model.

You of course have a trusted index, but indexers abuse those to promote their friends

Followers count doesn’t need to be trusted, accurate, or complicated.

but the way Damus force user to click “Download Follower” is just ugly. Saving/caching integer value locally doesnt cost that much but yet intuitive in UX perspective

yes its planned in nostrdb, as well as cached wot scores based on incoming contact lists. Like i said its the best you can do, other than hyperloglog counts