Taxonomy for ATmospheric Lexicon and App Directories

Hi Folks, Dorian again. You may remember me from such poasts as the one a few weeks ago about the protocol-agnostic PDS I plan to cook up. Well I’m back as I’ve been summoned by Christian to tease you all with another one: I know there’s been recent chatter about creating an app directory (or several?), so what might that look like? Even better: what if the metadata that drove such an app directory was on the protocol—so anybody who wanted to make their own app directory could make one? What if...

ATmosphere App Catalog

A catalog of ever-growing apps built on AT Protocol.

ATmosphere App Catalog

A catalog of ever-growing apps built on AT Protocol.

Interoperable Atmosphere apps with Lexicons - Applied Meteorology

Lexicons create a shared language for apps on the Atmosphere

Taxonomy for ATmospheric Lexicon and App Directories

I kept going to pull quotes but just like, all of this. lol Something really basic like a taxonomy of concepts has the potential to skew heavily social, because at a technical level there’s almost nothing to it: you have an identity with some labels (synonyms, language-tagged strings—not sure how those’ll be implemented), you might have a definition, and then you have a handful of semantic relations, and the concept scheme class to yoke them together. (Again, I’m using SKOS as a template for th...

What is the Atmosphere? · Leaflet Lab Notes

“The Atmosphere is an ecosystem of apps that use Atmosphere accounts.An Atmosphere account exists outside of any single app. It consists of a username and a big folder of all the content and relationships a person has. It's public!Atmosphere apps use this folder to create social experiences like blogging, tweeting, and sharing. Because everything is public, Atmosphere apps can create uniquely seamless experiences between themselves!”

atproto community

atproto community ecosystem Organizing [https://atmosphereconf.org](https://atmosphereconf.org), sharing community news, and AT Community Fund leads.

A taxonomy of ATmosphere applications

Last week I spent an energizing, educational, occasionally infuriating week in Vancouver around the ATmosphereConf, a community event gathering developers, investors, data scientists, the odd academic

Ecosystem Plugins - Wesley's notes

Bridging the interop gap and addressing the long-tail of user needs

Your platform is not an ecosystem

Another day, another exhortation to join an “ecosystem” that’s anything but. I could pick a hundred examples, but one that recently caught my eye was an ad placed in the Financial Times by the Singapore stock exchange, SGX Group, promising “multiple growth avenues, one trusted ecosystem”. SGX wants companies to list on its exchange rather than, say, the Hong Kong one which has more or less the same exclusive offer. SGX promises “access (to) Asia through our trusted ecosystem anchored in Singapore.” Ecosystems can be a lot of things. ‘Trusted’, by which they mean centrally policed to achieve defined, lower-risk outcomes, is not one of them. Calling built environments ‘ecosystems’ is common everywhere from financial services to supply chains to – quite a stretch, here – a retirement living complex. But it’s most often used in the tech world to describe the relations between software, services and hardware typically owned by a single company. For example, it’s how Google describes everything that hangs off the Android operating system. These kinds of proprietary and deterministic architectures are called ecosystems so often that we’ve stopped noticing. And that’s kind of the point. We need to start seeing this metaphor again, and what it’s hiding in plain sight. But first, a reminder of what an ecosystem actually is.