GNU Social package


I’m developing a package for GNU social and it goes by a good way. It can be installed, removed and upgraded, but so far LDAP and SSOwat configuration isn’t implemented yet and may be domain’s configuration could be improved.

My question is:

Although is still in development, where can I share my contribution?


You can share the link (I found it)

You can move the app here

I send you an invitation to join that organization.

You can add the app in community list

I tested it. The install goes well and it works fine.

We can’t authenticate right now?

1 Like

Thanks for the links, Moul.

Authentication is available with usual registration in GNU social as a public site, but users aren’t the same of Yunohost database.

Ok, I choose Community.

It’s a lightweight app. I like it

De más, creo que es la única aplicatíon con un manifesto traducido en español.

Sí, creo que es la única :slight_smile:

I’m very interested in autonomous communities development. Yunohost is fine for that, has most apps to connect people and GNU Social is a very good software to federate communities between them. It has OStatus engine to comunicate «states» and not only to send text messages. I’m a member of a spanish language GNU Social node ( for almost two years and some of we are building our own communities and helping others to create them, so Yunohost has arrived as a revelation.

1 Like

You can join our XMPP chat rooms:

I mean to use only one repository because you add YnH-Apps repo on the list and you develop on your repo.
For that you could change owner (if you want to) of the repo.

One issue: be more explicit about the type of install (community, open) or add a in the readme how to create an account.

Excuses for that commit to the old repository. I did it because I weren’t too sure that the change works fine and I wanted to avoid the possibility of a commit with wrong code. It isn’t necessary to change owner.

Could you suggest me best practice for testing changes on scripts?

In other hand, a description note about types of profiles is added at readme. When LDAP were working, Public profile won’t be very useful, but so far I think it would be better set Public profile as default than Community.

You could push on a dev branch using git branch and git checkout.


By the way, I could make it works with a self-signed certificate.

Hi, this looks like a very interesting app
SSO and LDAP authentication are possible so it is promising

What is the use of the Qvitter plugin exactly?


LDAP is possible, however I didn’t make it work with SSO.

Qvitter is a GUI for GNU Social that looks like twitter and improve default GUI.
The main problem of Qvitter is that doesn’t work with virtual directories.

App updated with LDAP integration

1 Like

That’s pretty cool, thanks about that !