le site friendi.ca ne répond plus

Le premier compte friendica que j’avais créé a été sur friendi.ca. Je trouvais l’adresse sympa et facile à retenir. Le problème c’est que le site ne fonctionne plus. Il y a un message

Apologies but this site is unavailable at the moment. Please try again later.

Voici une raison de plus de s’autohéberger ou de chercher un autre site friendi.ca.

An introduction to the protocol that powers Hubzilla

The world is full of protocols. Some are loosely defined by society, and some are rigidly defined by their architects. In many urban environments, for example, there is a protocol for how you ride an escalator: if you choose to stand, you stand on the right side so that those who choose to step can get past on the left. If you ignore this protocol, you may get some annoyed looks but you will still get where you are going. More rigid protocols, such as the hypertext transfer protocol (HTTP) that governs most communication on the web, can be much stricter and more elaborate. If your browser puts one semicolon in the wrong place you can forget about seeing those cute cat videos.

So what does that have to do with Hubzilla? And for that matter, what is Hubzilla anyway? Hubzilla is free and open source software designed to support your freedom and privacy; anyone can run it on their own server and inspect the code to learn how it works. It is an advanced platform for online communications and content publishing that provides decentralized access control. That last bit is the critical difference between Hubzilla and all the other blogging platforms, social networking sites, and messaging systems that dominate the web today, and it is precisely the motivation for inventing Zot instead of choosing from the plethora of existing communication protocols. To appreciate what is so innovative about Zot, we need to explain first what « access control » means and then why « decentralized » makes the problem of access control challenging.

Like protocols, the world has no shortage of access control. Does your house have locks on the doors? Do you let everyone watch you take a shower, or do you prefer to control access to that activity? How about conversations about your finances? I bet you publish those on billboards, right? Of course not! We all constantly control access to things for many reasons.

And sometimes you want to have a private conversation with someone that no one else should read.

Electronic publications and communications are no different. You may want to publish an article like this one for the whole world to read, but you may also want to participate in a restricted access forum online where members of your neighborhood can discuss community issues. And sometimes you want to have a private conversation with someone that no one else should read.

The traditional centralized solutions to these problems have existed for many years and are what virtually everyone currently uses online. This is because it is relatively easy to manage access control when you have one central authority acting as the gatekeeper to content. Facebook is the most influential example of this model. If you send a message to a select group of friends, only they have access to it because Facebook (1) authenticates them by identifying who they are based on their knowledge of their secret account password and (2) authorizes them to access the message by verifying that they are on the message’s access control list (ACL), which is the technical term for what you created when you « sent » them the message.

There are several fundamental and serious problems with this centralized model. Arguably the biggest problem is that you do not own your identity. But that’s absurd, you might immediately retort, of course I own my identity! Well, let’s consider what ownership means. Ownership of identity means, for one thing, control. If you own your identity, you control it somehow. With Facebook and similar centralized services, they alone have the power to create and delete your online identity. They grant you access to your identity when you log in. As the years roll by and you share all sorts of content with all the people you have connected with, you may be alarmed to discovered that you need the centralized service. If you want to leave, all of that shared content and all those connections vaporize. What’s worse, you can’t even share something privately with people unless they also allow their identities to become hostage to the platform. It’s like some kind of pyramid scheme.

They grant you access to your identity when you log in.

Now we can begin to appreciate some of the benefits of decentralization in our online communications. When you register an account on a “hub” — a server running Hubzilla — you can make connections with other people and share things even when they are on completely independent hubs operated by different companies or organizations. This is the essence of what it means when we say Hubzilla is a decentralized network. We like to call the network of Hubzilla-powered websites “the grid”. There is no single entity that controls the network or, by extension, you. It is ironic that this needs explanation, because the most ubiquitous and long-lasting online communication system — email — is a shining example of decentralization. Anyone can run an email server and exchange emails with other people, even if they are using an email server hosted by a separate business or university. As robust as email has been historically, however, it lacks a lot of capabilities that we want in modern communication. It is designed for passing small messages back and forth; it is not designed for controlling access to published content hosted on a modern website using secure encryption methods. This is what Hubzilla is designed to do. Hubzilla lets you do things like share photos privately with only your family and friends, or publish news articles only to paying subscribers, even if none of these people have an account on the server hosting the content.

What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity.

