First of all, huge thanks for @matt for creating such an amazing service!! It fills an important niche and I look forward to Write.as becoming 100% libre (“free as in freedom”) like Mastodon!
Since I want to support this effort, I am looking into getting an account and seriously considering starting at the paid Casual level. But I have a few questions first:
(1) I am super excited to learn of ActivityPub integration and the federation abilities of Write.as (thank you!). However, it is a new “thing” for me so stupid question: Should I set up a Write.as account even if I have another account for something else that’s federated via ActivityPub? For example, if I have a Mastodon account somewhere, do I use it to sign into Write.as or do I still need my own Write.as account? If so, do they somehow link together? I’d appreciate some explanation on how all this fit together.
(2) Is the Markdown I can use when writing limited to what’s currently described in the guide? There are several things I’d really like to use when writing Markdown including (but not limited to): (a) Having image/figure captions attached to my images; (b) Video embedding (not just YouTube/Vimeo but also more generally); (c ) Make images themselves links to URLs I specify; (d) code blocks with syntax highlighting. Can any of the above be done on Write.as and/or are they in the pipeline? If so, is there a published and updated development roadmap?
(3) It seems that Write.as is currently financially sustainable, and I love your dedication to privacy and open source, that’s why I am seriously considering becoming a paid member. However, can you give any hints on the long term financial sustainability of Write.as (i.e. it will likely still be here 5+ years from now)? Radical finanacial transparancy would be so cool! Have you considered managing this project through Open Collective? If not I strongly suggest you check it out! Many successful projects run on Open Collective.
Sorry for the long questions, but I ask them because I am excited about Write.as! Thank you again @matt for such a great work!