XSF Communications Team - 2025-10-27

Good afternoon. I have added support of DOAP (XMPP) to Greasemonkey Newspaper extension, so it is possible to view DOAP files as XHTML inside HTTP client software, such as Falkon, Otter Browser, et cetera. https://greasyfork.org/en/scripts/465932-newspaper-syndication-feed-reader Is this qualified to be featured in the XMPP Newsletter?

Dear all, After the disucssions on publication efforts, we investigated our options and choose SocialBu as aggregator and distributor for almost all of our social media accounts. This service allows us to prepare, schedule and also cross-platform manage media posts. We also will investigate their automation options in the future. We have taken the cost on our private cost so far asking Board for a continuous support. CC Guus

Sounds like a good tool to have! Are we already test-running that tomorrow-morning, or is that a bit optimistic?

> Sounds like a good tool to have! Are we already test-running that tomorrow-morning, or is that a bit optimistic? So far everything is scheduled. Please check the publication of the blogpost and nothing holds it back of course ↺

The blogpost has already been merged, so that should automatically pop up tomorrow just after 8 in the morning (CET) without further human intervention needed.

One good thing would be to double-check that the URLs that are in the social media posts correspond with what will be live. I see no reason why they wouldn't be, but that's something that we can only verify tomorrow morning.

> The blogpost has already been merged, so that should automatically pop up tomorrow just after 8 in the morning (CET) without further human intervention needed. I know, but I speak out of expierence with the infrastructure 🥲 ↺

> One good thing would be to double-check that the URLs that are in the social media posts correspond with what will be live. I see no reason why they wouldn't be, but that's something that we can only verify tomorrow morning. That too ↺

emus: are the social media posts scheduled to go out automatically? If so: at what time? (what's the window in which I can raise alarm if something is not quite right)?

09:30 am ↺

Is that good? ↺

Excellent.

> One good thing would be to double-check that the URLs that are in the social media posts correspond with what will be live. I see no reason why they wouldn't be, but that's something that we can only verify tomorrow morning. I double checked that yesterday

💪

Given that this bew tool will make doing social media postings dramatically more easy/less time consuming: can we reconsider doing that second wave?

> Given that this bew tool will make doing social media postings dramatically more easy/less time consuming: can we reconsider doing that second wave? I would prefer to align with Board first as this puts potential extra pressure on us with Sponsor Tiers. So this is not a capability issue. But sure, in general, we can expand our activites with this. (And Board need to pay the 190$ annually to keep this capability of course) ↺

> Dear all, > > After the disucssions on publication efforts, we investigated our options and choose SocialBu as aggregator and distributor for almost all of our social media accounts. > > This service allows us to prepare, schedule and also cross-platform manage media posts. We also will investigate their automation options in the future. > > We have taken the cost on our private cost so far asking Board for a continuous support. > > CC Guus emus. I am currently working on content publishing and distribution platform which supports Gemini, HTTP, and XMPP; and I intend to add ActivityPub support also. With additional help, more networks may be added. https://git.xmpp-it.net/sch/Rivista https://journal.woodpeckersnest.eu ↺

Additionally, it will also be able to aggregate contents. Slixfeed already aggregates contents, and publishes them over HTTP, similarly to the form of the so called "planet" platforms. ✏

What is the pressure with relation to Sponsor Tiers, emus?

I don't think we promise _any_ social media amplification to sponsors - we only promise blog posts.

(and, fwiw, a 190$ annual fee should be a no-brainer to accept for Board, in my opinion)

cool

> I don't think we promise _any_ social media amplification to sponsors - we only promise blog posts. We may do create amplifications through such activities. And they may put this as inquiry to Board / XSF. Next problem is that this is formally advertise with sponsor posts. We are actually not allowed to on nodes like fosstodon. Im also not sure for reddit. ↺

> I don't think we promise _any_ social media amplification to sponsors - we only promise blog posts. And we create again, anplifications for others, and to keep this fair and balance interest, we need rules I forsee. ↺

I think we put lots of efforts to get this as right as we can at the moment. I think its more important to ensure others are sharing this.

> We may do create amplifications through such activities. And they may put this as inquiry to Board / XSF. > > Next problem is that this is formally advertise with sponsor posts. We are actually not allowed to on nodes like fosstodon. Im also not sure for reddit. let's talk about this once the situation arises ↺

while we're currently running a testing phase with SocialBu, we can schedule waves of posts easily. naturally, this becomes harder if we don't continue using it after the testing phase. I don't think Comm-Team is setting expectations there.

Well, then go ahead.

cal0pteryx: are you still near a computer? I love your super quick fix for that summary suggestion that I did! I currently am working on a chromebook where I can't do any development. If you have some time to tinker, could you try and see how your new feature works for that blog post, with this custom summary? > Healthcare messaging must be secure, interoperable, and compliant, yet too often relies on closed consumer platforms. In the Netherlands, the forthcoming NTA 7532 specification aims to provide a national framework for secure, auditable communication between healthcare professionals. This open letter explains how the XMPP standard offers a proven foundation for NTA 7532, supporting vendor-independent and interoperable messaging. By engaging with initiatives like NTA 7532, the XSF promotes open, privacy-respecting communication technologies and invites collaboration with Dutch healthcare stakeholders and the global XMPP community.

https://upload.spacecloud.one:5281/file_share/068ffcf1-fb84-7880-8dfd-87eb6763ecf3/1.png

top: before; bottom: with your custom summary

Oh, that looks a lot better - no more weird inline headers!

Can you push that change to the blog (assuming that it's not possible for that to mess up the automation that was set up today) please?

newsletter editors: I hope you start making use of this new feature too! It's a small thing but brings a nice improvement.

> Can you push that change to the blog (assuming that it's not possible for that to mess up the automation that was set up today) please? sure, just pushed :) ↺

You rock!