To be clear, providing decentralized access control is an impressive feat per se. There are only a few other platforms available that provide this capability on the « standard » internet of websites accessible by browsers over HTTP. What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity. Truly owning your online identity means that you maintain your contacts and access to the things people have shared with you even if you change accounts on different servers. It means that you can have clones of your identity on independent hubs allowing you to maintain your online presence and continue communicating even when one of your servers is unavailable (temporarily or permanently). No other platform provides this level of robust identity ownership.

Visit http://hubzilla.org to learn more about what Hubzilla can do for you…

Sortie de friendica 3.2

L’équipe Friendica est fier de vous présenter Friendica 3.2, la nouvelle version de votre serveur de communication fédéré personnel.

Voici les nouveautés :

– Friendica est maintenant sous license AGPL

– Import / export de compte utilisateur

– Amélioration des thèmes

– Meilleure gestion des fils de discussion StatusNet

– Support de Open Graph et Dublin Core

– Mise à jour des communication avec Diaspora

– Utilisation de APC si il est présent

– Amélioration de l’installateur

– Amélioration de l’administration- Amélioration de la performance en optimisant des requètes

– Amélioration de la recherche

Correction des bugd

Plus de détails sur  https://github.com/friendica/friendica/blob/3.2/changelist.txt

Comment mettre à jour :

Simplement copier par FTP les sources en écrasant les anciens.
Télécharger la version friendica 3.2 https://github.com/friendica/friendica/archive/3.2.zip

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

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.

PeerTube 1.4 is out!

Peertube 1.4 just came out! Here’s a quick overview of what’s new…

Plug-in system

Since PeerTube’s launch, we have been aware that every administrator and user wishes to see the software fulfill their needs. As Framasoft cannot and will not develop every feature that could be hoped for, we have from the start of the project planned on creating a plug-in system.

We are pleased to announce that the foundation stones of this system have been laid in this 1.4 release! It might be very basic for now, but we plan on improving it bit by bit in Peertube’s future releases.

Now, this system allows each administrator to create specific plug-ins depending on their needs. They may install extensions created by other people on their instance as well. For example, it is now possible to install community created graphical themes to change the instance visual interface.

A better interface

We strive to improve PeerTube’s interface by collecting users’ opinions so that we know what is causing them trouble (in terms of understanding and usability for example). Even though this is a time-consuming undertaking, this new release already offers you a few modifications.

First of all, we realized that most people who discover PeerTube have a hard time understanding the difference between a channel and an account. Indeed, on others video broadcasting services (such as YouTube) these two things are pretty much the same.

However, on PeerTube each account is linked to one or multiple channels that can be named as the users sees fit. You also have to create at least one channel when creating an account. Once the channels have been created, users can upload videos to each channel to organize their contents (for example, you could have a channel about cooking and another one about biking).

Our wonderful community of translators is once again to thank for their work, after they enriched PeerTube with 3 new languages: Finnish, Greek and Scottish Gaelic, making PeerTube now available in 22 languages.

We also added a new feature allowing you to upload an audio file directly to PeerTube: the software will automatically create a video from the audio file. This much awaited for feature should make life easier for music makers 🙂

Last information : peertube has an official information channel : @peertube@framapiaf.org

More information about Peertube

4 Major Protocols for federated social web

Mike Macgirvin explain what is a computer protocol and why multi-protocol systems can’t really evolve.

« A computer protocol is a language. If two or more computers use the same protocol they can theoretically communicate. Like human languages, these protocols have limitations and the things which can be expressed using that protocol only include concepts that are present in the culture which created it.

For instance in Latin, all objects have gender. In English they do not. You can’t create a perfect mapping between the two unless you know the gender of all objects – and English speakers will not know this.

This is the reason why multi-protocol systems can’t really evolve – unless each and every component protocol evolves. The multi-protocol system needs to embody those things in common amongst all of its components. You can’t just add a feature unless it is supported by each and every underlying protocol. We’ve tried. This just leads to confusion.

It is also the reason why some protocols are inadequate for different use cases. A protocol designed around Twitter interactions cannot express the same concepts as one that was designed around Facebook interactions – and vice versa. They come from different cultures and have entirely different uses and expectations. Twitter is a soapbox platform. Facebook is more of a conversational platform. They can’t be made to look and act the same because they aren’t the same.

Then you have protocols that were built around cultures that aren’t even formally recognised yet. In this case freedom and privacy loving Facebook refugees who want to be decentralised but not bound to individual servers.

ActivityPub may solve the second part eventually and provide nomadic identity, but it’s still a Twitter interaction because that is the culture which created it. Ditto for permissions and spam prevention and abuse. That protocol is derived from a culture where privacy and permission didn’t even exist and people depend on their site owner to make them safe. This safety vanishes in a nomadic world and other mechanisms are needed. The precise mechanisms needed by the former are completely different than the mechanisms required by the latter.

