Red

by  Commander Zot

I've been working on Red for three months (off and on, there are lots of demands on my time). Here is an update.

Most of us think of "online networking" and think only in terms of "social networking" because of all the influence that Facebook has had in that realm. It has become apparent that the abuse of privacy has only one solution - take the private information out of the hands of outsiders and keep it under the control of those who are communicating. This means that a future which involves "privacy" belongs to decentralised communications, not to centralised data silos. We knew that already and was the basis for Friendica.

But also we've come to accept that the "social" part of networking is the only thing that matters. That everything on the modern web is all about friends.

It's not.

Red is an attempt to look at all of this from a higher level and see where we've been and where we're going. The whole "social" bit came about because email couldn't protect us from spam. So we started only accepting messages from "friends". And so now we have these huge corporations which are geared around the concept of communicating with friends.

Facebook is merely a communications system with web accessible resources, all focused on the concept of "friends". There is also inherent censorship and blockage of people with non-mainstream beliefs.  Filtering is performed which uses Facebook algorithms to decide which content by which friends you can see at any one time. What you see in your stream isn't under your control.

Now let's look at Red. Red is simply a network. It has attached web resources. It is decentralised. It isn't concerned with the "social" bit, because "social" just means a granting of permissions to do stuff. Red has a permissions system which can emulate "social networking", and much more.

But Red isn't about people. It's about thought streams.  We call them "channels". You can create any number of channels, and some of these can represent people - like you for instance. And they can interact just like in a social network. But channels can represent any thought stream, hobby, interest, person,  discussion topic, anything. They can be about your music. They can be scientific discussions on a particular topic or range of topics. They can be a personal blog or a marketing site for a new product. You can attach web resources to channels such as  photo albums and event listings and static web pages. And you can create rules on how other channels or collections of channels can interact with each of them - or not. 

So each channel is essentially a content management system attached to a communications system and a set of rules about what interactions are allowed - and what content is visible to any or all other channels. And since it is decentralised, private information is only shared with the hubs of other channels that are involved.

Important: There isn't any central repository anywhere which has access to *all* private information.

You also have an analogue dial representing the "affinity" between this channel and any other specific channel. If you're "channel surfing" you can look at specific other channels, or mixtures of other channels, or those with a specific range of affinity. And if those channels permit you to do so, you can interact with them. You can also interact with specific subsets of channels. In a social network context you might call this a "private group".

And you can change channels. They are all separate entities, so things can't leak between your channels. So not only does each channel have privacy controls for the other channels it interacts with, different channels can interact with completely different sets of permissions.

In Friendica for instance you can create private profiles and photos that can only be seen by co-workers, and another which can only be seen by potential girlfriends. In Red, you can do exactly the same. But you can also interact with co-workers on a completely different channel and share work related stuff without having to worry about what permissions you might need to set on each thing you post or share. One is a different thought stream entirely from the other.   

The other big thing we're doing in Red is taking the internet domain name system out of the equation. You need this to visit web resources, but you don't need it for basic communications. You can move around and interact from other places. So if your channel doesn't require web resources, you can communicate from anywhere. We hope to build desktop and mobile communication clients which can operate independently of the content management web servers, and allow you to stay in communication even if those go down - (which happens). 

So in summary, Red isn't a social network in any classical sense, though it contains all the same components as a classical social network and has better privacy controls. So one could use it in that manner.

Red is a matrix of interacting thought streams.

Want to connect to the grid? We're still several months away from a solid prototype. This is a lot more complicated than a decentralised social network and it's taking some time to develop because nobody has ever done anything quite like this before.

Stay tuned.

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.

 

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.

Police repression against demonstrators in France against gay marriage

25th of may 2013 Paris a group of young people sing against gay mariage. Look how police react.

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

Exodus


Exodus is the story of Moses.

The 3D was good when the pictures doesn’t move a lot.

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é.

friendica-diaspora

 

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.

contactsfriendida

 

Voila vous allez pouvoir suivre les contacts diaspora depuis friendica.

Création d’un compte totalement ou partiellement caché

Si vous avez un compte friendica, peut être voulez vous rendre publique certaines notices et pas d’autres. Vous pourriez par exemple écrire des notices publiques comme si vous écriviez sur votre blog (Friendica sera alors votre blog) mais, vous pourriez en plus écrire des notices privés visible seulement à un groupe (votre famille, vos amis proches etc…) ou seulement à une seule personne.

Voici la marche à suivre pour que tout ceci fonctionne bien:
Allez dans réglages (la petite roue) > Réglages > Compte

Vous arrivez par défaut de toute façon sur cette page.

La première partie Compte ne concerne qu’un changement de mot de passe, vous avez ensuite Réglages basiques puis Réglages de sécurités et vie privée. c’est cette partie qui va nous intéressé.

Cacher les détails du profil aux visiteurs inconnus? : Il faut répondre NON

La compréhension de cette traduction n’est pas facile à comprendre. Si vous répondez OUI, votre profile sera visible uniquement aux personnes connectés. Il faudra donc répondre NON pour que ce que vous voulez publier publiquement soit visible à tous les visiteurs.

