Hubzilla
Hubzilla est un puissant "couteau-suisse" dans le Template:Internal Link, souvent décrit comme un gystème de gestion de contenu social, mais avec des fonctionalités de réseau social, de microblog et de nuages.
 This article is too long and detailed for a beginners guide and "What is" page. Some of it should probably be moved to Hubzilla. |
| |
| Hubzilla logo | |
 Hubzilla
| |
| Page web | hubzilla.org |
| Instances liste | fediverse.observer |
A quoi ressemble Hubzilla?
A quoi ressemble Hubzilla?
Impression générale
Avec la richesse de ses fonctionalités, Hubzilla ne s'adresse pas vraiment aux débutants du Fédiverse. Il ne ressemble pas ou ne se rapproche d'aucun projets de microblog dans le Fédiverse. Il ne mimique pas non plus le style et l'expérience d'une plateforme commerciale particulière.
Le projet du Fédiverse le plus proche serait Template:Internal Link, suivi par Template:Internal Link, en partie parce que Hubzilla était une branche Friendica. Cependant, aucun d’entre eux n’offrent autant de fonctionnalités qu'Hubzilla.
Hubzilla's Web interface is extensively themeable, much like wholly different Web interfaces for Template:Internal Link, but as of now, there is only one supported theme, Redbasic. It can be extensively configured, though. It also has a dark mode that can be activated manually or automatically.
Avec une identité web Hubzilla appelée "canal" et la fonction "Identité nomade", les canaux peuvent être dissociés du hub où ils sont créés. Ils peuvent être portés vers un hub différent, mais aussi clonés, auquel cas l'identité et les données du canal existeront simultanément dans plusieurs endroits.
Template:Internal Link apps don't work with Hubzilla.
De plus, avec la fonction "Open Web Auth", il est possible d'accéder simplement au contenu de différents sites Web, sans avoir à saisir de nom d'utilisateur et de mot de passe pour chaque site. Il s'agit d'une identification de l'utilisateur en un seul clic : la possibilité d'accéder à des sites en cliquant simplement sur des liens vers des sites distants.
Grâce à un ingénieux mécanisme de "contrôle d'accès", qui permet également de créer des groupes et des forums, vous pouvez désormais commencer à communiquer de manière plus confidentielle et contrôler exactement qui peut voir vos messages et vos fichiers.
Comptes
Comment créer un compte?
Démarrer avec votre compte Fediverse
Bonnes pratiques
Applications mobile
Hubzilla
Liens externes
Also, channels aren't bound to one hub. They also make Template:Internal Link possible: You can clone any of your channels across two or more hubs, and these clones always stay in sync. It basically gives you real-time backup.
Channels can be exported in their entirety with an optional built-in "app", and they can be imported into accounts. This is not for moving channels which nomadic identity can handle much more easily and gracefully, but rather for local backups.
Hubzilla supports single sign-on via Template:Internal Link. If you're logged in, other instances with OpenWebAuth can recognise you and, for example, give you special permissions. OpenWebAuth even takes into account which one of your channels is currently active.
Connections
Connections are generally either only out-going or mutual. There are no followers without following back. That's because all connections have to be confirmed, either automatically or manually, and when they're confirmed, they're also followed back.
Each connection can be configured extensively. It can be assigned a contact role which is a customisable set of permissions. It can be added to one or several privacy groups which are similar to Friendica groups, Template:Internal Link aspects, Google+ circles or Mastodon groups. It can be assigned a profile if multiple profiles are activated. It can be blocked, ignored, hidden or archived, and so forth.
Hubzilla itself is not based on ActivityPub. Support for ActivityPub is established through an "app" named Pubcrawl which is optional for both hubs and channels. At hub level, it is on by default. On channel level, however, it has to be manually activated ("installed") before connections to Mastodon & Co. can be created.
In addition, Hubzilla federates with diaspora*, the OStatus protocol and even e-mail. Channels can subscribe to RSS and Atom feeds, and they generate their own RSS feeds. Posts can be forwarded to WordPress and other blogs that use XMLRPC. Hubzilla also used to be fully federated with Twitter/X which is now reduced to an optional crosspost connector.
Streams
Streams are Hubzilla's timelines. The equivalent to Mastodon's personal timeline is the channel stream. However, it is more flexible: Only direct messages, posts/comments marked with a star or posts/comments from the channel itself can be shown. Also, all posts/comments from a certain privacy group, all threads from a certain forum (amongst others, Hubzilla recognises Friendica discussion groups and Template:Internal Link communities as such), all filed posts/comments from a certain category (similar to Mastodon's bookmarks, but with folders as categories) can be shown, and all posts/comments from a certain contact can be shown.
Hubzilla does not have anything like Mastodon's local timeline. There is also the public stream, pubstream in short, which is the equivalent to Mastodon's federated timeline. It can be activated by the hub admin, it is off by default, and most hubs keep it off in order to stay out of trouble because it is unmoderated.
All timelines have three sorting algorithms: threads by most recent post; threads by most recent comment; unthreaded single posts and comments. The sorting for the channel stream can be selected by the owner, the sorting for the pubstream can only be selected by the admin.
Posts
Just like Friendica, (streams), Lemmy and Template:Internal Link, Hubzilla has a different thread structure than most of the rest of the Fediverse. Most Fediverse projects have threads like Twitter/X which consist of any number of technically identical posts. Friendica, Hubzilla and (streams) are more like Facebook, Tumblr, forums or comment sections on blogs or news sites: Their threads consist of exactly one post at the beginning, and everything that follows is not a post, but a comment.
Posts and comments even have separate entry masks: The one for posts is at the top of your personal stream, the one for comments is below each post.
Comments always have the same access permissions and the same visibility as the post they belong to. Only the author of the post can change them for the whole thread.
Also, the author of a post can moderate the thread following the post and delete comments.
Unlike on micro-blogging projects, posts can have a title which is also federated to Lemmy and /kbin. Writing the title of a new post at the top of the post is not necessary.
What micro-blogging projects use for content warnings is used for its original purpose on Hubzilla, namely as a summary. This is also because posts and comments have a practically unlimited character count. Technically, it's usually a high five-digit number, and it's configurable by the hub admin.
Hashtags are handled slightly differently because they can include more characters, and usual Mastodon tricks for interrupting hashtags don't work.
In addition to hashtags, posts can be given one or multiple categories. These are only used within the channel and can help finding posts.
Hubzilla has very extensive text formatting capabilities. It uses BBcode as its internal markup language for posts and comments. Specific expansions of Hubzilla's BBcode implementation can even make a post or a comment appear differently, depending on the on-looker, especially in conjunction with OpenWebAuth.
The handling of images and other media is a lot different from Mastodon and other micro-blogging projects. They aren't uploaded and attached to posts. Instead, they're first uploaded to the managed file space which is part of each channel. Then they are embedded into posts or, with a trick, comments as links to the uploaded files. Template:Internal Link and theoretically unlimited in length, too.
The number of images and other media that can be added to posts is practically unlimited again. Also, they can be placed anywhere in a post. However, Mastodon will convert only the last four to file attachments, move them from within the post to below it, reverse their order and completely discard the others if there are more than four.
There is also the possibility to attach a file to a post. It is then uploaded to the file space, too, so you always know where these files end up.
Posts and comments can be edited and deleted at any time. Any following comments will be deleted along with them. Posts or comments sharing a post or a comment that is deleted are not deleted.
Posts and comments from connections can be liked and disliked (another feature introduced by Friendica), and all posts and comments can be "saved in folders" for easier access. In addition, posts can be marked with a star which is only used internally; Mastodon's stars are likes just like those on Hubzilla.
Quoting
Hubzilla supports and can generate standard-compliant quotes. It doesn't have a dedicated quote button; the reply button generates a quote when at least a part of the post or comment to be quoted is marked first.
Like everything else in posts and comments, quotes are generated with BBcode in a fashion not dissimilar from how this is done in bulletin board forums. This means that quotes can be shortened to excerpts and/or split. In theory, it's even possible to quote multiple sources. In practice, this doesn't make much sense because a comment is always a follow-up to only reference one post or comment.
Partager
A feature like "retweeting" on Twitter/X, "reblogging" on Tumblr or "boosting" on Mastodon, i.e. forwarding posts as they are, is not available on Hubzilla.
Instead, posts and comments can be "shared" by referencing them in a new post or comment. It's basically the same as a "quote-tweet", but without copying the original post into the editor. For those who receive the post or comment, the reference is expanded to the whole shared post or comment, mentioning the author and giving a link to the original.
It is possible to share multiple posts/comments in one new post/comment.
Messages directs
Les messages directs sont également disponibles. Pour les garder privés sans avoir à définir manuellement les droits d'accès, les contacts auxquels un message direct doit être envoyé sont mentionnés avec @! au lieu de seulement @. Pour des raisons évidentes, ils ne peuvent être partagés. Sinon, ce sont comme des posts.
Autres fonctionalités
Voici quelques fonctionnalités supplémentaires de Hubzilla, dont certaines sont facultatives et pas nécessairement disponibles sur chaque hub.
Recherche
Hubzilla dispose d'une recherche très polyvalente qui peut trouver des publications par texte intégral, hashtags ou URL. Il peut également rechercher des chaînes/comptes, notamment des forums, et rechercher dans la documentation intégrée. Les recherches peuvent être enregistrées pour être répétées.
Sur certains hubs, la recherche publique locale peut être désactivée par l'admin.
Sondages
Comme la plupart des autres fonctions sur Hubzilla, le nombre de choix dans les sondages est pratiquement illimité. Les sondages offrent également plusieurs choix en option.
Avertissements de contenu automatisés
L'"application" facultative "NSFW" peut automatiquement placer des publications entières, des commentaires et des messages directs avec tout leur contenu derrière un bouton d'avertissement de contenu. En comparaison avec l'utilisation de filtres pour faire la même chose sur Mastodon, la configuration est à la fois simple et flexible : il n'y a qu'un seul champ de texte avec une liste de mots-clés séparés par des virgules. Si l'un d'entre eux est détecté dans un message entrant, il est remplacé par un bouton portant le mot-clé détecté. La liste prend en charge les mots et les expressions régulières, et même les langues peuvent être filtrées positivement ou négativement.
À cause de cette application, il est généralement recommandé d'ajouter le mot « NSFW » ou le hashtag « #NSFW » aux publications, commentaires et messages directs ayant un contenu « adulte » ; "NSFW" est l'un des deux mots-clés par défaut.
Clavarder
Les chaînes Hubzilla peuvent éventuellement avoir leur propre chat. L'accès à ce chat est réglementé par le propriétaire de la chaîne.
Channel sources
L'application facultative « Channel Sources » republie automatiquement tous les messages provenant d'une ou de plusieurs connexions. La source est toujours nommée, mais les publications ne sont pas partagées au sens habituel d'Hubzilla.
Espace fichier avec WebDAV
Chaque chaîne Hubzilla possède son propre espace fichiers avec un gestionnaire de fichiers intégré. Il prend en charge les sous-dossiers avec différentes autorisations d'accès et dispose d'un connecteur WebDAV, il peut donc être utilisé comme stockage de fichiers sur le nuage.
Calendrier avec CalDAV
Hubzilla ne possède pas qu'un seul mais deux systèmes séparés de calendrier.
L'un est le calendrier public qui est hérité de Friendica. Il peut afficher les évènements à venir dans votre sidebar et notifier vos abonnés sur les évènements à venir.
L'autre est un serveur privé de calendrier avec un accès CalDAV. Il peut seulement afficher les évènements à venir dans votre sidebar. Les calendriers CalDAV peuvent être partagés avec d'autres chaines Hubzilla, optionnellement avec un accès d'écriture.
CardDAV
Hubzilla also offers a CardDAV address book, but it doesn't have a graphical frontend.
Marquepages
L'application facultative marquepage est pour sauvegarder les liens dans les commentaires ou posts. Ces marquepages peuvent être privés ou partagées avec d'autres chaînes Hubzilla.
Articles
While formatted blog-style long-form posting is perfectly possible in normal Hubzilla posts, it also has an optional dedicated "app" for that. Articles can act like a blog with its own set of categories. It doesn't generate an RSS feed, though, and posted articles are neither forwarded nor advertised to connections; advertising them has to be done manually.
Les articles supporte le BBcode pour la mise en forme du texte.
Wikis
Une autre « application » facultative est « Wiki » qui permet d'avoir plusieurs wikis distincts sur n'importe quelle chaîne Hubzilla, chacun avec plusieurs pages. Au lieu d'un langage markup wiki dédié, ils utilisent soit BBcode, soit Markdown pour le formatage avec quelques ajouts typiques des wikis.
D'autres chaînes Hubzilla peuvent être autorisées à modifier des wikis sur une chaîne avec un rôle de contact spécial.
Pages web
Hubzilla peut également être utilisé comme hébergeur de pages Web, en utilisant l'« application » facultative « Pages Web ». Ces pages peuvent être mise en forme avec BBcode, Markup ou HTML. Par défaut, elles doivent être plutôt simples, mais les capacités des « Pages Web » peuvent être étendues par l'admin du hub.
Hubzilla's own official website is running on a Hubzilla channel.
Comparaison avec d'autres projets
Quels sont ses avantages par rapports à Mastodon ?
- Federates with diaspora* and StatusNet
- Connections with channels or entire instances of Hubzilla or (streams) that have ActivityPub off
- Native WordPress crossposter that makes WordPress federation fully bidirectional
- Optional automatic night/dark mode
- Multiple channels per account; no need to have multiple accounts
- Multiple profiles per channel
- Nomadic identity makes your content resilient against instance shutdown and moving your entire channel with everything on it very easy
- Full channel export for backup
- Moderated public and private discussion groups/forums (which are channels with specific role settings and thus can be nomadic themselves)
- Single sign-on through OpenWebAuth (planned for Mastodon)
- Very detailed permission settings
- Very easy Facebook-style point-and-click group editing plus adding connections to groups in the connection editor
- Preview buttons for posts and comments
- Virtually unlimited post length
- Summary (content warning on Mastodon & Co.) actually hides the whole post including all images
- Quotes fully supported
- Much more text formatting can be displayed (headlines, horizontal rules, spoilers, text colours, highlight colours etc.)
- Text in own posts/comments can be formatted
- Hyperlinks concealed under text can be created as a more elegant alternative to the URL in plain sight
- More than four images per post/comment
- Images anywhere in the text instead of only below it
- More than four poll options
- More characters possible in hashtags (double-edged sword)
- Moderate your own threads, delete comments in them
- Managed file space for images and other files, you know where your files are
- Images aren't compressed or shrunk when uploaded
- Add the same image to as many posts/comments as you want without re-uploading it
- Easy-to-use automated reader-side content warnings (NSFW app) which also hide the whole post
- Lots of additional features
- Can integrate third-party add-ons
- Code repositories not hosted on GitHub
Quelles sont les limitations/inconvénients par rapport à Mastodon ?
- No official mobile app named "Hubzilla"
- No iOS apps available, no alternative to the Web interface on iPhone and iPad
- The only working Android app, Nomad, is abandoned and hasn't been maintained in years
- Incompatible with Mastodon apps
- Cumbersome, maze-like default Web UI that hasn't changed much since 2012
- Much more difficult to use
- Incomplete and partially very outdated documentation
- ActivityPub is deactivated on new channels by default and has to be manually activated
- No Unlisted setting
- No per-post language choice
- No built-in translator
- No "Mastodon-style" content warnings for comments
- No boosts; only does quote-tweet-style "shares" instead
- Existing content warnings aren't automatically taken over when replying
- No automatic mentions when replying (unnecessary for Friendica, Hubzilla and (streams), but mandatory for Mastodon & Co.)
- Separate way of mentioning privately may be confusing
- Post and comment editors geared towards desktop/laptop computers with hardware keyboards
- Adding images to posts much less straight-forward
- Alt-text has to be manually edited into BBcode, no official documentation for this and no UI element either
- Posts and comments often not shown on Mastodon as they were written due to incompabilities
- Ignores not given full-text search opt-in
- Regular filters are impractical to the point of bordering on useless, depending on the intended use-case
- Not nearly as many channels possible on one hub as accounts are possible on one Mastodon server
Quels sont ses avantages par rapport à Friendica ?
- Connections with channels or entire instances of Hubzilla or (streams) that have ActivityPub off
- Multiple channels per account; no need to have multiple accounts
- Nomadic identity makes your content resilient against instance shutdown and moving even easier (Friendica was the reason why nomadic identity was invented)
- More advanced permission settings
- Dedicated summary field
- Polls which have been completely removed from Friendica
- WebDAV for the file space
- Lots of additional features
Quelles sont les limitations/inconvénients par rapport à Friendica ?
- Pas de compatibilité avec les applications de Mastodon.
- Seulement un seul thème disponible pour l'interface web, et ce n'est plus dévoloppé depuis 2012
- Pas de vue en arborescence pour les fils
- Pas d'indicateur sur l'origine d'un post ou commentaire.
Pour aller plus loin
Template:Internal Link
Template:Internal Link
Template:Internal Link
Liens externes
Main article: Template:Internal Link.