Continue reading on Unthread

Oh, lol, I mentioned it on another thread. 😅

Good examples are book, music, tv/movie trackers, and most Standard Site platforms. I have duplicate scrobble data under Rocksky and TealFM. I have duplicate data under BookHive and Popfeed.

Yes, data is there but there's always that messaging that it's just a matter of developing a new one that will reuse or import that data.

The best example right now are Standard Site platforms, most if not all. Standard Site is good but the goal was to have a universal way to backup content, not to use it as the source of truth.

From the perspective of the target market being told "you own your data and you don't have to worry about a platform going down" (or variations of that messaging, like "not platform-locked"), it's not really the case right now.

Let's say one has a blog on Leaflet and it went down. Yes, their content was backed up universally as plaintext via Standard Site. If they want to move to another platform, they still have to do it manually.

If the Social Web, or its individual networks, will say that users are not platform-locked, it should be easy to display data using any platform without the need to manually copy-paste or ask for an import tool.

"Hi new_platform dev, can we ask for an import tool for old_platform?"

Creating an import tool is extra work for a dev. Reading another project's lexicons is no doubt an interoperability nightmare. A good example is Margin and Semble, some things are one-way, some are two-way.

The Community Lexicons are great, but we still hope at least half of the ATmosphere devs are on board.

Yes, financial support is a factor too. And it's no doubt a driving factor for many. So, yes, it's not easy.

To close, there's a need to rephrase some explanations here and there to set the proper expectations. One such is "not platform-locked" or variations of it, because we still are.

Is it this about the messaging? Partly yes, it's the immediate one. Long-term, no, true "not platform-locked" is the ultimate goal.

• Interoperability
• Shared lexicons
• ATproto as the source of truth instead of as a backup
• Data/Content being viewable from any platform—removing the need to ask platform devs to create an import tool. (The only import tool we need is from non-Social Web to Social Web.)

The Social Web is getting there, but occasionally, it seems to be being sidelined if not forgotten.