First, Manton’s business model is for users to not own their content. You might be able to own your domain name, but if you have a hosted Micro.blog blog, the content itself is hosted on Micro.blog servers, not yours. You can export your data, or use an RSS feed to auto-post it to somewhere you control directly, but if you’re not hosting the content yourself, how does having a custom domain equal self-hosting your content and truly owning it?
Couple questions about ‘owning’ your content on the Indieweb.
A few follow-up questions to this:
In the old days, when an ISP (or your college or whatever) would give you a public_html folder to put your website in—did you own your content?
In modern times, when you rent a virtual server slice to run Apache and serve your website from a Wordpress database—do you own your content?
If you put up an essay on a pastebin site—do you own your content?
I don’t really see the difference between using FTP to pass your stuff ‘in’/‘out’ of a public_html folder and using Micro.blog’s API to pass your stuff ‘in’/‘out’. If you can get your stuff ‘in’ and ‘out’—isn’t that the key? The API is just a different kind of FTP.
The public_html folder isn’t owned. The virtual slice isn’t owned. The domain isn’t owned. The pastebin isn’t owned. The API isn’t owned. What does it mean to ‘own’ anyway?
This is one thing that is really cut and dry with Beaker Browser. You do own the content because it originates directly from the machine under your fingers that you own.
(Not trying to defend Micro.blog or weigh in on the other interesting matters of this post—perhaps I should just shut up—just thinking about this one thing.)