Memory enables sticky, personalized agentic experiences and creates strong lock-in.

Context compounds: the more an LLM knows about you, the better results it can provide and the more you use it.

Vendor lock-in is everywhere — Wix, Shopify, no-code platforms, even overly restrictive SaaS tools. If you haven’t written the code, don’t truly own or control the product and data, and can’t deploy or host it wherever and however you choose — then you haven’t actually built anything.

SMR suggests existence of important lock-in effects and legacies related to the build-up of material stocks.

In the author’s view, using a combination of content-addressing, signed content, and petnames would help decentralise that layer. It keeps centralisation around aggregators (because of the scarcity of attention), but mitigates their harmful lock-in.

Does anyone has it’s Zettelkasten in Google Docs, Microsoft Word or Plain Tex (without a hood app like obsidian or The Archive)? .t3_15fjb97._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }

I think the only purpose of this is to detain programmers from doing anything a non-Microsoft way.

So ActionCable needs Redis! Is this the first time Rails is aligning with a vendor product? Why not abstract it like AR/AJ?

manually specifying the order isn't really a great solution (as tempting as it sounds) because you'll probably have broken behaviour if you subsequently move away from Rollup.

easy access/edit/backup and then restore saved data using the integrated Bookmark Manager (even on smartphone / tablet) even if the addon is not installed

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

One thing that would certainly be a game-changer would be some form of standardized RCS end-to-end encryption that allows secure messages to be sent outside Google Messages.

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.

If you don't—or can't—lock your users in, the best way to compete is to innovate at a breakneck pace. Let's use Google Search as an example. It's a product that cannot lock users in: users don't have to install software to use it; they don't have to upload data to use it; they don't have to sign two-year contracts; and if they decide to try another search engine, they merely type it into their browser's location bar, and they're off and running.

it is far preferable to spend your engineering effort on innovation than it is to build bigger walls and stronger doors that prevent users from leaving

Want to keep your users? Just make it easy for them to leave.

Users are starting to realize, however, that as they store more and more of their personal data in services that are not physically accessible, they run the risk of losing vast swaths of their online legacy if they don't have a means of removing their data.

Export and migrate your data between hosting options at any time

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.

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.

Publishers previously lost a lot of revenue from textbooks because many students bought secondhand, rented, pirated or just skipped buying textbooks altogether. Inclusive-access programs have changed that.