Comment ajouter un contact diaspora sur friendica

Tout d’abord, il faut que le serveur friendica puisse communiquer avec diaspora. Si vous êtes administrateur, vous devez aller dans l’administration de votre site puis cliquer sur site et chercher le paramétre “Activer le support de Diaspora”. Il doit être activé.



Une fois ceci activé ou contrôlé, nous allons ajouter un contact diaspora. Diaspora a eu la bonne idée d’afficher sur le profile l’identifiant. Il ressemble à un email. utilisateur@pod. Vous copier donc cet identifiant et vous le collez dans friendica. Pour cela allez dans vos contacts. Et dans la champ “Ajouter un nouveau contact” collez l’identifiant diaspora.



Voila vous allez pouvoir suivre les contacts diaspora depuis friendica.

Comment enlever l’information langue sur les posts

Sur certains thème par exemple vier, une information langue s’affiche. Le problème c’est que c’est inutile.

Pour l’enlever il faut ajouter une ligne dans le fichier .htconfig.php

$a->config[‘system’][‘suppress_language’] = true;


How to create a community with Hubzilla?


Your home based on the free network

Sometimes we start a post with How, we have the answer and sometimes when it is a real question. That has been always a dilem. When you are looking for information you can ask your search engine a question and you expect finding an answer but sometime you find a question.

As I read the vision of Mike the creator of Hubzilla, I understand that he want to propose a tool that helps us to create community. That goad is excellent and I agree. If community is able to communicate together that is a plus. But now let’s concentrate on community.

Community is a niche market, you don’t target all people but only specific motivated people. I am just asking myself and hubzilla creators and developpers how to do that.For exemple you can create a community arount football, ecology, politics, religion or a hobby.

  • First you need to informe that this community exists.

That communication is public. You need to tell the world that every body whith specific interest is welcome in this community. How are you going to make it. You need to create a nice attractive webpage that explain the rules and the benefit of this community. That could be done quite easily but I am not sure how with hubzilla.

  • Second you need to select members.

That point is my problem if I refer to redmatrix. Redmatrix had only public community or private one. Both kind of community has it’s problem. Public community could be flooded with spammers and the moderator would have lot of problems deleting mass creation accounts. Even real account created by human been manualy should be in the specific interest. At the opposite if you close registration how would you send invitation ? You must know people first, then send invitation then how invitation creation works ? That part should be polished and easy. You don’t need to be a geek to understand how things works. That should be obvious.

My idea. I remember long ago was ning. I remember how easy it was to create a community and how easy it was to select members with a precreation questionnaire form. Or many Mike has an other idea. I would like to know how. I am just wondering how hubzilla will face that aspect of the fantastic tool.



Hubzilla how to stop following a channel

Hubzilla is a powerful platform for creating interconnected websites featuring a decentralized identity, communications, and permissions framework built using common webserver technology.

In this post we will see how to manage connections or contacts. Hubzilla could be not easy to understand because it has lot of fonctionalities. Members has so many options that it could be lost.

Facebook has an easy way to understand because contact have bidirectional relationship.

Twitter and google + have only one directional relationship. I can follow someone or not.

Hubzilla go fearther. it has fine tuning options that let member at the control. You can decide for each connection what you give for permission.

First when you want to have interaction with ‘someone’ (a chanel) you have to add it at the connexions list at the “Enter the channel address“. You can add either by or by url. You can enter diaspora contact with the same way. (take care of the option that is not selected by default)

Then the new relation receive a relation request. It can accept or refuse.
That is nice for selection relation. If you create a hub for your family for exemple you will accept only your family members.

But now how to manage relations. If you accept at the begining many relations you will be quickly floded by messages on your wall. So you will be able to select people you will follow or not.

Go to the arrow on each post and select Edit connection.


Then Individual Permissions

Then unckeck Can send me private mail messages.


That means that you will not receive this channel anymore, but he will be able to read your posts and comment it.


In the first column their setting we can’t change it is only for information. The relation can change it. We only can change the second column : My setting

