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

Création d’une application yii tutorial partie 2

Le but de ce tutorial est de créer une application de gestion d’adresse.
Nous allons utiliser une ligne de commande pour créer une nouvelle application Yii et Gii pour générer du code. Pour une question de convention, nous considérons que vous avez installer Yii sur le répertoire YiiRoot.

% YiiRoot/framework/yiic webapp WebRoot/adresses

Create a Web application under ‘/…/adresses’? (yes|no) [no]:
Répondez yes

Puis …

Vous devriez avoir le message suivant.

Your application has been created successfully under /home/cb/public_html/1/adresse-dev/adresses.

Vérifiez maintenant votre répertoire Yii, vous constaterez qu’un nouveau répertoire a été créer. C’est votre application

Sans écrire une seule ligne de code, vous pouvez maintenant tester votre première application avec l’url suivante. Eventuellement adapter le début de votre url.

http://hostname/../adresses/index.php

 

L’application ainsi générée comprend déjà les fonctionnalités suivantes :

  • Une page d’accueil où s’affichent quelques instructions (cf. capture d’écran précédente)
  • Un formulaire de contact complet, avec CAPTCHA
  • Un formulaire d’identification (login)
  • La possibilité d’accueillir par son nom un utilisateur identifié
  • La possibilité de mettre fin à la session (logout)

C’est une façon vraiment agréable de commencer une application Web, surtout si l’on considère que vous n’avez encore écrit aucune ligne de code. Remarquez que le formulaire de contact ne fonctionnera qu’à partir du moment où vous aurez renseigné votre adresse mail dans la configuration de l’application. Pour vous identifier, vous pouvez utiliser un des identifiant/mot de passe suivants : demo/demo ouadmin/admin.

Le dossier assets est utilisé pour l’intégration dejQuery (le framework JavaScript). Le nom des dossiers css et images est assez explicite.Le répertoire protected est le plus important : c’est dans ce dossier que vous modifierez le code pour changer l’apparence et le comportement de votre site. Enfin, le dossier themes vous permettra de modifier lestemplates du site, un peu comme vous le feriez dans un blog WordPress.

Vous devez vous assurer que le serveur Web dispose des droits d’écriture dans le dossier assets, sans quoi vous serez confrontés à des erreurs.

Nous venons donc de voir comment commencer le développement d’une application Web basée sur Yii. Pour chaque site que vous créerez avec Yii, vous devriez repasser par ces différentes étapes.

Tutorial yii Partie 3 : configuration de la base de donnée mysql

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.

Friendi.ca is now closed

I regret to inform everyone that have decided to close Friendi.ca due to scalability and inactivity issues. Unfortunately, the friendica platform is not made to handle huge amount of data. I have been struggling this past few weeks to stabilize the server that often uses 100% of its resources. It seems that I wasn’t the only having this issue. Not to mention its development is pretty inactive as well; it seems that the lead devs decided to dedicate their time on Red instead (which I think is a fail). The Friendi.ca community itself is also inactive. Sure, there are people posting, but most of it are either spam or a mirror from Twitter or Facebook, so I wouldn’t call it an activity from Friendi.ca. I also received reports that some messages are not being received or sent by friends from other networks. It seems that this is an issue to the friendica core itself. I cannot do anything about it. And unfortunately, I cannot dedicate my time to fix these issues.

Diaspora

Diaspora is an alternatif social network like facebook or google+. it is a free personal web serve that implements a distributed social networking service. Installations of the software form nodes (termed “pods”) which make up the distributed Diaspora social network.

Diaspora is intended to address privacy concerns related to centralized social networks by allowing users set up their own server (or “pod”) to host content; pods can then interact to share status updates, photographs, and other social data. It allows its users to host their data with a traditional web host, a cloud-based host, an ISP, or a friend. The framework, which is being built on Ruby on Rails, is free software and can be experimented with by external developers.

You can create freely an account and share content.

Afterwards, however, Salzberg and his team struggled to actually build the service. By the time they released a beta version in late 2011, Google had already come out with Google+, stealing much of Diaspora’s thunder. Over the summer, the founders decided to hand over control of Diaspora to the community and started working on a photo remixing tool called Makr.io.

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 «