So, basically the platform you stopped to use increased the incoming traffic and even makes the half of the "Mastodon" traffic in the last days? Doesn't this show how important this source is and how much potential there still is?
Next, I'm wondering why "Mastodon" is defined as "Mastodon". #Mastodon is one of multiple solutions in the #Fediverse and I'm more than pretty sure that many people are not using Mastodon, rather than #snac / #snac2, #GoToSocial,... It's like setting "Internet Explorer" as a synonym for browsers.
I've been getting a lot of Mastodon sidekiq errors: ActivityPub:ProcessingWorker "ActiveRecord::StatementInvalid: PG::CardinalityViolation: ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time HINT: Ensure that no rows proposed for insertion within the same command..."
It always comes back to a post that is from "snac/2.71"
The specific argument starts out with:
post ID (I think), "{\n \"@context\": \"https://www.w3.org/ns/activitystreams\",\n \"type\": \"Update\",\n \"id\".....redacted
Snac2 is an excellent software solution for accessing the Fediverse. It is lightweight, very easy to compile and install, has minimal dependencies, and the development is progressing along a clear, clean, and logical path - thank you, @grunfink
Since last December, BSD Cafe has had, among its services, a snac instance - https://snac.bsd.cafe - which has been used sparingly, mainly by some for testing purposes. I’ve kept it as a 'testing' option.
In light of the interest it is generating (we now have stable users) and given that development is evolving to allow for both inbound and outbound movement, I have decided to designate it as a stable solution for accessing the Fediverse and to consider it a primary service of the BSD Cafe.
It has always received the utmost attention, I have consistently updated it promptly, and it has always been accessible, but I have also modified all the descriptions to clarify that it is a stable and definitive solution.
For more information, there is always a dedicated page on our wiki: https://wiki.bsd.cafe/snac.bsd.cafe
Stay Tuned!
A small compendium of the Fediverse platforms I use/know well.
In the past few days, I revisited some of my old Fediverse instances since some friends asked me to help them set up a new one. I also took the chance to perform maintenance on some leftover instances. Here's my experience:
Akkoma: My oldest instance still running, opened in 2022. It was offline for a few months (3/4). I updated everything to the latest version and restarted it. I’m not sure why, but it’s extremely slow, with a heavy load on Postgres and many queries just to open the main page. I like Akkoma - I'll investigate further.
GoToSocial: I updated a friend's instance - GoToSocial itself was up-to-date, but the underlying system wasn’t. I noticed that once it exceeds 2000 followings, it becomes a bit slow. The database is PostgreSQL, but that's not the issue. The GoToSocial process becomes somewhat heavy on the VPS. Still, it's very usable and a software with great potential, in my opinion. The Mastodon API is implemented quite well and works with the major software.
Mitra: It seems well-built. The person had around 1000 followers and followings on a Mastodon account, which they moved from a large instance. No speed issues, though sending a message makes the server “heavy” for a bit, but it’s temporary. The Mastodon API is partially implemented, but the software is advancing quickly, and I find its native interface quite pleasant.
Snac2: I've always had a soft spot for Snac2. The lack of a database and some design choices make it an excellent solution for small instances. For example, sending posts to all known instances increases visibility and interaction. Its basic, JavaScript-free interface is very clear, though it might not be the best for those used to Mastodon. But the Mastodon API is improving version by version, and I think the developer is doing an excellent job. It struggles a bit with larger numbers, but that's due to the underlying file system, not the software itself. If "move" support (both in and out) were added, I would recommend it to anyone starting self-hosting for single-user or small community instances because "move" is one of the options that gives the most freedom in Fediverse software.
Mastodon: My “old” personal instance was stuck at version 4.1.x and had been offline for a few months. I updated the FreeBSD Jail and upgraded Mastodon to 4.2.12 and then to 4.3.0-beta1. No issues. I also helped a friend (who had an old Pleroma-based instance they barely used) migrate. This user has around 5000 followers and followings - Mastodon is running on FreeBSD on a VPS (arm64) for just over 3 euros a month, with no significant issues (apart from media storage, but that's not Mastodon’s fault). Mastodon is sometimes said to be heavy, and that's partly true, but its modularity ensures that even in cases of overload, queues may slow down, but navigation and the local timeline remain reasonably fast. I think this is a good thing for any larger-scale use of an instance.
In short, I think things are moving in the right direction, and the software is evolving nicely. Well done, devs!
apologies to everyone getting re-follows from me: I re-made my instance using #pleroma as I think I was getting too ambitious with my amount of follows and #snac kept crashing under federation of outgoing messages (as far as I could tell anyway - read down, this is now fixed!).
Absolutely love snac, grunfink has done an awesome job and I think for more instances that people might expect, it is badass.
So yeah, will be progressively adding back follows, hopefully not too many instances have a tantrum that I re-used the user/domain on a different setup...
edit: just now have been in contact with grunfink, so might do further testing on snac in future since only myself and one other have run into this issue just now.
re-edit: fix tested and worked perfect! I would definitely suggest anyone considering a simpler way to do a social media instance, to seriously look at snac. #snac2
I will leave this instance here as the main one though from now on.