freedomboneeee/doc/EN/app_pleroma.org

58 lines
3.8 KiB
Org Mode
Raw Permalink Normal View History

2017-11-08 15:35:39 +01:00
#+TITLE:
#+AUTHOR: Bob Mottram
#+EMAIL: bob@freedombone.net
#+KEYWORDS: freedombone, pleroma
#+DESCRIPTION: How to use Pleroma
#+OPTIONS: ^:nil toc:nil
#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
2018-04-12 14:01:49 +02:00
#+attr_html: :width 80% :height 10% :align center
2017-11-08 15:35:39 +01:00
[[file:images/logo.png]]
2018-02-21 17:16:59 +01:00
#+BEGIN_QUOTE
"/The way to keep giant companies from sterilizing the Internet is to make their sites irrelevant. If all the cool stuff happens elsewhere, people will follow. We did this with AOL and Prodigy, and we can do it again./" -- Maciej Cegłowski
#+END_QUOTE
Pleroma is an OStatus and ActivityPub compatible social networking server, compatible with GNU Social, PostActiv and Mastodon. It is high-performance and so is especially well suited for running on low power single board computers without much RAM.
2017-11-08 15:35:39 +01:00
2018-02-21 15:59:34 +01:00
Some general advice about life in the fediverse [[./fediverse.html][can be found here]].
2018-04-12 14:01:49 +02:00
#+attr_html: :width 100% :align center
2017-11-08 15:35:39 +01:00
[[file:images/pleroma.jpg]]
* Installation
Log into your system with:
#+begin_src bash
ssh myusername@mydomain -p 2222
#+end_src
2018-06-16 22:53:50 +02:00
Using cursor keys and Enter key select *Administrator controls* and type in your password.
2017-11-08 15:35:39 +01:00
Select *Add/Remove Apps* then *pleroma*. You will then be asked for a domain name and if you are using FreeDNS also the code for the domain which can be found under *Dynamic DNS* on the FreeDNS site (the random string from "/quick cron example/" which appears after /update.php?/ and before />>/). For more details on obtaining a domain and making it accessible via dynamic DNS see the [[./faq.html][FAQ]]. Typically the domain name you use will be a subdomain, such as /pleroma.mydomainname.net/. It will need to be a domain which you have bought somewhere and own and not one of the FreeDNS subdomains, otherwise you won't be able to get a SSL/TLS certificate for it.
* Initial setup
2018-04-18 16:49:15 +02:00
The first thing you'll need to do is to obtain your login details. From the *administrator control panel* select *security settings* then *passwords* then *pleroma*. This gives the password you will need to log in, together with the username you gave during installation of the Freedombone system.
2017-11-08 15:35:39 +01:00
Once you have done that then you can disable further registrations from the *Administrator control panel* by going to *App Settings* then *pleroma* then *Disable new account registrations*. This may take a while because the app gets recompiled afterwards.
2017-11-12 19:46:26 +01:00
* Mastodon user interface
If you prefer a Tweetdeck-style user interface, similar to Mastodon, then once you have registered an account navigate to */yourpleromadomainname/web* and log in.
2018-04-12 14:01:49 +02:00
#+attr_html: :width 100% :align center
2017-11-12 19:46:26 +01:00
[[file:images/pleromamastodon.jpg]]
2018-03-12 22:54:01 +01:00
* Mobile apps
It's also possible to use Mastodon apps together with Pleroma, such as Tusky, since it supports the Mastodon API. You may need to install *IcecatMobile* and set it as your default browser (under *Settings/Apps/Menu*) in order for the initial oauth registration process to work.
2018-03-13 13:59:05 +01:00
2018-04-12 14:01:49 +02:00
#+attr_html: :width 50% :align center
2018-03-13 13:59:05 +01:00
[[file:images/tusky.jpg]]
2018-04-12 14:01:49 +02:00
* Blocking controls
2018-04-12 14:01:49 +02:00
#+attr_html: :width 80% :align center
[[file:images/controlpanel/control_panel_blocking.jpg]]
The biggest hazard with Pleroma is that it's part of a public federated communications system. This means that conversations and replies from other servers may end up in your "whole known network" stream. The internet being what it is, some of these could be undesirable. You can block individual users or entire domains by going to the *Administrator control panel* and selecting *Domain or User Blocking*, then adding or removing entries. This blocks domains at the firewall level and also at the level of database and file storage.
If you want to block a particular user then select *Block a domain or user* and enter the user in the format *username@domaintoblock* (similar to an email address).