# What existing/emerging standards should we evaluate?

**URL:** <https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34>\
**Category:** Standards\
**Tags:** ocaps\
**Created:** [January 27, 2022, 8:35pm UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34 "2022-01-27T20:35:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![frandallfarmer](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/frandallfarmer/32/3_2.png) [@frandallfarmer](https://community.spritely.institute/u/frandallfarmer)\
**Post date:** [January 27, 2022, 8:35pm UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/1 "2022-01-27T20:35:44Z")

</div>

Please post links and thoughts about existing or emerging standards that we should consider adopting/joining and those that might be competing for headspace. We need to be able to answer the question “How are you different than X?”

---

<div class="post-metadata">

**Author:** ![alanhkarp](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/alanhkarp/32/20_2.png) [@alanhkarp](https://community.spritely.institute/u/alanhkarp)\
**Post date:** [February 2, 2022, 1:26am UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/2 "2022-02-02T01:26:01Z")

</div>

One of the lessons learned from OAuth 1 was that developers do not understand crypto. You can provide all the libraries you like; you can give them a gazillion examples; they’ll still get it wrong. A key feature of OAuth 2 was that the only crypto you needed was HTTPS. I expect HTTPS to be too heavyweight for some Spritely applications, but it would be nice if we could get away with just mutual TLS as the only required crypto. That rules out capability certificates, but I’m OK with that.

Conflict-free Replicated Data Types (CRDTs) are something that may help maintain consistency.

---

<div class="post-metadata">

**Author:** ![alanhkarp](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/alanhkarp/32/20_2.png) [@alanhkarp](https://community.spritely.institute/u/alanhkarp)\
**Post date:** [February 2, 2022, 10:37pm UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/3 "2022-02-02T22:37:33Z")

</div>

Sam Smith’s [Keri](https://keri.one/) is an alternative to distributed ledgers that provides a decentralized root of trust and key rotation. There’s a lot about identity in the material linked from the web page. Don’t be put off by that. A capability designates the object it is authorizing access to. What is that designation? It could well be a Keri identity.

---

<div class="post-metadata">

**Author:** ![danny](https://avatars.discourse-cdn.com/v4/letter/d/848f3c/32.png) [@danny](https://community.spritely.institute/u/danny)\
**Post date:** [May 16, 2022, 11:37pm UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/4 "2022-05-16T23:37:26Z")

</div>

I think it’s worth looking at what’s becoming Bluesky’s experimental stack: [UCAN, IPLD, and DID](https://github.com/bluesky-social/adx).

---

<div class="post-metadata">

**Author:** ![alanhkarp](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/alanhkarp/32/20_2.png) [@alanhkarp](https://community.spritely.institute/u/alanhkarp)\
**Post date:** [May 17, 2022, 4:35am UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/5 "2022-05-17T04:35:02Z")

</div>

I’ve looked at UCAN. It seems pretty good even though I had a few quibbles.

---

<div class="post-metadata">

**Author:** ![frandallfarmer](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/frandallfarmer/32/3_2.png) [@frandallfarmer](https://community.spritely.institute/u/frandallfarmer)\
**Post date:** [May 28, 2022, 10:37pm UTC](https://community.spritely.institute/t/what-existing-emerging-standards-should-we-evaluate/34/6 "2022-05-28T22:37:06Z")

</div>

Interesting things about Fuchsia:

> **[A Kernel Hacker Meets Fuchsia OS](https://a13xp0p0v.github.io/2022/05/24/pwn-fuchsia.html)**
>
> Fuchsia is a general-purpose open-source operating system created by Google. It is based on the Zircon microkernel written in C++ and is currently under active development. The developers say that Fuchsia is designed with a focus on security,...
