Zotlabs|Zot

Motivational welcome post

hEARt PhoniX

Fri, 28 Jun 2019 15:00:47 +0000

We are a great team, I am not sure wether to laugh or run. But ... we won't get any dumber and there is the slight chance to get something done along the way.
So: Let's do it.

zot w3c welcome

Harald Klimach

Mon, 01 Jul 2019 13:53:48 +0000

OK, so the W3C group is at: zot protocol Community Group

To standardize the Zot protocol currently used in Hubzilla and Zap, and to push its adoption for social web.

There are also some hints for Good practices.

In

https://start.hubzilla.org/channel/francewhoa/?f=&mid=3eae5a48be78d66deaeb5933d1ce16f89f6f4e9fbefdcf5e1b74fc078ce3a092@start.hubzilla.org

we said we want to keep the communications and work on the Zot specification on the Zot-based platforms as much as possible.

The currently existing specification resides at framagit: Zot / zap.

Mike sees the following points that need to be addressed:

Some deficiencies in the spec that I'm currently aware of are:

- more detail on the existing/deployed permissions. Permissions are extensible and can be somewhat arbitrary but we do use a few of the existing ones in ways that need to be better documented.

- Detail on 2 or 3 extensions we've provided to ActivityStreams to make our life easier. They aren't absolutely necessary but are good to have in a Zot environment.

- Nomadic content is not well documented. It also isn't really being used at the moment but will be important going forward.

However, to me (not a webdeveloper) the specification itself looks rather vague and not very detailed.
I think we could start off with detailing the Transport and Protocol Basics with the details from the reference implementation in Zap.