@nolan AMP's rewriting of stuff to be hosted by Google specifically in a way that increases their surveillance, with *pressure* to do so in exchange for a boost in traffic that will absolutely go away anyway once they've forced the entire ecosystem to move over to it, is a sure sign of monopolistic behavior that Google deserves to get hit with an antitrust lawsuit for more than anything else I've seen so far.
I just added what I think is the coolest part to OcapPub... the "Composition" section! This especially shows off how cool ocap design is: Alyssa schedules a backup of her file to run twice a day, and yet the job scheduler which runs the backup has neither access to read the file nor write anything else to the backup service! https://gitlab.com/spritely/ocappub/blob/master/README.org
I'm realizing that what the more interesting demo would be to show, now that we have "mutable datashards" URIs, how you can make a user profile that can also survive if a server goes down. You just point your datashards URI to a new inbox on a different server and push that update to the network!
An actor can allow another actor to tell them what to become, but only if they consensually pass the authority to do that to the other actor. I suspect that'll be rare.
ActivityPub Conf's organization has happened from extremely limited resources, but I think at this point I think it's going to be amazing. Looking at the list of people registered and talks already submitted gives me confidence that this is going to be a heck of an event.
Books in the Oxford Very Short Introduction series I have read / am reading so far: - Sexual Selection (done) - History of the Jewish People (done) - Zionism (almost done) - Utilitarianism (started)
Queued up for next are: - Economics - Islamic History - Literary Theory - Statistics - Artificial Intelligence - The Roman Empire
The way they are doing this is by adding a Certificate Authority (CA) that allows them to snoop all traffic.
This is, by the way, why SSL is criticized as being "only as secure as the weakest CA in your system". Here it's deliberate, but that's a problem in general.
There's a lot there already, and we haven't even gotten to Part 2, the "How to Build It" section yet. I'll begin work on that tomorrow.
What's here already is more or less an explanation of *why* OcapPub is taking the particular direction it is taking, and why other approaches run into serious problems.