Ok, I could be reading too much into it, but it really would be nice if maybe I wasn't the only one that mentioned maybe it's something they should look into?
@mousey Replace #Matrix with something more performant, reliable, and less resource intensive like #XMPP. Similarly, #Mastodon is probably the least attractive choice to promote for the #Fediverse. The interface is clunky, and hosting it is ridiculously expensive for large userbases. Consider #MissKey or #Pleroma instead. Much easier to setup and maintain!
Do any of the #Fediverse platforms have a function to swipe through a whole timeline of media/photos? I mean like in one post with several photos you can click/swipe through them, this function for a whole timeline.
Any Mastodon kompatible app? Maybe hidden somewhere in Pleroma?
Seit seinen Anfangstagen hat #Facebook penibel darauf geachtet, alle... zu #eliminieren.
Der einfachste Weg das zu erreichen, ist es, Firmen zu kaufen, die eines Tages zur Konkurrenz werden könnten.
I decided to move my Pleroma instance from my old cloud service to the new, free one (guess which one). The reason for moving is simply cost cutting. Turned out it it took more time than I anticipated.
First, I spun up a VM with specs I thought would be enough to host a Pleroma instance. I set up one with 2 cores and 12 GB RAM, and 100 GB block storage. Other than same number of cores this was an upgrade to the previous VM, which only had about 2 GB RAM and 60 GB block storage.
I largely followed the instructions here on backing up and moving instance. I stopped the Pleroma service, then dump the PostgreSQL database.
The rather tricky part is moving the files. Not only Pleroma configs, but also nginx config and systemd service file. I can recreate them, but it seems easier to just copy them to the new server. You can copy paste the text files, but what about the database dump? It was time for me to get acquainted with scp (secure copy). The database dump was about 792 MB, but it was transferred rather quickly.
The time-consuming part was restoring the database back when I was reinstalling Pleroma on the new server. When it was still not finished after 36 hours, I decided that the VM was probably adequate to handle day-to-day load for Pleroma, but underpowered for database restore task. I boosted the capacity by upping the processor cores to 8. I also did some PostgreSQL tuning (using PGTune).
I repeated the restoration task, and this time it was finished after about 12 hours. After the reinstallation task was completed I lowered the specs of the VM back to the original state.
Lesson learned: Database restoration task is very computationally intensive. When I searched around, the time-consuming nature of the task is apparently a known problem. I also appreciate the ability of cloud services to temporarily scale up VMs capability when necessary.
Other recent changes include updated Spanish translations, fixing the font shown when viewing a post's history, workarounds for buggy behaviour from #Mastodon, #Pleroma, and #Friendica servers, and more.
Any #Pleroma/#Akkoma users out there who have had any luck with the #bitlbee integration, or any other way of #IRC bridging?
I used bitlbee-mastodon on Mastodon before, but it breaks on Pleroma because of streaming API incompatibilities. There seem to be an open issue on Pleroma too which apparently hasn’t been actioned in years.
@zimpenfishsuggested here to use the native Bitlbee identica plugin, but I haven’t had any luck with that either.
Is there anyone currently working on these issues, or who has any alternatives at hand, before I try and do some more debugging myself?
Ya know, since projects like @nodebb have mentioned wanting to bring in #ActivityPub federation, I realise that that could end up being a strength of AP's implementations - choosing your preferred format of discussion.
A lot of us have been lamenting the loss of small community forums in favour of Discord servers, and Discord's own built-in forums leave something to be desired.
But it's struck me that since #Lemmy/#Kbin communities are easy enough to participate in on services like #Mastodon, #Pleroma and #Firefish - Why wouldn't federated message boards be the same way?
Hell, why couldn't a message board have a forum that's just a subscription to a link-sharing community? Why couldn't Lemmy/Kbin users be able to follow a forum?
There's some exciting inter-operability ideas to be had as software grows around this standard.
"This document is dedicated to all citizens of planet Earth. You deserve freedom of communication; we hope we have contributed in some part, however small, towards that goal and right."
If this "privacy setting" for #quoteposts is implemented with it enabled by default, the result will be disastrous. :reisensweat: Since there is no other way to enforce this setting other than #defederation, we are going to see Mastodon servers strong-arming those software developers who are "non-compliant" by threatening a #fediblock. :reisensweat: Developers of the -key and -oma families will suddenly have to scramble to make their implementation of #quotetweets compatible with Mastodon's "privacy-friendly" implementation. :satsuki_sadge: This way of "extending" the fediverse is not acceptable, and everyone who has opposed #Facebook joining the fediverse due to #EmbraceExtendExtinguish should also oppose this issue which just eventually leads to the same result.
Przeglądam Wasze wpisy i łapię się za głowę, ile osób zaliczyło covid. Maskujcie się, szczepcie się, uważajcie, bo mamy kolejną górkę. I chyba tak już zostanie...
:jahy_hmm: This is an index of any hobby related stuff I do. ([Buyfag], [YASD], [MineCraft IRL], [Obenkyo], [Shit Scripts], etc). Doing this so i could find and post hobby rated topics in one thread, separated from my shit posting. <<< Prev /thread
Separating Frontend and Backend versions (pleroma.social)