Fediverse-Serie: Pleroma & Akkoma: Einfache Kommunikation im Fediverse - GNU/Linux.ch
Pleroma und Akkoma gehören wegen ihrer Einfachheit zu den beliebtesten Diensten im Fediverse. Gegenüber Mastodon bieten sie default 5000 Zeichen und einige weitere Funktionen.
Herkunft und Einbindung ins Fediverse
Pleroma und dessen Fork Akkoma gehören einerseits neben Mastodon, Calckey/Firefish, Misskey, Foundkey und GoToSocial nicht nur wegen des Aussehens und Handlings zu der Sparte der twitterähnlichnen Microbloggingdienste im Fediverse. Es unterscheidet sich andererseits recht deutlich insbesondere von Mastodon, wobei das klassische Aussehen doch recht ähnlich ist - aber davon später mehr.
Wenn Du gerne eine Art Mastodon mit richtigen Microblogging-Möglichkeiten haben willst, dann würde ich tatsächlich stark zu Pleroma oder Akkoma raten!
Pleroma/Akkoma ist ähnlich wie Mastodon, aber übersichtlicher und mit mehr Funktionen: Es kann zusätzlich längere Posts (default bis 5000 Zeichen Länge) und Textformatierungen wie Markdown, "schöne Links", Zitate, Aufzählungslisten u.v.m. (was allerdings wie alle Textformatierungen nicht von Mastodon, aber von allen anderen Diensten dargestellt wird)....
Ückück und das Fediverse - meine neue Kolumne bei @gnulinux
Ein neues Projekt steht an und ich freue mich sehr. Ab diesem Monat werde ich regelmäßig für GNU/Linux.ch über das Fediverse schreiben, mal spezielle Projekte vorstellen, mal von Veranstaltungen berichten, mal einen Blick auf die Meta-Ebene vagen - es gibt jedenfalls genug zu berichten, dass ich eine Weile beschäftigt bin :D
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! 💪🏾
While folks are thinking of leaving #Mastodon, just a friendly reminder that #Pleroma let a known TERF (Alex Gleason) join the project and only kicked him out because of conflict over code.
Dobrym podejściem są też web-aplikacje starające się integrować wiele profili z różnych serwisów. Np. #Phanpy, który ostatnio integruje #Mastodon i #Pixelfed (jego Media-firt UI jest świetne).
Innym tematem jest uparte trzymanie się przez Mastodona obsługi jedynie typu Note (i ułomne wyświetlanie Article). A ponieważ Mastodon dominuje w #Fedi, nie rozwija się (tak jak mogłoby) wsparcie dla innych typów treści #ActivityPub: image, video, audio, artist, album, track, playlist. De facto obrazki czy filmiki albo audio to po prostu załączniki do typu Note, bo Masto tak ma i nic innego nie wyświetli :/
Więc IMO pole do rozwoju jest ogromne, nie trzymajmy się kurczowo jednego konta (to wymysł marketingowców budujących silosy), zostańmy przy jeden login do wielu usług, jeśli już musimy ;)
I think the fedi needs to be more about clients/apps than it is currently.
Agreed, and I kinda touched on this earlier about how the #Threadiverse should've simply been a frontend where people just use their main fedi account instead of having to create another account for forums in a link aggregator... :sagume_think:
Tbh all the #fediverse implementations in the first place should've been backends first and foremost. Why should I not be able to have #Misskey's frontend in #Mastodon or #Pleroma? And the other way around too. This does mean that we will have to all agree on a common client API and MastoAPI will dominate, but I'd rather have Mastodon dictate client API than fediverse implementations. :seija_coffee:
Tbh I think the #Threadiverse like #Lemmy and #kbin would make a lot more sense if they were simply frontends and perhaps a backend too but just for the forums themselves. IOW, no accounts live in Lemmy or kbin, all users post from their preferred #fediverse account instead.
Sure you can already technically do that from your #Mastodon or #Misskey or whatever fedi you're in, but that means using whatever app you're on right now, which almost certainly means it's not a #linkaggregator UI. Not ideal at all.
If I had any good programming skills I'd make it so that the link aggregator is merely a client that uses the Mastodon (with #Pleroma extensions too) and Misskey APIs, treat (almost) all #ActivityPub actors as their own forums or subs, and each post would be a boost from said actor. Users authenticate from their preferred fedi account. Voting would be tallied by few special actors, which internally receive votes via direct messages (the app will make this transparent, but this also means you can technically vote without the app if you know the exact command), which will effectively make votes secret to non-admins like in #Reddit. Users can also choose which vote counters they want to rely from.
This would make the fediverse-powered link aggregator very flexible and minimal, imo. It may look janky but that's the general idea I have. :seija_coffee:
I don't use them, but just for fun, I decided to try #tweesecake and #twblue on #pleroma. They both fail differently. First off, both require that you log out or authorization won't work. But if you log out then log in again while authorizing, they will. But at that point, #twblue will just crash. The error in the log says it's trying to do something with Pleroma that it doesn't implement. Tweesecake, on the other hand, pretends to work. It loads the messages and mentions buffers just fine. Then it adds exactly 160 items to the home buffer, all of them blank. If you leave it open, new items will stream into the home buffer. They, also, will be blank. I didn't expect either client to work; I just find the wildly differing failures amusing.
I made the way to delete some cookies from #Vivaldi#browser then cdrom.tokyo came back.
Tried to make a post with a gif image in. Suddenly cracked down and got blank. Had to delete the cookies again. Just sent some text, took some seconds to post.
Why it takes too long time for a post?
Why it fails when I upload an gif?
A popular multiservice scrobbler for Android, “Pano Scrobbler”, added scrobble support for #Pleroma and forks.
I haven't seen how it looks, and unfortunately I can't test it myself. It's hard to find a good Pleroma instance with an open registration, and my original Pleroma instance closed and I only found out a few days ago.
(I did found a good instance, but I haven't received the verification email yet, for a few days now. Unless there's an issue, or I typed my email wrong? Hahaha.)
Anyway, anyone tried it? Not Pano directly, but scrobbling to a Pleroma instance. How does it look? Is it posting one message per scrobble? Or, it shows on your profile only? Or, does it add a scrobble footer automatically when you create a new post?