Hashtag

#interoperability

148 posts tagged with this hashtag.

@fsfe@mastodon.social

The @EUCommission published its first review on April 28.

We welcome that the EC has recognised our calls for greater transparency and accountability in the enforcement process. This is a step in the right direction.

We also welcome the recognition that by design is important for fair digital markets.

@smallcircles@social.coop · Reply to @reiver ⊼ (Charles) :batman:

@reiver

The article was triggered by a discussion on JSON vs JSON-LD I started on SocialHub.

This is imho the biggest pain point of the fediverse: we never specified how an extension is to be built according to best-practics such that a maximum level of is retained even when the balloons by its influx of new participants and apps & service providers.

I don't think our current post-facto interoperability work method - the best-we-have but still poor person's tool - is able to facilitate that kind of growth, and yet people are clamoring for it. Bring it on, they say. But not having much talk on what would be the most likely outcome of that, when it happens.

@ppcland@mastodon.social
@ppcland@mastodon.social
@smallcircles@social.coop · Reply to @reiver ⊼ (Charles) :batman:

@reiver

Today "ActivityStreams: Where do you want to go to today?" might be a slogan we borrowed from Microsoft.

The question is whether should be used - besides all the things it is already being used for - to also map to file systems.

The nature of is generally shunned in favor of plain . That in itself is fine, as long as:

a) information still represents valid .

b) information models still follow data modeling best practices.

c) information models are designed with in mind.

Not saying your approach is good or bad, just observing that everyone mapping and overloading their own app-specific semantics to the poor AS vocab looks to me a worst-practice. We can get away with it, as we made post-facto interop the poor man's accepted practice, lacking more rigorous extension process and guidance.

There are likely existing standardized ontologies.

@josemurilo@mato.social

A good thread on and . Excerpt:

"i think this just tests the and what people want to do with it to the limits, we're seeing vibe coded AT Protocol too!

Definitely highlights rough or under defined parts of specs & tests ."
@thisismissem.social

social.wake.st

wakest likes your bugs ⁂ (@liaizon@wake.st)

Slop coded fediverse servers are multiplying I guess we need to start tracking this somewhere!? What happens when there are more AI generated server frameworks then human written ones? The do-ocracy of implementation first protocol inconsistency sorta wins right now but that brakes down when there are more bots making the call then humans

Slop coded fediverse servers are multiplying I guess we need to start tracking this somewhere!? What happens when there are more AI generated server frameworks then human written ones? The do-ocracy of implementation first protocol inconsistency sorta wins right now but that brakes down when there are more bots making the call then humans

@josemurilo@mato.social

A good thread on and . Excerpt:

"i think this just tests the and what people want to do with it to the limits, we're seeing vibe coded AT Protocol too!

Definitely highlights rough or under defined parts of specs & tests ."
@thisismissem.social

social.wake.st

wakest likes your bugs ⁂ (@liaizon@wake.st)

Slop coded fediverse servers are multiplying I guess we need to start tracking this somewhere!? What happens when there are more AI generated server frameworks then human written ones? The do-ocracy of implementation first protocol inconsistency sorta wins right now but that brakes down when there are more bots making the call then humans

Slop coded fediverse servers are multiplying I guess we need to start tracking this somewhere!? What happens when there are more AI generated server frameworks then human written ones? The do-ocracy of implementation first protocol inconsistency sorta wins right now but that brakes down when there are more bots making the call then humans

@smallcircles@social.coop · Reply to Alex

@alex @MichalBryxi @evan

> The NoBot isn't app specific fwiw, it's pretty standard.

"pretty" boils down to de-facto standard, or rather it became a sorta kinda requirement by means of post-facto . In other words: Who comes first, and popularizes some custom app-specific extension, becomes owner of that part of the spec that is now considered protocol-native.

is app-specific too. Or Microblogging domain-specific perhaps, albeit implicitly then.

When it comes to considering it standard, we talk about accepting protocol decay. Specifically:

- Considering the way account profiles are handled to be part of the protocol.
- To handle special control words (or just ) in the profile text.

social.coop/@smallcircles/1161

social.coop

🫧 socialcoding.. (@smallcircles@social.coop)

Attached: 1 image I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828 Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498 @ben@werd.social #SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse

@smallcircles@social.coop · Reply to 🫧 socialcoding..

I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the

See also and for discussion: discuss.coding.social/t/diagra

Or join the Social experience design chatroom at: matrix.to/#/#socialcoding-foun

Also posted to at: socialhub.activitypub.rocks/t/

@ben

Diagram. Interoperability in practice. A chart with a horizontal axis that goes in 2 directions. On the left it moves towards chaotic grassroots growth, and on the right side towards open standards adoption. The Y-axis indicates level of complexity. The center indicates a low level of complexity.

On the left side of the axis we first find the ActivityPub open standard, with a relatively low complexity level. However the prevailing method to evolving the ecosystem is driven by post facto interoperability, where tech debt and protocol decay is introduced and accepted, which must be refactored and evolve alongside the open standard. Since this doesn’t happen, the fediverse grassroots environment is shifting more to the left into non-lineary increasing accidental complexity. Deviating more and more from the ActivityPub standard and the promise that it holds to offer the Future of Social networking.

On the right side, to contrast against fediverse, we find the Solid Project led by Sir Tim Berners-Lee, which is based on a whole range of W3C Linked Data related open standards and draft documents. There is no grassroots movement that drives progress, but a steering committee. Progress is restrained by open standards adoption and support. Higher levels of interoperability require more rigour and formal standardization, and this also leads to non-linear growth of, in this case, engineered complexity. Solution developers have to wait for many standards to mature, leading to inertia.
ALT text

Diagram. Interoperability in practice. A chart with a horizontal axis that goes in 2 directions. On the left it moves towards chaotic grassroots growth, and on the right side towards open standards adoption. The Y-axis indicates level of complexity. The center indicates a low level of complexity. On the left side of the axis we first find the ActivityPub open standard, with a relatively low complexity level. However the prevailing method to evolving the ecosystem is driven by post facto interoperability, where tech debt and protocol decay is introduced and accepted, which must be refactored and evolve alongside the open standard. Since this doesn’t happen, the fediverse grassroots environment is shifting more to the left into non-lineary increasing accidental complexity. Deviating more and more from the ActivityPub standard and the promise that it holds to offer the Future of Social networking. On the right side, to contrast against fediverse, we find the Solid Project led by Sir Tim Berners-Lee, which is based on a whole range of W3C Linked Data related open standards and draft documents. There is no grassroots movement that drives progress, but a steering committee. Progress is restrained by open standards adoption and support. Higher levels of interoperability require more rigour and formal standardization, and this also leads to non-linear growth of, in this case, engineered complexity. Solution developers have to wait for many standards to mature, leading to inertia.

@smallcircles@social.coop

:blobhyperthink:

The is a consensus between app on the app they want to spend time on to connect with the next app.

Taking care of their own herd, the users that flocked to their platform, they form narrow bridges, so a user may graze a bit of the grass in the adjacent meadow that is owned by a fellow dev.

Until now this -centric land ownership model works quite well, as a recent with delightful outcome among the lifestock has shown. And for every new land owner we can just build exponential more bridges to connect them all. Right?

