11 Matching Annotations
  1. Nov 2020
  2. Oct 2020
    1. With Alphabet Inc.’s Google, and Facebook Inc. and its WhatsApp messaging service used by hundreds of millions of Indians, India is examining methods China has used to protect domestic startups and take control of citizens’ data.

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

    1. I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media. (Website, blog, mailing list, etc.)
    1. We believe that Facebook is also actively encouraging people to use tools like Buffer Publish for their business or organization, rather than personal use. They are continuing to support the use of Facebook Pages, rather than personal Profiles, for things like scheduling and analytics.

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

    1. Third, the post-LMS world should protect the pedagogical prerogatives and intellectual property rights of faculty members at all levels of employment. This means, for example, that contingent faculty should be free to take the online courses they develop wherever they happen to be teaching. Similarly, professors who choose to tape their own lectures should retain exclusive rights to those tapes. After all, it’s not as if you have to turn over your lecture notes to your old university whenever you change jobs.

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

    1. For example, the idea of “data ownership” is often championed as a solution. But what is the point of owning data that should not exist in the first place? All that does is further institutionalise and legitimate data capture. It’s like negotiating how many hours a day a seven-year-old should be allowed to work, rather than contesting the fundamental legitimacy of child labour. Data ownership also fails to reckon with the realities of behavioural surplus. Surveillance capitalists extract predictive value from the exclamation points in your post, not merely the content of what you write, or from how you walk and not merely where you walk. Users might get “ownership” of the data that they give to surveillance capitalists in the first place, but they will not get ownership of the surplus or the predictions gleaned from it – not without new legal concepts built on an understanding of these operations.
    1. 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? Compared to hosting your own blog and auto-posting it to Micro.blog, which won't cost you and won't make Micro.blog any revenue, posting for a hosted blog seems to decrease your ownership.

      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.

    2. Manton says owning your domain so you can move your content without breaking URLs is owning your content, whereas I believe if your content still lives on someone else's server, and requires them to run the server and run their code so you can access your content, it's not really yours at all, as they could remove your access at any time.

      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.

    1. The main thing Smith has learned over the past seven years is “the importance of ownership.” He admitted that Tumblr initially helped him “build a community around the idea of digital news.” However, it soon became clear that Tumblr was the only one reaping the rewards of its growing community. As he aptly put it, “Tumblr wasn’t seriously thinking about the importance of revenue or business opportunities for their creators.”
  3. Mar 2020