localhost_frssoft/ocappub
1
0
Fork 0
mirror of https://gitlab.com/spritely/ocappub.git synced 2024-11-26 23:23:03 +00:00
Code Issues Projects Releases Wiki Activity

Must we boil the ocean?

Browse Source
This commit is contained in:
Christopher Lemmer Webber 2019-07-18 17:23:26 -04:00
parent be27c3e64f
commit 43a856e86c
No known key found for this signature in database
GPG Key ID: 4BC025925FF8F4D3
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.org
View File

@ -683,6 +683,23 @@ But the framework for all of this is object capabilities.
** Must we boil the ocean? ** Must we boil the ocean?
All this sounds fine and well, but we are pressed with a problem: we
/already have/ ActivityPub implementations in the wild, and those
implementations filled in the holes in the spec in the best ways they
knew how.
We do not want to have to throw away the network we have.
As such, this document does not try to solve all possible problems.
For example, a Webfinger-centric interface is roughly incompatible
with Tor onion services, even if supporing such services would be
desirable and could be more easily accomplished with a [[https://github.com/cwebber/rebooting-the-web-of-trust-spring2018/blob/petnames/draft-documents/making-dids-invisible-with-petnames.md][petname system]].
As such, this document simply assumes that we will live with
webfinger-based addresses for now, even if not optimal for the long
term.
Incremental improvement is better than no improvement at all, and
there is a lot we can make better.
* How to build it * How to build it
** Object capabilities (ocaps) ** Object capabilities (ocaps)