Q: Are Dives embeddable?

And a follow-up, if we share/embed a Dive publicly - does that mean anyone who views could get access to the token associated with the Dive? If so - what's the safe pattern here for public sharing?

Hey Sahil, Dives aren't embeddable just yet, but it's something the team is actively working on and should be coming in the near future!

For your follow up question, what is your specific use case? Would love to pass any information to our team!

Was wondering if we'd be able to replace our Mapbox map on https://dosomething.org/sweep-spot with a Dive

Thanks for sharing, i'll pass this on.

Seconding that my company has a need to embed a dive publicly. Even better would be if we could put it behind a simple password, similar to sharing airtable interface publicly works. See this screen recording as a demo.

Tia M. for visibility. Thank you!

We have a simple dashboard of the public political ad spending on meta. We use it internally, but want to be able to share it with our allies in other states (we are a political consulting firm), but don't want to expose it to adversarial firms.

Hey Nick, embedded Dives are actually live! You can check out the documentation here to help you get started. On the password piece, since the embed flow is designed to drop into your own app, the simplest path to what you're describing is to put a lightweight password gate in front of a page that hosts the embedded Dive. Does that should like a good option?

Thanks! I saw that, but that requires a lot of infrastructure on my end. I just want to be able to paste an iframe snippet into a squarespace site. I don't want to have to deal with hosting a server and implementing that auth flow, which is complicated (you need a mermaid diagram, that scares me 😉 ). Is there a reason why that is not feasible? Or maybe if your engineers wrote a single file js file that I could throw up on a cloudflare worker, then maybe that would be simple enough for me, such that I could do <iframe src="https://my-worker.workers.dev".... . Or it makes sense and is nice that you give us app developers the control the auth to the dive ourselves using this current API, but it would be nice if you added a wrapper abstraction on top where I could just paste an iframe url.

Hey Nick, Thanks for the explanation. The current setup for embedded Dives is as described in the docs, but I've summarized your request into a feature request and I'm speaking with the team about potential avenues for this use case. I'll keep you posted and let me know if you have any other questions.

Thank you! I'd be happy to chat more about my usecase if you/they want more clarification.