#Tag · bonfire.mavnn.eu

AI sovereignty has been a hot topic at India's AI Impact Summit. Eileen Donahoe and Konstantinos Komaitis write for Tech Policy about what governments need to do to make that a reality, without their countries becoming isolated — it's all about interoperability. "In an interoperable world, standards are power—and governments that ignore them will find sovereignty decided elsewhere," they conclude.

https://flip.it/XsEiLu

#Technology #Tech #AI #DigitalSovereignty #Interoperability

Tech Policy Press

Why AI Sovereignty Depends on Interoperability Standards

In the AI era, sovereignty is exercised less through territorial control than through infrastructure design, write Eileen Donahoe and Konstantinos Komaitis.

Flipboard Tech Desk

@[email protected] · 3 days ago

https://flip.it/XsEiLu

#Technology #Tech #AI #DigitalSovereignty #Interoperability

Tech Policy Press

Why AI Sovereignty Depends on Interoperability Standards

In the AI era, sovereignty is exercised less through territorial control than through infrastructure design, write Eileen Donahoe and Konstantinos Komaitis.

Sean Tilley

@[email protected] · 5 days ago

Here’s the thing: Mastodon already has a really good API. There’s a whole ecosystem of clients around it, to the point that many other Fediverse implementations adopted it, so that they can use the apps.

I don’t think this is a bad thing in and of itself. But, if we want projects like Mastodon to support it, the value proposition has to provide things that the Mastodon API does not.

I think a killer feature to focus on would be identity management.

just small circles 🕊

@[email protected] replied · 5 days ago

@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 #interoperability 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 #ActivityPub 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.