Friendica 3.3 Ginger est sorti

Cette nouvelle version nous montre que le projet Friendica n’est pas mort. Ce projet est tout simplement mûre et continue d’être améliorer avec un rythme moins rapide.

Voici les amélioration de cette version

thèmes

  • Arrêt du support des thèmes non maintenus. On va pouvoir continuer à les utiliser mais ne seront plus dans la liste des thèmes
  • Fusion des thèmes “zéro” en un thème avec variantes.
  • Nouveau avatar par défaut par Andi Stadler

Ergonomie

  • La page réseau est maintenant la page par défaut après une connexion
  • Les sections sur la page de paramètres utilisateurs sont maintenant rétractables
  • Mise à jour automatique du flux de réseau a été amélion

interaction

  • Après un l’ajout d’nouveau contact, l’utilisateur est dirigé vers la page du nouveau contact (Au lieu de la page distante)
  • De nombreuses améliorations sur tous les connecteurs.
  • Nouveau connecteur app.net
  • L’algorithme pour raccourcir messages lors de la publication de plates-formes limitées a été amélioré.
  • Améliorations pour les fonctionnalités de flux RSS / Atom

Coeur du système

  • Plus de soutien apc en raison des problèmes avec PHP 5.5
  • Mise à jour des bibliothèques suivantes: Smarty 3.1.19, 1.6.4 fullcalendar, jquery 1.11, jgrowl 1.3.0
  • Modernisateur ajouté 2.8.3, un meilleur support du navigateur
  • Mises à jour de la structure DB pour de meilleures performances
  • préparations à l’implémentation de PDO dans une version future
  • Nouveau système de notification
  • Traductions de l’interface web mise à jour, les traductions maintenant également possibles séparément de l’interface utilisateur principale et fait pour CS, IT, RO, DE addon
  • Quelques bugs ont été corrigés pour l’importation de profil
  • Manipulation de BBCode et le reformatage par exemple Markdown a été améliorée
  • Pour la communication avec les contacts OStatus (StatusNet / GNU sociale / de rstatus) un serveur Push interne a été ajouté et sera utilisé par défaut par les nouvelles installations

addons

  • Traduction fait maintenant à transifex ainsi
  • Statistiques addon de participer à l’enquête Diaspora *
  • Nouveau connecteur bidirectionnel pour app.net
  • Nouveau connecteur de relais pour la Diaspora *
  • Nouveau connecteur pour le service de tampon
  • Améliorations pour les connecteurs avec Twitter, StatusNet / GNU social, pump.io, google + et facebook
  • Améliorations d’intégration de min-Jappix-
  • Changement dans la structure de la git:

Lire l’article officiel en anglais

gnusocial : starting startdaemons.sh

Once you have installed your gnusocial, you can run startdaemons.sh
I recommand to make it by cron every day for example .
At 6:00 run sh /…/…/scripts/stopdaemons.sh
and at 6:05 sh /…/…/scripts/startdaemons.sh

Installing your own gnusocial

How to connect your GnuSocial with Twitter

If you have your own GnuSocial, you can configure the TwitterBridge. This Twitter “bridge” plugin allows you to integrate your GnuSocial instance with Twitter. Installing it will allow your users to:

– automatically post notices to their Twitter accounts

– automatically subscribe to other Twitter users who are also using

– your StatusNet install, if possible (requires running a daemon)

– import their Twitter friends’ tweets (requires running a daemon)

– allow users to authenticate using Twitter (‘Sign in with Twitter’).

twitterbridge

Here is a How to step by step for connecting your GnuSocial account with your twitter. Step 1 to 5 is administration configuration.

1. Configuration in GnuSocial

Edit you config.php file (should be on your root directory of GnuSocial) and just add the following line

addPlugin('TwitterBridge');

Once it is done, upload it.

2. Creation of your Twitter app

Second step, you should create a twitter application. Go to https://apps.twitter.com/. If you are not connected to Twitter, sign in with your twitter account. Then clic Create New App

how to connect your GnuSocial with Twitter step 2

how to connect your GnuSocial with Twitter step 2

– Name : Your should invent a name for your application. Should be unique so, try to invent a unique name.

– Description : Write something to help you in case you have many applications

– Website : Type here the URL of your GnuSocial website.

– Don’t forget to read and valide the Developer Rules of the Road at the end of this form

– Clic on Create your Twitter application

201408181

3 Change the permission

Clic on API Key, then Mofify app permision to read an write.
Clic ont the Tab Permission and change permission to read and write

4 Create your access token

Clic API Key, and at the bottom of the page, Create my access token. Check that this token have read and write permission (waite a little and refrench the page)

5 Twitter bridge settings

Go to the admin panel of your GnuSocial. You should have Twitter option. Then enter :
– Consumer Key : put the API Key
– Consumer Secret put the API secret
– Application name

Now your users should connect with twitter.

6. Connect your account with Twitter

Now the most important step is not done. This is the easiest (if all previous steps was done correctly).
In your GnuSocial go to Setting > Twitter > Connect my Twitter account > Validate
It’s done.

 

 

