expired certificate posts security risk to users of madoko local?

[tlyim]

The server at www.madoko.net cannot be connected with https, apparently due to certificate expired.

This also affect the use of madoko local.

Without https connection, it's not clear if allowing access to local drive posts a significant security risk to a user.

Can you please have a look at the expired certificate issue? Many thanks.

[Edmond110]

I can confirm, @tlyim, that the certificate has expired, at least that is the message when madoko.net is visited in Chrome. Safari doesn't complain for whatever reason, I don't know. Madoko is a great tool — it would be nice to still have access to it, though I realize there are alternatives.

[tlyim]

Thanks for your confirmation, @Edmond110 . Any alternative that you feel is worth a mention? Thanks.

[Edmond110]

The two alternatives I am looking at are Scrivomatic, which allows Scrivener to interact with Pandoc, and Quarto accessed via a plug-in for VS Code.

[tlyim]

Thanks for your reply. I had a look at Quarto and explored how it can substitute the {.fragment} functionality of Madoko. In case anyone is interested, some workarounds are discussed in the pages below:

• Fragments in 2-level bullet list (non-standard) quarto-dev/quarto-cli#1459
• Large '_files' folder created by RStudio, causing slow version control with Git quarto-dev/quarto-cli#1537