Are you aware of alternative ways to provide content in multiple languages?

Yes, as far as I know there's not been any improvements to the 'po' module.

Is this still the case?

It would be good to use letsencrypt for that, the difficulty is that they only allow renewing a limited number of certs per month, and doubling the number of domains would be problimatic.

There are ways to bundle multiple domain into a letsencrypt cert, and getting source.foo.branchable.com at the same time it gets foo.branchable.com is doable, but would add complexity.

It might be simpler to get rid of the "source." domain and move that to somewhere under the main domain. Where exactly to avoid conflicting with any page names? Probably not "/source" ...

The web interface does not allow disabling openid and emailauth plugins because that's probaly how the admin logs in and they could lock themselves out making that change.

Branchable admins can do it, so the procedure is:

1. Create an account using password authentication.
2. Change site configuration so that account is one of the admins.
3. Contact us to make the change.

I see you already had done #1 and #2 for guppy.branchable.com, so I've disabled openid and emailauth for that site.

See Read access restrictions.

Yes, if someone can see your email, they can login as you. The login emails do have some safeguards:

• A login link can only be used once, so if you've used it, and were successfully logged in, you know noone else also used it.
• A login link expires after 1 day.
• Only the most recently emailed login link can be used to log in.

This should make it secure enough for casual users editing a wiki or commenting. In some cases, it's not the best choice for logging in as a site's administrator, and you can keep the administrator logins limited to openid if necessary.

Encrypting the login email with gpg is a good idea, but would have to be implemented in ikiwiki ... and you would have to paste in their gpg public key so it knew who to encrypt to.

Thanks a lot, it is a very useful feature, that I just used. But I wonder... anybody eavesdropping on the network can get the login links. Would it make sense to send them gpg-encrypted ? (provided of course that the user adds a key ID in the setup.)

I see. I guess, I'll have to respect your position and see if I can figure something out. I have opened an issue over at the plugins repo, to see what they think about either of your suggestions.

That's right, you'd need to ask Debian to get it packaged (or package it yourself and get that package into Debian).

Alternatively, it might make sense to add the plugin to Ikiwiki, and as long as its dependecies are available in Debian (which Pandoc is), it could then be enabled on Branchable.

This may seem a roundabout way to get Branchable to support something, but many people can add packages to Debian, and anyone can submit patches to Ikiwiki to add plugins, while only a few people administer Branchable.