In this way you will unfollow a channel without deleting it. It sill have the possibility to read you and comment your post (if the

EdgeRank and Content Filtering

Facebook has gotten a lot of press recently over its "EdgeRank" feature. This is basically a filter that sits between you and your friends. Facebook decides what to allow through the filter so that you can see it.  Current estimates are that you only see about 15% of the posts made by your friends. How and why they do this are interesting topics. It seems mostly to be a way to get advertisers to pay more money to get in your face. There's also a claim that seeing all posts and activities would quickly get tedious and therefore you should only be able to see stuff that's "interesting". Since Facebook knows you so well, they're evidently able to decide without a doubt what you'll find "interesting". They don't need to ask you. 

Regardless, wasn't the point of "social networking" so that you could communicate with your friends? A service which claims to provide this, yet somewhat arbitrarily blocks communication between you and your friends would seem to be an anachronism. It kind of takes the "social" out of "social networking" if you're just sending your posts into space and all your friends are prevented from seeing them.

In a world where you have lots of incoming information streams from lots of different sources, you really do need a way to "cut to the chase" and quickly locate information of relevance. This could be in the form of search tools and the ability to view specific streams from your catalogue - rather than the entire firehose.

Here on the free web, the concept of a communications service deciding what communications to allow is an alien and very strange concept.  We think this should be in your hands, under your control. Actually we think that all your online activities should be under your control - so you don't appear in one of your friends' pages pitching vacation packages and toiletries without your knowledge. 

Friendica lets you decide what and how much to see. We've got lots of different "search modes" on your stream to slice and dice the firehose any way you desire. Our next generation project ("Red") adds an entirely new dimension to this - allowing you to "zoom in and zoom out" from your close friends to your most distant acquaintances dynamically.

Is the free web a good match for you? I can't say. You could ask your friends, but chances are they won't ever see the question.


Until next time, this is Commander Zot - saying over and out.


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.

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


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


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 .
git clone 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 . and 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 is more the federation. it shows hub/pod for diaspora, friendica and hubzilla.



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

Hubzilla 1.1

One month after the version 1.0 a new version comes today.

The bigest change is situated in the administration panel that is improved.

here is the announcement of Mike
Greetings and Happy New Year. The Hubzilla developers are pleased to announce the immediate release of Hubzilla 1.1, our decentralised community platform specialising in cross-domain identity and privacy


Hubzilla 1.1

Rewrote and simplified the Queue manager and delivery system
Rewrote and simplified the outer layers of the Zot protocol
Use a standard version numbering scheme in addition to the snapshot tags
Provide a channel blacklist for blocking channels with abusive or illegal content at the hub level
Make the black/white lists pluggable
Update template library
Support for letsencrypt certs in various places
Cleanup of login and register pages
Better error responses for permission denied on channel file repositories
Disabled the public stream by default for new installs (can be enabled if desired)
Cleanup of API authentication and rework the old OAuth1 stuff
Add API “status with media” support compatible with Twitter and conflicting method for GNU-social
Rework photo ActivityStreams objects to align better with ActivityStreams producers/consumers
Several minor API fixes to work better with AndStatus client
Invitation only site – experimental support added, needs more work
Fix delivery loop condition due to corrupted data which resulted in recursive upstream delivery
Provide more support for external (git) widget collections.
Extend the Queue API to 3rd-party network addons which have experienced downtime recently.
Regression: Inherited permissions were not explicitly set
Regression: “Xyz posted on your wall” notification sent when creating webpages at another channel
Regression: Custom permissions not pre-populated on channel creation with named role.
Provide “Public” string when a post can be made public, instead of “visible to default audience”
Allow hub admin to specify a default role type for the first channel created, reducing complexity
Ability for a hub admin to set feature defaults and lock them, reducing complexity
Change default expiration of delivery reports to 10 days to accomodate sites with reduced

Pageheader addon ported from Friendica
Hubwall (allow admin to send email to all accounts on this hub) created
GNU-social – queueing added
Diaspora – fixes for various failures to update profile photos, updates to queue API
Cross Domain Authenticated Chess (Andrew Manning’s repository)

And… the normal “lots of bugs fixed, translations updated, and documentation improved”

more information …

Debian founder Ian Murdock has died

The founder of Deb Ian distribution Ian Murdock died the 28th of december 2015 at the age of 42. Police Department did not immediately have information on Murdock’s cause of death.
He gave his name to the debian distribution. The word “Debian” was formed as a combination his girlfriend Debra Lynn and his own first. name Ian,

“Ian helped pioneer the notion of a truly open project and community, embracing open design and open contribution; in fact the formative document of the open source movement itself (the Open Source Definition) was originally a Debian position statement,” Docker chief executive Ben Golub wrote in the blog post. “It is a testament to Ian’s commitment to openness and community that there are now more than 1,000 people currently involved in Debian development.”

In Memoriam: Ian Murdock

Friendica 3.4.3 released

we are happy to announce the release of Friendica 3.4.3, the last planed minor release of the Lily of the valley family before the release of Friendica 3.5 in spring 2016. As such version 3.4.3 bundles a couple bug fixes with a number of new features. For the full list, please read the CHANGELOG, but let me highlight some things from the long list.

  • Support to events attendance. Users can mark their participation to an event,
  • Private forums are mentioned automatically like community forums,
  • The UI in the aspects of dealing with contacts was streamlined,
  • The Forumlist widget moved from the addons into the core (you can just disable that addon),
  • Federation with Diaspora* and GNU Social was improved,
  • The API was improved, especially to fix some incompatibilities with the AndStatus clients.
And just a hint, in case you muss the little flag for language settings: have a look into the basic settings of your account, you will find the language settings there from now on.

How to Update?

If you have an installation using the git repository directly, all you have to do is a git pull in the friendica directory and the addons directory. That will fetch the new version from the master branch and you are ready to go. If you want to use the bleeding edge code from the development branch of Friendica 3.5 Asparagus, checkout the develop branch in your repository.

Alternatively you can find a zip file of the released version of friendica at for download. Just unzip it on your local machine and replace the files on your server with the new files.

Friendica at the 32c3

Friendica will be present at the 32nd Chaos Communication Congress (32c3) on Day 2 (that is Monday, December 28) at the Assembly of the FSFE. Have a look at the congress wiki for details on the session. A great opportunity to meet some of the Friendica developers and other users in the real world.

read more

Hubzilla : internet of the future

Looking back on the journey that began nearly six years ago trying to create an open social network which respects your privacy. There were struggles and battles with other projects and egos and companies competing in that space; so we moved the space. Everybody and their uncle is building a social network;
— and 99.9999999% of them will fail.

What we ended up creating is a model for the internet of the future; where passwords are a thing of the past and nobody can own you or your thoughts and ideas, and then sell these as a business model. Where the playing field is level; and privacy is a fundamental right. What we originally focused on – the “social network”, is a miniscule and unimportant part of what we’ve built. It’s just an appliance – because *of course* people communicate. That’s what they do. And *of course* they expect privacy when they wish to be private; and they also expect privacy to just work. And when they wish to shout to “the world”, they expect to be able to do that also.

We may never be wildly successful in any kind of business sense, but in my book we’re already wildly successful. We’ve turned our revolutionary ideas of what the internet “could be” into something that’s real and that you can actually use.

And now we’ve set it free. Hubzilla

Older posts «