Default settings:
blossom.primal.net
Media mirrors disabled
I'm also unable to upload media on Android. Maybe something doesn't like talking to the media servers? CC nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet500ww4r nostr:nprofile1qqstzzcdte06a8rvfz5vwlm7t2759fu7jjqwykjqjsz36jayec2y26cprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsud245w
Not sure why I did this as an RT instead of a reply 🫠
I'm also unable to upload media on Android. Maybe something doesn't like talking to the media servers? CC nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet500ww4r nostr:nprofile1qqstzzcdte06a8rvfz5vwlm7t2759fu7jjqwykjqjsz36jayec2y26cprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsud245w
I think it's mobile vs desktop. I don't see the images in Android, but desktop appears fine
I can't see the note you're referencing 😭
🔔 🔔 NEW OP_RETURN 🔔 🔔
Book of Nakamoto, Chapter 3, Verses 4–11 And Satoshi spake, not in whispers but in hex, saying: “Thou shalt not embed thine data in every field, for the blockchain is not thy diary.” “Yet I bestow upon thee OP_RETURN, a sanctuary for up to 40 bytes — no more, lest ye walk the path of vanity.” “For 40 is the number of discipline: 40 bytes for thy message, no more than is righteous, no less than is truthful.” “And behold, I give thee one more blessing: the coinbase message. A field untouched by consensus, wherein miners may write freely.” “Use it to bear witness, to mark genesis, to declare revolt — as I once wrote about the Chancellor” “But thou shalt not waste it with shills and tokens of greed, or the wrath of prune shall be upon thee.” And so the nodes upheld this covenant, and the mempool was serene. So go forth, brothers and sisters. Let us inscribe only that which is worthy. And let thy payloads be small, lest one abuse the sacred ledger for thine idle bytes. In the name of the Nonce, the Witness, and the Unspent, Amen.
https://mempool.space/tx/91c1fdaa933cd573dfe0cf9ee80d7f9f7f55f72d5da35c8d1abcac734d95c911
I shared an issue with the latest Primal release, and immediately multiple different team members were on the case and reproduced the issue before I could even send crash logs. nostr:nprofile1qqs9xtvrphl7p8qnua0gk9zusft33lqjkqqr7cwkr6g8wusu0lle8jcq9vhrm team is cracked! 💪💪💪
This is before even downloading. The APK hash listed in zapstore don't match the APK hash given in the release notes.
When I download the APK from github, I am able to confirm the hash matches the release notes, but I don't understand why Zapstore would show a different APK hash 🤷♂️
Ha, that's fair and I also agree with that take. IPFS isn't about censorship resistance though, it's about load balancing 🤷♂️
Would it be better for me to report this on GitHub?
Yeah, I can receive zaps but not send. I am using NWC, and it seems to crash when the payment request is made.
For context, I am on a degoogled device, so maybe one of the recent changes relies on googleplay services, which don't exist on my phone? 🤷♂️
Ugh, I just tried to upload a screen capture of my issue, but the app crashes in the final step of the media upload 😭
CC @miljan
nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvyzvgs2 I'd love to get your take on this. Don't want to waste my time if this sort of stuff has already been tried and failed.
Just updated, but now my zaps are broken. Every time I try to zap you, my app crashes 😭
Fantastic! Curious, is a UnifiedPush notification backend possible? For those of us on degoogled devices?
Oh trust me, I'm no IPFS maxi. But yeah, it's commonly mistaken for a storage service, so people often publish files without actual actually making sure it's stored (aka pinned) on a server somewhere. As a result their files disappear from the cache and fail to load.
There are lots of examples of IPFS working great when used correctly (i.e. making sure the content is pinned somewhere). Which is where Blossom + IPFS might be interesting... Blossom media servers could pin the files and IPFS could distribute those files very efficiently.
In fact, since IPFS would take nearly 100% of the bandwidth burden, the Blossom servers could be any low cost devices self hosted at home by enthusiasts without worrying about getting DOS'd when their meme goes viral.
When I say distribution, I mean in the sense of a CDN which acts like a caching layer to quickly replicate a file all around the world to distribute the load away from the primary storage server(s); which is what IPFS is. IPFS doesn't do storage it does caching and makes distribution much more efficient.
Don't get me wrong, Blossom looks great, but afaict it's just a content addressing protocol for retrieval from storage servers.
In fact, as I write this, I'm wondering if Blossom could be used in conjunction with IPFS to get the best of both worlds. Blossom media servers would become a lot cheaper to operate if there was a caching layer in front.... Damnit I don't have time for more projects 😆
Anyone know why the APK hash for Cake Wallet shown in #zapstore doesn't match the hash published on github? nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3
I'm new to Blossom, but it seems Blossom is intended for file storage, but IPFS is intended for file distribution. It seems they solve different problems. What am I missing?
Lol, so you dodged the main point and decided to argue everything else. Anyone can see for themselves that it would be more private to not have an LSP in the first place, rather than hope that Bolt11 has confused their LSP sufficiently.
I don't think you're actually willing to accept new information here, so no point in arguing. I'm out. Cheers mate 🍻
