Individuals and organisations wishing to support the Hubzilla project are invited to apply for membership of the Hubzilla Association.
Information on the membership process can be found on this page.
Information on the membership process can be found on this page.
Here's a brief look at the ongoing development of the Superblock addon for Hubzilla by Harald. Stay tuned for more!
This new theme brings many of the user interface improvements that users requested in the 2026 Hubzilla survey to life.
Please give it a try and share your feedback, experiences, and any issues or bugs you encounter. Thank you!
Before you can use this theme, it must be made available by your hub's administrator. If you don't see it on your hub yet, please contact your admin.
Please give it a try and share your feedback, experiences, and any issues or bugs you encounter. Thank you!
Before you can use this theme, it must be made available by your hub's administrator. If you don't see it on your hub yet, please contact your admin.
Survey 2026 results:
The access controlling mechanism needs a better user interface. Choosing custom access should become possible without a lot of scrolling. When clicking on "is visible to", and a connection group or custom selection is shown, that should be expandable to see all members of that group. Switching to "post to public by default" should become simpler and more obvious. A friendlier way than selecting a contact is asked for private messaging. This shows that the @! tag is not known to all users.
Users find privacy roles complicated or say they don't understand them. There should be more predefined roles. "can edit wiki" should be possible to set per wiki, and from the wiki page.
Users ask for bulk actions to become able to be performed on contacts, such as "delete user", "assign user to privacy role", "no boosts from this user", "not following this contact", "mute this contact", and add category/tag. It should become possible to add notes to a contact as well. Users ask for a better filtering/searching/sorting order of contacts (i.e. filter by contact role, by privacy group, by category). The contact list should adapt dynamically to the filtering and searching. An export feature of optionally filtered (i.e. blocked) contacts would be appreciated, as well as an "import a contact list" feature which applies bulk actions (i.e. "block") on it. It's considered very hard to find a contact without already knowing the handle. I.e. the "add connections" field should search for the user whether the @ is in front or not. It's not clear what "New connections" means (how many days, weeks, month,...). The UI should offer less and clear navigation choices: Items from the "Contact tools" dropdown should be moved into the main dialog. Instead of editing a contact it in a pop-up, it should be done in a proper page where we have an overview of all contact settings. We should get an info when a contact unfollows you, and what the red/orange/green buttons stands for. A filter "via zot/activitypub/..." to be applicable on the timeline would be appreciated, also a filter by preferred language(s) of channels to be appicable on the directory.
Users wish drafts to be autosaved so posts can be edited on a different device later. Posts should not be reformatted when saving them, so that the user can edit the original post, not some modified version of it. A good graphical editor would be appreciated, and better interoperability between Markdown and BBCode when Markdown is enabled. Markdown should become supported by all kinds of Hubzilla apps. Some help/manual for formatting should be provided beside the composing window. Commenting should not be done in a pop-up, to be able to read previous comments while typing.
It is wished to make it easier to embed media in general. How it is done now is felt slow and complicated. Drag/drop and copy/paste for media is missed, as well as the option to add alt text (with character count) to pictures and videos, and a GUI-supported way to choose its preview size, original size and alignment. Alt-text should be taken over by the Photo app. Audio Players should be stylable (width, height, waveform on/off, cover on/off, title on/off), and support a "Buy in high resolution" option, in connection with the cart addon eventually, or adding an outbound link to that option - with support for multiple players in the post, and compatibility with Activitypub. There should be an UI for setting the thumbnail of a video. There should be a video only storage space.
The hidden text feature should become Activitypub compatible and able to be used with an icon for "hide and show on click" at the bottom of the editor field.
Both composing and displaying language-based content needs improvement. Mastodon is mentioned as setting the standard here. When composing, now we can choose only = or !=. We would want also "in (list of languages)" or "not in (list of languages)". The User language preferences should be captured in profile and matched to directory and content.
A fully functional full-text search covering all public (and internal, regardless of access rights) posts, articles and maps, as well as a fully functional full-text search on the wiki, would be desirable. Make searches more intuitive with filters (i.e. only my own posts). Documentation search needs to be fixed.
There should be a way to give individuals access to certain wikis, but not to all wikis in the user's channel (see above, under access controlling). Wikis should be categorizable. How to share calendars is not obvious to all, while others ask a more small screen friendly way to do this.
The distinction between Hubzilla Apps and Addons is not clear. Apps/Addons should become searchable and filterable. Available and installed apps should show on the same page. Activating/desactivating should be possible to do with one click on that page. The philosophy for updating apps ist not clear for some users. It would be appreciated if revisions could be added to each app, so that it is clear if an app needs to be updated. Admins should become able to install Addons directly from the Admin UI.
Placing apps/addons in the navigation should become possible to do by drag and drop. The star for the app tray could be replaced with the three dots so it's more obvious at first glance what it does.
The UX needs to be more streamlined from the perspective of a new user so the learning curve can be reduced. The UI/UX needs to be user language and mobile friendly. The number of necessary clicks should be reduced in general. It is asked that development concentrates on a few core functionalities and improve those rather than trying to offer everything. A better integration with Open Street Maps is asked, so that location features could be more like in (streams). It is proposed that the default theme should be other than redbasic. It should look more like one of the adminlte themes. Having the timeline, calendars, contacts, etc. in one place, like in MS Outlook, is wished.
Hubzilla Association's thoughts and plan:
The Hubzilla Association appreciates all these ideas about improvement a lot. Above, they're grouped into the topics (1) access controlling, (2) content publishing, (3) collaboration, (4) apps, and 5 (general UI/UX). The Hubzilla community could launch fundraising campaigns (containing some of the collected concrete ideas), seperately for each topic (or for parts of them), and hope for a big support of the campaigns by the community. And we could start by thinking together about what topic should be worked first, and what next. The Hubzilla Association could take care of the organizational part of such fundraising campaigns. Ideas for fundraising initiatives are welcome.
Concerning the proposal of concentrating the development on a few core functionalities: We already did so by moving apps like Wiki, Articles and Cards out of the core repository into the Addons repository. Like that, other developers than the core developers can take care of them. Existing functionalities will not be removed.
What do you think should we do next, concerning these ideas for improving Hubzilla? Please share your thoughts as comments.
Access Controlling, Connections and Directory
The access controlling mechanism needs a better user interface. Choosing custom access should become possible without a lot of scrolling. When clicking on "is visible to", and a connection group or custom selection is shown, that should be expandable to see all members of that group. Switching to "post to public by default" should become simpler and more obvious. A friendlier way than selecting a contact is asked for private messaging. This shows that the @! tag is not known to all users.
Users find privacy roles complicated or say they don't understand them. There should be more predefined roles. "can edit wiki" should be possible to set per wiki, and from the wiki page.
Users ask for bulk actions to become able to be performed on contacts, such as "delete user", "assign user to privacy role", "no boosts from this user", "not following this contact", "mute this contact", and add category/tag. It should become possible to add notes to a contact as well. Users ask for a better filtering/searching/sorting order of contacts (i.e. filter by contact role, by privacy group, by category). The contact list should adapt dynamically to the filtering and searching. An export feature of optionally filtered (i.e. blocked) contacts would be appreciated, as well as an "import a contact list" feature which applies bulk actions (i.e. "block") on it. It's considered very hard to find a contact without already knowing the handle. I.e. the "add connections" field should search for the user whether the @ is in front or not. It's not clear what "New connections" means (how many days, weeks, month,...). The UI should offer less and clear navigation choices: Items from the "Contact tools" dropdown should be moved into the main dialog. Instead of editing a contact it in a pop-up, it should be done in a proper page where we have an overview of all contact settings. We should get an info when a contact unfollows you, and what the red/orange/green buttons stands for. A filter "via zot/activitypub/..." to be applicable on the timeline would be appreciated, also a filter by preferred language(s) of channels to be appicable on the directory.
Publishing (composing, editing), searching, and filtering content
Users wish drafts to be autosaved so posts can be edited on a different device later. Posts should not be reformatted when saving them, so that the user can edit the original post, not some modified version of it. A good graphical editor would be appreciated, and better interoperability between Markdown and BBCode when Markdown is enabled. Markdown should become supported by all kinds of Hubzilla apps. Some help/manual for formatting should be provided beside the composing window. Commenting should not be done in a pop-up, to be able to read previous comments while typing.
It is wished to make it easier to embed media in general. How it is done now is felt slow and complicated. Drag/drop and copy/paste for media is missed, as well as the option to add alt text (with character count) to pictures and videos, and a GUI-supported way to choose its preview size, original size and alignment. Alt-text should be taken over by the Photo app. Audio Players should be stylable (width, height, waveform on/off, cover on/off, title on/off), and support a "Buy in high resolution" option, in connection with the cart addon eventually, or adding an outbound link to that option - with support for multiple players in the post, and compatibility with Activitypub. There should be an UI for setting the thumbnail of a video. There should be a video only storage space.
The hidden text feature should become Activitypub compatible and able to be used with an icon for "hide and show on click" at the bottom of the editor field.
Both composing and displaying language-based content needs improvement. Mastodon is mentioned as setting the standard here. When composing, now we can choose only = or !=. We would want also "in (list of languages)" or "not in (list of languages)". The User language preferences should be captured in profile and matched to directory and content.
A fully functional full-text search covering all public (and internal, regardless of access rights) posts, articles and maps, as well as a fully functional full-text search on the wiki, would be desirable. Make searches more intuitive with filters (i.e. only my own posts). Documentation search needs to be fixed.
Collaboration
There should be a way to give individuals access to certain wikis, but not to all wikis in the user's channel (see above, under access controlling). Wikis should be categorizable. How to share calendars is not obvious to all, while others ask a more small screen friendly way to do this.
Apps/Addons
The distinction between Hubzilla Apps and Addons is not clear. Apps/Addons should become searchable and filterable. Available and installed apps should show on the same page. Activating/desactivating should be possible to do with one click on that page. The philosophy for updating apps ist not clear for some users. It would be appreciated if revisions could be added to each app, so that it is clear if an app needs to be updated. Admins should become able to install Addons directly from the Admin UI.
Placing apps/addons in the navigation should become possible to do by drag and drop. The star for the app tray could be replaced with the three dots so it's more obvious at first glance what it does.
Ideas and wishes for UI/UX:
The UX needs to be more streamlined from the perspective of a new user so the learning curve can be reduced. The UI/UX needs to be user language and mobile friendly. The number of necessary clicks should be reduced in general. It is asked that development concentrates on a few core functionalities and improve those rather than trying to offer everything. A better integration with Open Street Maps is asked, so that location features could be more like in (streams). It is proposed that the default theme should be other than redbasic. It should look more like one of the adminlte themes. Having the timeline, calendars, contacts, etc. in one place, like in MS Outlook, is wished.
Hubzilla Association's thoughts and plan:
The Hubzilla Association appreciates all these ideas about improvement a lot. Above, they're grouped into the topics (1) access controlling, (2) content publishing, (3) collaboration, (4) apps, and 5 (general UI/UX). The Hubzilla community could launch fundraising campaigns (containing some of the collected concrete ideas), seperately for each topic (or for parts of them), and hope for a big support of the campaigns by the community. And we could start by thinking together about what topic should be worked first, and what next. The Hubzilla Association could take care of the organizational part of such fundraising campaigns. Ideas for fundraising initiatives are welcome.
Concerning the proposal of concentrating the development on a few core functionalities: We already did so by moving apps like Wiki, Articles and Cards out of the core repository into the Addons repository. Like that, other developers than the core developers can take care of them. Existing functionalities will not be removed.
What do you think should we do next, concerning these ideas for improving Hubzilla? Please share your thoughts as comments.
For UI/UX improvement i would like to point out to a new approach i have been trying with a new theme based on solidjs, which i have shared in current alpha version here: https://utsukta.org/display/cf5d9128-7da9-41c6-a328-daa507a8422c
This theme separates the frontend from the backend and implements hubzilla UI as a SPA(single page application) which simplifies the user experience by reducing the navigation needed to get something done.
Addressing accessibility has also been a goal with this approach, making sure that the interface is up to web accessibility standards.
While this is in very early development stage and needs much more work to be fully functional, i hope it can be helpful in addressing these shortcomings that people face.
This theme separates the frontend from the backend and implements hubzilla UI as a SPA(single page application) which simplifies the user experience by reducing the navigation needed to get something done.
Addressing accessibility has also been a goal with this approach, making sure that the interface is up to web accessibility standards.
While this is in very early development stage and needs much more work to be fully functional, i hope it can be helpful in addressing these shortcomings that people face.
Survey 2026 results:
According to the survey, Hubzilla is considered by the majority to be suited well for hosting webpages, while a minority considers lightweight or standard CMS a better option, stating Hubzilla to be too powerful for just that purpose with a too big database footpring, missing simplicity of use, accessibility and first class support for Markdown/Aasciidoc/RestructuredText.
Almost all survey participants find Hubzilla to be suited well for networking within the Fediverse and macroblogging. When it comes to microblogging, a few prefer Maston, Sharkey or Mitra, while missing in Hubzilla a mobile client (respective Mastodon API support), or MS Outlook-like apps showing a timeline or managing contacts and calendars.
The majority of survey participants find Hubzilla useful for sharing events. A minority disagrees with that, prefering Mobilizon, WordPress, Email newsletters or the Nextcloud calendar. They miss nicer looking event pages, compatibility with Mobilizon and events reaching Mastodon, and outside the Fediverse.
A big part of survey participants find Hubzilla not suited for decision-making (scheduling etc.). Nextcloud or Framadate are preferred tools for them, which offer more scheduling tools, as well as an easy guest/anonymous access management.
The majority of survey participants find Hubzilla useful for sharing data (cloud). A minority prefers Nextcloud. Missed features in Hubzilla are a desktop app to sync the data, Open Cloud Mesh support, a better UI for file sharing (with an optional expiration date, anonymous access, and the option to protect by a password).
Half of the survey participants find Hubzilla useful for presenting pictures/photos. One fourth prefers Nextcloud, Pixelfed, Lychee or "an own website". The other fourth didn't answer the question. Missed features are photo tagging, timeline view and other organizational tools. Mastodon not blanking out sensitive images when a message coming from Hubzilla containing the hashtag "nsfw" or "sensitive" is mentioned as suboptimal.
Half of the survey participants didn't answer if they find Hubzilla useful for hosting and moderating forums. A big majority of those who answered find it useful. The remaining participants prefer dedicated forum software such as Discourse or NodeBB. Missed features in Hubzilla forums are the possibility to participate from other Fediverse platforms, easy ways to find threads and responses, upvoting, marking as solved, and grouping of threads.
Most survey participants agree only partially with Hubzilla being useful for syncing via WebDAV, CalDAV, CardDAV. Nextcloud is preferred by many. An easier webinterface and a desktop app are missed in Hubzilla, as well as more and better options to protect such data with a password.
In the survey, we didn't get enough responses about Hubzilla being suited or not for these use cases: streaming audio, streaming video, learning management, extending device storage via WebDAV, and collaboration on documents (Wiki, Collabora). We refrain from drawing any conclusions on these matters.
Hubzilla Association's thoughts and plan:
The Hubzilla Association could now, in order to get fast "results", secure funding and developer resources for improving user satisfaction for some of the use cases. We could for example focus on those for which satisfaction is already high, which are, in this order, (1) networking within the Fediverse, (2) macroblogging, (3) microblogging, (4) hosting webpages, and (5) presenting pictures/photos. Another strategy, which might demand more effort and time, could be securing funding and developer resources for improving (and empowering more broadly) one (or some) already favourable basic conditions of Hubzilla, such as built-in OpenWebAuth, and enhance their qualities to make fitting missing features happen. Or, since there are developers out there who could build things on our platform to make it friendly for specific use cases, we could let them know this, and provide them additional documentation on how to do it. We have heard several people say that they want to build something and use Hubzilla to do it, but didn't yet because they could not figure out how to do it. So, if we provide more resources for developers, we may find a lot of interesting addons, themes, and widgets being built. For that, a revision of the "Developer's Guide" is planned. Also, we would like to encourage developers of addons etc. to ask in the @Hubzilla Development forum, so everybody can learn from it together.
What do you think should we do next, concerning use cases for Hubzilla? Please share your thoughts as comments.
According to the survey, Hubzilla is considered by the majority to be suited well for hosting webpages, while a minority considers lightweight or standard CMS a better option, stating Hubzilla to be too powerful for just that purpose with a too big database footpring, missing simplicity of use, accessibility and first class support for Markdown/Aasciidoc/RestructuredText.
Almost all survey participants find Hubzilla to be suited well for networking within the Fediverse and macroblogging. When it comes to microblogging, a few prefer Maston, Sharkey or Mitra, while missing in Hubzilla a mobile client (respective Mastodon API support), or MS Outlook-like apps showing a timeline or managing contacts and calendars.
The majority of survey participants find Hubzilla useful for sharing events. A minority disagrees with that, prefering Mobilizon, WordPress, Email newsletters or the Nextcloud calendar. They miss nicer looking event pages, compatibility with Mobilizon and events reaching Mastodon, and outside the Fediverse.
A big part of survey participants find Hubzilla not suited for decision-making (scheduling etc.). Nextcloud or Framadate are preferred tools for them, which offer more scheduling tools, as well as an easy guest/anonymous access management.
The majority of survey participants find Hubzilla useful for sharing data (cloud). A minority prefers Nextcloud. Missed features in Hubzilla are a desktop app to sync the data, Open Cloud Mesh support, a better UI for file sharing (with an optional expiration date, anonymous access, and the option to protect by a password).
Half of the survey participants find Hubzilla useful for presenting pictures/photos. One fourth prefers Nextcloud, Pixelfed, Lychee or "an own website". The other fourth didn't answer the question. Missed features are photo tagging, timeline view and other organizational tools. Mastodon not blanking out sensitive images when a message coming from Hubzilla containing the hashtag "nsfw" or "sensitive" is mentioned as suboptimal.
Half of the survey participants didn't answer if they find Hubzilla useful for hosting and moderating forums. A big majority of those who answered find it useful. The remaining participants prefer dedicated forum software such as Discourse or NodeBB. Missed features in Hubzilla forums are the possibility to participate from other Fediverse platforms, easy ways to find threads and responses, upvoting, marking as solved, and grouping of threads.
Most survey participants agree only partially with Hubzilla being useful for syncing via WebDAV, CalDAV, CardDAV. Nextcloud is preferred by many. An easier webinterface and a desktop app are missed in Hubzilla, as well as more and better options to protect such data with a password.
In the survey, we didn't get enough responses about Hubzilla being suited or not for these use cases: streaming audio, streaming video, learning management, extending device storage via WebDAV, and collaboration on documents (Wiki, Collabora). We refrain from drawing any conclusions on these matters.
Hubzilla Association's thoughts and plan:
The Hubzilla Association could now, in order to get fast "results", secure funding and developer resources for improving user satisfaction for some of the use cases. We could for example focus on those for which satisfaction is already high, which are, in this order, (1) networking within the Fediverse, (2) macroblogging, (3) microblogging, (4) hosting webpages, and (5) presenting pictures/photos. Another strategy, which might demand more effort and time, could be securing funding and developer resources for improving (and empowering more broadly) one (or some) already favourable basic conditions of Hubzilla, such as built-in OpenWebAuth, and enhance their qualities to make fitting missing features happen. Or, since there are developers out there who could build things on our platform to make it friendly for specific use cases, we could let them know this, and provide them additional documentation on how to do it. We have heard several people say that they want to build something and use Hubzilla to do it, but didn't yet because they could not figure out how to do it. So, if we provide more resources for developers, we may find a lot of interesting addons, themes, and widgets being built. For that, a revision of the "Developer's Guide" is planned. Also, we would like to encourage developers of addons etc. to ask in the @Hubzilla Development forum, so everybody can learn from it together.
What do you think should we do next, concerning use cases for Hubzilla? Please share your thoughts as comments.
Survey 2026 results:
According to the survey, the time for a user to get familiar with Hubzilla so that they felt comfortable to use it varies a lot, from "some days" to "more than 6 months", with more than half of the responses indicating 2 weeks to 2 months. Most users use it once or several times a day.
More than half of the current users use Hubzilla on an own hub. Finding a trustful hub run by someone else seems to be not so easy. Most of those who don't run their own hub wish to do so in the future. For that, most need more own resources.
Hubzilla Association's thoughts and plan:
We want to simplify the user experience so the user interface becomes self-explainatory, and to include a tour for beginners into the user interface, to make onboarding easier and to shorten the time needed to become familiar with the software.
We think that encouraging web hosting companies to offer Hubzilla as a service (and offering them support for doing so) could be a great way to lower the barriers for users for running their own hub.
What do you think should we do next, concerning Hubzilla onboarding and finding hubs or hosted services? Please share your thoughts as comments.
According to the survey, the time for a user to get familiar with Hubzilla so that they felt comfortable to use it varies a lot, from "some days" to "more than 6 months", with more than half of the responses indicating 2 weeks to 2 months. Most users use it once or several times a day.
More than half of the current users use Hubzilla on an own hub. Finding a trustful hub run by someone else seems to be not so easy. Most of those who don't run their own hub wish to do so in the future. For that, most need more own resources.
Hubzilla Association's thoughts and plan:
We want to simplify the user experience so the user interface becomes self-explainatory, and to include a tour for beginners into the user interface, to make onboarding easier and to shorten the time needed to become familiar with the software.
We think that encouraging web hosting companies to offer Hubzilla as a service (and offering them support for doing so) could be a great way to lower the barriers for users for running their own hub.
What do you think should we do next, concerning Hubzilla onboarding and finding hubs or hosted services? Please share your thoughts as comments.
@Hubzilla Info I am using it since 3++ years, and i find certain things still completely counter intuitive. That said use it, because a lot fo what it does is great :) But it is definately more of an oversized Mercedes for coders to maitain and unxderstand, then a publicly usable software.
Survey 2026 results:
According to the survey, Hubzilla is used mainly by individuals. There are also a few businesses and organisations using it. While most individuals use it frequently, most businesses and organisations use it occasionally. Most common fields for which individuals use Hubzilla are Tech, Human Relation, Art and Science. For businesses, it's Tech, Art and Education. For organisations, it's Tech, Human Relation, Education and Science.
The software features of Hubzilla, and Hubzilla being an open source project, are clearly reasons for which Hubzilla has been chosen to be used. Also the interests and communication culture of its community seems to be rather important for that choice. Hubzilla being backed by the Hubzilla Association seems to be relevant for the choice of the platform, whereas the image of the Hubzilla project (name, public appearance) seems to be less relevant.
Under the presumption that certain aspects improve, current users would use Hubzilla more often or more intensively as an individual. For that to happen, the software features and functionalities have to improve, whereas the organisational structure, the communication culture of the community and the image of the Hubzilla project are considered partially important for that to happen.
Most of the current users use Hubzilla for more than three years now, while there are also some new or less longtime users. We interpret this as Hubzilla being the "last haven" where most users stay, once they settled.
Hubzilla Association's thoughts and plan:
The Hubzilla Association's takeaway from this is that while the dominating demographic is individuals, but with almost 20% using it in the capacity of some sort of organization, we definitely think it's worth keeping that use case in mind. We think it is important to develop Hubzilla further to satisfy the needs of the current user group, which is using Hubzilla for Tech, Human Relation, Art, Science and Education, and which values a good communication culture of the community. We want Hubzilla to keep satisfying long time users, and to become the daily driver for future long time users. The main focus for future developments should be on improving the software features, while organisational and PR efforts should not be neglected. We want to continue to support the healthy communication culture of the community.
What should we do next regarding target groups of Hubzilla? Please share your thoughts as comments.
According to the survey, Hubzilla is used mainly by individuals. There are also a few businesses and organisations using it. While most individuals use it frequently, most businesses and organisations use it occasionally. Most common fields for which individuals use Hubzilla are Tech, Human Relation, Art and Science. For businesses, it's Tech, Art and Education. For organisations, it's Tech, Human Relation, Education and Science.
The software features of Hubzilla, and Hubzilla being an open source project, are clearly reasons for which Hubzilla has been chosen to be used. Also the interests and communication culture of its community seems to be rather important for that choice. Hubzilla being backed by the Hubzilla Association seems to be relevant for the choice of the platform, whereas the image of the Hubzilla project (name, public appearance) seems to be less relevant.
Under the presumption that certain aspects improve, current users would use Hubzilla more often or more intensively as an individual. For that to happen, the software features and functionalities have to improve, whereas the organisational structure, the communication culture of the community and the image of the Hubzilla project are considered partially important for that to happen.
Most of the current users use Hubzilla for more than three years now, while there are also some new or less longtime users. We interpret this as Hubzilla being the "last haven" where most users stay, once they settled.
Hubzilla Association's thoughts and plan:
The Hubzilla Association's takeaway from this is that while the dominating demographic is individuals, but with almost 20% using it in the capacity of some sort of organization, we definitely think it's worth keeping that use case in mind. We think it is important to develop Hubzilla further to satisfy the needs of the current user group, which is using Hubzilla for Tech, Human Relation, Art, Science and Education, and which values a good communication culture of the community. We want Hubzilla to keep satisfying long time users, and to become the daily driver for future long time users. The main focus for future developments should be on improving the software features, while organisational and PR efforts should not be neglected. We want to continue to support the healthy communication culture of the community.
What should we do next regarding target groups of Hubzilla? Please share your thoughts as comments.
The survey was done March-April 2026 and got in total 54 (including non-complete) responses. The Hubzilla Association would like to thank to all participants! This survey provides an excellent foundation for taking further action, but we should keep in mind that only a portion of the community participated in the survey, so the results aren’t 100% representative.
The Hubzilla Association presents its analysis and interpretation report of the survey, which it wants to be understood as a source for inspiration for what the community with the support of the association can do in the future. It should not be taken as a roadmap of the association. The association doesn't have enough resources yet to realise a roadmap.
The survey shows that the community cares a lot about Hubzilla and has excellent thoughts about how to improve it. All the responses can be found at the bottom of the report.
This analysis and interpretation of the survey is an invitation to the community to try to identify some focal points on which we can join our efforts in the near future. The association could accompany such a focalising process by initiating, and then organisationally taking care, of
This focalising process can start now. On the International Hubzilla Meetup 2027 in Vienna, Austria, on February 27 - 28, 2027, which is open to anyone, we intend to continue the discussions and working groups.
Meanwile, the association intends to grow. Eventually, we will have enough resources in the future to kickoff development efforts ourselves. New members are always welcome.
The Hubzilla Association feels encouraged by your feedback that Hubzilla is important, and intends to harness this energy to create even more joyful and satisfying experiences for current and future Hubzilla users. Thank you for continuing this trip with us! On this channel, we will publish excerpts of the report, one per topic. Please join the discussions there.
The Hubzilla Association presents its analysis and interpretation report of the survey, which it wants to be understood as a source for inspiration for what the community with the support of the association can do in the future. It should not be taken as a roadmap of the association. The association doesn't have enough resources yet to realise a roadmap.
The survey shows that the community cares a lot about Hubzilla and has excellent thoughts about how to improve it. All the responses can be found at the bottom of the report.
This analysis and interpretation of the survey is an invitation to the community to try to identify some focal points on which we can join our efforts in the near future. The association could accompany such a focalising process by initiating, and then organisationally taking care, of
- working groups and meetups (in which the responses to the survey could also be discussed)
- bringing more developers on board (reaching out to them; providing good documentation and support)
- raising funds (specifically for well-defined development goals)
This focalising process can start now. On the International Hubzilla Meetup 2027 in Vienna, Austria, on February 27 - 28, 2027, which is open to anyone, we intend to continue the discussions and working groups.
Meanwile, the association intends to grow. Eventually, we will have enough resources in the future to kickoff development efforts ourselves. New members are always welcome.
The Hubzilla Association feels encouraged by your feedback that Hubzilla is important, and intends to harness this energy to create even more joyful and satisfying experiences for current and future Hubzilla users. Thank you for continuing this trip with us! On this channel, we will publish excerpts of the report, one per topic. Please join the discussions there.
Here are the discussion threads:
Powered by the Hubzilla Fediverse Server. Celebrating 16 Years of Innovation.
Artwork by aaatelier.eu / Logo-Lettering by bueropecher.de