mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

11K
active users

#interoperability

9 posts8 participants0 posts today
Axel Knauf<p>I wanted to bridge IRC to XMPP and vice versa, here's how to do this with <a href="https://github.com/42wim/matterbridge?tab=readme-ov-file#matterbridge" rel="nofollow noopener" target="_blank">matterbridge</a>.</p><p>After having set up both <a href="https://fedi.4x31.dev/@id/statuses/01K2SMRQMMAPVCQ80TCAVZ0DBX" rel="nofollow noopener" target="_blank">IRC</a> and <a href="https://fedi.4x31.dev/@id/statuses/01K42Y23A3EF1SYQHCJMAVWCY3" rel="nofollow noopener" target="_blank">XMPP</a> servers on my VPS recently I realized that it's annoying to keep multiple clients running with accounts logged into each of them. So I wanted to bridge a specific IRC channel with a XMPP/Jabber group chat channel.</p><p>After a little research I went with <code>matterbridge</code> and set it up like this:</p><ul><li>Created a dedicated IRC user to join my existing channel <code>#lounge</code></li><li>IRC runs <a href="https://ergo.chat/" rel="nofollow noopener" target="_blank">ergo</a> with SASL auth enabled</li><li>Created a dedicated XMPP user to join group chat <code>bridging</code></li><li>XMPP is a <a href="https://prosody.im/" rel="nofollow noopener" target="_blank">prosody</a> server with <code>mod_muc</code> enabled</li></ul><p>My <code>matterbridge.toml</code> looks like this:</p><pre><code>[irc] [irc.default] Nick="bridge" NickServNick="bridge" NickServPassword="secret" Server="irc.example.org:6697" UseTLS=true UseSASL=true SkipTLSVerify=false RemoteNickFormat="[{PROTOCOL}] &lt;{NICK}&gt; " [xmpp] [xmpp.default] Server="xmpp.example.org:5222" Jid="bridge@xmpp.example.org" Password="secret" Muc="muc.xmpp.example.org" Nick="bridge" RemoteNickFormat="[{PROTOCOL}] &lt;{NICK}&gt; " [[gateway]] name="irc2xmpp" enable=true [[gateway.inout]] account="irc.default" channel="#lounge" [[gateway.inout]] account="xmpp.default" channel="bridging" </code></pre><p>I've created a dedicated non-login user on my VPS, downloaded the <a href="https://github.com/42wim/matterbridge/releases/tag/v1.26.0" rel="nofollow noopener" target="_blank">latest binary release</a>, verified the checksums and set up a <code>systemd</code> unit with this config (as per the docs):</p><pre><code>[Unit] Description=Matterbridge daemon After=network-online.target [Service] Type=simple ExecStart=/home/matterbridge/bin/matterbridge -conf /home/matterbridge/matterbridge.toml Restart=always RestartSec=30s User=matterbridge [Install] WantedBy=multi-user.target </code></pre><p>Then I ran reloaded <code>systemd</code>'s config and enabled the service. Logging in to the two chat solutions I was able to verify that messages are sent across. Hooray for interoperability!</p><p>Having this infrastructure in place I may want to bring in <a href="https://github.com/42wim/matterbridge/wiki/Gateway-config-%28channel-rules%29" rel="nofollow noopener" target="_blank">all kinds of other chat protocols</a> that are supported, .. &lt;3</p><p><a href="https://fedi.4x31.dev/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a> <a href="https://fedi.4x31.dev/tags/irc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IRC</span></a> <a href="https://fedi.4x31.dev/tags/xmpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a> <a href="https://fedi.4x31.dev/tags/bridge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bridge</span></a> <a href="https://fedi.4x31.dev/tags/matterbridge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>matterbridge</span></a> <a href="https://fedi.4x31.dev/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interoperability</span></a> <a href="https://fedi.4x31.dev/tags/chat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chat</span></a></p>
Harald Sack<p>2nd contribution by <span class="h-card" translate="no"><a href="https://sigmoid.social/@fizise" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fizise</span></a></span> team is presented by <span class="h-card" translate="no"><a href="https://sigmoid.social/@enorouzi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>enorouzi</span></a></span>: "AI4DiTraRe: Building the BFO-Compliant Chemotion Knowledge Graph", which is a <a href="https://sigmoid.social/tags/BFO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BFO</span></a> aligned, scalable <a href="https://sigmoid.social/tags/knowledgegraph" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>knowledgegraph</span></a> of experimental <a href="https://sigmoid.social/tags/chemistry" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chemistry</span></a> data that facilitates <a href="https://sigmoid.social/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interoperability</span></a>, <a href="https://sigmoid.social/tags/provenance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>provenance</span></a> tracking, and <a href="https://sigmoid.social/tags/Reasoning" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Reasoning</span></a> supporting AI-driven research and discovery. Joint work w <span class="h-card" translate="no"><a href="https://sigmoid.social/@joerg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>joerg</span></a></span> Nicole Jung</p><p>paper: <a href="https://sci-k.github.io/2025/papers/paper16.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">sci-k.github.io/2025/papers/pa</span><span class="invisible">per16.pdf</span></a><br>Chemotion-KG: <a href="https://ditrare.ise.fiz-karlsruhe.de/chemotion-kg/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ditrare.ise.fiz-karlsruhe.de/c</span><span class="invisible">hemotion-kg/</span></a></p><p><a href="https://sigmoid.social/tags/ditrare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ditrare</span></a> <a href="https://sigmoid.social/tags/semanticweb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>semanticweb</span></a> <a href="https://sigmoid.social/tags/ontologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ontologies</span></a> <a href="https://sigmoid.social/tags/chemistry" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chemistry</span></a> <span class="h-card" translate="no"><a href="https://nfdi.social/@NFDI4Chem" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>NFDI4Chem</span></a></span> <span class="h-card" translate="no"><a href="https://social.kit.edu/@DiTraRe" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>DiTraRe</span></a></span> <a href="https://sigmoid.social/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ai</span></a></p>
Andrea Callegaro<p>The idea of leaving <a href="https://mas.to/tags/whatsapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>whatsapp</span></a> for a more open, secure, and <a href="https://mas.to/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> respecting alternative is really appealing.</p><p>However, many people still only use WhatsApp, including for work chats. And as long as this remains the case, switching isn't easy</p><p>If this issue were solved, I’m sure a lot more people would move away.</p><p><a href="https://mas.to/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mas.to/tags/signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>signal</span></a> <a href="https://mas.to/tags/matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>matrix</span></a> <a href="https://mas.to/tags/chat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chat</span></a> <a href="https://mas.to/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interoperability</span></a></p>

