«

»

Hubzilla uno

Mike Macgirvin make this information

Hubzilla UNO is a configuration of Hubzilla specifically designed to appeal to a broad
community. All configurations and options and site features which have traditionally
caused confusion amongst those who are unfamiliar with and alienated by Hubzila’s advanced
technical concepts have been removed. The result is a software base which is drastically
simplified and approachable by a much larger audience, with a corresponding loss of
(significant) functionality.

This is accomplished by taking a normal hubzilla server and disabling all the advanced features.
Not tucked away as hidden options as per the current design, but in fact the advanced features
are completely disabled and unavailable.

A server can choose to be a Hubzilla UNO server at installation time. This is a permanent and
potentially irreversible decision. One can migrate their UNO channel to a « normal » hubzilla server,
but they *cannot* clone it (in either direction). This also means that hubzilla UNO can achieve a
high degree of compatibility and federation with other primitive communication services; which is
impossible for a hubzilla server that supports clones. Hubzilla UNO is also 100% compatible with
Hubzilla and « federates » without any limitations. This provides a compatibility bridge to traditional
services and networks for those willing to give up Hubzilla’s nomadic identity feature.

The most difficult decision is providing support for forums. Since forums require understanding
of the concept of « multiple channels per account » and this has traditionally caused confusion, it
was decided that forums would not be supported on hubzilla UNO. Members may interact with forums
that are provided on traditional hubzilla servers.

no nomadic clones
no permission options (ACL only).
no DAV (file uploads are still available through the web interface)
no multi-channels
no multi-profiles
no webpages
no bookmarks
no forums
no apps
no built-in « webchat »
no channel sources

limited features, all of which will have been preset

Development tasks:

Most of this work is reasonably straight-foward and merely involves appropriate « #ifdef » code blocks.
The largest development task is to bring back support for the older Friendica style account migration
since cloning will not be an option. This means if your hub shuts down, we will attempt to re-establish
your connections from a new service; but you cannot « just carry on » during brief outages.

—–

Probably some rough edges but this is mostly done. Import of UNO channels into a traditional hubzilla server is blocked until the migration bit is worked out. It’s basically taking Hubzilla and stripping it down. Even stripped of a large number of advanced features it still has orders of magnitude more functionality than Diaspora (for instance) as far as conversational community software goes, so this configuration may appeal to a number of people.