I recommand to just leave the first option “send my notices to Twitter” on. That means that when you are going to write something public on your GnuSocial, that will post to your twitter account as well.

I don’t recommand to select “Subscribe to my Twitter friends here”. Except if you have a strong server.

 

Installing your own gnusocial

How to install gnusocial ? ssh mode

Gnusocial is a twitter like software that you can install on your own server. The advantage of gnusocial over twitter is that it is federated. All gnusocial instance can communicate to each other. Like email or xmpp (jabber) you will have an Ostatus id like user@server.

First step is you don’t know what is gnusocial is to play with it. You have public

Installation :
Before going to the installation, let’s check the requirement
– php 5.4 at least
– ssh access is

Go to the directory where you will install gnusocial I will name the directory gnusocial
run this command
git clone git://gitorious.org/social/mainline.git .

Don’t forget the . (dot) at the end.

When it is done go to your new gnusocial
You should have a page like

No configuration file found.

I looked for configuration files in the following places:
/etc/statusnet/statusnet.php
/etc/statusnet/laconica.php
/etc/laconica/laconica.php
/etc/statusnet/localhost.php
/etc/laconica/localhost.php
/etc/statusnet/localhost_~cb/2/gnusocial.php
/etc/laconica/localhost_~cb/2/gnusocial.php
/home/../…/gnusocial/config.php

You may wish to run the installer to fix this.
Go to the installer.

click on Go to the installer.
You should have some permission to change just follow what is it mentioned
4 directories should have write access
chmod a+w gnusocial
chmod a+w gnusocial/avatar/
chmod a+w gnusocial/file/
chmod a+w gnusocial/background/

when it is done refresh the page (install.php)
A form will appear.
Just feel the form

  • Site name : what ever you want
  • Database Hostname : usualy it is localhost but not always
  • Database name (you have to create a database for that first or you should know the name of it
  • Database user
  • Database password
  • Administrator nickname that will be the admin account
  • Admin password
  • Type of site : Private : all will be hidden, single user (if you want only for you), community (ideal for a group, a class, a family etc..) , public (if you want a free registration for every body, that option need a strong server and administration care)

Choose community even if you will use it only for you. It is very easy to restrict registration. If you want to share you gnusocial with a friend, it will not be possible otherwise.

done

 

Starting deamons.sh
How to connect your GnuSocial with Twitter

Coming in September 2014: Friendica Hackathon in Berlin, Germany

(Reposted from Tobias Diekershoff)

Upcoming in September: Friendica Hackathon in Berlin, Germany.

From Sept. 5th to 7th 2014, some Friendica developers and users will be gathering in Berlin to work on software improvements. Everyone is invited to join.
The plan is to work on some issues (label Berlin2014) and to get to know other friendica friends in person. We hope to see non-coders as well as coders! People who know about UI, who would like to test or document changes are very welcome! If you can't come in person but you'd like to work with us, join us on IRC (#friendica on freenode, UTC +2 ;) ) or in the forum!

The venue:
Groessenwahn, Kinzigstr. 9, 10247 Berlin, Germany (http://kinzig9.de/gwl.html)
The venue is not accessible in a wheel chair.

If you are somehow involved with friendica and you would like to join, poke us! There is still a limited amount of sleeping places available.

"Us" - that's tugelblend@snarl.de, tobias@f.diekershoff.de and freiefunken@pink.pilot.io

Hope to see you in September!!!

Redmatrix and friendica

As an analogy – I wonder how many people go to Ford dealerships and tell them they really want a Jeep or a Volkswagen and when the Ford dealer manages to actually produce one from the back lot, then complain because it’s the wrong colour or doesn’t have snow tires on it.

Friendica was built for and designed around service federation. RedMatrix is designed around a consistent privacy model. The two goals are unfortunately somewhat incompatible as every different communication service has a somewhat different privacy model. Friendica’s is completely different from RedMatrix, for instance. They started off essentially the same, but we had to water down the Friendica model a bit and make lots of compromises so it would co-exist with other social networks. I’m tired of producing software that has privacy issues just because some other network we want to communicate with has privacy issues. We can’t federate with Friendica because there are too many anti-cert zealots and half the network issues browser warnings. We can’t federate with Diaspora because they can’t protect private photos. We can’t federate with GNU-social/StatusNet because nothing at all is private. We can’t federate with Facebook because we don’t want to and they won’t allows us to. At the end of the day there’s nobody left to federate with.

La plus grand faiblesse de friendica

Si friendica compte un grand nombre de qualités comme installation facile et rapide, compatibilité avec la fédération ostatus, envoie vers twitter, pump io et la liste est longue, ce réseau a une grande faiblesse.

Il y a très peu de francophones. Les quelques francophones qui se sont inscrits sont resté quelques jours voir quelques semaines avant de déserté ailleur. Résultat le nombre de francophone est très très faible.

Un réseau social sans personne n’est plus un réseau social mais un logiciel inutile, des lignes de codes inhumaines. Voila donc francophones du monde entier, sachez qui facebook n’est pas le seul réseau ni twitter ou google+, vous maitriserez vos donnés et ne serez plus dépendant d’une multinationale.

Older posts «