Dec 15 00:16:50 pleroma: [error] Could not decode user at fetch <a href="https://www.threads.net/ap/users/mosseri/" rel="noopener">threads.net/ap/users/mosseri/</a>, {:content_type, "text/html; charset="utf-8""}
Dec 15 00:16:52 pleroma: [error] Could not decode user at fetch <a href="https://www.threads.net/ap/users/mosseri/" rel="noopener">threads.net/ap/users/mosseri/</a>, {:content_type, "text/html; charset="utf-8""}
@Zerglingman ⚠ Conversation IDs can be found in direct messages with the pleroma.direct_conversation_id key, do not confuse it with pleroma.conversation_id.
Found 4 new servers found and 10 servers de-listed since 1 hours ago. Check out the Monthly and Daily Stats by software or server or the entire fediverse.
24,583 servers checked. 13,741,344 Total Users, 1,731,428 Monthly Active Users today vs 1,741,129 yesterday for the entire fediverse.
Il seguente link lo consiglio a chiunque abbia voglia di pubblicare dei contenuti da condividere con le communities Lemmy. Naturalmente rispettando le regole del server.
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...
After rewatching this video of #ElonMusk melting down, I realize that the #Fediverse may have a new problem: 300 million #Twitter migrants seeking out new home.
If you are on a #Mastodon, #Misskey, #Pleroma, #Pixelfed, etcetera instance, you might want to consider sending some funds to the site owner (& Fediverse platform creators) as they will need it sooner rather than later.
I expect the cost of instances to increase further once #Threads embraces #ActivityPub.
I'll do it again in #english, maybe it is of interest for others too:
@heiseonline is on of the biggest official accounts on #Mastodon by a german media organization. It's now a year old and I had a look into the ~62k followers. Turns out, that federation in the #fediverse seems to work: Less than a fourth are from mastodon.social, the rest are on more than 1900 different instances.
YES!
This is precisely what every university (and scholarly society!!) should be doing: have their own instance and drop X like a hot potato:
"an instance has been created [... ] on university servers, which is open to the university's organizational units. The active use of X will be significantly reduced."
I wanted to try the default mastodon social instance to get the hang of it - and I know there’s all kind of specific-interest ones like for art, music, tech, games, etc. but does anyone out there have some recommendations for other decent, all-purpose ones?
Was mir hier auf #Firefish wirklich noch ganz dringend fehlt, ist die "Glocke" in Profilen wie bei z.B. #Pleroma. Die Benachrichtigung für neue Posts von wenigen Accounts.
Diese Funktion verändert die Nutzung von Social Media für mich sehr angenehm. Man könnte meinen, dass diese Benachrichtigung einen ständig wieder rein zieht. Bei mir beobachte ich aber das Gegenteil: Mit der Bimmel hört das Gefühl auf, etwas zu verpassen. Dadurch legt man den Tab viel öfter zur Seite. Ohne das beobachte ich mich, dass ich viel länger einfach rumscrolle.
Die Listen Funktion, mit der ich mir Favoriten zusammen klicken kann, ist da leider nur ein schwacher Ersatz für mich. Zum einen benachrichtigt da auch nichts, zum anderen kommen da halt dann bei Firefish auch Antworten auf andere Posts rein und nicht nur die originären Posts der Favoriten. Dadurch wäre das Geklingel dann auch wieder kontraproduktiv.
Vorschläge, wie man damit am besten umgehen könnte? 🙂
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.
Y a-t-il des admins Pleroma / Soapbox / Akkoma qui peuvent me confirmer si l'on peut empêcher l'indexage des moteurs de recherche comme le fait Masto ?
Most #bigtech social media platforms allow personalisation: like a profile picture or a header image for example.
What if we'd use these to advertise the #fediverse? Help those unaware of the existence of the fediverse to explore it & experience the Internet as intended.
Use those in-active Twitter/X, Facebook, Instagram etc accounts for some good!
What do you think? Could we organize something like this?
@zleap kindly serves a copy of a fediverse flyer we made in Feb 2021. Its only dated because it doesn't push #Akkoma but Pleroma, which no longer works in Tor. If our memory is correct #Pleroma slows Tor to a crawl. The flyer is based around the older icon. Is also probably too complex understand in some parts.
Nice to see the Pleroma team getting an NLNet grant so development can pick back up. I missed it when it happened but apparently there was a big shakeup with the Pleroma dev team. I'm glad they seem to be recovering from that and hopefully we'll see some sustained progress with Pleroma again.
Danke, das das Fediverse so bunt an Software ist und jeder seine Software finden kann. 👍
Falls ihr eine Funktion vermisst, liegt es vielleicht auch nur daran, das ihr die falsche Software für das Fediverse nutzt.
Mastodon scheint für viele zu reichen, nur ist Mastodon nicht alles
@caos Es setzen nicht alle Plattformen "Markdown" gleich um. #Pleroma macht aus Markdown HTML und sendet es dann so. #Firefish sendet "richtiges Markdown" - so viel ich weiss - das kann dann auch #Pleroma nicht richtig darstellen. @caos@kathakatze@nick
Separating Frontend and Backend versions (pleroma.social)
Pleroma Blog - We got a grant from NLNet! (pleroma.social)
Nice to see the Pleroma team getting an NLNet grant so development can pick back up. I missed it when it happened but apparently there was a big shakeup with the Pleroma dev team. I'm glad they seem to be recovering from that and hopefully we'll see some sustained progress with Pleroma again.