@Oscar Merry
Building Fountain - the nostr powered podcast app
Relays (3)
- wss://relay.fountain.fm – read & write
- wss://relay.primal.net – read & write
- wss://relay.damus.io – read & write
Recent Notes
Wavlake, Fountain and RSS Blue have always made publisher feeds for artist and selfhosters can use sovereignfeeds to make their own. I've been building this into Music Side Project 2.0 to make it easi...
@ChadF and 33 others since Wavlake don't support feed redirects - the best thing for Artists if they want to switch to self-hosting is to delete their content from Wavlake after they've setup new feeds on Music Side Project.
However if not done correctly this creates another issue of duplicate artist profiles in Fountain and other apps. Maybe Music Side Project could have an "Import from Existing Feed" function that maintains the publisher, album, and track guids?
The most important thing is that the guids stay the same - if this is the case we can resolve duplicates on our side easily without losing any of the nostr data.
However if not done correctly this creates another issue of duplicate artist profiles in Fountain and other apps. Maybe Music Side Project could have an "Import from Existing Feed" function that maintains the publisher, album, and track guids?
The most important thing is that the guids stay the same - if this is the case we can resolve duplicates on our side easily without losing any of the nostr data.
1
Ah sorry sir. I missed it, however it appears broken. I'm running GrapheneOS on a Pixel 10 with Amber as a signer. https://blossom.primal.net/2ee812c3b8c70421d33196b92587dd60bb5af5ebad4b1bc8745bb54855...
I'll investigate - are you on the latest version 1.4.8?
1🫂1
The Fountain app was using over 40GB on my phone so I nuked the data from storage settings. To log back in requires using my nsec. Why not allow for alternative methods such as Amber nostr:nprofile1qq...
We do support Amber remote signer - do you not see this option?
1🤙1🫂1
@Vitor Pamplona @hodlbod 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?
Should I go ahead and make this switch now? Is anything to consider in terms support from clients?
5❤️1
How long before clips work and videos download nostr:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscpzemhxue69uhhyetvv9ujumn0wd68ytnfdenx7qg5waehxw309aex2mrp0yhxgctdw4eju6t0xwpcd7 nos...
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.
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.
3❤️1
Burgers and Bitcoin meetup at 2 on 2/21 at Steak n Shake in Greenville, SC.
I wanted to follow your instructions, but the fountain app could really use some work. I'm posting this note for nostr:npr...
Thanks for the feedback - are you on iOS or Android? Were you signing in with your nsec or remote signer?
@primal thanks for fixing notification loading speed on web - super snappy now! 🙌
Highlights make nostr reads come to life.
https://blossom.primal.net/698d2de8348058db180ef9363a4f076323a8b22018a614427c8023364079c7b6.mp4
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.
"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.