trinity-1686a

> @trinity-1686a Do you have any idea about Gitea email? As far as I can tell, it is working. The provider used is sometime very restrictive on mail from domains...

I don't have the issue on the article you mentioned, but I do have it on [another one](https://fediverse.blog/~/PlumeDev/new-plume-alpha). Maybe it only happen for article wrote by self?

I no longer have this issue on the article I linked, do you still have it?

I'm pretty sure this come from [rocket_csrf](https://github.com/Plume-org/rocket_csrf) (which we manage), but I've not been able to reproduce reliably to see what is wrong with it. @serra-allgood the link you provide...

As an alternative which works without js : use an anchor to get them directly to the form instead of going back up

`Html(..)` means whatever is inside won't get escaped so there can be html content in it (otherwise pictures, links and so on would be escaped instead of shown properly). `article`...

I think you are right. Yes you can make WIP PR, just write it's WIP in the title or the first message so we know it's not ready for review...

the markdown processor we use is [pulldown-cmark](https://github.com/raphlinus/pulldown-cmark)

I've [forked pulldown-cmark](https://git.joinplu.me/Plume/pulldown-cmark) and proposed a [pull-request to Plume](https://git.joinplu.me/Plume/Plume/pulls/853) that should fix this issue. This is less than ideal, but I'm getting bored that this issue is still here while...

fwiw, using fork/exec to start a pluggable transport such as obfs4 is not an arti thing, it also concerns tor, and is actually a [requirement from the PT spec](https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt#n100). The...