Feature request: Share a conversation via a URL

[natesilva]

Is your feature request related to a problem? Please describe.

I should have an easy and secure way to share a conversation out of Witsy.

Use case:

• Share a work-related conversation with a co-worker.
• Share technical help with family members.
• Share with my kids the answers to crazy questions that they ask.

The recipient might not have Witsy. They should still be able to view the conversation. If they have Witsy it would be cool if they could continue/fork the conversation.

Describe the solution you'd like

• Achievable today: Update the Export as Markdown/Export as PDF feature to (optionally?) invoke the OS share sheet.
• Ideal solution: Generate a secure URL that can be shared. It could even include features like an expiration date or extra password protection (in addition to being an unguessable random URL shared via HTTPS). This is an obvious feature to make available in a paid edition, but a free alternative such as creating a private Gist on GitHub would be great. That wouldn’t work for non-developers, though.

Describe alternatives you've considered

Currently the only practical sharing is to export as Markdown or PDF.

[ljbred08]

Interesting idea; the problem is that Witsy has no cloud backend and it will likely stay that way I think because of the open-source philosophy and the fact that there is not many good reasons to have one. (Privacy/transparency is one reason not to: currently anyone can download and be sure that their data is completely local and safe as no cloud component exists.)

However, I can think of a few possible ways that one could accomplish this

• Data URL: data:text/html;charset=utf-8,<your_url_encoded_html_content>. Dead simple but extremely large and clunky URL to share and I don't know the limit on size (if there is one).
• Let the user provide an ngrok key so that Witsy can self-host the shared link and have it tunneled to the other person. Would probably work well (and Witsy retains all control locally) but requires the user making an ngrok API key and the link will disappear if the computer turns off.
• Upload HTML to a simple hosting service such as x0.at. Best solution from a user perspective but relies on a free third-party service which could be taken down at any time.

Probably we're stuck with the markdown copying for now unless you want to try investigating ideas such as the ones above.

[nbonamy]

Yeah not sure how to do that right now. I have been thinking about it for a long time but hard to find a solution that does not incur costs