4 ms·
Due to the 2000 character limit I couldn't add the following: I'm sorry if this comes across as a question that belongs on Stack Exchange. It's a genuine probl
by nstart 11y ago
Due to the 2000 character limit I couldn't add the following:
I'm sorry if this comes across as a question that belongs on Stack Exchange. It's a genuine problem that I've been putting off for the last two years, and I finally need to address it. IRC's and other resources have all eventually pointed me in the direction of central servers. I even tried using custom url prefixes like "reshare://" but the experience is terrible since any site can attempt to set the protocol handler for reshare://. Imagine browsing to a random site (like a torrent seeder) that tries to hijack the reshare:// protocol. So currently stuck. Would appreciate any feedback and thoughts on this.
Thanks :)
- logn 11y agoI don't think you should be so quick to dismiss custom protocol handlers. To me that's the correct way to do this. Browsers are responsible for not letting handlers be hijacked. It's already used widely for mailto links. Firefox: https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers https://developer.mozilla.org/en-US/docs/Web-based_protocol_... ; Chrome (needs web+ prefix): https://developers.google.com/web/updates/2011/06/Registering-a-custom-protocol-handler?hl=en https://developers.google.com/web/updates/2011/06/Registerin... There is cross-domain local storage but it involves a central server and iframes, https://github.com/zendesk/cross-storage https://github.com/zendesk/cross-storage
- nstart 11y agothank you! This definitely seems to open up a path that I can look into. As for custom protocol handlers, their experience is pretty messy. But well, try and use what you've got eh.