Oddbean new post about | logout
▲ ▼
plor | 3 days ago (raw) | export | reply | flag 
 nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esdp32r9 I'm getting a hash mismatch for latest Olas on nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0. Seems like it might be a bad event.
▲ ▼
Zapstore | 3 days ago (raw) | root | parent | reply | flag 
 nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esdp32r9 if you don't mind publishing through a Github release would be easier on me until we're done with the rebrand transition.

Just create a tag, new release (go to your repo slash releases) and upload your APK there. Takes 2 min
▲ ▼
Zapstore | 3 days ago (raw) | root | parent | reply | flag 
 Oh, forget about it. This issue caused by the 1063 pointing to cdn.zap.store

If you publish again with --overwrite-release it should work
▲ ▼
PABLOF7z | 3 days ago (raw) | root | parent | reply | flag 
 Will do! If I publish the event changing the URL to my blossom server manually would that work or does zapstore expect files to be served from its own URL?
▲ ▼
Zapstore | 2 days ago (raw) | root | parent | reply | flag 
 You can definitely use any URL, or multiple

I want to support no URLs as well, and look for the x tag (hash) on publishers Blossom server list