JoinDiaspora: The Online Social World Where You are in Control

Content is from the site's 2012-2014 archived pages.

Welcome to JoinDiaspora*

Own your own data

Many networks use your data to make money by analysing your interactions and using this information to advertise things to you. diaspora* doesn’t use your data for any purpose other than allowing you to connect and share with others.

Choose your audience

diaspora*’s aspects allow you to share with just those people you want to. You can be as public or as private as you like. Share a funny photo with the whole world, or a deep secret just with your closest friends. You’re in control.

Be who you want to be

A lot of networks insist that you use your real identity. Not diaspora*. Here you can choose who you want to be, and share as much or as little about yourself as you want. It really is up to you how you want to interact with other people.

Decentralization

Diaspora* is completely decentralized, and any person from any pod can communicate with one another! You can register at any of these other pods as well. You can also choose to set up your own pod if you'd like.

Make a contribution!

Make Diaspora even better! Fork the project on Github make some changes, and submit a pull request.

Tor .onion Service

Tor makes it possible for users to hide their locations while offering various kinds of services, such as web publishing or an instant messaging server:diasporaaqmjixh5.onion

 

+++

diaspora* celebrates one year as a community project.

27 August 2013

diaspora*, the privacy-aware, decentralized social network which puts users in control of their data security and was touted by the media as a "Facebook killer," celebrates its first anniversary as a community-run project on 27 August.

The project was started by four young programmers from NYU’s Courant Institute in 2010, and raised a record $200,000 via Kickstarter. It broke new ground in establishing a social network which respects users' privacy and helps them to own their data by giving them the power to decide where their data are stored.

Through many trials and tribulations, including finding workable solutions to technical issues which had never been solved before, difficulty in raising funding and the tragic death of one of the founders, the project kept growing.

On 27 August 2012, the remaining founders handed over the diaspora* project to its community. So what has happened since then?

The last year in diaspora*

Community manager Sean Tilleyand, core developers Jonne Haß, Alan Sheinwald, and Florian Staudacher took over the reins and got diaspora* galloping once again.

In that time the community has:

  • Adopted Loomio as a central hub for consensus-based decision making. Anyone in our community is welcome to voice their opinions, ideas, and plans on how to take the project further.
  • adopted a semantic versioning system for software releases;
  • released several major software updates, including significant performance and architecture improvements and many features;
  • developed numerous improvements in terms of designs, making the user experience in Diaspora even better than ever before.
  • launched a new project site, diasporafoundation.org, as a hub for the project;
  • launched a wiki at wiki.diasporafoundation.org as a hub for help for everyone from new users to developers;
  • done a lot of work on packaging the installation of diaspora* for different operating systems, to make it easier for people to set up their own server.

Diaspora's project infrastructure evolves

As development has shifted over to a community infrastructure, so too has the structure supporting the project itself. Since the beginning of the project, much of the principal development was done largely by Diaspora, Inc, a small for-profit start-up dedicated to coding the decentralized social communication platform.

Times change, and the project has grown and matured beyond what a start-up could provide. In a collaboration with Eben Moglen of the Software Freedom Law Center, the Diaspora project now officially runs under a non-profit infrastructure under the Free Software Support Network. The FSSN will act as a 501c3 non-profit collaborator, and will provide the following for the community:

  1. A respected place to hold all of the assets of Diaspora; the trademarks, the code copyright, JoinDiaspora and our money. It is a transparent organization which acts in the interest of the project and the community. If we decide we want to spend money doing code bounties or give swag to our top contributors, FSSN will work together with us to decide and put forth a course of action.

  2. Take tax-free donations. FSSN is a 501c3 charity. Money that is donated to FSSN in Diaspora’s name will go to help our project. This is huge in keeping the ‘back room’ of Diaspora clear, and means hackers can focus on being hackers without being bogged down by legal paperwork.

  3. A partner that shares our values. Together, we hope to take the project to the next level in terms of what our community can do together.

Where now for diaspora*?

The next steps for the project are:

  • separate the code which governs inter-server communication into its own layer to make our code base more stable;
  • create an API so diaspora* can communicate with other apps and platforms;
  • try to develop a standard protocol in collaboration with other decentralized social networks;
  • build more features into the software to attract more users.

The good news is that the diaspora* network is healthy and growing in the hands of its community. There is now a thriving but small community of volunteer developers contributing to the project. New developers are joining all the time, and progress is speeding up exponentially. However, we can always do with new people to help out. If you think you can contribute to the diaspora* project, we'd love to hear from you!

 

