Red – welcome to the network

 

The Friendica project is pleased to announce the Developer Preview release of "red" -  a new concept in online communications.

Because somebody has to stand up for the people of the internet...

You may obtain a copy via git at https://github.com/friendica/red

The Developer Preview is intended for developers to have a look at the emerging project and possibly influence its direction. This is not intended as a preview to the general public. There are bugs. There are security and privacy issues. Things could crash spectacularly. If this doesn't sound like fun to you, please avoid this preview and wait for a public preview or release. Not all the described features are complete, but you might be surprised how much works today - for a pre-release project of this scope.

Red is kind of like a decentralised social network (along the lines of  identi.ca, Friendica, and Diaspora) , but we've thrown away the rule book. Red has no concept of "people" or "friends" or "social". Red is a means of creating channels which can communicate with each other and to allow other channels permission to do things (or not). These channels can look like people and they can look like friends and they can be social.

They can also look like a great many other things - forums, groups, clubs, online websites, photo archives and blogs, wikis, corporate and small business websites, etc. They are just channels - with permissions that extend far beyond a single website. You can make them into whatever you wish them to be. You can associate web resources and files to these channels or stick with basic communications. There are no inherent limits. There is no central authority telling you what you can and cannot do. Any filtering that happens is by your choice. Any setting of permissions is your choice and yours alone.

You aren't tied to a single hub/website. If your own site gets shut down due to hardware or management issues or political pressure, the communication layer allows you to  pop up anywhere on the Internet and resume communicating with your friends, by inserting a thumb drive containing your vital identity details or importing your account from another server. 

Your resources can be access controlled to allow or deny any person or group you wish - and these permissions work across the Red network no matter what provider hosts the actual content. Red "magic-auth" allows anybody from any Red site to be identified before allowing them to see your private photos, files, web-pages, profiles, conversations, whatever.  To do this, you only login once to your own home hub. Everything else is, well - magic.

Red is free and open source and provided by volunteers who believe in freedom and despise corporations which think that privacy extortion is a business model. The name is derived from Spanish "la red" - e.g. "the network".

Welcome to "the network". Welcome to the free web. Welcome to the grid. Red has arrived.

Interpals

Interpals Pen Pals is one of the largest and most popular pen pal websites in the world. The website was created in 1998 as the International Penpal Page. The page was so popular that it was redesigned and recreated in 1999 as Interpals. One of the primary goals of Interpals is to help people find pen pals and friends from all over the world. The site is free to join. The sponsors and advertisers pay for the site.

Users are able to find pen pals from all over the world. To use the site, you first need to register for a free account. To do this, go to Interpals (see Resources below), click the « Register » link, and enter your name and a valid email address. You must be at least 13 to register. A confirmation will be sent to your email address. You will need to click on the link in the email in order to confirm your account. You will also need to agree to the site’s terms of service.
Everyone who registers for the site has access to a message box, which is an online mailbox through the site. If you find a pen pal you would like to connect with, you can send them a message. Likewise, if someone wants to contact you, they can send you a message through your message box. Everyone also gets a « wall », in which public messages can be left for friends and pen pals
Be aware of scams. Don’t respond to anyone who makes you uncomfortable. Report anyone who posts linappropriate material to the site administrators. If the site is used properly, you can find long-lasting friendships and interesting pen pals.

why it is not easy for decentralized social networks

A New Kid on the Block

Conditions for a Successful Market Entry of Decentralized Social Networks

 

diaspora, hubzilla, gnusocial

Friendica 3.2 Release

Friendica team is proud to present Friendica 3.2, the new version of our Personal Federated Communication Server.
What's new:

 

  •  Friendica now is licensed under the terms of AGPL
  • Import/Export user account
  • New and updated themes
  • Better handling of statusnet discussion threads
  • Support Open Graph and Dublin Core when showing single items
  • Updated communication with Diaspora
  • Use APC if present
  • Improved installation script
  • Improved administration panels
  • Improvements to SQL queries
  • Improvements to search function
  • Bug fixes:  #516, #517, #525, #476, #540, #546, #712, #728

