#[campegg]Unsure if this is the right place to ask, but looking at https://indieweb.org/snowflake, the question that springs to mind is, is the reason that so many developers opt to create an API that’s (more-or-less) unique for their service a form of litigation risk mitigation? (i.e. “I don’t want to be sued for copying [X], so I’ll do my own thing”). Assuming they do it “because they think their service is special” seems to
#[campegg]their actions to hubris when it might just be risk aversion.
#[tantek]campegg, no developer has brought that up in practice, while many have long opined about how their service is special
#[tantek]if you know of examples (citation from a developer offering that reasoning), happy to note it!
#[campegg][tantek] Understood, thanks! And no, I don’t know of any examples — more just curious
#[tantek]it's not just hubris, it's also some amount of (perceived) laziness (of difficulty, not necessarily time). it's perceived as easier to just make up an API for your needs, rather than attempt to re-use existing standards/conventions
#[tantek]often existing standards/conventions will have solved problems (i18n etc.) that the "new" developer has not even thought about, and thus they'll end up creating a poor quality (from a web perspective) API that will cost more time to fix
#[tantek]see for example every API that makes up a notion of a "person" e.g. address book card
#[campegg]100%… maps pretty closely to Larry Wall’s “three great virtues of a programmer”: laziness, impatience and hubris (https://thethreevirtues.com)