Publication of the SpatioTemporal Asset Catalog Community Standards: The Open Geospatial Consortium (#OGC) has officially published the SpatioTemporal Asset Catalog (#STAC) Community Standards, marking a key milestone in data #interoperability. Built for flexibility and scalability, STAC provides a standardized...
spatialists.ch/posts/2025/10/2 #GIS #GISchat #geospatial #SwissGIS

Spatialists – geospatial newsPublication of the SpatioTemporal Asset Catalog Community Standards – Spatialists – geospatial news
More from Spatialists

Interoperability refers to the ability of different systems, organizations, or devices to communicate, exchange data, and use the shared information effectively. One of the most impactful applications of this concept lies in Healthcare Interoperability, where seamless data exchange between hospitals, devices, and electronic records can save lives and improve patient outcomes.

Source: zh.wikipedia.org/wiki/%E4%BA%9
#healthcare #software #interoperability

zh.wikipedia.org互操作性 - 维基百科,自由的百科全书

Fediverse + interoperability
pls repost:

Interoperability between all the fediverse software is for me the best thing about thefediverse.

At the moment I'm trying to track it using #mermaid. With this I want to show some problems.

any one of you UI & #mermaids experts have a better way of showing it?

(code will be published on codeberg and help will be really appreciated but I will announce that separately)

At the October 2025 "W3C in Europe🇪🇺 " meeting, @simone, @w3c #security lead, discussed digital identity standards in Europe and related security challenges. He outlined the move from centralized to federated and decentralized identity models, supported by W3C technologies like #WebAuthn, Verifiable Credentials, DIDs, and the Digital Credentials API. Key challenges include #interoperability across EU states and protecting privacy and human rights.

🎬 Watch: youtu.be/qEGkGoxvjrI