Jump to content

Hubzilla/it: Difference between revisions

Hubzilla/it (view source)

Revision as of 08:52, 6 September 2023

22,076 bytes added ,  1 year ago
Updating to match new version of source page
VisualWikitext
(Updating to match new version of source page)
Tags: Mobile edit Mobile web edit
(Updating to match new version of source page)
Line 1: Line 1:
<languages/>
<languages/>
<div class="mw-translate-fuzzy">
{{Infobox/it |title=Hubzilla |website=hubzilla.org }}
{{Infobox/it |title=Hubzilla |website=hubzilla.org }}
Hubzilla è un “Content Management System” (CMS) e nel “Fediverse” sostituisce Facebook, Dropbox, Google Calender e molto altro.
Hubzilla è un “Content Management System” (CMS) e nel “Fediverse” sostituisce Facebook, Dropbox, Google Calender e molto altro.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla is a very powerful "jack-of-all-trades" in the {{Internal Link |target=What is the Fediverse? |link-name=Fediverse}}, often described as a decentralised social content management system, but with social networking, microblogging and cloud features.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
It evolved from a Facebook alternative and still offers Facebook-like social networking. On top of that, it can be a replacement for services like Dropbox, Google Cloud Storage, Google Calendar, Google Contacts and many others.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<!-- From here on, the (streams) article will be very similar. If you edit one, check if the same part exists on the other, and edit it, too. -->
</div>


== Come mi posso immaginare Hubzilla?  ==
== Come mi posso immaginare Hubzilla?  ==
Line 9: Line 23:
</div>
</div>


<div class="mw-translate-fuzzy">
== Lo spazio speciale di Hubzilla nel Fediverse ==
== Lo spazio speciale di Hubzilla nel Fediverse ==
</div>


<div class="mw-translate-fuzzy">
<div class="mw-translate-fuzzy">
Line 15: Line 31:
</div>
</div>


Con un'identità web di Hubzilla chiamata "channel" e la funzione "Nomadic identity", i channels possono essere svincolati dall'hub in cui sono stati creati. Possono essere trasferiti in un altro hub, ma anche clonati, nel qual caso l'identità e i dati del channel esisteranno contemporaneamente in più luoghi.  
<div class="mw-translate-fuzzy">
Con un'identità web di Hubzilla chiamata "channel" e la funzione "Nomadic identity", i channels possono essere svincolati dall'hub in cui sono stati creati. Possono essere trasferiti in un altro hub, ma anche clonati, nel qual caso l'identità e i dati del channel esisteranno contemporaneamente in più luoghi.
</div>


<div class="mw-translate-fuzzy">
Inoltre, con la funzione "Open Web Auth" è possibile accedere semplicemente al contenuto di diversi siti web, senza dover inserire username e password per ogni sito. Si tratta di un'identificazione dell'utente con un solo clic: la possibilità di accedere ai siti semplicemente facendo clic sui collegamenti a siti remoti.
Inoltre, con la funzione "Open Web Auth" è possibile accedere semplicemente al contenuto di diversi siti web, senza dover inserire username e password per ogni sito. Si tratta di un'identificazione dell'utente con un solo clic: la possibilità di accedere ai siti semplicemente facendo clic sui collegamenti a siti remoti.
</div>


<div class="mw-translate-fuzzy">
Con il sofisticato sistema di "Access control", che consente anche di creare gruppi e forum, potrete finalmente iniziare a comunicare in modo più privato e controllare esattamente chi potrà vedere i vostri messaggi e i vostri file.
Con il sofisticato sistema di "Access control", che consente anche di creare gruppi e forum, potrete finalmente iniziare a comunicare in modo più privato e controllare esattamente chi potrà vedere i vostri messaggi e i vostri file.
</div>


<div class="mw-translate-fuzzy">
== Ulteriori informazioni ==
== Ulteriori informazioni ==
</div>


<div class="mw-translate-fuzzy">
<div class="mw-translate-fuzzy">
Line 31: Line 55:
</div>
</div>