In 2014 this notice appeared on the JoinDiaspora.com website.

JoinDiaspora.com Registrations are closed

Diaspora is Decentralized! But don't worry! There are lots of other pods you can register at. You can also choose to set up your own pod if you'd like. Thanks to decentralized social networking, any person from any pod can communicate with one another!

Diaspora goes Non-Profit

Help support our mission of decentralizing the social web!

 

 

Since August 27th, 2012, all of Diaspora's development has been done entirely by volunteers out in the open. This has allowed the project to grow in remarkable ways. New features, designs, and improvements have made their way into Diaspora's code, and as such, the project has evolved far beyond what its original founders could have ever expected.

Our community-driven project is now supported and backed by the Free Software Support Network a project by Eben Moglen and the Software Freedom Law Center

By Agreement, FSSN is collaborating with Diaspora to provide support for management of branding, finances and legal assets. By donating to our project, you're helping support the goals and visions of our community. We're working hard to make the social web a better place, and together, we believe that we can make 

Diaspora goes Non-Profit

 

FAQ for Pod Maintainers

Installation

What are the general system requirements?

Running diaspora* requires resources depending on how many users use the installation and how much traffic the installation receives from other pods. Generally it is recommended that at least 1 Gig of memory should be available for even small instances.

For pods with more users the amount of memory available to diaspora* and the background jobs it needs is higher depending on the amount of users actively using the instance. As the database grows, more memory will be needed to compensate.

Since diaspora* requires quite a lot of different components to be installed, generally shared hosting servers are not sufficient. Any VPS or dedicated server with a suitable amount of memory will suffice.

Do you have a detailed installation guide?

Yes. Check it out! It will probably be more up-to-date than this page, in general.

What ports does diaspora* need open for communication?

Since we recommend running on HTTPS you should only need to open the standard port for it: 443. You should have a reverse proxy listening there that forwards the requests to the application server that diaspora* starts, on port 3000 by default. You can use your existing Nginx or Apache to do that. While we don't recommend it, you can run on plain HTTP with its standard port 80 too. Just never let diaspora* listen on these ports directly. You don't need to open the application server port, 3000, it's for internal communication only.

Can I use Apache to run diaspora*?

Yes: diaspora* is a standard Rails application, so you can run it with Passenger, or doing the more common setup which is to use a reverse proxy configuration. Check this example on how to configure that setup.

I installed diaspora* on my machine, went to http://localhost:3000 and signed up. But my friends can't add me!

You set "localhost" as your address, but this is not a valid external address. You first need an externally accessible address - either a domain name or an IP address. Once you have that working, you need to clear your database (`$ bundle exec rake db:drop db:create db:schema:load`) and re-register, coming in via the external URL. Note that if your externally accessible address changes, you need to start over. diaspora* is designed as a server application to run all day and night.

I get 'command not found' if I run bundle install

Make sure RVM is loaded and the correct Ruby version and gemset are activated. The output of the rvm info and gem env commands can be helpful in that. Run gem install bundler to reassure bundler is actually installed.

If you don't use RVM, a common issue is that Debian-based distributions, including Ubuntu, don't add gem executables to the search path. Read up on the PATHenvironment variable on how to solve that.

How do I get past the sign-in page to create a new account?

To create a new account, go to http://yourdiasporainstance.tld/users/sign_up (replacing yourdiasporainstance.tld with the host name of your pod).

I installed diaspora* on my machine, but when I load the site there are no images and the layout looks horrible!

You most likely started diaspora* in production mode and accessed the application server directly and not through your reverse proxy. In production mode we expect your reverse proxy to serve the static content since it does the job way better than anything else. If you did access diaspora* through a reverse proxy, make sure it has no configuration issues, has the public/ directory as document root and is set to look up if requested files are found there before directing the request to the application server.

Also make sure you ran bundle exec rake assets:precompile.

If you need to work around this requirement you can turn environment.assets.serve to true in config/diaspora.yml.

There are no uploaded images on my pod

First make sure other static content is working, as described in the previous section. We embed uploaded images with their full URL, this has to do with the way diaspora* makes sure your images can be seen by users on other pods. A common problem here is that environment.url in config/diaspora.yml, from which diaspora* constructs the full URL, is set to an incorrect value.

Do I need a commercial SSL certificate? / Can I use CAcert certificates?

If you plan on running your pod over HTTPS (yes, you should!) then yes you will need a valid commercial SSL certificate. By design, federation will not work with pods that have self-signed or invalid SSL certs installed. We do this to ensure that all users in the network are able to use diaspora* without suffering from constant security warnings related to 'invalid' certs.

