fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2025-01-10 16:12:09 +00:00
Code Issues Projects Releases Wiki Activity

Put <dfn> in own paragraph

Browse source
This commit is contained in:
Rohan Kumar 2022-02-11 14:51:01 -08:00
parent aa7e4d3167
commit 5ba82ea53d
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
2 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
content/posts/keeping-platforms-open.md
View file

@ -33,9 +33,9 @@ These three approaches overlap: they frequently feature platform monoculture and
### Forced migration
When one vendor controls all parts of a service (e.g., both a client and server), it has the means to create what I call a <dfn id="boxed-platform">boxed platform</dfn>: a subset of a larger open platform that can evolve at its own pace, without concern for compatibility or interoperability.
A <dfn id="boxed-platform">boxed platform</dfn> is a subset of a larger open platform that can evolve at its own pace, without concern for compatibility or interoperability.
Controlling both the server and client allows a vendor to update the client and server without worrying about breaking compatibility with other clients/servers in the larger network. It could update the client to point users to a server that uses a completely different, closed protocol. This is what happened to many XMPP users in the early 2000s.
When one vendor controls all parts of a service (e.g., both a client and server), it has the means to create a boxed platform. Controlling both the server and client allows a vendor to update the client and server without worrying about breaking compatibility with other clients/servers in the larger network. It could update the client to point users to a server that uses a completely different, closed protocol. This is what happened to many XMPP users in the early 2000s.
#### Case study: the boxing of XMPP

4
content/posts/whatsapp-and-the-domestication-of-users.md
View file

@ -38,7 +38,9 @@ In a WhatsApp world, people who want to keep in touch must abide by the followin
User domestication
------------------
WhatsApp rose by trapping previously-free beings in their corral and changing their habits to create dependence on masters. Over time, this made it difficult or impossible to return to their previous lifestyle. That process should sound familiar: it's eerily similar to the domestication of animals. I call this type of vendor lock-in <dfn id="user-domestication">user domestication</dfn>: the removal of user autonomy to trap users into serving vendors.
WhatsApp rose by trapping previously-free beings in their corral and changing their habits to create dependence on masters. Over time, this made it difficult or impossible to return to their previous lifestyle. That process should sound familiar: it's eerily similar to the domestication of animals.
I call this type of vendor lock-in <dfn id="user-domestication">user domestication</dfn>: the removal of user autonomy to trap users into serving vendors.
I chose this metaphor because animal domestication is a gradual process that isn't always deliberate, and typically revolves around one group becoming dependent upon another. For example: there's evidence that domestication of dogs began with socialization, resulting in not-entirely-artificial selection promoting genes that resulted in more friendliness with and dependence upon humans.[^1]