https://brainsteam.co.uk/annotations/

Example of someone owning their Hypothes.is annotations and publishing them on their own website.

https://whatever.scalzi.com/2022/11/25/how-to-weave-the-artisan-web/

“But Scalzi,” I hear you say, “How do we bring back that artisan, hand-crafted Web?” Well, it’s simple, really, and if you’re a writer/artist/musician/other sort of creator, it’s actually kind of essential:

https://pruvisto.org/debirdify/

Tool for moving some of your Twitter data over to Mastodon or other parts of the Fediverse.

Either ironic or maybe not the best advice when suggesting people might choose something like Notion or Evernote which could disappear with your data...

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Maria Farrell</span> in What is Ours is Only Ours to Give — Crooked Timber (<time class='dt-published'>05/18/2021 11:28:17</time>)</cite></small>

Owning your audience is key here.

Of course they're encouraging people to do this. Pushing them to the business side is where they're making all the money.

This is a slippery slope problem, but people are certainly capable of taking positions along a broad spectrum here.

The one thing I might worry about--particularly given micro.blog's--size is the relative bus factor of one represented by Manton himself. If something were to happen to him, what recourse has he built into make sure that people could export their data easily and leave the service if the worst were to come to happen? Is that documented somewhere?

Aside from this the service has one of the most reasonable turn-key solutions for domain and data ownership I've seen out there without running all of your own infrastructure.

I'm not sure that this is the problem that micro.blog is trying to solve. It's trying to solve the problem of how to be online as simply and easily as possible without maintaining the overhead of hosting and managing your own website.

As long as one can easily export their data at will and redirect their domain to another host, one should be fine. In some sense micro.blog makes it easier than changing phone carriers, which in most cases will abandon one's text messages without jumping through lots of hoops. .

One step that micro.blog could set up is providing a download dump of all content every six months to a year so that people have it backed up in an accessible fashion. Presently, to my knowledge, one could request this at any time and move when they wished.

An important logical point. Listing what they don't keep isn't as good as saying what they actually do with one's data.

And isn't this what everyone should really be doing anyway so that they own their own work and words?

Own your pedagogy. Send just like anything else out there...

Ownership of the data is important. One could certainly set up their own Hypothes.is server if they liked.

I personally take the data from my own Hypothes.is account and dump it into my local Obsidian.md vault for saving, crosslinking, and further thought.

Governments owning citizens' data directly?? Why not have the government empower citizens to own their own data?

FreeTime mode on the Amazon Kindle will provide you with reading statistics. You can find the raw data as an SQLite file under system > freetime > freetime.db.

https://wildland.io/2021/06/11/introducing-client-v0.1.html

This looks intriguing... A client for abstracting data stores for use anywhere.

Facebook provides some data portability, but makes an odd plea for regulation to make more functionality possible.

Why do this when they could choose to do the right thing? They don't need to be forced and could certainly try to enforce security. It wouldn't be any worse than unveiling the tons of personal data they've managed not to protect in the past.

https://www.somebits.com/weblog/tech/bad/goodreads-lost-all-my-data.html

A clarion call for owning your own data.

I like how Dr. Pacheco-Vega outlines some of his research process here.

Sharing it on Twitter is great, and so is storing a copy on his website. I do worry that it looks like the tweets are embedded via a simple URL method and not done individually, which means that if Twitter goes down or disappears, so does all of his work. Better would be to do a full blockquote embed method, so that if Twitter disappears he's got the text at least. Images would also need to be saved separately.

What are the common pitfalls when choosing a note taking application or platform?

Own your data

Prefer note taking systems that don't rely on a company's long term existence. While Evernote or OneNote have been around for a while, there's nothing to say they'll be around forever or even your entire lifetime. That shiny new startup note taking company may not gain traction in the market and exist in two years. If your notes are trapped inside a company's infrastructure and aren't exportable to another location, you're simply dead in the water. Make sure you have a method to be able to export and own the raw data of your notes.

Test driving many

and not choosing or sticking with one (or even a few)<br /> Don't get stunned into inaction by the number of choices.

Shiny object syndrome

is the situation where people focus all attention on something that is new, current or trendy, yet drop this as soon as something new takes its place.<br /> There will always be new and perhaps interesting note taking applications. Some may look fun and you'll be tempted to try them out and fragment your notes. Don't waste your time unless the benefits are manifestly clear and the pathway to exporting your notes is simple and easy. Otherwise you'll spend all your time importing/exporting and managing your notes and not taking and using them. Paper and pencil has been around for centuries and they work, so at a minimum do this. True innovation in this space is exceedingly rare, and even small affordances like the ability to have [[wikilinks]] and/or bi-directional links may save a few seconds here and there, in the long run these can still be done manually and having a system far exceeds the value of having the best system.

(Relate this to the same effect in the blogosphere of people switching CMSes and software and never actually writing content on their website. The purpose of the tool is using it and not collecting all the tools as a distraction for not using them. Remember which problem you're attempting to solve.)

Future needs and whataboutisms

Surely there will be future innovations in the note taking space or you may find some niche need that your current system doesn't solve. Given the maturity of the space even in a pen and paper world, this will be rare. Don't worry inordinately about the future, imitate what has worked for large numbers of people in the past and move forward from there.

Others? Probably...

We need to think more about the externalities of our data decisions.

This didn't work out too well for them did it?

an interesting neologism to describe something that many want