The behavior of opening-up of a website only is integrated into Damus. However which website to load is up to the user. In this case it’s Nostr.build. They will have a field to type in Nostr.build or any other image uploader website of their choice. This website will be loaded in Damus native sheet.

Reply to this note

Please Login to reply.

Discussion

Agree with Will, why not just bypass the website and directly integrate like Twitter? User can still choose their repository.

Like it’s done on Snort for example.

Last I checked, Snort let’s you choose an uploader (nostr.build is an option), but has an integrated button that uploads and paste the link. Let me check again..

You’re right. This is how it works now. And it’s great! So simple and fast. Why someone need to invent the wheel again?

I need your help to do this. I needed contract information (or api request response documentation) on how a client (Damus) will communicate to the server (Nostr.build) to send the image. After success what are the parameters that are received from the server. Based on this I can work on the direct integration. Will you be able to provide?