More in changelist.txt ( https://github.com/friendica/friendica/blob/3.2/changelist.txt )

How to update:
If you installed Friendica via git, simply pull from our repo ( https://github.com/friendica/friendica/ )
If you installed Friendica uploading files via FTP, download last version ( https://github.com/friendica/friendica/archive/3.2.zip ) and upload it to your server, overwriting old files.

Friendica Red – help us

My name is Mike Macgirvin. I am a software developer.

I'll get to the point.  Help us save the web.

Getting Facebook (and Google) out of our private lives is the most important technical challenge facing the web in this generation. We MUST do this, as the grip of control is reaching further and further where it doesn't belong - and the implications for the future are positively scary for humanity.

The way we must do this is to take back our personal and social communications.

I'VE ALREADY DONE THIS. I started a project two years ago to provide decentralised and distributed social communications. That project is now called Friendica. The project website is at http://friendica.com and code is at  https://github.com/friendica/friendica.

Friendica WORKS today (unlike similar projects which are still struggling at basic communications after two years, and after squandering huge amounts of money). Along the way I've asked people what they needed, I've listened to the community, and we've built an entire open development eco-system around Friendica.

It's time to take it to the next level. In order to do this, I need to devote full time to it and be able to hire a competent visual designer to help implement the vision.  The new project is called simply "Red".  Red is a social network - but at the same time it is unlike any social network that has ever existed.

Like Friendica, it can do anything that Facebook can do - except monitor, and track, and "use" all its members and their activities for marketing.

Like Friendica, Red is a completely open platform that is decentralised and distributed and will run on commodity servers, with all servers treated as equals. Like Friendica it is extensible via themes and plugins/addons. Like Friendica it will be the only distributed social service which offers strong (and non-intrusive) permission control for profiles, web pages, and photos.

But we're going a LOT further than that.

Here's what we're doing...

1. We're changing the out-dated concept of "friends" vs. "not friends".  Relationships in the real world are a continuum between "intimacy" and "total strangers". How we relate to individuals and what we share with them depends on where they fit in that spectrum. This spectrum is built into the Red experience.

2. The distributed social web suffers from the adage "only geeks run servers". We're going to change that. We've got a business model. We will get organisations and individuals to provide enough servers to support everybody on the planet because there's a profit motive. Many sites will offer free service, some will charge for extra features, such as huge numbers of friends and additional photo space. Subscription revenue will pay for running the hardware. Geeks can also run their own servers for family/friends and get it all for free.  The ability to obtain revenue and monetise the service will be built-in to the software. Whether you choose to use it is a personal (or business) choice.

Advertising on the web has gotten us into this situation. To get out of it, we have to draw a line in the sand. No advertising. No monitoring and no tracking. Our credo and reason for existence is that our customers are YOU and your PRIVACY is what we are being paid to protect.  Period.

3. We already know from building decentralised social systems that sites come and go and people move to other servers. We're building MOBILITY into the Red protocols.  You'll download your private key and address book to a thumb drive and be able to  communicate from any device or desktop, through any Red server on the planet - privately, to all your friends and associates. If you can still connect to your old server, we can get everything we need from there and you don't need to download it. Sure, you will also be able to save your posts and photo albums, but what we discovered in practice is that the most important thing about moving between server hubs is the ability to preserve your relationships.  You can pop up at any Red site at any time and still have all your friends.

4. The other thing we learned from Friendica is that one "interface" does not make everybody happy. Neither does one set of features. So along with the Red "look and feel", we are completely revamping the "theme" system to make it easy to build additional applications on top of our decentralised communications infrastructure. You can have dating sites, church social clubs, learning centers and more. You can have desktop apps and mobile/pad apps and web apps. These are all just templates you apply to our/(your) social framework. Also, these can either connect with the rest of the Red "grid", or they can be standalone and offer completely different functionality. Secure and private social communications are provided by a back-end engine, and we'll provide tools so you can build anything you wish on top of it.  We have an existing API which is already compatible with a few dozen third-party clients. We will be adding to this to provide access to our full range of privacy features.

I'm building Red today. I'm also heavily involved in Friendica and keeping it running smoothly.  But look - reality bites some times. I'm a family guy holding a day job. There isn't enough time in the day to pull this off. Everybody developing Friendica is/are volunteers.  The work ahead is monumental. If I'm doing this part time it's going to take 2-3 years.

So I'm looking for crowd funding to allow me to work on this full time. I'm a good project developer, but I also require the assistance of at least one good visual designer who can transform these ideas into a slick web interface. Visual design is something you have or you don't have, and I don't have it - so I need help.

I'd like to fund this project for my own salary and one designer and one capable server for one year - and I believe that by the end of that time we will have the means to be self-sustaining. If I can hire a couple of other people to help out, it will happen quicker. Time is of the essence. We're rapidly losing control of the web to the forces of darkness.

Everything we do is and will be published openly and you can track our progress.

I will be working with one or two crowd sourcing applications to launch an official campaign, but you can donate today - just PayPal mike@macgirvin.com. Alternatively if you do not wish to use PayPal, you can use Xoom.com: mike@macgirvin.com, or Flattr: Friendica --- and send this to a friend or three and help me get the word out.

Help us save the web.

Thank you.

Mike Macgirvin

How to install Hubzilla on Dreamhost

You can have the documentation on how to install Hubzilla on every hub. Example https://hubzilla.site/help/install You can just type /help/install

Here is a step by step tutorial how to install a hubzilla for your group, family or simply for yourself on Dreamhost. Dreamhost allow it even on the share hosting. If you don’t have an account on Dreamhost you can have $50 off if you click here

 

You can install hubzilla on a domaine or subdomaine. For this example let’s install on hub.supername.com You should create the subdomaine  and a database (note the name, the hostname of the database and the password)

 

How to install hubzilla with SSH

If you know ssh and linux command line, this solution is the best for you.

ssh user@serveur

type the ssh password

#go to the directory who has the same name as your subdomaine

cd hub.supername.com

#net step git don’t forget the point .

git clone https://github.com/redmatrix/hubzilla.git .

mkdir -p « store/[data]/smarty3 »

chmod -R 777 store

util/add_addon_repo https://github.com/redmatrix/hubzilla-addons.git hzaddons

 

The hardest part is done

Then go with a browser at the url of your site

First screen is to check if all prerequisit is ok on Dreamhost all is fine

Second screen : enter your mysql host, mysql user, password of the user and name of the database

third screen : email of the admin and the time zone

 

congratulation you installed your hubzilla successfuly

 

the last part is to create a cron task. With Dreamhost it is easy. go to your admin panel at dreamhost. Menu Goodies > cronjob

put

cd /home/username/hubzillasubdomain; /usr/local/php54/bin/php include/poller.php

on the cron job

Your server is ready. Use your administration email first. With this account you will be allowed to administrate your hubzilla

 

 

 

 

 

 

Hubzilla on wikipedia

As it is apparently hard to create a new page on wikipedia, here is the draft version of hubzilla page. A draft could be deleted and as this page is not bad and could be copy just in case.

https://en.wikipedia.org/wiki/Draft:Hubzilla

Hubzilla (formerly known as Redmatrix) is a community management platform that is designed to mesh with other instances running the same software. It is considered a platform for federated networking, and is compatible with both Diaspora and Friendica. Hubzilla is notable for combining aspects of social networking, blogging, forums, cloud storage and content management all into one application.

Hubzilla
Original author(s) Mike Macgirvin
Developer(s) Hubzilla community
Stable release 1.3. / March 2016
Written in PHP
Operating system Cross-platform
Platform Apache, Nginx
Type community management platform
License MIT License
Website [1]

 

Development History

In 2012, Mike Macgirvin of the Friendica project stepped down[1], and formed an experimental communication platform named Friendica Red. This system existed for exploratory purposes, and was designed based on lessons learned from developing Friendica.

Much of the design concepts for the new platform would be based on ideas about user identity management and privacy permissions. It leverages a unique federation protocol named Zot, which acts as the design successor to Friendica’s DFRN protocol.

As time went on, Friendica Red was rebranded RedMatrix, before the name Hubzilla was decided on. On December 24th, 2015, Hubzilla 1.0 was officially launched[2].

Features

Hubzilla can be defined as a decentralized communication and publishing platform. Any server running Hubzilla is defined as a hub, which can function independently of any other hub in the network.

Channels

Channels are a core concept for the platform – in short, each channel is an activity stream of objects that can represent a specific action, such as a posting a status or uploading a photo. This stream can show both public and private activities, and an ACL permissions system determines which users can access a given entry. Each channel also contains a unique Webfinger address, for example https://example.com/channel/bob would be represented as bob@example.com

A Channel can be created for the following use-cases:

  • A Social Stream
  • Blogging
  • Branded Product Streams
  • Group Forums

A user is assigned their first channel upon registration, but they can create as many different channels as their hub allows. Each channel in turn can connect to another channel as a contact. This mechanism will allow a user to interact with posts, as well as post on the wall of other channels as themselves. Private messages and statuses can also be passed back-and-forth from one connected channel to another.

MagicAuth

MagicAuth is a type of in-browser encryption that grants access permissions on remote hubs. In a sense, it is a workaround to a long-standing problem in federated social networks: ordinarily, users couldn’t visit each other’s profiles and directly interact with them if both people are connected through different servers. MagicAuth exists as a means of granting access permissions to visiting users. The use-case works like so:

  1. Bob’s channel is on https://example.com/channel/bob, with the channel address of bob@example.com
  2. Bob visits Alice’s channel at https://othersite.com/channel/alice, ie, alice@othersite.com
  3. When Bob visits, his browser session performs a cryptographic handshake with Alice’s channel
  4. Bob is allowed to comment and like posts on Alice’s channel while he is visiting.
  5. Bob will also see private posts meant for him when visiting.
  6. If Alice allows people to make posts on her wall, Bob will be able to do that as well.

Cloud Storage

By default, each channel is given DAV access for file storage. This storage includes uploaded photo albums, and can allow for videos and other documents. Cloud storage can be accessed through a DAV client, and in some instances be integrated into the desktop file manager itself.

Web Pages

Channels are allowed to create web pages based on a templating system.

Directories

Themes and Layouts

Plugins

OpenID

Hubzilla can also function as an OpenID provider, allowing users to log into OpenID-enabled sites with their Hubzilla channels.

See also

References

 

 

  1. Macgirvin, Mike. « Hubzilla (1.0) release ».

External links

The first web site

Do you know the first web site of the world.  It was http://info.cern.ch In Switzerland

Even today you can browse it as it was in 1991.

 

 

Hubzilla 1.3 released

hubzillaWe are please to announce the immediate availability of Hubzilla Community Server V1.3, our web software for building and linking decentralised community websites. The current release is building on our momentum to provide a much more configurable and adaptable platform for creating and linking website communities of all sizes and descriptions while providing autonomous privacy controls for all web resources.

The highlights are
1) ability to attach metadata to more stored resources which allows new types of plugins/addons to be created,
2) radically simplified setup and operation provided by the « Hubzilla UNO » configuration, and
3) continued work on the web interface to provide a pleasant and smooth flowing experience.