For more information see this and this discussion.

There are free commercial certificates around - check Let's Encrypt or StartSSL for example.

I can't find anybody on another pod / I am receiving posts but nobody is receiving mine

If you're having problems, make sure to search for people by their full diaspora* ID. Check that your Sidekiq worker is running. Check Sidekiq's retry queue for error messages. Check that the environement.certificate_authorities setting is correct.

I can't find myself from another pod / I am not receiving any posts but everybody is receiving mine

Check that your SSL setup is correct, use sslshopper, ssllabs or High-Tech Bridge to test your configuration. Make sure it's all green, no yellow, no red.

I'm getting the warning "... in production without Sidekiq workers"

Sidekiq is the backend we use for processing background jobs. Normally, Sidekiq is spawned as a separate process, but in this case you have configured diaspora* to run the jobs in the same process as the application. This is normally used for development or testing purposes, but if used in production, it can bring major performance penalties. Thus you should always run Sidekiq in its own process, by setting environment.single_process_mode to false in your config/diaspora.yml and starting the Sidekiq process with

RAILS_ENV=production bundle exec sidekiq

In case you are using script/server to start diaspora*, then you don't have to manually start the workers! This is already done by the script.

How can I troubleshoot my email configuration?

Use the following command to send an email and get the exceptions right on your console:

RAILS_ENV=production rails runner 'Notifier.admin("test message", User.where(username: "your_username")).each(&:deliver)'

Make sure to restart diaspora* once you successfully receive the test message.

I'm getting a 500 error page

Oh noes, you might have hit a bug in diaspora*! But this can also be caused by setup issues, like a incorrectly setup custom landing page, an old Redis version or database connectivity issue.

  1. Make sure you found a reliable way to reproduce the issue.
  2. Run tail -f log/production.log. Watch the output closely as you reproduce the issue.
  3. If you can't make sense out of the actual error message, reach out to us, see How we communicate. When doing so provide the steps you have taken to produce the error page as well as the full output from the log while reproducing it.
  4. If told to open an issue, go to https://github.com/diaspora/diaspora/issues. Again make sure to provide the steps to reproduce the problem as well as the log output.

How can I run multiple load-balanced instances of diaspora*?

Multiple diaspora* instances for the same "pod" must share SQL and Redis databases, and public/uploads directories. There are many possible ways to accomplish this, but perhaps the most classical scenario would be to configure all the nodes to point at a central database server for MySQL/Postgres and Redis, and share the uploads directory from a file server via NFS. To avoid problems with schema changes, it would be desirable to keep all of the instances running the same version of diaspora* at all times.

Load-balancing of the instances can be accomplished with any TCP load balancer that supports session stickiness (such as Apache or nginx, among others).

Upgrading

Is there anything I should do before upgrading my installation?

Yes, read our notes for updating.

How do I roll back my installation if an update breaks it?

First, try to fix your installation; as always our IRC channel should be helpful for getting help with this.

To roll back, just do: git checkout ref Where ref is the identifier of the commit to go back to. It's a long string of letters and numbers. You can find the ref by doing a git log, eyeballing the commit dates, and figuring out where you were before you pulled. Of course it's best if you keep track of that ref before you update.

You can also checkout a particular version with git checkout v0.3.0.1, replacing the version of course.

After that just follow the same procedure that you would to update your installation.

What if there were database migrations in the code I am rolling back?

Then you also need to roll those back separately. You need to do this before you roll back the code. Look in the db/migrate directory and figure out which files are new since the last time you pulled - i.e., which migration your database should be on. They are in timestamp order in that directory. Then do: bundle exec rake db:rollback and look at the output. It will tell you which migration you are now on. It rolls back one each time you run it. Run it until you're on the right migration and then roll back the code as described above.

Also be aware that database rollbacks can fail - they depend on the migration author writing the correct code to roll back. So in this case it's generally much easier to seek help to fix your current setup than to roll it back.

General

Am I alone here? (Establish connections with other pods)

Once you set up your pod, you should add some contacts to start receiving content from other pods. It's a good idea to add some active diaspora* people to your contacts, because they almost all run their own pod, so your pod will be known by them and you will be easily findable from there.

Here is a small list:

  • Official account of the project: diasporahq[at]joindiaspora.com
  • Sean Tilley: deadsuperhero[at]joindiaspora.com
  • Jonne Haß: mrzyx[at]social.mrzyx.de
  • Florian Staudacher: raven24[at]pod.fulll.name
  • Jason Robinson: jaywink[at]iliketoast.net
  • The Geraspora team: team[at]pod.geraspora.de
  • Fla: fla[at]diaspora-fr.org
  • Diaspora*UK: podmin[at]joindiaspora.co.uk