social.coop/@smallcircles/1161

social.coop

🫧 socialcoding.. (@smallcircles@social.coop)

Complete this sentence: "I experience #fediverse as a .." #Poll #AskFedi #Microblogging #Mastodon #ActivityPub [ ] Bustling city [ ] Cozy village [ ] Ghost town [ ] Other (please comment)

@smallcircles@social.coop · Reply to 洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee @COSCUP

As you know I am proponent to emphasize the social aspects more, to drive healthy evolution of the .

The app-centric is a pure technosphere, where a tech-first approach deals with getting app features to the next app, and the protocol matures via post-facto 'follow-the-leader' . What happens in the sociosphere between people using the tech is de-facto of secondary concern, and apps are tweaked to try to deal with externalities. The resulting social landscape has become one of neighboring app kingdoms with guarded borders separating them. Everyone speaks microblog to each other, albeit with thick accents, hard to understand. The fediverse is social *because* of the people, and despite of the tech, that still severely restrains them.

It would be nice if the track name not just indicated a technology name. E.g. coding.social uses:

- Fediverse, a peopleverse
-
-

coding.social

Joyful creation for the Social web

We reimagine the social web and cocreate a peopleverse.

@petersuber@fediscience.org

"The [maker of ] has called on the European Commission in an open letter not to rely solely on 's proprietary format in the ongoing consultation on the Cyber Resilience Act (CRA). The EU Commission had published a call for feedback on the CRA guidelines on March 3, 2026. Feedback can be submitted exclusively via an XLSX template until March 31, 2026."
heise.de/en/news/LibreOffice-c

heise.de

LibreOffice criticizes EU Commission over proprietary XLSX formats

The Document Foundation criticizes the EU Commission for exclusively using Microsoft's XLSX format in the Cyber Resilience Act consultation.

@petersuber@fediscience.org

"The [maker of ] has called on the European Commission in an open letter not to rely solely on 's proprietary format in the ongoing consultation on the Cyber Resilience Act (CRA). The EU Commission had published a call for feedback on the CRA guidelines on March 3, 2026. Feedback can be submitted exclusively via an XLSX template until March 31, 2026."
heise.de/en/news/LibreOffice-c

heise.de

LibreOffice criticizes EU Commission over proprietary XLSX formats

The Document Foundation criticizes the EU Commission for exclusively using Microsoft's XLSX format in the Cyber Resilience Act consultation.

@smallcircles@social.coop · Reply to 洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee @COSCUP

As you know I am proponent to emphasize the social aspects more, to drive healthy evolution of the .

The app-centric is a pure technosphere, where a tech-first approach deals with getting app features to the next app, and the protocol matures via post-facto 'follow-the-leader' . What happens in the sociosphere between people using the tech is de-facto of secondary concern, and apps are tweaked to try to deal with externalities. The resulting social landscape has become one of neighboring app kingdoms with guarded borders separating them. Everyone speaks microblog to each other, albeit with thick accents, hard to understand. The fediverse is social *because* of the people, and despite of the tech, that still severely restrains them.

It would be nice if the track name not just indicated a technology name. E.g. coding.social uses:

- Fediverse, a peopleverse
-
-

coding.social

Joyful creation for the Social web

We reimagine the social web and cocreate a peopleverse.

@smallcircles@social.coop · Reply to 🫧 socialcoding..

Even more remarkable is the near complete absence of the developer community in mingling in the social side of the discussion.

To learn how actually *experience* this here fediverse. A which results from them tying their apps together, to hopefully get more than the sum of individual parts. By means of facilitating , technically speaking. But it involves more than getting that feature across the wire to the next app.

There's exists a clear gap between and , where the latter must serve the former to bring real solutions. Otherwise it is all apps and not much seamless social fabric to navigate. No peopleverse anywhere in sight. Just apps and users of them.

The apps see great success, and I enjoy their use a lot. But I don't see a future for the app-centric fediverse where it comes to providing mankind the future of .

social.coop/@smallcircles/1161

social.coop

🫧 socialcoding.. (@smallcircles@social.coop)

#ThoughtProvoker :blobhyperthink: The current fediverse is an evolutionary dead-end for 2 reasons: 1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay. 2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out. Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with. To avoid fedi to become less and less attractive to newcomers, we must now consider: “Why do we want to grow the open social web, and for whom?” -- @ben@werd.social http://coding.social/blog/shared-ownership/

@smallcircles@social.coop

:blobhyperthink:

The current fediverse is an evolutionary dead-end for 2 reasons:

1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.

2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.

Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.

To avoid fedi to become less and less attractive to newcomers, we must now consider:

“Why do we want to grow the open social web, and for whom?” -- @ben

coding.social/blog/shared-owne

coding.social

Shared responsible social web ownership

We strive for an inclusive social web that is by the people and for the people. But how do we guarantee equity and shared ownership?

@sovtechfund@mastodon.social · Reply to Sovereign Tech Agency

In our latest blog post, we explain our motivation for engaging in standards, reflect on conversations with maintainers, and outline the reasoning behind our current survey. The survey is still open and we encourage you to contribute your perspective.

➡️ Read our blog post: sovereign.tech/news/open-stand

➡️ Participate in the survey (runs until March, 9th): survey.sovereigntechfund.de/99

(2/2)

survey.sovereigntechfund.de

Powered by LimeSurvey – The Freshest Online Survey Tool

Create surveys in seconds with LimeSurvey. Easy to use, secure, and trusted by professionals worldwide. Get started free and unlock fresh insights today!

@smallcircles@social.coop · Reply to 🫧 socialcoding..

@david_megginson @ben

Though with regards to progress, there's a difference in both approaches.

At the side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.

While at side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix breakages.

The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.

@funkwhale@social.funkwhale.audio
@funkwhale@social.funkwhale.audio
@funkwhale@social.funkwhale.audio
@smallcircles@social.coop · Reply to 🫧 socialcoding..

, a *great start* providing the key ingredients.

, where things are cooked into a mush, by pragmatic though unsustainable fast-food preparation.

Recipe:

- Mash everything into
- Overload the semantic frying pan
- Sprinkle in combinatorial complexities
- Cook until too hot

Then simply keep stirring with increasing whack-a-mole maintenance burdens until project phased out.

Or become the post-facto leader and dominate the restaurant chain.

Recipe improvement tips:

- Add spice to the mix where you can!
- Participate in collective cooking.

@smallcircles@social.coop · Reply to VirtualPierogi

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at or .

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

@smallcircles@social.coop · Reply to Sean Tilley

@deadsuperhero

Yes. Mastodon has always given their own product decisions precedence over healthy evolution of the ecosystem as a whole. And despite many people being very frustrated about that, I think this is perfectly valid decision. After all choosing to implement an open standard should not come with the obligation to maintain/evolve that standard. It is only smart to do so, and Mastodon did this with an eye on their own product development.

Imho it is really the broader dev ecosystem that is at fault in letting the fedi be taken hostage by past Mastodon decisions, making them the post-facto leader. As for Mastodon API I'd argue that its users are not on the fediverse. They are on Mastodon.

Identity management may be killer feature, but only when first a sound foundation is in place. AS/AP isn't as-yet robust enough to be the future of social networking. I'd say the extensibility mechanism is killer feature, and having SDK's and devtools for that.