Please find out more about the project at http://hubzilla.org or visit our project page at https://github.com/redmatrix/hubzilla .

Summary of changes in this release:

Admin Security configuration page created which consolidates several previously hidden settings:
Communication white/black lists
Channel white/black lists
OEmbed white/black lists
Admin Profile Fields page created which manages the availability and order of standard profile fields and allows new fields to be created/managed
Allow guest/visitor access to view personal calendar
« Poke » module reworked – page UI updated and « poke basic » setting introduced which limits the available poke « verbs ».
« Mood » module UI reworked
« profile_photo » module UI reworked
« cover_photo » module UI reworked
« new_channel » module UI reworked
« register » module UI reworked
« pubsites » module UI reworked
item-meta (« iconfig ») created which implements arbitrary storage for item metadata for plugins
abook-meta (« abconfig ») created which implements arbitrary storage for connection metadata for plugins
« Strict transport security header » made optional as it conflicts with some existing Apache/nginx configurations
« Hubzilla UNO » (Hubzilla with radically simplified and locked site settings) implemented as an install configuration.
.well-known directory conflict worked out to support LetsEncrypt cert ownership checks without disrupting webfinger and other internal uses of .well-known
Lots of work on ‘zcards’ which are self-contained HTML representations of a channel including cover photos, profile photos, and some text information
Long standing bug uncovered which failed to properly restrict the lower time limit for public feed requests
A number of fixes to « readmore » to fix page jumping
Bugfix: persons other than the channel owner who have permission to upload photos to a channel could not do so if the js_upload plugin/addon was enabled
Siteinfo incorrectly identifying secondary directory servers
Allow admin to set and lock features when UNO is configured
Atom feeds: alter how events are formatted to be compatible with GNU-social
Moved several more classes to « composer format » and provided an autoloader.
Bugfix: require existing password to change password
Bugfix: allow relative_date() to be translated to Polish which has more than two plural forms.
Plugin API: add « requires » keyword to module header to indicate dependent addons
ActivityStreams improvements and cleanup: photo and file activities
UI cleanup for editing profile when multiple profiles enabled
Removed the « markdown » feature as there are numerous issues and no maintainer.
Provide « footer » bbcode to ease theming of post footer content
Bugfix: install issues caused by composer code refactor and typo in postgres load file

