This should be fixed on the latest version 1.4.8 - can you let me know if you are seeing any issues on this version? On sharing to nostr - we removed this option as we're working on more native sharing flow that should be coming soon - for now you can share either the link or the video natively by saving it and then posting from your main nostr client.

Thanks for the feedback - are you on iOS or Android? Were you signing in with your nsec or remote signer?

Great rant about Carney 🔥 https://fountain.fm/episode/5QJuJ1C2pOE26U8GIvDs

Yep look out for a new beta version dropping in the next ~24 hours - I'll follow up here as well

does damus pre-load audio from links in notes that contain og:audio metadata? It's great that damus renders a play button when these links are shared - but the pre-loading means we have to filter out any download stats for damus because we're not sure they represent real plays.

We have a big update coming to clipping this week - it should be available in beta tomorrow if you want to help test?

are you on the latest version 1.4.6?

I'll investigate - are you on the latest version 1.4.8?

We do support Amber remote signer - do you not see this option?

great thanks - will make the switch 👍

I see NIP-27 was changed to use q tags rather than e tags with mention markers - https://github.com/nostr-protocol/nips/pull/1751 Should I go ahead and make this switch now? Is anything to consider in terms support from clients?

yep here - https://fountain.fm/p/

thanks for fixing notification loading speed on web - super snappy now! 🙌

The NIP-84 spec says this: "A comment tag may be added to create a quote highlight. This MUST be rendered like a quote repost with the highlight as the quoted note. This is to prevent the creation and multiple notes (highlight + kind 1) for a single highlight action, which looks bad in micro-blogging clients where these notes may appear in succession." Based on this your highlight share would appear twice in client feeds that follow the spec? Not saying one way is better than the other but would be great to have alignment between clients on the proper way to share highlights to feeds.

this issue should be fixed in the latest version 1.4.7 - can you update to this version and let me know if you still experience anything like what you reported.