-
emus
deuill: ❤
-
flow
emus, FYI: XML elements in markdown are not rendered, e.g. https://github.com/xsf/xmpp.org/commit/9da2eb74e0a4729eaf17bcecbc88485b423bef79#diff-f4b174882d8adce2dc4936973907384a28020cc6305b138add2f5d3a669ef887R126 <sign/> does not appear in https://xmpp.org/2020/11/newsletter-11-november/
-
flow
that's probably something the newsletter editor(s) should be aware of, as we probably will mention an XML element here and then in the XSF newsletter
-
jonas’
flow, oh it does
-
jonas’
but only in the source code
-
Zash
Yay HTML passtrough
-
jonas’
Fix 'to'-attribute requirements: All content elements which are signed using OpenPGP need that attribute to prevent Surreptitious Forward Attacks. The <crypt> element does not require one, as the intented recipient is established by the encryption itself. The XEP had the requirements for <sign> and <crypt> mixed up.</crypt></sign></crypt>✎ -
jonas’
> Fix 'to'-attribute requirements: All content elements which are signed using OpenPGP need that attribute to prevent Surreptitious Forward Attacks. The <crypt> element does not require one, as the intented recipient is established by the encryption itself. The XEP had the requirements for <sign> and <crypt> mixed up.</crypt></sign></crypt> ✏
-
flow
IIRC the workaround is to use backticks around the XML elements in markdown
-
Zash
or backslash-escape, yes
-
Ge0rG
Somebody should add tooling to disallow html pass through without an explicit flag in the file
-
Zash
flow, PR it?
-
Zash
Ge0rG: Slightest idea of how one would do that to pelican?
-
Ge0rG
Zash: nope
-
emus
flow, jonas’: Thanks for reporting. I understood there was no intention to render actually? wurstsalat
-
flow
emus, the XML elements should appear in the sentence, as otherwise the sentence is broken
-
emus
ok, lets remind wurstsalat
-
wurstsalat
I’ll keep that in mind, thanks flow !