Plugins:
keepout – « block public on steroids »
pubsubhubbub – provides PuSH support to Atom feeds, required for GNU-social federation
GNUsocial protocol – under development
Diaspora protocol – some work to ease migration to the new signing format
Diaspost – disabled; numerous issues and no maintainer
smileybutton – theme work and fixed compatibility with other jot-tools plugins

 

more information

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.

Hubzilla 1.2 Community Server released.

http://hubzilla.org
https://github.com/redmatrix/hubzilla

CHANGES from 1.1:

Provide extra HTTP security headers (several of them).
Allow a site to disable delivery reports if disk space is limited
Regression: Wrong theme when viewing single post as non-member
Some Diaspora profile photos use relative URLs – force absolute
Add locked features to siteinfo report to aid remote debugging
Provide version compatibility checking to plugins (minversion, maxversion, and minphpversion)
Account config storage
Provide optional integrated registration and channel create form
cli utility for managing addons
issue with sharing photo « items »
cover photo manager: upload, crop, and store
cover photo widget created
rework the connections list page and provide a few management features there
fixed issue with Comanche layout definitions loaded by plugins
provide ability to separate delivery functions from item_store() and item_store_update() – some forum messages were being redelivered when cloned.
call build_sync_packet() on pdledit changes
Abstract the project name and version so these can be customised or removed
Allow hiding the ratings links on a per-site basis
db_type not present in international setup templates – was unable to choose postgres.
item_photo_menu logically divided into a) actions on the post, b) actions related to the author
bug: default channel not reset to 0 when last channel removed
create widget containing only the contact block
regression: public forums granted send stream permissions to connections
workaround Firefox’s refusal to honour disabling autocomplete of passwords
regression: photo’s uploaded to a channel by a guest (with file write permissions) not saved correctly.
provide mechanisms for custom .well-known handlers (needed for LetsEncrypt ownership verification)
proc_run modified to use exec() instead of proc_open() – causing issues on some PHP installations
remote delegation failure under a specific set of circumstances which we were finally able to duplicate
Delegation section of Channel Manager was missing names and contained useless notification icons.
Change « expire » channel setting to show system limit if there is one.
Regression: provide a one-click ignore of pending connection
Config to control directory keyword generation on client and server.
« Collections » renamed to « Privacy Groups », documentation improved
widget_item – allow use of page title instead of message id
Add site black/white list checking to all .well-known services
reduce incidents of screen jumping when « showmore » is activated
add oembed provider for photos