@smallcircles@social.coop · Reply to 🫧 socialcoding..

@sri @jsalvador @ben @nlnet

The fediverse has been weirdly stuck for many years, driven by app developers who attended first and foremost to their own app projects and only secondary to the technology base the entire app is built upon. There was also hardly funding to do anything else. It may be pragmatic approach, but its not smart, eventually weakening the entire ecosystem. And here we are today, with a mountain of protocol decay and tech debt holding us back.

For many years people, me included, have argued that we should focus on getting robust extensibility mechanisms in place, fill the holes, and not handwave it to say "yeah it is this and that sorta kinda". requires way more rigour at the protocol level.

Nice effect that had, was it opened people's eyes to the benefits of having a sound technology base. The ATProto ecosystems excites newcomers, whereas fedi only frustrates with its high barrier to entry and whack-a-mole dev.

@kirschner@mastodon.social

So great to again dedicated people from the European Commission's enforcement team, civil society and researchers on the panel

" regulation in the EU: Opening and for "
fosdem.org/2026/schedule/event

lecture hall with someone in the back holding an I love free software balloon.
ALT text

lecture hall with someone in the back holding an I love free software balloon.

5 people on a panel.
ALT text

5 people on a panel.

@rosylf@c.im

@maikel re: 12, 13, 14.

I've been on a slow descent into and integrating ecological patterns into "regular" life (do "regular" and "regulate" share etymology?), and the "CHAOS" aspect reminds me of nature, where resources aren't piled into silos or shelves or cabinets, but are readily available in adequate quantities all over. Keeping all things into a confined "order" merely means we have to fight the "chaos" of entropy that life has already learned to inhabit. Fighting it is a useless endeavor, usually ;)

Obsidian? Do you mean Obisian.md? I LOVE that tool. I keep a first-level directory on my portable drive solely as a workspace for my Obsidian projects (I have so many, but never too many, aha!). I'm curious about your note taking; have you used ? I haven't made full use of it, in shame, so if you do, I'm interested in your and how you structure your thoughts with it.

I second your preference for PDFs. If I might nerd out, I really wish that the family of standards took off for documents; PDFs used to (and some still do) rely on an XML format to bring all of the images and layers and what-have-you into one coherent package: the Portable Document Format (). If XML had better support across tech ecosystems, our notes (, typed, and automatic annotations) could inhabit one coherent substrate, all while preserving the operations and presentations we expect now from siloed formats, but also while enabling without reinventing tools that have existed for decades. I could imagine handwritten annotations being re-encoded as Scalable Vector Graphics (, used on webpages!) and included directly within the document you are annotating: never lost annotations or the document they reference again, because they _can_ stay together.

@simona@mastodon.design

"Threads, however, supports ActivityPub. Users on Threads can choose to share their posts with other Activity Pub servers, including Mastodon." – Well, only if the instance and/or end user decides so.

Surprised the article doesn't mention the absence of algorithm and advertising in the Fediverse. Imho it's a good selling point.

mastodon.social

Mastodon (@Mastodon@mastodon.social)

Not sure where to start with Mastodon? Here's some new year coverage from @TechCrunch@mstdn.social that provides a great overview. 🫶🏻 Want to learn even more? There's a fantastic community ready to help you level up your Fediverse skills. 🎉 https://techcrunch.com/2026/01/01/what-is-mastodon/

@Mastodon@mastodon.social

Not sure where to start with Mastodon? Here's some new year coverage from @TechCrunch that provides a great overview. 🫶🏻

Want to learn even more? There's a fantastic community ready to help you level up your Fediverse skills. 🎉

techcrunch.com/2026/01/01/what

techcrunch.com

A beginner's guide to Mastodon, the open source Twitter alternative | TechCrunch

Mastodon has almost doubled its userbase since Elon Musk took control of Twitter last month. Here's what you need to know about the platform.

@simona@mastodon.design

"Threads, however, supports ActivityPub. Users on Threads can choose to share their posts with other Activity Pub servers, including Mastodon." – Well, only if the instance and/or end user decides so.

Surprised the article doesn't mention the absence of algorithm and advertising in the Fediverse. Imho it's a good selling point.

mastodon.social

Mastodon (@Mastodon@mastodon.social)

Not sure where to start with Mastodon? Here's some new year coverage from @TechCrunch@mstdn.social that provides a great overview. 🫶🏻 Want to learn even more? There's a fantastic community ready to help you level up your Fediverse skills. 🎉 https://techcrunch.com/2026/01/01/what-is-mastodon/

@Mastodon@mastodon.social

Not sure where to start with Mastodon? Here's some new year coverage from @TechCrunch that provides a great overview. 🫶🏻

Want to learn even more? There's a fantastic community ready to help you level up your Fediverse skills. 🎉

techcrunch.com/2026/01/01/what

techcrunch.com

A beginner's guide to Mastodon, the open source Twitter alternative | TechCrunch

Mastodon has almost doubled its userbase since Elon Musk took control of Twitter last month. Here's what you need to know about the platform.

@Em0nM4stodon@infosec.exchange
@Em0nM4stodon@infosec.exchange
@Em0nM4stodon@infosec.exchange
@linuxfoundation@social.lfx.dev

Today we launch the Agentic AI Foundation (AAIF) with project contributions of MCP (Anthropic), goose (Block) and AGENTS.md (OpenAI), creating a shared ecosystem for tools, standards, and community-driven innovation.

Learn more about this major step toward open, interoperable agentic AI: linuxfoundation.org/press/linu

@linuxfoundation@social.lfx.dev

Today we launch the Agentic AI Foundation (AAIF) with project contributions of MCP (Anthropic), goose (Block) and AGENTS.md (OpenAI), creating a shared ecosystem for tools, standards, and community-driven innovation.

Learn more about this major step toward open, interoperable agentic AI: linuxfoundation.org/press/linu

@w3cdevs@w3c.social

⏰ The deadline to submit a proposal for the @w3c workshop on Smart Voice Agents (Feb 2026, virtual) is 27 Nov 2025!

Smart voice agents need clearer use cases, stronger , better -based interaction, and improved accuracy, , and multilingual support. Broader concerns include device coordination, , , regulatory gaps and emerging business models.

Don’t miss your chance to present your work and submit now: w3.org/2025/10/smartagents-wor

W3C Workshop on Smart Voice Agents - February 2026, Virtual on zoom
ALT text

W3C Workshop on Smart Voice Agents - February 2026, Virtual on zoom

@w3cdevs@w3c.social

⏰ The deadline to submit a proposal for the @w3c workshop on Smart Voice Agents (Feb 2026, virtual) is 27 Nov 2025!

Smart voice agents need clearer use cases, stronger , better -based interaction, and improved accuracy, , and multilingual support. Broader concerns include device coordination, , , regulatory gaps and emerging business models.

Don’t miss your chance to present your work and submit now: w3.org/2025/10/smartagents-wor

W3C Workshop on Smart Voice Agents - February 2026, Virtual on zoom
ALT text

W3C Workshop on Smart Voice Agents - February 2026, Virtual on zoom

@NGICommons@eupolicy.social

