High Range, Australia, last edited: Sun, 27 May 2018 18:13:45 +1000
Consider that the project that is the gold standard of ActivityPub compatibility (think extinct elephant) doesn't work with Example2, Example3, Example4, or Example5 of the ActivityPub spec. It will reject these activities and silently drop them as "malformed". These four examples describe in detail how basic, simple communications work in ActivityPub.
Alexandre Hannud Abdo
Since the heavy lifting is being done in a repository none of you can see, here's what's happening at the moment with zot6.
The basic protocol is just about defined. It's not *too* much different than zot, but there are still substantial changes in the way data is organised and transferred. So far I have only had to add one table column to the database. There will be more.
Sometime in the next week (or so) I expect to be able to connect two channels. The last remaining hurdle is (yet another) permission system upgrade. This is a hard slog as I'm trying to do away with a static permission list completely and let permissions like 'can shave my cat' appear at any time and just work. The current architecture does this but there's a nasty little upgrade process to merge it into the system.
Sometime in the next 2-3 weeks I expect to be able to start sending messages.
On the longer term roadmap and in rough order (I can't define a timeline until the earlier components start to materialise):
- Finish the protocol supporting documentation
- remove bbcode as the base content type
- Release the zot6 base project 'zap' for pioneers to play with
- Strip out everything that isn't a social network suitable for the intellectually challenged and release it as 'denim'.
- add support for the activitystreams data type
- migrate the new protocol to hubzilla
The basic protocol is just about defined. It's not *too* much different than zot, but there are still substantial changes in the way data is organised and transferred. So far I have only had to add one table column to the database. There will be more.
Sometime in the next week (or so) I expect to be able to connect two channels. The last remaining hurdle is (yet another) permission system upgrade. This is a hard slog as I'm trying to do away with a static permission list completely and let permissions like 'can shave my cat' appear at any time and just work. The current architecture does this but there's a nasty little upgrade process to merge it into the system.
Sometime in the next 2-3 weeks I expect to be able to start sending messages.
On the longer term roadmap and in rough order (I can't define a timeline until the earlier components start to materialise):
- Finish the protocol supporting documentation
- remove bbcode as the base content type
- Release the zot6 base project 'zap' for pioneers to play with
- Strip out everything that isn't a social network suitable for the intellectually challenged and release it as 'denim'.
- add support for the activitystreams data type
- migrate the new protocol to hubzilla
Stephan Maus
Hubzilla @ sasiflo
Waitman Gobble
Mario Vavti
Raymond Monret
Klaus
Jake Moomaw
Haakon Meland Eriksen (Els Mussols)
Is this going to be another attempt to make some simplified version of Hubzilla like you tried with "Uno"? That seemed like a good idea at first but ended up being more complicated than it was worth if I remember correctly.
Is this going to be another attempt to make some simplified version of Hubzilla like you tried with "Uno"? That seemed like a good idea at first but ended up being more complicated than it was worth if I remember correctly.
When a reporter asked, “How did it feel to fail 1,000 times?” (Thomas) Edison replied, “I didn’t fail 1,000 times. The light bulb was an invention with 1,000 steps.”
Anmol Sharma
Thomas Runge
last edited: Sun, 27 May 2018 16:55:57 +1000
Thanks Mile for all the great work!
It might be too much to ask but could Zot6 (or Zot7?) support role based access control?
My intuition is that it would be fairly complicated to implement in a fully decentralised fashion.
I'll post a message about RBAC on the support forum so as not to take up too much space on this thread.
It might be too much to ask but could Zot6 (or Zot7?) support role based access control?
My intuition is that it would be fairly complicated to implement in a fully decentralised fashion.
I'll post a message about RBAC on the support forum so as not to take up too much space on this thread.