Because it is a different culture.

We currently have at least four separate (major) cultures present in the so-called fediverse and they all use different protocols for a reason. Those protocols reflect the cultures which spawned them and fulfill the needs and desires of those communities. It’s time to stop pretending they can be reconciled.

The 4 major protocols are Ostatus, ActivityPub, Diaspora, and Zot. « 


How to comment a peertube video from a mastodon account?

Peertube is a wonderfull video plateform. You can comment any video from any peertube instance if you have a Mastodon or Pleroma account. It should work theoreticaly with any compatible ActivityPub Account.

Go to the video you want to comment. Here is an example.


Do not try to comment from this page, if you don’t have a peertube account. It is complicated. But go to your Mastodon account.

  1. Copy the url of the peertube video
  2. In your Mastodon account paste it in the search box

3. Write your comment

Now see the video page of peertube

Osada resurrected

Osada is a full featured social network application running under the ActivityPub protocol. It also communicates with and inter-operates with servers on the Zot6 network (such as Zap and Hubzilla 4.x). Due to limitations in the ActivityPub protocol, Osada does **not** offer nomadic identity or enhanced privacy modes.

Osada was created originally by Mike Macgirvin, the force behind Friendica, RedMatrix, Hubzilla, and Zap. Mike is the quintessential mad scientist and possibly a visitor from the future: I’m still uncertain. Many of his ideas have proven to be years ahead of their time. This project was abandoned in early 2019 so Mike could devote all of his efforts towards advanced social network technologies – in particular Zap. With Mike’s permission the stewardship has been take of the codebase to provide an ActivityPub project with some of the more advanced features made possible by the Zot6 and OpenWebAuth protocols.

Osada has a new repository talke care https://gitlab.com/apfed/osada

Osada is abandoned

6 month after his launch. The project Osada is abandoned by his creator.

Osada will be spun off (separated from Zap) and officially abandoned. If you want to take over the project, go for it. The implementation of Zot6 there is now frozen because future Zot6 work (and Zot8 – more on that in a moment) will not be compatible with ActivityPub. At all. As far as I know Osada is the only viable ActivityPub server for events and groups, but Friendica and Hubzilla aren’t very far off.

For those of you who don’t remember, Osada was a new platform with a UI reminiscent of Hubzilla that was specifically developed to support both Zot6 and ActivityPub-based networks. Macgirvin seems to indicate, in hindsight, that this was a mistake.

Zotiverse in january 2019

Zotiverse is a new word. It is the univesere that use zot protocole. : Hubzilla – Osada – Zap. Zot is much more powerfull than ActivityPub. It allow higher degree of security and anonity. But the best of zot is the nomadic identity.

Hubzilla is the most established product. It should be considered more of an « application platform » or maybe a « publication platform » (kind of like what WordPress has become since it now has plugins that allow you to do almost anything – it’s more than a Content Management System). « Social Media » on Hubzilla was one of the first use-cases adopted by a large number of people – and so many think it is primarily a social media platform. It is not. It is a privacy and security aware application platform that can support a huge number of use cases through the plugin/addon architecture which is lean and efficient.

Osada is more intended for end users interested specifically in Social Media applications that want to be able to communicate with ActivityPub but also have SOME of the privacy and security capabilities offered by Hubzilla. ActivityPub has a larger user base but is fundamentally incompatible with certain privacy and security models. So, anything related to ActivityPub is going to be a compromise. Osada is a social media platform that brings as much of the privacy and security features of Hubzilla as is possible while still providing integration with ActivityPub

Zap is a social media platform for those who are privacy and security minded and are not willing to compromise privacy and security just because « everybody is doing it. » It has the full range of privacy, security, and censorship resistant features inherent in the Zot protocol as Hubzilla (without Federation addons).

If you are an « end-user » of social media and want to be able to seamlessly communicate with ActivityPub, you want to use Osada. If privacy, security, and censorship resistance is important to you and you’re willing to give up access to other protocols in order to maintain those things, you probably want Zap. If you are primarily interested in providing content and data to others on an extensible and robust manner with privacy, security, and with built in ability to provide redundancy in case of failure or as a censorship resistance feature, you want to consider Hubzilla.

In other words, Hubzilla, Osada and Zap are the same kind of application with different tasts.