✈️ The @NGICommons team is heading to Brussels (20–21 Nov) for the !

Panels include MEPs, EC officials, open-source leaders, and Commons communities. All focused on building a resilient, interoperable, public-interest digital ecosystem

Stay tuned for more updates!
commons.ngi.eu/2025/11/20/ngi-

@martelinnovate @cnrs @linuxfoundation @openfuture @OpenForumEurope

@j2bryson@mastodon.social · Reply to Joanna Bryson, blathering

We're back to hear more bashing on the regulation that's helping us not demolish our own security like the US is and UK has. This time from Ralf Wintergerst, President, Bitkom in the context of

The EUDI Wallet: A Key Enabler in Building a Digital Europe Rooted in Sovereignty, Trust and

(everyone is talking about interoperability today but no one can pronounce it :-D I shouldn't joke my German and French are also terrible.)

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@hongminhee@hollo.social

Just opened an issue for a major new task for : building an smoke test suite.

To ensure Fedify-built servers federate correctly with the wider , we're planning to run automated E2E tests in against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

github.com

Interoperability smoke test suite · Issue #481 · fedify-dev/fedify

Summary As a server framework, Fedify's core value lies in its ability to correctly interoperate with other ActivityPub implementations in the Fediverse. Currently, we rely on unit tests and manual...

@w3cdevs@w3c.social

At the October 2025 "W3C in Europe🇪🇺 " meeting, @simone, @w3c 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 , Verifiable Credentials, DIDs, and the Digital Credentials API. Key challenges include across EU states and protecting privacy and human rights.

🎬 Watch: youtu.be/qEGkGoxvjrI

Snapshot of the video recording of Simone Onofri's presentation showing a slide about one of the challenges we face, globally but particularly in Europe, is the development of technologies that respect security, privacy and human rights.
ALT text

Snapshot of the video recording of Simone Onofri's presentation showing a slide about one of the challenges we face, globally but particularly in Europe, is the development of technologies that respect security, privacy and human rights.

@w3cdevs@w3c.social

At the October 2025 "W3C in Europe🇪🇺 " meeting, @simone, @w3c 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 , Verifiable Credentials, DIDs, and the Digital Credentials API. Key challenges include across EU states and protecting privacy and human rights.

🎬 Watch: youtu.be/qEGkGoxvjrI

Snapshot of the video recording of Simone Onofri's presentation showing a slide about one of the challenges we face, globally but particularly in Europe, is the development of technologies that respect security, privacy and human rights.
ALT text

Snapshot of the video recording of Simone Onofri's presentation showing a slide about one of the challenges we face, globally but particularly in Europe, is the development of technologies that respect security, privacy and human rights.

@NGICommons@eupolicy.social

🔧🌍 It’s !

Every 14 October, we celebrate the unsung heroes of international collaboration — the experts behind voluntary technical standards developed by IEC, ISO & ITU.

This year’s theme: a shared vision for a better world. 🌱
commons.ngi.eu/event/seminar-i

In NL, @forumstandaardisatie is marking the day with “Interoperability Day,” diving into and 🇳🇱

commons.ngi.eu

Seminar Interoperability Day 2025 - NGI Commons

Cloud and data sovereignty are the themes of the second edition of Interoperability Day. During the seminar, visitors will learn more about initiatives, solutions, and (upcoming) regulations regarding cloud and...

@smallcircles@social.coop

Check out the new @bonfire Social release candidate. What a wonderful well-designed experience, and superb release notes!

bonfirenetworks.org/posts/bonf

🎉 Congratulations to the team @ivan and @mayel for making it this far, through all that tireless hard work. And also to @nlnet and @ngi for supporting this important project. Future of social networking in the making.

To developers, have a look at those great docs:

docs.bonfirenetworks.org/feder

docs.bonfirenetworks.org

Bonfire Federation Interoperability Guide — Bonfire v1.0.0-social-rc.3

@smallcircles@social.coop

Check out the new @bonfire Social release candidate. What a wonderful well-designed experience, and superb release notes!

bonfirenetworks.org/posts/bonf

🎉 Congratulations to the team @ivan and @mayel for making it this far, through all that tireless hard work. And also to @nlnet and @ngi for supporting this important project. Future of social networking in the making.

To developers, have a look at those great docs:

docs.bonfirenetworks.org/feder

docs.bonfirenetworks.org

Bonfire Federation Interoperability Guide — Bonfire v1.0.0-social-rc.3

@smallcircles@social.coop

Check out the new @bonfire Social release candidate. What a wonderful well-designed experience, and superb release notes!

bonfirenetworks.org/posts/bonf

🎉 Congratulations to the team @ivan and @mayel for making it this far, through all that tireless hard work. And also to @nlnet and @ngi for supporting this important project. Future of social networking in the making.

To developers, have a look at those great docs:

docs.bonfirenetworks.org/feder

docs.bonfirenetworks.org

Bonfire Federation Interoperability Guide — Bonfire v1.0.0-social-rc.3

@smallcircles@social.coop

Check out the new @bonfire Social release candidate. What a wonderful well-designed experience, and superb release notes!

bonfirenetworks.org/posts/bonf

🎉 Congratulations to the team @ivan and @mayel for making it this far, through all that tireless hard work. And also to @nlnet and @ngi for supporting this important project. Future of social networking in the making.

To developers, have a look at those great docs:

docs.bonfirenetworks.org/feder

docs.bonfirenetworks.org

Bonfire Federation Interoperability Guide — Bonfire v1.0.0-social-rc.3

@smallcircles@social.coop

Check out the new @bonfire Social release candidate. What a wonderful well-designed experience, and superb release notes!

bonfirenetworks.org/posts/bonf

🎉 Congratulations to the team @ivan and @mayel for making it this far, through all that tireless hard work. And also to @nlnet and @ngi for supporting this important project. Future of social networking in the making.

To developers, have a look at those great docs:

docs.bonfirenetworks.org/feder

docs.bonfirenetworks.org

Bonfire Federation Interoperability Guide — Bonfire v1.0.0-social-rc.3

@w3cdevs@w3c.social

📢 Curious about Baseline, developer surveys, or the web platform's evolution? And how individual can get involved and make their voice heard?

The @w3c WebDX is hosting an on Reddit, on September 18 starting at 9:00am ET!

Post your questions at reddit.com/r/webdev/comments/1

AMA - Ask Me Anything
ALT text

AMA - Ask Me Anything

@w3cdevs@w3c.social

📢 Curious about Baseline, developer surveys, or the web platform's evolution? And how individual can get involved and make their voice heard?

The @w3c WebDX is hosting an on Reddit, on September 18 starting at 9:00am ET!

Post your questions at reddit.com/r/webdev/comments/1

AMA - Ask Me Anything
ALT text

AMA - Ask Me Anything

@w3cdevs@w3c.social

📢 Curious about Baseline, developer surveys, or the web platform's evolution? And how individual can get involved and make their voice heard?

The @w3c WebDX is hosting an on Reddit, on September 18 starting at 9:00am ET!

Post your questions at reddit.com/r/webdev/comments/1

AMA - Ask Me Anything
ALT text

AMA - Ask Me Anything

@NGICommons@eupolicy.social

💡 Governments play a crucial role to support the .

@ChristopherWilson (from @MyDataglobal) highlights their vital role and emphasises that the design challenge is also a key consideration.

Let’s build systems that serve people, not platforms.
commons.ngi.eu/videos/

@martelinnovate @OpenForumEurope @openfuture @cnrs @linuxfoundation @ngi

Christopher Wilson from MyData interviewed by NGI Commons
ALT text

Christopher Wilson from MyData interviewed by NGI Commons

@1br0wn@eupolicy.social

New: project 🍏

Good hardware, if overpriced ✔️

Bad software & services, deliberately lacking

Today, I shut off Apple's closed service entirely. Now using as a universal inbox, with , & DMs ✅

Goal: shutting off all 🍏 services will make it much easier to switch to cheaper hardware in future. Which is why Apple’s entire business model depends on tying their hardware to their software & services

@w3cdevs@w3c.social

Web Extensions let users customize their browsers by altering their behaviors and page content through small applications developed by third party . This proposed new @w3c Web Extensions aims to standardize a common core of cross-browser extension that has emerged from recent progress in , making cross-browser extension development easier.

▶️ w3c.github.io/charter-drafts/2

Feedback and input welcome: github.com/w3c/charter-drafts/ [wg/webextensions]

github.com

w3c/charter-drafts

Draft W3C WG and CG charters for public review. Contribute to w3c/charter-drafts development by creating an account on GitHub.

@w3cdevs@w3c.social

Web Extensions let users customize their browsers by altering their behaviors and page content through small applications developed by third party . This proposed new @w3c Web Extensions aims to standardize a common core of cross-browser extension that has emerged from recent progress in , making cross-browser extension development easier.

▶️ w3c.github.io/charter-drafts/2

Feedback and input welcome: github.com/w3c/charter-drafts/ [wg/webextensions]

github.com

w3c/charter-drafts

Draft W3C WG and CG charters for public review. Contribute to w3c/charter-drafts development by creating an account on GitHub.

@1br0wn@eupolicy.social
@ilumium@eupolicy.social
@ilumium@eupolicy.social
@1br0wn@eupolicy.social

So many alternative services are finally getting to the point they are mainstream consumer-ready - which is *essential* if they are going to grow into serious challengers 👏

I'm now hosting all my own videos on @peertube. Bye ! p.lu/c/interoperability/videos

p.lu

Interoperability

Educational materials about interoperability as a tool to give users more choice and generate competitive pressure in monopolised markets

@1br0wn@eupolicy.social

Looking forward v much to our discussion this morning at the UK's Competition & Markets Authority on : lessons (for the ) from regulation!

Tim Cowen (Preiskell & Co. antitrust chair) and Prof. @chrismarsden.bsky.social are both world authorities on this topic 👀 And we have a surprise guest to talk about payments & water regulation lessons!

Here are my background slides docs.google.com/presentation/d

docs.google.com

Interop demos

Interoperability is already here… …it’s just unevenly distributed (William Gibson)

@1br0wn@eupolicy.social

"reached 100m sign-ups faster than any other app in history, which you can partly attribute to its linkage to and streamlined profile creation via your IG info. But even so, it’ll go down as a record either way, while Threads also reached 100m active users in just a few months."

From: @tchambers
indieweb.social/@tchambers/114

indieweb.social

Tim Chambers (@tchambers@indieweb.social)

#Threads growth continues…. https://www.socialmediatoday.com/news/threads-celebrates-second-anniversary-party-hats/752287/

@1br0wn@eupolicy.social

"reached 100m sign-ups faster than any other app in history, which you can partly attribute to its linkage to and streamlined profile creation via your IG info. But even so, it’ll go down as a record either way, while Threads also reached 100m active users in just a few months."

From: @tchambers
indieweb.social/@tchambers/114

indieweb.social

Tim Chambers (@tchambers@indieweb.social)

#Threads growth continues…. https://www.socialmediatoday.com/news/threads-celebrates-second-anniversary-party-hats/752287/

@1br0wn@eupolicy.social

Looking forward v much to our discussion this morning at the UK's Competition & Markets Authority on : lessons (for the ) from regulation!

Tim Cowen (Preiskell & Co. antitrust chair) and Prof. @chrismarsden.bsky.social are both world authorities on this topic 👀 And we have a surprise guest to talk about payments & water regulation lessons!

Here are my background slides docs.google.com/presentation/d

docs.google.com

Interop demos

Interoperability is already here… …it’s just unevenly distributed (William Gibson)

@1br0wn@eupolicy.social

Thank you @EUCommission for committing (at the end of today's workshop) to further explore the geolocalisation obstacles is imposing on for ! And good work @Amandine for raising the problem so clearly 👏

Screenshot of Ian Brown's questions in the online Q&A (Slido):

* Does the Commission accept this restrictive Meta interpretation? GDPR, for example, explicitly applies to data controllers OUTSIDE the EU offering services within the EU, or monitoring the behaviour of EU residents 

* Don't the EDPS, EDPB, and other members of the DMA high-level panel have something to say that the Commission thinks Matrix and others being forced by Meta to geolocate all their users is trivial/unproblematic?! 

* I thought BEREC clearly said (i ts review of the original Meta reference offer) that a separate inbox for third-party chats was not acceptable? 

* Given how the geolocalisation DMA interpretation of Meta is causing such damage to fair and contestable NIICS, will the EC open an investigation and then take action to remove this obstacle?
ALT text

Screenshot of Ian Brown's questions in the online Q&A (Slido): * Does the Commission accept this restrictive Meta interpretation? GDPR, for example, explicitly applies to data controllers OUTSIDE the EU offering services within the EU, or monitoring the behaviour of EU residents * Don't the EDPS, EDPB, and other members of the DMA high-level panel have something to say that the Commission thinks Matrix and others being forced by Meta to geolocate all their users is trivial/unproblematic?! * I thought BEREC clearly said (i ts review of the original Meta reference offer) that a separate inbox for third-party chats was not acceptable? * Given how the geolocalisation DMA interpretation of Meta is causing such damage to fair and contestable NIICS, will the EC open an investigation and then take action to remove this obstacle?

@1br0wn@eupolicy.social

Thank you @EUCommission for committing (at the end of today's workshop) to further explore the geolocalisation obstacles is imposing on for ! And good work @Amandine for raising the problem so clearly 👏

Screenshot of Ian Brown's questions in the online Q&A (Slido):

* Does the Commission accept this restrictive Meta interpretation? GDPR, for example, explicitly applies to data controllers OUTSIDE the EU offering services within the EU, or monitoring the behaviour of EU residents 

* Don't the EDPS, EDPB, and other members of the DMA high-level panel have something to say that the Commission thinks Matrix and others being forced by Meta to geolocate all their users is trivial/unproblematic?! 

* I thought BEREC clearly said (i ts review of the original Meta reference offer) that a separate inbox for third-party chats was not acceptable? 

* Given how the geolocalisation DMA interpretation of Meta is causing such damage to fair and contestable NIICS, will the EC open an investigation and then take action to remove this obstacle?
ALT text

Screenshot of Ian Brown's questions in the online Q&A (Slido): * Does the Commission accept this restrictive Meta interpretation? GDPR, for example, explicitly applies to data controllers OUTSIDE the EU offering services within the EU, or monitoring the behaviour of EU residents * Don't the EDPS, EDPB, and other members of the DMA high-level panel have something to say that the Commission thinks Matrix and others being forced by Meta to geolocate all their users is trivial/unproblematic?! * I thought BEREC clearly said (i ts review of the original Meta reference offer) that a separate inbox for third-party chats was not acceptable? * Given how the geolocalisation DMA interpretation of Meta is causing such damage to fair and contestable NIICS, will the EC open an investigation and then take action to remove this obstacle?

@1br0wn@eupolicy.social
@ianbrown.tech@bsky.brid.gy

I was sad we didn’t have live translation for our workshop, although the live transcription & rapid video publication hopefully helped non-English speakers with access to translation/interpretation tools. Meta’s smart glasses demo of the latter was amazing 😳

RE: https://bsky.app/profile/did:plc:jxlyustxwaohron4vq5zzflc/post/3lsgmztkwbe27

Me wearing Meta/Ray Ban smart glasses
ALT text

Me wearing Meta/Ray Ban smart glasses

@1br0wn@eupolicy.social
@1br0wn@eupolicy.social

Will next week's Internet Governance Forum in Oslo be the final ? Some at the hope so…

It would be quite a mistake to hand more power to the Member States at the expense of all the multistakeholders who have contributed so much over the years to the flying circus!

Don't miss our Tuesday lunchtime workshop: -Preserving and the !
igf2025.sched.com/event/246Ho?

Ian's IGF passes from 2009 (4th) to 2024
ALT text

Ian's IGF passes from 2009 (4th) to 2024

@ianbrown.tech@bsky.brid.gy

I was sad we didn’t have live translation for our workshop, although the live transcription & rapid video publication hopefully helped non-English speakers with access to translation/interpretation tools. Meta’s smart glasses demo of the latter was amazing 😳

RE: https://bsky.app/profile/did:plc:jxlyustxwaohron4vq5zzflc/post/3lsgmztkwbe27

Me wearing Meta/Ray Ban smart glasses
ALT text

Me wearing Meta/Ray Ban smart glasses

@b3s@mas.to

Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse

Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?

This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.

Reply via your timeline 🌀
new.vex.blue/articles/2024/09/

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

@b3s@mas.to

Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse

Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?

This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.

Reply via your timeline 🌀
new.vex.blue/articles/2024/09/

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

@b3s@mas.to

Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse

Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?

This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.

Reply via your timeline 🌀
new.vex.blue/articles/2024/09/

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

@b3s@mas.to

Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse

Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?

This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.

Reply via your timeline 🌀
new.vex.blue/articles/2024/09/

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"
ALT text

Bluesky logo, Green background on the right with Text saying "Welcone to the Fediverse"

@1br0wn@eupolicy.social

Will next week's Internet Governance Forum in Oslo be the final ? Some at the hope so…

It would be quite a mistake to hand more power to the Member States at the expense of all the multistakeholders who have contributed so much over the years to the flying circus!

Don't miss our Tuesday lunchtime workshop: -Preserving and the !
igf2025.sched.com/event/246Ho?

Ian's IGF passes from 2009 (4th) to 2024
ALT text

Ian's IGF passes from 2009 (4th) to 2024

@1tech@mastodon.social · Reply to 1TE.CH Tech News

 🔒 Unlike Facebook, Instagram, LinkedIn, Reddit, TikTok, YouTube, XTwitter, decentralised networks don’t harvest your data for profit: You are in !

 🚀 prevents corporate control, ensuring and moderation: Open standards ensure and foster .

👉 in the ⁂ on : Fedizen.EU (2/2)

@watswo@mastodon.social

This video is a colorful introduction to the guided by filmmaker & Fediverse advocate Watch now to discover a whole new world of social media, one where is respected, users are empowered, and has no say.
What a simple, powerful statement about the fediverse by @_elena in her amazing movie. Thanks a lot!!!

videos.elenarossini.com/w/64Vu

videos.elenarossini.com

Introducing the Fediverse: a New Era of Social Media

This video is a colorful introduction to the Fediverse, guided by filmmaker & Fediverse advocate Elena Rossini. Watch now to discover a whole new world of social media, one where privacy is res...

@_elena@mastodon.social

Good morning Fedi friends!

I'm adding additional foreign language subtitles to my fediverse intro video (premiering this afternoon at , then launching widely on Monday).

Proud to have Czech subs thanks to the generous help of @jan (whose avatar has a little cameo in the video, in the section about ).

Current subs:
🇬🇧 English
🇫🇷 French
🇧🇷 Brazilian Portuguese
🇨🇿 Czech

Soon:
🇮🇹 Italian
🇪🇸 Spanish
🇩🇪 German

Thank you for the support! Wishing you all a lovely day 🌞

a still image from my fedi intro video that shows an open laptop... there are Czech subtitles on and a pop up menu on the right that shows available subs: Czech, English, French and Brazilian Portuguese
ALT text

a still image from my fedi intro video that shows an open laptop... there are Czech subtitles on and a pop up menu on the right that shows available subs: Czech, English, French and Brazilian Portuguese

@toxi@mastodon.thi.ng

— New version (v0.27.0) of thi.ng/genart-api, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

This version features an overhaul of the platform provided PRNG (pseudo-random number generator) handling and makes it easier to create multiple PRNGs for artworks which require/desire them...

Related section in the README:
github.com/thi-ng/genart-api/b

Also, just as a reminder, the project has:

- no external dependencies
- adapters for 3 art platforms (EditArt, fxhash, Layer)
- 6 example projects
- testing/dev sandbox with two parameter editors
- WebAssembly bindings & demo (currently for only)

Happy coding! :)

github.com

genart-api/README.md at main · thi-ng/genart-api

Generalized API for browser-based generative art projects, plug & play support for platform specifics, parameter declarations, GUI creation, IPC - thi-ng/genart-api

@1br0wn@eupolicy.social

New: project 🍏

Good hardware, if overpriced ✔️

Bad software & services, deliberately lacking

Today, I shut off Apple's closed service entirely. Now using as a universal inbox, with , & DMs ✅

Goal: shutting off all 🍏 services will make it much easier to switch to cheaper hardware in future. Which is why Apple’s entire business model depends on tying their hardware to their software & services

@1br0wn@eupolicy.social

NICE! @ivory now showing proper previews of Bluesky links, looking just like a quote-post of a native Fediverse post! for the win! /cc @wavesblog

Preview of Bluesky post rendered properly, with initial text of the post and a photo of a gurning Mark Zuckerberg talking to one of the European Commission executive vice presidents about god knows what
ALT text

Preview of Bluesky post rendered properly, with initial text of the post and a photo of a gurning Mark Zuckerberg talking to one of the European Commission executive vice presidents about god knows what

@1br0wn@eupolicy.social

NICE! @ivory now showing proper previews of Bluesky links, looking just like a quote-post of a native Fediverse post! for the win! /cc @wavesblog

Preview of Bluesky post rendered properly, with initial text of the post and a photo of a gurning Mark Zuckerberg talking to one of the European Commission executive vice presidents about god knows what
ALT text

Preview of Bluesky post rendered properly, with initial text of the post and a photo of a gurning Mark Zuckerberg talking to one of the European Commission executive vice presidents about god knows what

@carla@hci.social

I'm hiring a PhD student in Copenhagen, Denmark to do research on and in messaging apps!

This is a fully funded 3-year position in the Copenhagen campus of Aalborg University. The student will join my project "mInt" (for "messaging interoperability" ;)) and will be co-supervised by me and @nielsvanberkel .

More info and application form here: stillinger.aau.dk/phd-stilling. Deadline is May 18.

stillinger.aau.dk

PhD Stipend in Human-Computer Interaction Principles for Messaging Interoperability

The PhD position is supported by the project mInt:  Human-centered design principles for effective management of social boundaries in interoperable t...

@carla@hci.social

I'm hiring a PhD student in Copenhagen, Denmark to do research on and in messaging apps!

This is a fully funded 3-year position in the Copenhagen campus of Aalborg University. The student will join my project "mInt" (for "messaging interoperability" ;)) and will be co-supervised by me and @nielsvanberkel .