Addons:

CSS theming of pageheader plugin
xmpp addon ported from Friendica
Diaspora private mail issues after the third reply
Occasional issue with Diaspora connection requests
Add notification email to Diaspora PMs
Allow anonymising platform and version for statistics
msgfooter addon created
removed embedly plugin
sync clones after superblock addition
« keepout » plugin created

source

how to update friendica with ssh

here is a new version on how to update your friendica
we assume you have acces with ssh to your serveur

With filezila rename your directory where you have your friendica to friendiold
make a new directory name it friendi but you can choose the name you want
run the commands bellow you can copy past it

cd friendi
git clone https://github.com/friendica/friendica .
git clone https://github.com/friendica/friendica-addons.git addon

copy the old .htconfig.php from the old directory to the new one. It is done

Friendica 3.4.3-2 has been released

There were recently changes in the Dias­pora* pro­to­col which dis­turbed the fed­er­ated com­mu­ni­ca­tion between the projects. To com­pen­sate the changes Frien­dica 3.4.32 has been released

How to Update?

If you have an instal­la­tion using the git repos­i­tory directly, all you have to do is a git pull in the frien­dica direc­tory. That will fetch the new ver­sion from the mas­ter branch and you are ready to go. The devel­op­ment branch of Frien­dica 3.5 Aspara­gus, has been updated as well.