Now we are in transiton period. Because Hubzilla use an old version of zot. Osada and Zap use a new version (zot6). Once the Zot6 implementation on Hubzilla is complete, all of these projects will be able to intercommunicate with users on each of the others with fine-grained access control.

Source : a post of M Dent

Add ActivityPub to your wordpress blog

Matthias Pfefferle annouce the avaibility of the plugin ActivityPub for wordpress.

This plugin implements the ActivityPub for your Blog. Your readers will be able to follow your Blogposts on Mastodon and other Federated Plattforms that support ActivityPub.

You can follow new post from any other activitypub account and comment. The comments comes directly to your wordpress comments.

Hubzilla 3.8 out

Mario announce in a post the availibility of Hubzilla 3.8

As you can see from the changelog, Hubzilla has gone through a very busy development cycle. To simplify the settings and improve the general UX, we have re-organised the entire apps and settings infrastructure.
Some features from the « Additional Features » section have been transformed to stand-alone apps and will need to be installed by the channel owner. Other features have been moved to the per app settings pages which are now easily accessible from the navigation bar or the app store.
Some addons have already been ported to the new apps infrastructure. This work is ongoing and will be completed during the next development cycle.

Other notable changes:


    • Remove tech-levels
    • Markdown table support
    • New addon (channelreputation) which provides a reputation system for community channels
    • Implement a subscriptions submodule for the cart addon
    • New addon (hsse) that implements a WYSIWYG editor
    • Experimental queue worker improvements (off by default)
    • Many under the hood improvements and bugfixes


As always, a big THANK YOU! to the translators and everybody who is helping to improve Hubzilla.

Howto upgrade:
Due to some profound changes to the addons it is necessary to follow this update procedure:


  • util/safemode on this will disable all enabled addons
  • util/udall the actual update which executes git pull for core and addon repos
  • util/safemode off this enables the previously disabled addons again
  • Install the upgrade info addon (optional) – this will show some info about the upgrade to your community members

Osada decentralised social networking

After Gnusocial, after Diaspora, After Friendica, hubzilla, Mastodon and others an new social network is coming.


Osada is a decentralised social networking application more familiar to refugees from Facebook and other conversational style social networks than it might be to those migrating from microblogging social applications such as Twitter.

Osada is very easy to use and provides a range of features either natively or through standard ‘Apps’. These include photo albums and file storage managers, events with attendance support, and topical groups/forums, all of which respect your personal privacy groups (such as Friends, Family, Coworkers, you name it).

ActivityPub Support

Osada has native support for the ActivityPub protocol (W3C standard) as well as the more advanced but lesser known Zot6 protocol. It can inter-operate with other social networking applications and projects in either of these spaces; for instance Mastodon, Pleroma, Pixelfed, PeerTube, Funkwhale, Zap, Friendica, Hubzilla, and many more.


A novel Osada feature which is unique to Zotlabs projects is the built-in hyper-drive social engine. This technology is essentially the secret sauce behind Facebook’s meteoric growth over a decade ago and this is the first time we’ve managed to replicate the essential bits using a decentralised protocol.

Public servers

There are a small but growing number of public servers available if you would like to try Osada without providing your own personal or community server environment. A list of these is available here. Only sites on this list with « Osada » in the « Software » name are compatible with projects using the W3C ActivityPub protocol. As the project is still in its infancy, we welcome additional public servers. There is a lot of interest in the project and we could use some help spreading the load.

Free and Open Source

The architecture supports themes and addons and a number of these are available today. Osada is open source under the permissive MIT license and runs on most modern LAMP servers, using MySQL/PostGres and Apache/Nginx. We are passionate about providing ethical and decentralised services running on open source platforms.

If you want to install it go to


PeerTube 1.0 : a free and federated video plateforme

Peertube is a federation of sites that host videos. PeerTube uses WebTorrent technology. Each server hosts a torrent and each web browser viewing a video reshares it. This allows to share the load between the server itself and the clients as well as the bandwidth used through P2P technology.

The system works via a federation of instances run by independent entities. Each PeerTube server can host any number of videos by itself, and can additionally federate with other servers to let users watch. This federation permits to collectively host a large number of videos in a unified platform, without having to build an infrastructure comparable to that of the web giants. Each server is operated by and stays under the sole administration of a distinct entity.

PeerTube uses the ActivityPub protocol, in order to allow decentralization and compatibility with other services such as Hubzilla, Mastodon

15th of October 2018 the first version 1.0.0 has been relases.

If you want to know more about peertube and join an instance : go to https://joinpeertube.org/en/


Articles plus anciens «