More info and application form here: stillinger.aau.dk/phd-stilling. Deadline is May 18.

stillinger.aau.dk

PhD Stipend in Human-Computer Interaction Principles for Messaging Interoperability

The PhD position is supported by the project mInt:  Human-centered design principles for effective management of social boundaries in interoperable t...

@carla@hci.social

I'm hiring a PhD student in Copenhagen, Denmark to do research on and in messaging apps!

This is a fully funded 3-year position in the Copenhagen campus of Aalborg University. The student will join my project "mInt" (for "messaging interoperability" ;)) and will be co-supervised by me and @nielsvanberkel .

More info and application form here: stillinger.aau.dk/phd-stilling. Deadline is May 18.

stillinger.aau.dk

PhD Stipend in Human-Computer Interaction Principles for Messaging Interoperability

The PhD position is supported by the project mInt:  Human-centered design principles for effective management of social boundaries in interoperable t...

@llas@defcon.social

What happened to 'interoperability by design'?

In December, 2024, the @EUCommission had proposed an interesting path for Apple to achieve higher standards of interoperability under the . The final version excluded several of these requirements.

A coalition of organisations and experts, have weighted the positives and negatives of the final decision of how developers can request from .

fsfe.org/news/2025/news-202504

fsfe.org

DMA: European Commission falls short on interoperability requirements for Apple - FSFE

