I have been learning Hubzilla since December 2020, with the goal of launching a professional website based on this software (HUBZILLA.PL,) accessible to non-technical people and one that encourages numerous hosts of fellow being to move from the world of Facebook to the world of Fediverse. As this website is mainly intended for Polish speakers, I decided to translate the documentation first. And here I ran into problems due to the poor quality of this documentation: many outdated, foggy and inadequate articles. I am working hard on creating new Hubzill documentation, so far in Polish, but I would like to create something that has arms and legs.
Meanwhile, I started looking at other programs in the Zotlabs family, in particular the Zap platform. I also started comparing the code of both programs. As a result, I came to the conclusion that Hubzill's development seems to be going in the wrong direction.
Hubzilla is derived from Zap, and in @mike's idea (I suppose), it was intended to be an extension of Zap with various functionalities needed by the target user. The core of both platforms was supposed to be the same, as was the core of the documentation. Meanwhile, Hubzilla is starting to differ from Zap more and more, both in core code and conceptually.
I have the impression that Hubzill's development is surrounded by a dense fog and we can't see where to go. We have to put up a signpost! This signpost must lead to a "brilliant goal" and take into account trends in modern technology of creating web applications and common programming standards. I mean PSR, frontend technology, API, etc.
The brilliant goal? I think this is what @mike came up with a long time ago: a software for a social internet portal (internet portal sensu stricto and "portal" to Fediverse). The kind of website you visit in the morning and everything is there: social news streams, RSS streams, ... even email. Of course, there must also be your own website, blog, etc.
It's worth starting with naming. A website based on Hubzilla is "hub", whereas in Frendica it is "node", and in Zap it is "website". The English words "hub" and "node" have network connotations and emphasize the network, not service character of the website. They are rather indigestible to the average user and can be confusing - not every Hubzilla "hub" is a node in the Fediverse network. Taking into account the genius goal, I propose to unify this name and adopt the term "portal" as the name of a website based on the Zotlabs library.
If so, let's create a common name for the type of website that is the portal of the Zot network: "Zot Social Portal - ZSP". This name would refer to all social portals using the Zot protocol (the Zotlabs library), i.e. portals based on Hubzilla, Zap, or on each a individual software, if it uses the Zotlabs library. I dream about a social platform based on the Symfony framework and using the Zotlabs library.