#mastohelp
I installed #pleroma via OTP release and i can log in, I'm federated and is mostly working. But I cannot upload media: it fails saying the uploaded file cannot be moved from /tmp to pleroma's media folder. I tried to write in both position with the pleroma user to be sure the user can actually write: it can. Anyone has an hint on what is possibly going wrong?
How? You know you can join more than one server and export/import your follow lists?
There's no reason to be beholden to just one server and when I joined #Mastodon last November almost everyone I followed was on more than one instance.
Does anyone know if posts from Pleroma/Akkoma can be embedded?
This closed issue from three years ago suggests this should be possible, but I can't seem to get this to work. Unless this is not typically enabled on instances?
TIL that you can click on timestamps in the notification section to open the full conversation thread in Pleroma UI. 🤯
This is a game changer for me. I won't feel the need for a custom front end anymore. Such a simple thing has been a major pain point all this while.🤣
I would be very interested in knowing if there are #fediverse projects other than #mastodon that will be committed to keeping a pure Fediverse, #activityPub spec and compatibility THAT IS NOT lead or even influenced by #meta ...
I fear that our BENEVOLENT Dictator may succumb to the dark side quite quickly:(
It almost feels like Mastodon do not want us to self host. There is no direct link on the main webpage to install on server. Digging through the docs, finally found documentation and there is no Docker container or a package for any OS for easy installation. They require us to install from source along with all the dependencies. I don't mean to bad mouth it but they do not do enough to encourage self hosting (if not discourage).
Would like to know your opinions or ideas on how to self host it easily with minimum maintenance (auto upgrades, etc).
Just upgraded #Pleroma, which I’d been putting off for a while.
I had been using the packaged, “OTP”, version of Pleroma, but it turned out the package is ancient, and it required an older cryptography library. Because I’d upgraded to a newer version of #Ubuntu, the older crypto library had been removed and replaced with a newer version.
The whole process took maybe half an hour, and no more than 10 or so commands. Basically:
Stop Pleroma (so it’s not running while trying to backup/update): sudo systemctl stop pleroma.
Backup my instance.
First make a place to store the backup: mkdir -p ~/backup/pleroma. I made it (temporarily!) world-writable to make things easier: chmod 777 ~/backup/pleroma.
Backup the configuration: sudo cp /etc/pleroma/config.exs /home/saria/backup/pleroma.
Delete the Pleroma installation (actually, just put it to one side for now, just in case): sudo mv /opt/pleroma /home/saria/backup/pleroma/old-installation and sudo mv /etc/pleroma /home/saria/backup/pleroma/old-configuration.
Adjust stuff that differs between the OTP installation and the source installation.
Update the pleroma user’s home directory: sudo usermod -d /var/lib/pleroma pleroma (Here I got an error that the pleroma user was still running process 758. No problem, just sudo kill 758, then retry.)
Make the “new” locations: sudo mkdir - /opt/pleroma /var/lib/pleroma. (I think /var/lib/pleroma already existed, and was storing images and uploads, which was fine.)
Make the pleroma user the owner of those locations: sudo chown -R pleroma: /opt/pleroma /var/lib/pleroma.
Edit the configuration file config/prod.secret.exs, copying all the important stuff (passwords, salts, personal settings) from the old file at /home/saria/backup/pleroma/old-configuration/config.exs.
Run the database migration: sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate.
Restart Pleroma: sudo systemctl start pleroma. I discovered (using sudo systemctl status pleroma) that Pleroma would not start. I realised that was because the systemd service file was still trying to start the old, OTP version. So I replaced the service file with the one from the source installation (sudo cp -f /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service) and tried again. Now I got an error from systemd because the service file had changed, telling me I had to do systemd daemon-reload. So I did sudo systemd daemon-reload, and tried to start Pleroma again. Success! 🦸🏾♀️
As you can see, I ran into some hiccups, but the documentation and error messages were clear enough that I was able to fix stuff and move on.
Now, I am no expert on any of this stuff! I know literally nothing about Erlang or Elixir (the languages/tools/whatever that Pleroma is made with). But as you can see, if you take the time to carefully read the documentation, and understand what each step is actually doing, it’s really not that hard! 💪🏾
Really sad that #Pleroma does not have good photo support, I really would love to just swipe through photos sometimes or have a timeline that just contains posts with photos.
There is only #Pixelfed that comes close to what I wait for since 2015 to happen in the #Fediverse, but not really close. It seems to be very easy idea, but probably impossible to program or implement. 😔😢
I've written a bit of an extensive guide on navigating ActivityPub and its many apps, and instances, along with some initial questions new users might have, and links to mobile apps.
But I'm a freedom of speech homie so I wouldn't complain about it too much; if the speech offends you, you should be able to block or mute him yourself on your end.
New filings reveal FBI authorized use of DEADLY FORCE when they raided Mar-a-Lago (notthebee.com)