Despite initial promising steps, the European Commission’s measures on Apple’s compliance with interoperability procedures under the Digital Markets Act fa...

@delta@chaos.social

The talk from @compl4xx is public. It goes into topics such as

- why chatmail servers?
- how to setup a server with your child
- (avoiding) spam filtering
- metadata and guaranteed end to end encryption in
- for email message routing

Thanks to attendees for the great energy even if was the last talk on the day and also for questions and conversations afterwards!

ftp.fau.de/fosdem/2025/k4601/f

@delta@chaos.social

The talk from @compl4xx is public. It goes into topics such as

- why chatmail servers?
- how to setup a server with your child
- (avoiding) spam filtering
- metadata and guaranteed end to end encryption in
- for email message routing

Thanks to attendees for the great energy even if was the last talk on the day and also for questions and conversations afterwards!

ftp.fau.de/fosdem/2025/k4601/f

@toxi@mastodon.thi.ng

Another day, another release (v0.25.0):

This update mainly features the new `@genart-api/wasm` package, providing Zig & TypeScript bindings for core GenArtAPI functionality (i.e. so far mostly parameter handling).

This WASM bridge/integration is designed as an API module for the thi.ng/wasm-api toolchain. Installation & build instructions are in the readme.

New package homepage:
github.com/thi-ng/genart-api/t

