Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
Derek Ross | 1 months ago (raw) | root | parent | reply | flag +1 
 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.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 Can you check date time of the server and date time of the phone?
▲ ▼
Derek Ross | 1 months ago (raw) | root | parent | reply | flag +1 
 My sever and docker container are in sync with NTP running. Phone seems accurate too.
▲ ▼
Lux | 1 months ago (raw) | root | parent | reply | flag +2 
 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 @Vitor Pamplona
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag +2 
 Interesting. How big is your acceptable deviation? 

I have a feeling that some phones stay a few seconds in the future.
▲ ▼
Lux | 1 months ago (raw) | root | parent | reply | flag +2 
 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.
▲ ▼
Kieran | 1 months ago (raw) | root | parent | reply | flag +1 
 Ah maybe we don't use that one atm, only content type header, will check
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag +1 
 I also send it as part of the multipart file.  I am not sure where that goes though 🤔