inappropriately change or overwrite JSON files compared to Markdown files

There is a growing need for open standards for formats used to represent text, images, video and other collections of data, so that one producer's data will be accessible to another's software.

Introduction of the Compose specification makes a clean distinction between the Compose YAML file model and the docker-compose implementation.

Why save sessions as bookmarks? - all the data saved will be there no matter what addon you may use in the feature

They are proof that our openness about our data formats means that you do not have to fear data lock-in.

It’s this third way that we avoid lock-in that is relevant to today’s topic. Our data format design is specified well enough so that people with no connection to AgileBits can write software to be able to handle it.

The second way we avoid locking you into 1Password is through the ability to export data to a more neutral format. Not all versions are yet where we want them to be with respect to export, and we’re working on that. But there is usually some path, if not always a simple click away, to export your 1Password data.

Your task list is a plain text file, not some proprietary format owned by a company or locked to a specific application.

And since it’s just a client, you can always use the todo.txt format text file created by it in the very beginning with any other client. Give it a try.

In this system, plaintext files are used for most of the backbone of your organizational system.

Countless productivity apps and sites store your tasks in their own proprietary database and file format. But you can work with your todo.txt file in every text editor ever made, regardless of operating system or vendor.

Most to-do lists give you no control over your data. Your tasks live inside the app, not in a document you can edit, and syncing is handled by whichever company made the app. If you don't like this, todo.txt is a great alternative.