<div class="mw-translate-fuzzy">
== Link esterni ==
== Link esterni ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
On top of that, Hubzilla kept Friendica's multiple profile per account and optionally offers multiple profiles per channel. You can assign specific profiles to your connections and show them different sides and aspects of your identity.
</div>
[[Category:What is/it]] [[Category:Hubzilla/it]] [[Category:Beginners guide/it]] [[Category:What are Fediverse projects?/it]]
<div lang="en" dir="ltr" class="mw-content-ltr">
Also, channels aren't bound to one hub. They also make {{Internal Link |target=What is nomadic identity? |link-name=nomadic identity}} 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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla supports single sign-on via {{Internal Link |target=What is OpenWebAuth? |link-name=OpenWebAuth}}. 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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Connections ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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, {{Internal Link |target=What is diaspora*? |link-name=diaspora*}} 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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Posts ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Just like Friendica, (streams), {{Internal Link |target=What is Lemmy? |link-name=Lemmy}} and {{Internal Link |target=What is kbin? |link-name=/kbin}}, 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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Also, the author of a post can moderate the thread following the post and delete comments.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hashtags are handled slightly differently because they can include more characters, and usual Mastodon tricks for interrupting hashtags don't work.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
In addition to hashtags, posts can be given one or multiple categories. These are only used within the channel and can help finding posts.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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. {{Internal Link |target=How to add alt-text to images on Hubzilla and (streams) |link-name=Alt-text is added by editing the BBcode}} and theoretically unlimited in length, too.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Quoting ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Sharing ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Instead, posts and comments can be "shared" by referencing them in a new post or comment. 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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
It is possible to share multiple posts/comments in one new post/comment.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Direct messages ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Direct messages are available, too. To keep them private without having to set the access rights manually, the contacts to which a direct message is to be sent are mentioned with <code>@!</code> instead of only <code>@</code>. For obvious reasons, they cannot be shared. Otherwise, they are like posts.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== Other features ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Here are some more of Hubzilla's features, some of which are optional and not necessarily available on each hub.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Search ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla has a very versatile search that can find posts by full text, hashtags or URL. It can also search for channels/accounts including specifically forums, and it can search the built-in documentation. Searches can be saved to be repeated.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Some hubs may have their local public search deactivated by the admin.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Polls ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Just like most other things on Hubzilla, the number of choices on polls is practically unlimited. Polls also offer multiple choices as an option.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Automated content warnings ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The optional "app" ''NSFW'' can automatically put entire posts, comments and direct messages with all their contents behind a content warning button. In comparison with using filters to do the same thing on Mastodon, the configuration is both easy and flexible: There is only one text field with a comma-separated list of keywords. If one of them is detected in an in-coming message, it is replaced with a button with the detected keyword on it. The list supports words and regular expressions, and even languages can be filtered positively or negatively.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Because of this app, it is generally recommended to add the word "NSFW" or the hashtag "#NSFW" to posts, comments and direct messages with "adult" content; "NSFW" is one of the two default keywords.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Chat ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla channels can optionally have their own chat. Access to this chat is regulated by the channel owner.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Channel sources ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The optional ''Channel Sources'' "app" automatically reposts all posts coming in from one or multiple connections. The source is always named, but the posts are not shared in Hubzilla's usual sense.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== File space with WebDAV ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Each Hubzilla channel has its own file space, complete with a built-in file manager. It supports subfolders with variable access permissions, and it has a WebDAV connector, so it can be used as a cloud file storage.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Calendars with CalDAV ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla has not one, but two separate calendar systems.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
One is the public calendar which it inherited from Friendica. It can display upcoming events in your sidebar and notify your followers about upcoming events.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The other one is a private calendar server with CalDAV access. It can only display upcoming events in your sidebar. CalDAV calendars can be shared with other Hubzilla channels, optionally with write access.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== CardDAV ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla also offers a CardDAV address book, but it doesn't have a graphical frontend.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Bookmarks ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
The optional ''Bookmarks'' "app" is for bookmarking links in posts or comments. These bookmarks can be private or shared with other Hubzilla channels.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Articles ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Articles support BBcode for text formatting.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Wikis ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Another optional "app" is ''Wiki'' which makes it possible to have multiple separate wikis on any Hubzilla channel, each with multiple pages. Instead of a dedicated wiki markup language, they use either BBcode or Markdown for formatting with a few additions typical for wikis.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Other Hubzilla channels can be allowed to edit wikis on a channel with a special contact role.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Webpages ====
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla can optionally even used as a webpage host, using the optional "app" ''Webpages''. These pages can be formatted with BBcode, Markup or HTML. By default, they have to be rather simple, but the capabilities of ''Webpages'' can be expanded by the hub admin.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Hubzilla's own official website is running on a Hubzilla channel.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Comparison with other projects ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== What are some advantages over Mastodon? ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* 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
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== What are some limitations/drawbacks in comparison with Mastodon? ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* No mobile apps available, incompatible with Mastodon apps, no alternative to the Web interface
* 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
* 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
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== What are some advantages over Friendica? ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* 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
* Polls which have been completely removed from Friendica
* WebDAV for the file space
* Lots of additional features
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
=== What are some limitations/drawbacks in comparison with Friendica? ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* No compatibility with Mastodon apps
* Only one Web UI theme available, and it's stuck in 2012
* No tree-style thread view
* No indicator which project a post or comment came from
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== Further reading ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
{{Internal Link |target=Hubzilla |link-name=Hubzilla}} <br>
{{Internal Link |target=How do I get an account? |link-name=How do I get an account?}} <br>
<!-- Commented out for the time being because not applicable to Hubzilla {{Internal Link |target=Getting started with your Fediverse account |link-name=Getting started with your Fediverse account}} <br> -->
{{Internal Link |target=Best practices |link-name=Best practices}} <br>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
== External links ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Main article: [[Special:MyLanguage/Fediverse weblinks#Hubzilla | Weblinks]]
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<div lang="en" dir="ltr" class="mw-content-ltr">
* [http://hubzilla.org Hubzilla project site]
* [https://hubzilla.org Hubzilla project site]
* [https://framagit.org/hubzilla/core Hubzilla Git repository]
* [https://framagit.org/hubzilla/core Hubzilla Git repository]
* [https://framagit.org/hubzilla/addons Hubzilla add-ons Git repository] (includes the ActivityPub connector Pubcrawl)
* [https://gnulinux.ch/serie-fediverse-dienste-hubzilla Hubzilla - die mächtige ungeschminkte Königin des Fediverse]
* [https://gnulinux.ch/serie-fediverse-dienste-hubzilla Hubzilla - die mächtige ungeschminkte Königin des Fediverse]
</div>
</div>
{{Navbar/Hubzilla}}
{{Navbar/Hubzilla}}
FuzzyBot
10,793

edits

Retrieved from "https://joinfediverse.wiki/Special:MobileDiff/20479"