Example project (w/ param editor):
demo.thi.ng/genart-api/param-e

Example Zig source code:
github.com/thi-ng/genart-api/b

github.com

genart-api/examples/zig-test/zig/main.zig at main · thi-ng/genart-api

Generalized API for browser-based generative art projects, plug & play support for platform specifics, parameter declarations, GUI creation, IPC - thi-ng/genart-api

@toxi@mastodon.thi.ng

New release of thi.ng/genart-api (v0.24.0) — a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

This release contains quite a few new features, as well as several important fixes for bugs which were accidentally introduced in the two most recent versions...

- extracted the debug time provider & FPS overlay to separate package
- updated `bigint` param handling (esp. randomization)
- added `collector` and `iteration` metadata accessors
- updated platform adapters (esp. the one)
- fixed image & ramp param handling
- added a bunch of utilities to core API to deduplicate code in various adapters
- updated/fixed examples & docs
- added more tests (and updated core API to be more testable outside the browser)

All changes since v0.21.0:
github.com/thi-ng/genart-api/c

🎉

github.com

Comparing v0.21.0...v0.24.0 · thi-ng/genart-api

Generalized API for browser-based generative art projects, plug & play support for platform specifics, parameter declarations, GUI creation, IPC - Comparing v0.21.0...v0.24.0 · thi-ng/genart-api

@toxi@mastodon.thi.ng

(1st release cycle of 2025) 🎉 — New additions & updates to thi.ng/genart-api, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

- Added fxhash.xyz platform adapter (incl. support & adaptations for 10 of the 17 built-in GenArtAPI param types)
- Added `bigint` & `binary` data param types
- Updated parameter type definitions & factories (date, datetime, time, numlist, strlist, text, vector)
- Ensure any given default values are valid (and can be coerced)
- Added MurmurHash3 (128 bit version) functions (e.g. seed PRNGs)
- Added tests for all parameter types (factory functions & implementations)
- Added tests for utility functions
- Added GitHub actions (running tests)
- Various API docs updates, clarifications & fixes
- Update/refactor EditArt & Layer platform adapters
- Updated main & adapter readmes

New adapter package `@genart-api/adapter-fxhash`:
github.com/thi-ng/genart-api/t

Commits since last release:
github.com/thi-ng/genart-api/c

github.com

Comparing v0.20.0...v0.21.0 · thi-ng/genart-api

Generalized API for browser-based generative art projects, plug & play support for platform specifics, parameter declarations, GUI creation, IPC - Comparing v0.20.0...v0.21.0 · thi-ng/genart-api

@toxi@mastodon.thi.ng

Another new release of (v0.20.0), due to some urgent additions & updates of partially outdated documentation and refactoring/cleaning up of some parameter types. This project already contains more docs than code and because things are moving so fast, I forgot to update some parts... (Sorry for any confusion caused...)

Other notable updates:

- Simplified the core API's param value getter for obtaining time-based or randomized values (please check docs[1])
- Updated vector param definition
- Added a `.configure()` method for the EditArt platform adapter to allow manual selection of adapted params (to override the default auto-selection)[2]

You can see all the changes since the last release here:
github.com/thi-ng/genart-api/c

[1] docs.thi.ng/genart-api/core/in
[2] github.com/thi-ng/genart-api/t

@toxi@mastodon.thi.ng

and already second update this week, plus the addition of a new platform adapter package for publishing artwork to editart.xyz (ready ahead of 😉)... (cc/ @pifragile)

This new release (all packages at v0.19.0 now) also includes several updates to API docs and adapter readme's:

- github.com/thi-ng/genart-api
- github.com/thi-ng/genart-api/t
- github.com/thi-ng/genart-api/t

All implementations are WIP (but fully functional, to the best of my knowledge!). If there's demand, I'm considering adding more parameter type adaptations also for the EditArt adapater (e.g. to support vector/XY params, as already done for the Layer adapter...)

Since I've been told "people/artists don't read anymore", tonight I'm starting to record a video walkthrough, wish me luck! :)

@toxi@mastodon.thi.ng

New release of thi.ng/genart-api, a modular cross-platform API/SDK for browser-based computational/algorithmic/generative art projects, helping to reduce artists' efforts to adapt work for different art platforms/environments/uses/workflows.

Main new v0.18.0 additions:

- The param editor reference implementation now groups parameters by their declared group and sorts them by given order (both optional)
- The `@genart-api/adapter-layer` package supports adaptations/translations for more param types, incl. vectors, which are not yet natively supported by that platform. E.g. vectors will be transparently represented as multiple, separate numeric params on the platform side, but your artwork is blissfully unaware of this and still only would deal with vectors. The platform adapter does all the reconcilation and handling of param changes...
- Started adding tests
- Updated API docs & readme's

As always, feedback highly appreciated — this project is in active development...

I'm aware, the target audience for this larger project is quite limited, but the benefits are real (and palpable!), not just for artists in this field (but especially for them!)... I'll do my best to illustrate the (recurring) problems being solved here, demystify some of the concepts and squeeze in recording a short(ish) video showing how to develop a small project from scratch using this system/setup and then repurpose it and show related tools still in development...

@toxi@mastodon.thi.ng

(the 13th) — New version (v0.17.0) of thi.ng/genart-api with the following updates:

- Added platform adapter IDs for use with external editors/tooling
- Updated editors[1] to check for platform adapter & API version compatibility, display warnings if needed...
- Added/migrated three different seedable PRNG implementations in API core package (SFC32, XorShift128, XsAdd). These are completely independent and can be used by platform adapters and/or artworks (also multiple instances)
- Initial release of first platform adapter for an upcoming art platform (currently invite only)
- Restructured all example projects
- Updated readme & API docs (docs.thi.ng/genart-api/core/)

[1] The param editor/sandbox requires your artwork to use the latest version of these packages: `@genart-api/core` and `@genart-api/adapter-urlparams`.

demo.thi.ng/genart-api/param-e

New improved version (of editor) with many more features (incl. variation/preset management) is in the works...

@toxi@mastodon.thi.ng

Major project updates from this past week:

thi.ng/genart-api

- Restructured the project as monorepo, splitting out core API and platform adapter(s) as separate packages
- Switched package scope from `@thi.ng` to `@genart-api` to highlight project/platform independence (not directly related with other thi.ng projects).
- Published new packages: `@genart-api/core` and `@genart-api/adapter-urlparams`
- Moved API docs to docs.thi.ng/genart-api/core/
- Added support for n-dimensional vector parameters and added support in the reference platform adapter and in param editor
- Updated all examples & parameter editor. The latter is now only compatible with this latest API version (v0.16.0)
- Updated docs/readme

If you want to find out more, the project readme has _a lot_ more information. Also feel free to get in touch with any questions/proposals!

@toxi@mastodon.thi.ng

It just dawned on me that I haven't been mentioning five(!) recent thi.ng/genart-api updates, all from the past month... 😱

The latest version (v0.14.0, just released) is largely about an overhaul of messaging related functionality and also addresses use cases related to managing multiple artworks embedded (via `<iframe>`s) in a single document/page (think: online gallery scenarios...)

If you're already using GenArtAPI message/event listeners in your own artwork, you might have to rename some of them. This commit has the important details:

github.com/thi-ng/genart-api/c

Also, the online parameter editors have been updated and are now only working with the latest version of the API, so be sure to update your artwork projects to stay compatible:

Generic editor harness (for your own compatible artworks):
demo.thi.ng/genart-api/param-e

Demo (with test artwork):
demo.thi.ng/genart-api/param-e

Other recent changes/additions (in no particular order):

- added new message types to poll the artwork/API for current state/info
- update message names & naming convention
- added ability to configure the API behavior/features (also via messaging)
- option to emit frame messages w/ current timing/frame info
- message broadcasting to multiple GenArtAPI instances/artworks
- inject common defaults for optional settings in param specs
- fixed date/datetime param handling (in editor)
- updated/fixed time providers
- updated debug time provider (w/ FPS visualization overlay)
- use gzip compression for image param values (in default platform adapter)
- added version info
- various documentation updates
- (WIP) WASM bindings for Zig-based artworks
- (WIP) unpublished progress on real platform adapters

Some of these features are all about enabling new use cases and improving usability of external tooling around artworks adapting GenArtAPI, for example:

- Ability to broadcast start/stop messages to either individual or all artworks embedded in a page
- Ability for the param editor to configure the artwork currently being worked on to emit timing & frame information (which then can be integrated in the editor UI without the editor knowing anything else about the artwork)
- Enable editors to identify an artwork/project and store param presets grouped by project ID
- Allow editors (or other tools) to check the API version used by the artwork by first sending a `genart:get-info` message, then listening for `genart:info` response (then maybe display a warning if version is incompatible)
- etc.

If you want to find out more, the project readme has _a lot_ more information. Also feel free to get in touch with any questions!

@rolle@mementomori.social

Each party that is building the "new era of social media" have their own agendas.

Bluesky states literally "Bluesky is an open network. With one account, you can access both an easy-to-use social network and a shared identity across the entire social internet."

Nostr states: "Nostr is a simple, open protocol that enables global, decentralized, and censorship-resistant social media."

Threads says: "Threads is part of the fediverse, also known as the federated universe. The fediverse is a global, open, social network of independent servers operated by third parties around the world."

But they are still more or less separate and not "easy". It's this fantasy of having interoperability, but years go by and everyone are still developing their own protocols and apps. Bluesky and Threads can be partly connected to the Fediverse, but limited to one-way or opt-in setting. It's not "across the entire social internet", nowhere near.

As of right now I can reach most platforms via ActivityPub and I can fully have the control to myself with my own server on the Fediverse. That can't be achieved with Bluesky or Threads, with them you are always dependent on someone else's servers. I hope some day we'll get the bigger players fully connected too, somehow, better and easier.

@hongminhee@fosstodon.org

Imagine what if every website implemented HTTP/TLS themselves. There would be so much fragmentation that we wouldn't see the we see today.

To me, that's what the looks like today. Mastodon, Pixelfed, etc. have their own implementations of , WebFinger, HTTP Signatures, etc. and each one behaves slightly differently, which leads to poor interoperability. Adoption of new standards is slow.

I wish each major programming language had something like .

@_elena@mastodon.social

Hello Fedi Friends!

I've been running lots of tests between and the rest of the and I've been learning so many interesting things! I cannot wait to write about all this for . (For the record these are content aggregators, the Fedi’s answer to ).

I may have to resort to hand-written graphs because some of the stuff is a bit convoluted 😅

Spoiler alert:
↔️ ✅🥳
↔️ ❌😵‍💫
↔️ ⚠️😐