Alter­na­tively you can find a zip file of the released ver­sion of frien­dica at github​.com for down­load. Just unzip it on your local machine and replace the files on your server with the new files.

Why the number of hubzilla channels is growing so slowly ?

You have 2 sites that show the growing of hubzilla 1 . http://hubchart.hubzilla.it/ and the-federation.info. Here is the graphic of hubchart who show that less than 900 channels are active on hubzilla. This is not growing anymore but very stable. The other site the.federation.info is more the federation. it shows hub/pod for diaspora, friendica and hubzilla.

20160123

 

Hubzilla is a fantastic tool for community communication. It has lot of features and we can do lot of things. But there is no massive adoption. After the publication of version 1, some blog posts was publish and few testers subscribe. But something is missing.

 

Why it is so difficult to attract users ? That is a real question. I don’t have easy answer but just hypotheses. If you have other hypotheses I would be happy to know your ideas. How to attracts users ?

 

Here is some of my ideas but only few explications. Maybe we could work on these directions.

  • First Hubzilla is not known. People don’t know it. We must write articles about hubzilla and make it known.
  • Hubzilla is complicated. Exept few developpers and early adopters who are experts and love it, most people don’t understand fully what is hubzilla. For them it is a kind of social network like diaspora. They don’t understand what is the nomadic identity and what is the advantage of hubzilla. Furthermore if we use it, you can find so many parameters and settings, too many. You can easily get lost in the settings.
  • Ergonomy is better but should be improved. People don’t have to read documentation to use it. If you ask a question and someone reply : read the documentation, you got the wrong answer. Documentation is important but should not be mandatory for basic users.
  • Virality. That is the main point. If a user is happy he should talk to everybody. Hey come with me and use this wonderfull software !!!! What is missing to improve the virality of Hubzilla ?
  • Fidelity. You try and you stay, you test and you adopt. Personaly at the begining I force myself to try hubzilla. I felt lost. But after a period, now I am kind of addicted. But the effort to get addicted was hight. User should feel well after the first try and return. If we improve simplicity and ergonomy it would be easier for adoption.
  • Network effect and invitation process. You can use hubzilla like a blog but most of people use it like a discussion platform, like a forum or social network. If you find people with the same interest it is easier. If your blog get comment it encourage you and write more posts. If you read interesting contents you come back more often. Additionaly if you know real friends here you return. Why facebook is so popular just because you know people. You invite people who know and you are invited by people who know. In hubzilla the invitation process is too basic and too hard to use.

 

Now I would like to propose few directions. I know developpers are all volonteers and give free times to hubzilla. But adoption of hubzilla is not only the work of developpers and even more hub administrators but this is a job for all. We can all write about hubzilla everywhere. More you write about it more it will be known. This is the evangelism.

But I am conviced that hub administrator have the main role for that. Each community have an administrator and even moderator. His role is really important. The adoption of hubzilla has no means. But the adoption of specific hub is different. Each hub should have specificity. I mean public hubs. You can compare a hub at forums. Do you remember phpbb. If you launch a forum and do nothing, no body will come. But if you define the subject, and invite people and try to put a content inside that will attract people. Exemple forum about astronomy. You can invite all passionate people. With hubzilla you can do that. Create public forums private forums and invite people passionate whit it. General hubs is nice but specific hubs are better. When people have one zot account they don’t have to have a second one for football forums for exemple or private discussion with family etc… Each administrator should makes the effort of attracting people, they should explain the advantages.

Administrators are the key users between members and developpers. They should be empathetic and understand how users feels and what they needs. They should have idea how to improve simplicity, ergonomy., virality and fidelity. Sometimes one little things and do huge difference.

 

why it is not easy for decentralized social networks

A New Kid on the Block

Conditions for a Successful Market Entry of Decentralized Social Networks

 

diaspora, hubzilla, gnusocial

Articles plus anciens «

» Articles plus récents