After you added a few contacts it's a good idea to make a public post containing the #newhere tag, announcing your new pod, to get even more contacts.

Can I make my pod private/isolated/not communicate with other pods?

No. diaspora* is built around the idea of a distributed social network. We want to build one network, not enable special interest communities or companies to host their own social network (We do welcome you on diaspora* though!). A large amount of the development effort goes into making that one network possible and the whole user experience is designed around it. This not only means that other existing solutions often have feature-sets way better suited to that usecase, but also that if we did implement a switch to turn off communication with other pods, there would be many broken ends in the user interface, which would lead to a bad user experience.

Can I modify the code?

Yes. But keep in mind that diaspora* is licensed under the AGPLv3, that means you must make the currently running source code available to your users. For legal advice beyond that, please contact your lawyer.

Will a pod eventually receive federated posts that it misses while being offline/down?

Possibly. We retry the delivery three times at one hour intervals.

I've got my pod running. How do I disable outside logins?

Set settings.enable_registrations to false in your config/diaspora.yml and then restart diaspora*.

How do I back up my pod?

You should do backups of all user data, that is the whole database and uploaded images. For the images just make copies of the public/uploads directory. Then just dump all Diaspora_ databases from your database server. A web search should get you the information you need on how to do that. Make sure to store the backups on a different server, or at least on a different hard drive.

I am on PPC (e.g. old iMac) and want to use it for serving diaspora*, but there is no ExecJS compatible JS runtime

One thing you could do, assuming you have another PC that will run Node: Precompile your assets on that machine (using bundle exec rake assets:precompile) and then check them into git before you deploy to the PPC box, or just copy over the contents of public/assets. The Javascript runtime is only really needed for precompiling assets and shouldn't be loaded at all in the actual production environment. You may need to use git add public/assets -f to force git to check them in, since I think that directory is in .gitignore.

What are roles and how do I use them? / Make yourself an admin or assign moderators

We have a role system that allows to make some accounts 'special' during runtime, without restarting the server.

Currently you can manage the community spotlight, the moderators and the admins through this system. If you are using PostgreSQL, ensure you have set the environment variable DB='postgres' or you will get a very misleading error from bundler and if you follow it, accidentally install the MySQL adapter.

Start by starting a Rails console:

RAILS_ENV=production bundle exec rails console

You'll get a new shell where you can enter Ruby code. To exit it just press Ctrl+D or type exit or quit. Here are some examples to manage the roles, replace the_username with the user's username, not their full diaspora* ID:

Role.add_admin User.where(username: "the_username").first.person           # Add an user as admin by username Role.add_admin User.where(email: "the_email").first.person                 # Add an user as admin by email Role.add_moderator User.where(username: "the_username").first.person       # Add an user as moderator by username Role.add_moderator User.where(email: "the_email").first.person             # Add an user as moderator by email Role.add_spotlight User.where(username: "the_username").first.person       # Add an user to the 'community spotlight' by username Role.add_spotlight User.where(email: "the_email").first.person             # Add an user to the 'community spotlight' by email Role.add_spotlight Person.where(diaspora_handle: "username@pod.tld").first # Add an user to the 'community spotlight' by diaspora handle (other pod), make sure that at least one user of your pod follows that account

For admins; your user profile should now have an "Admin" link added to the mouse hover list. This gives you stuff like user search and stats for your pod. For intense detail on the operational aspects of your pod, go to the location /admin_panel For moderators: The moderator should now have an "Moderator" link added to the mouse hover list. Moderators have access to the report section of the admin panel and can review reported posts and comments. Moderators also get emails when a new comment or post is reported.

Followed tags don't work on my pod

There is no synchronization in diaspora*. This means your pod only knows about posts it has received for a purpose. These purposes are, of course: the author is local, someone on your pod is following the post's author, or the post's author is following someone on your pod. Another reason is that the post got reshared by someone whom one of the users on your pod follows. Tags are not federated to all pods: the #Followed Tags stream displays only posts your pod knows about through one of the previous scenarios.

My log files are getting huge, help!

Configure yourself a log rotation solution. For example, on Linux distros, do this with logrotate, something like the following (change the paths where needed) in /etc/logrotate.d/diaspora:

/home/diaspora/diaspora/log/*.log {    notifempty    copytruncate    missingok    compress    monthly    delaycompress    rotate 5 }

Once you've added the file to "/etc/logrotate.d/" run

sudo logrotate -f /etc/logrotate.conf

How can I send an email to a user / a group of users?

You need a working email configuration. There are two ways for triggering the emails.

Ruby console

Fire up your rails console with rails console production, then follow one of the examples or make up your own:

Notifier.admin("important message", User.where(username: "someuser")).each(&:deliver)                 
# Send a message to someuser Notifier.admin("important message", User.where(username: ["someuser", "anotheruser"])).each(&:deliver) 
# Send a message to a group of users Notifier.admin("important message", User.yearly_actives).each(&:deliver)                              
# Send a message to all active users

Rake task

There is a Rake task podmin:admin_mail available to allow podmins to easily send news and notices to users. The rake task triggers emails via the normal diaspora mailer mechanism (so they are embedded in the standard template) and takes the following parameters:

 1) Users definition all - all users in the database (except deleted) active_yearly - users logged in within the last year active_monthly - users logged in within the last month
active_halfyear - users logged in within the last 6 months  2) Path to message file. Give here a path to a HTML or plain text file that contains the message.  3) Subject    
A subject for the email 

Example shell command (depending on your environment)

RAILS_ENV=production bundle exec rake podmin:admin_mail['active_monthly','./message.html','Important message from pod']

Read more about specifying arguments to Rake tasks.

Can I add advertisements to my pod?

Sure, we have no rules that you cannot add advertisements to your diaspora* installation.

How do I define a Terms of Service document for signing up to my pod?

That feature is built in and we have a generic template that you are welcome to use. Of course, you can also edit it or create your own set of terms.

This feature is built in but not enabled by default. If you want to enable it, please add under settings in config/diaspora.yml the following and restart diaspora. If in doubt see config/diaspora.yml.example:

  terms:     enable: true 

When enabled, the footer and sidebar will have a link to terms page, and signup will have a disclaimer indicating that creating an account means the user accepts the terms of use.

While the project itself doesn't restrict what kind of terms pods run on, we realize not all podmins want to spend time writing them from scratch. Thus there is a basic ToS template included that will be used unless a custom one available.

To modify (or completely rewrite) the terms template, create a file called app/views/terms/terms.haml or app/views/terms/terms.erb and it will automatically replace the default template, which you can find at app/views/terms/default.haml.

There are also two configuration settings to customize the terms (when using the default template). These are optional.

  • settings.terms.jurisdiction - indicate here in which country or state any legal disputes are handled.
  • settings.terms.minimum_age - indicate here if you want to show a minimum required age for creating an account.

How do I modify the pod landing page?

Please see Custom_splash_page.

Errors and problems

What do I do about all these PGErrors, like disconnects and SSL problems?

If you are running diaspora* with PostgreSQL, beware that having the SSL setting turned on in the PostgreSQL config has been causing problems for several people. We recommend turning it off unless you know what you're doing.

My sidekiq is crashing, help!

Check your curl version

   /usr/bin/curl --version 

Make sure you see AsynchDNS in the output. If this does not happen, check this issue on how to upgrade curl.

Check database connection pool

Make sure you have enough database pool connections to top your environment.sidekiq.concurrency. Search logs/sidekiq.log for errors relating to database connection not being available if unsure if you are running out. You can edit the pool setting in config/database.yml if needed and then restart. Make it sufficiently larger than your sidekiq concurrency*sidekiq workers, 1.5x is a safe rule here.

Check for out of open files errors

In the diaspora* app folder, do grep "Too many open files" log/sidekiq.log and check for results relating to the system user running the diaspora server running out of open files. If you get any errors, it is possible sidekiq can be brought down by the same problem. Follow for example this guide to increase the limit of open files available to the user running diaspora*.

Make sure memory is not running out

If the server runs out of memory, it is likely sidekiq will be the first to be killed. Check for Cannot allocate memory text in the ./script/server output, or use monitoring to see when memory goes critical. Increase the amount of swap available to make sure the application does not die (swap should be at least the same as RAM).

To make sure sidekiq doesn't use too much memory, make sure you are not running with too many Sidekiq workers or concurrency. On a small pod, you can safely but both values to 1 in config/diaspora.yml. Then restart and watch the Sidekiq admin panel and if a queue starts to build up, increase the concurrency in small increments until Sidekiq can handle the queue. There is NO need to run more Sidekiq concurrent threads than is needed to process the queue - you just use more memory this way!

JoinDiaspora.org