Using a new Primal? Are you taking advantage of the Blossom 🌸 protocol? Mirror? Censorship and single service failure resistance?
Login to reply
Replies (26)
Could ELI5 this?
When you upload media in your (in this case Primal) client, you should setup the mirroring of your media, so it is automatically uploaded to one more media host (blossom.band) in this case. If/when your primary media host is unavailable, capable client will automatically fetch it from the backup and people will still be able to see it.
Turn on dark mode right now or I'm gonna freak out 😂
To my fairly old eyes this works better 🤣
Done. Thanks.
Any chance you can explain how to use follow packs on primal on iPhone ?
I added blossom.band to Nostur (iOS) and tried adding an image (from Photos gallery) and it told me it isn’t in the correct format. Any idea why?
Nostur is not providing content-type as expected? Specs are clear about doing that. @Fabian any ideas?
I left a comment on one of their posts but haven’t heard anything yet.
Hmm, I am not sure what this error actually means. It is something that is produced by Nostur. I see that your picture was uploaded:
I just used Nostr.build to post this so you could see the error.
Oh…I misunderstood. You see that on blossom.band?
Yes, the link is from blossom band: @Galaxie 5000.blossom. band/ad15b6cad2dda9c74727138df1d95545ed2dcad2f9eb183d5d9a78757aebd9d8.jpg
Ok I’ll just have to see what they say
You could also try and see if Amethyst, Primal or any other client does and if it works. I am not sure if nip94 tags are causing the issue
Its throwing errors but uploading successfully
@Fabian I think I found the issue. It seems that Nostur expects full nip96 like response in blossom nip94 tags, while BUD08 just states tags array of arrays under nip94 field, nothing else. Initially I got it wrong too, and returned it as your check does. Now it is fixed and complies with BUD08 specs.
GitHub
nostr-essentials/Sources/NostrEssentials/NIP-96/UploadResponse.swift at d6f550579d15c850635c7c1ae73a7f4f6b80d1f6 · nostur-com/nostr-essentials
Start building your project with these nostr essentials - nostur-com/nostr-essentials
GitHub
nostr-essentials/Sources/NostrEssentials/Blossom/BlossomUploadResponse.swift at d6f550579d15c850635c7c1ae73a7f4f6b80d1f6 · nostur-com/nostr-essentials
Start building your project with these nostr essentials - nostur-com/nostr-essentials
GitHub
nostr-essentials/Sources/NostrEssentials/Blossom/BlossomUploader.swift at d6f550579d15c850635c7c1ae73a7f4f6b80d1f6 · nostur-com/nostr-essentials
Start building your project with these nostr essentials - nostur-com/nostr-essentials
I found a bug in Nostur, see my other response
Lol looks like you posted that at almost the same time. Thanks!
View quoted note →
Yeah, it took me some time to dig through the endless dependency tree to track it 😂🤣
I see, fixing this now thanks!
I made identical mistake in the beginning, and @Kieran spotted it before I realized the fault 😂🤣
When I was implementing it I was expecting it to be like nip96 too lol
🙏