Nostr Web Client

It's a NIP-96 and blossom server... That doesn't play nicely with Amethyst, but works well for Snort.

It doesn't?

I'm getting the same authorization errors I had weeks ago on my own install of it that I told you about.

Now I'm getting this though. https://nostrcheck.me/media/3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24/6c25bf90ead8362c786b590aa319b64c6a10e1181ef66e6316994010a27bbf17.webp

What's the server address you are pasting in the Media Servers screen?

https://nostrcheck.me/media/3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24/9e8c707d893c9eb300c3f21dc7b7daaa3162e32435470126928c50bb3660db10.webp

I'm using it on Amethyst and it works, maybe run latest version

If I'm not running the latest version seconds after launch I have failed.

It seems to be intermittent just like my local install. I tried it several times with failure and the last two times it worked. However as before I have to manually add the .webp extension.

I think it's up to clients to add file extensions nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau kind 1 posts require it for parsing

Ohhh.. I didn't know that. How does that work? Are you returning the nip94Event with tags where the filename doesn't have an extension?

From mime type

nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpramhxue69uhkummnw3ez6un9d3shjtnyv4ex26mjdaehxtndv5hsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshszxthwden5te0wfjkccte9ekk7mt0wd68ytnsd9hxktc79dllq any chance you can whitelist my key to test this on your server? :)

Nevermind, I can test on void.cat directly

Sorry. Yeah we're running the same docker verisons I believe.

Added your npub anyway so that you can test since I have whitelisted npubs and Kieran does not.

On void.cat, the mime type for a PNG is coming as application/octet-stream

Is that correct?

It just returns the content type from the upload, you're getting the fallback type so probably didn't set it in the request

So, I am sending image/png as form field content_type, but it always returns with application/octet-stream.

I am not sure what I am doing wrong to get this.

Also, I'm getting a NIP-98 related timestamp error on Amethyst using my own install as well as Kieran's server.

route96:routes::nip96::_ > Request guard `Nip98Auth failed: "Created timestamp is in the future"

If I disable whitelisted npubs it works, since it's not using authorization.

Can you check date time of the server and date time of the phone?

My sever and docker container are in sync with NTP running. Phone seems accurate too.

Luxas 1y ago

Yes, I had this same issue with timestamp on Amethyst for NostrMedia.com and had to set an acceptable time deviation rule. As for the other errors, mine is both Blossom and NIP-96, but afaik most folks aren't having issues uploading, if you also wanted another sample to test nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

Interesting. How big is your acceptable deviation?

I have a feeling that some phones stay a few seconds in the future.

Luxas 1y ago

I set it pretty far-future at 5sec. But I think it was only closer to being 1-2 sec off. I should prob scale that back down now.

Ah maybe we don't use that one atm, only content type header, will check

I also send it as part of the multipart file. I am not sure where that goes though 🤔

Maybe it's because you have multiple servers in your list, try with just your route96 server

RandalM 1y ago

Talk down to me. What does it do?

Route96 id a "Nostr media server". You can run your own or use the publicly available one at https://void.cat or https://nostr.download

Lez 1y ago

Probably already discussed, but why do we have 2 protocols for 1 task? It seems there is a lot of overlapping between them.