XSF Communications Team - 2025-01-08

Blasta might be fully compatible with Libervia and Movim. I have wrote the reasons to the mailing-list Standards. https://mail.jabber.org/hyperkitty/list/standards@xmpp.org/thread/QPHHLQKQJBHOE4ZW5IQFVLNXXABH26DW/ *Blasta, Libervia, and Movim*

gnemmi. Please kindly read the post and tell me what do you think.

Hello and good morning everyone!

You guys .. I guess someone had to do it .. and that someone ended up to be me =P

https://github.com/xsf/xmpp.org/pull/1469

Created 2025-01-10-fosdem2025.md based on content/blog/2024-01-04-fosdem2024.md Things that still need to be checked and/or confirmed: Will Goffi be the only one doing a presentation? Will the booth be at the traditional location ( K building 2nd floor, beside the elevator )? Will there be swag and other goodies besides stickers? I did ask around but I couldn't find more information than what it's already available in the file 😕

cal0pteryx, MattJ, could you please take a look when you have a spare minute and confirm or tell me what to correct on that document?

I hope I didn't do *that* bad .. 🫠

Schimon, will do!

Also, goffi you might want to check it out and confirm the information is correct or that it needs updating and/or editing 😉

> 'evening *. Do you think the Italian wiki would be worth mentioning? https://wiki.xmpp-it.net/ Pardon me if it already was, my memory isn't the best; I should check the past newsletters, but asking is faster ^^ Yes. I've been thinking about the possibility of adding an "## XMPP Resources" title to the Newsletter ... that would allow us to add information about wikis and other resources like the recent updates on search.jabber.network ↺

> cal0pteryx, MattJ, could you please take a look when you have a spare minute and confirm or tell me what to correct on that document? Sorry, it wasn't MattJ .. my bad .. I actually meant ralphm ↺

I think it goes without saying that https://github.com/xsf/xmpp.org/pull/1469 is open for reviews .. but, there you go, I said it 😊

Schimon, I just read your mail and IMHO I think that your best bet is to go straight to the source and get in touch with goffi and edhelas to talk about it and ask them what they think. They, both, have always been *super nice guys* to me. So I don't think you would have much of a problem if you try to contact them in regards to the content of your mail.

Schimon, also of interest: have you seen this? https://fosdem.org/2025/schedule/event/fosdem-2025-5721-a-universal-and-stable-api-to-everything-xmpp/

Schimon What I'm doing in Movim is to publish Atom with two <content/> elements, one with type = xhtml and one with type = text that is actually the Markdown

This allows articles to be easily edited and when I republish I convert the Markdown > XHTML

Schimon,; told you 😁

edhelas, ❤️

edhelas. Concerning to the formatted XHTML. Based on my last observation at posts that were sourced from Movim. The contents that are generated by Movim are always _stored_ as plaintext. It means, that server-side frontend has to parse the Markdown formatted text. This is what I did with Rivista XJP, as most of my test posts are of Movim. Is this correct? ✏

Nope, as I explained above

Yes. Thank you. I will examine my statement.

edhelas. The main content field of Blasta is currently a plaintext summary. Soon, a formatted content field, probably in the style of Movim, be added. The summary and content fields are optional (also by the standard itself). When both fields are utilized: - Summary be shown if a post is displayed in a list (e.g. search results). - Content be shown if a single post is viewed (e.g. permalink).

Schimon you were actually aware of that, you opened a ticket about it https://github.com/movim/movim/issues/1335

edhelas. Yes. But the message that you have wrote here implied that messages are stored as XHTML and then are converted to Markdown upon editing. This is why I have sent a question again, assuming that it has changed.

I still think that text/markdown, albeit is not a part of the Atom Syndication Format would be useful, until this matter is settled by XMPP or IETF. ✏

*Lagrange* (Gemini and Gopher browser) I have asked to add four (4) distinguished icons to represent XMPP hyperlinks. Please vote and comment for this feature. https://github.com/skyjake/lagrange/issues/706

No, if you read carefully my message above, Movim store TWO <contents/> one in Markdown, one in XHTML ✏

gnemmi: thanks for that. The section about my talk seems alright.

Schimon: the "text" content is mandatory in the specification, even if you publish xhtml, so if you publish rich content you need both. If it's text only, obviously one is enough. Also Libervia is current using XEP-0277 indeed, but I'll probably move to edhelas's specification as it should be compatible, I just have no time for that now (and I won't have time for anything until FOSDEM).

Schimon: and side remark, you should ask this kind of question on jdev@, standard@ is to talk about specification themselves (it's not a big deal I think, I'm just saying that for your future messages).

> No, if you read carefully my message above, Movim store TWO <contents/> one in Markdown, one in XHTML edhelas. Sorry. I have forgot to mention that I probably parsed only one element (probably summary), so I did not notice it. I will examine again. Thank you for your time, attention and help in clarifying this concern. ↺

> Schimon: the "text" content is mandatory in the specification, even if you publish xhtml, so if you publish rich content you need both. If it's text only, obviously one is enough. Also Libervia is current using XEP-0277 indeed, but I'll probably move to edhelas's specification as it should be compatible, I just have no time for that now (and I won't have time for anything until FOSDEM). Fine, so I will be sure to be compatible with XEP-0472 of edhelas. ↺

> Schimon: and side remark, you should ask this kind of question on jdev@, standard@ is to talk about specification themselves (it's not a big deal I think, I'm just saying that for your future messages). goffi. I am aware of it, yet @jdev has been closed in favour of @standard. Has not it? ✏ ↺

> gnemmi: thanks for that. The section about my talk seems alright. Perfect! You are very welcome! 🤗🤗🤗

Thanks for checking!

Schimon: ah right, sorry, I forgot about that.

https://mail.jabber.org/hyperkitty/list/jdev@jabber.org/thread/SVFQNPNIDBUJA7PGNGV4A7PFAOCKOBM5/ list shutdown

so yes I guess, standard@ is the place to go now then.

my bad.

No worries. I am for @jdev, and I want it to be reinstated.

>> 'evening *. Do you think the Italian wiki would be worth mentioning? https://wiki.xmpp-it.net/ Pardon me if it already was, my memory isn't the best; I should check the past newsletters, but asking is faster ^^ > Yes. I've been thinking about the possibility of adding an "## XMPP Resources" title to the Newsletter ... that would allow us to add information about wikis and other resources like the recent updates on search.jabber.network 👍 ↺

gnemmi. I think that this would be worth to follow, and publish once XMPP support is established. https://github.com/snarfed/granary/issues/860 XMPP PubSub

gnemmi, I reviewed and published the current newsletter. Great work! :)