A reminder to move to smaller instances for a better experience
A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.
Github Issue 2910 is the kind of PostgreSQL problems that the developers ignored for months and people still defend the developer choices to have the code doing real-time counting of every single comment and post for numbers nobody needs to needs done in real-time.
PostgreSQL is voodoo to this project, they do everything they can to avoid going to !postgresql@lemmy.ml community and asking for help, learning 101 about how to fix their SQL TRIGGER logic like Github Issue 2910 spelled out June 4.
I know you are salty about how you are getting treated over at GitHub, but you should look at it objectively, Blaze is clearly advocating that people join top instances that’s not lemmy.world or lemmy.ml, not nobody instances that only have 1-2 users. They certainly aren’t going offline as quickly as they come online.
I know you are salty about how you are getting treated over at GitHub
No, it isn’t about my personal treatment. It’s about the cultist attitude you have towards Lemmy and the leaders without any ability to see what they are doing behind the scenes with the code. I know cults and religious faith is how many people enjoy the world.
A 2-line SQL TRIGGER removal takes about minutes to fix. It was crashing the entire site constantly. They sat by and asked for donations of money.
A 2-line SQL TRIGGER removal takes about minutes to fix.
Then go fix it and open a PR
No, it’s everything to do about your personal treatment, stop deceiving yourself. Just because you claim you have autism doesn’t immediately grant you the right to be entitled. You don’t get your way so you spam create multiple issues to call out the developers, and you expect people to believe it isn’t personal for you?
If you aren’t happy with the Lemmy developers, fork the project, run your own fork, convince others to use your fork. It’s a FOSS world, no one has to do what you say, even if you claim to be autistic.
What is a SQL trigger and why is it taking down servers? Do you know how to fix it?
A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.
I am always advocating for any of the top 25 instances that are not Lemmy.world or Lemmy.ml
For the rest of your post, I don’t know what that has to do with people aggreating on LW.
For the rest of your post, I don’t know what that has to do with people aggreating on LW.
aggregation refers to the lemmy database tables, site_ aggregates, community, person. The SQL TRIGGER logic lemmy_server uses that has been the source of so many crashes the past 60+ days.
A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.
And this will always… always be the biggest problem in the FOSS community.
“I dont like X, so I’m going to leave and make my own version of X”
So userbases get spread thin, manpower gets spread thin, developers get spread thin, and the user experiences degrades for everyone until it pushes them back to the bullshit websites and products.
This is exactly what federation is meant to solve: power in numbers without the centralization. Is that so hard to understand?
Sometimes I question why people not in favor of the decentralization are commenting on a Fediverse platform. Why not go to Tildes, Squabbles or another centralized alternative? There is plenty of fish in the sea.
For the rest of your post, I don’t know what that has to do with people aggreating on LW.
And, factually, the project leaders telling everyone to create 1000 new instances and shutting down sign-up on Lemmy.ml caused more performance problems.
They had a bug in their PostgreSQL TRIGGER logic where 1500 instances were updating + 1 comment and +1 post counting instead of WHERE site_id = 1, a single database row. So each new Lemmy server that went online made the table larger and crashes more frequent on lemmy.ml
The amount of disk writing by lemmy was ignored
They’ve neither told people to create 1000 new instances, nor have they closed signups on lemmy.ml.
Again, you should really stop revolving your entire life over one GitHub issue, and go touch grass.
The developers of Lemmy seem to make every effort they can to avoid using Lemmy itself to discuss their !postgresql@lemmy.ml learning 101. They have made massive mistakes in SQL TRIGGER logic that they avoided to such a degree that their social motives are in question now. Github Issue 2910 was opened June 4, almost a month before the Reddit API deadline, and they ignored it. Just like they hang out on Matrix Chat and don’t use Lemmy their own self to discuss code.
They have cultivated a kind of voodoo attitude towards PostgreSQL where people using Lemmy won’t actually scrutinize the Rust code or PostgreSQL tuning parameters.
I mean having a bunch of new servers is not a problem. Just choose one that’s been up for a while and more stable.
You can also just have multiple accounts. I have one on lemm.ee just for this reason.
Yeah, I have .world where I first signed up. It occasionally had some issues so I added another that I just mostly read on if the other isn’t working
It’d be nice to export/import subscriptions but I’m sure eventually the servers will get past it
You can use that script https://github.com/CMahaff/lasim
I’m afraid that as long as you have to go to github and run such scripts for these things, Lemmy will stay a nerd-only place.
That was my main. The instance vanished faster than cotton candy being held by a raccoon standing in a pond.
It’s funny, at this point I don’t feel like I even have a main account. I just randomly pick an instance every time I go Lemmying
Same, I have accounts on lemmy.ml, lemmy.world, and Kbin.social. I’m just waiting for a good app to be compatible with Kbin. Right now all the apps coming out are geared toward Lemmy.
I forgot that I had a lemmy.ee account and set up my own instance a few days ago while lemmy.world was down.
Right now it’s just a free Google cloud VM instance and a $3/year domain. It was super easy to set up with Lemmy-Easy-Deploy and I’ll never have an issue with going down. I’ll either be busy looking through Lemmy, or busy trying to figure out why it went down!
Is there a readily available tool that can export/import community subs? I have two accounts on different instances but would like them to have to same subscriptions
I’ve not used it myself but heard good things about https://github.com/CMahaff/lasim
Lemmy.one, my instance of choice, has been down since Thursday - just a reminder that smaller instance isn’t always the solution. Having a few solid account choices on multiple instances is the way to go.
It’s a bit frustrating though. If I didn’t know better about the fediverse, I would’ve thought Lemmy in general was down, with no heads up or somewhere to see what’s going on.
Lemmy One still down by the way
I have a few for this reason. Is there, or perhaps will there be a way for subscriptions to the shared across accounts?
Maybe this is already I thing and I’m oblivious.
I haven’t had a chance to try it yet but here is this:
Lemmy.dbzer0.com is pretty stable, both in terms of release timing/server uptime, and also in terms of not flooding your feed with “politically instable” instances on both sides. Avoid the echo chambers.
Quoting myself from a previous post:
First of all, it’s really fine to stay on LW for now, no need to rush anything. But if at some point you have some time for this, then read the following.
So, to pick your instance, you can have a look at https://lemmy.fediverse.observer/list, filter by “1m” to see what are the most popular ones. As you can see, with a 27433 monthly users, Lemmy.world is by far the most popular, which is why you might experience some issues from time to time.
You should have a look at the next instances on the list. Short story: lemm.ee, sh.itjust.works, lemmy.one, sopuli.xyz and reddthat.com are solid choices.
You are looking at instances with quite a lot of people (the more people help with filling your “All” feed), just not the most populous one (lemmy.world), the original one (lemmy.ml), and instances that are too specific, either due to country or specific focus.
Long story:
spoiler
- lemmy.ml is the original insance, also quite crowded, not really the best choice
- lemm.ee can be nice, you can have a look at it and see how fast it is for you. The admin communicates a lot and is very helpful.
- sh.itjust.works had some rough time in the last few days. You might also not like the name, that’s okay.
- beehaw.org does not federate with the big instances, so if you go there, you will be in their own space. It can a valid choice, but please have a look at their guidelines first, they tend to moderate a lot. Can work for you, or not.
- feddit.de, lemmy.ca, discuss.tchncs.de, feddit.uk, aussie.zone are country specific instances, so probably not interesting to you if you are not from there
- lemmynsfw is a NSFW instance, probably not the one you want to move to
- programming.dev is an instance focused on programming
- lemmy.blahaj.zone is a pro queer instance
.
To migrate your settings (including subscriptions and blocked instances), you can use that script: https://github.com/CMahaff/lasim
I think there is a huge misconception many people have that a larger instance is more likely to stay around, but due to the nonlinear costs involved in hosting fediverse instances this is not true.
Basically there is a sweet-spot around a few thousand (~2500) members where costs are low enough for a single admin paying things out of their own pocket long term is possible, but also enough members willing to occasionally donate or contribute otherwise to cover costs.
To be honest, I know it’s a controversial view, but I would almost like to see Ruud and the LW admins block registrations for a while, along with a communication “Have a look at those other instances, they are well managed, you can access all of Lemmy just as well from there”
I’m not looking forward to 5 years from now, where instances like this are the mastodon.social of federated reddit-likes. As much as they should block registrations, I don’t think they will. …but I have a hat on stand by, just in case I need to eat it.
If anyone’s looking, my instance is open for everyone and I plan on supporting it long-term. https://lemmings.world
LASIM author here, ironically on my own alt: Just an FYI that support for Lemmy 0.18.3 is not yet out, but keep an eye out for it soon (I have it working on a branch but I need to test it more before release).
This is the first breaking API change since it’s creation, so here are the limitations:
- Old version (0.1.2) will only support API 0.18.1 and 0.18.2
- New version (0.2.0) will only support 0.18.3 (and above until there are more breaking API changes)
- Profiles downloaded with 0.1.2 (and below) will automatically be converted to work with 0.2.0.
So that all means:
- You can use the old LASIM to migrate between 0.18.2 Lemmy instances
- You can use the new LASIM to migrate between 0.18.3 Lemmy instances
- You can use the old LASIM to download from an 0.18.2 instance then use the new LASIM to upload to a 0.18.3 instance
- You cannot use the new LASIN to download from a 0.18.3 instance and then the old LASIM to upload to a 0.18.2 instance (unless you are comfortable doing some manual work editing the JSON file so “old LASIM” understands it).
This will be true of every release with breaking API changes.
EDIT: PR is out. Once it builds, I’ll publish a new release! https://github.com/CMahaff/lasim/pull/21
EDIT 2: Release is published! https://github.com/CMahaff/lasim/releases/tag/v0.2.0
Thank you for the heads up! You might want to add that to the ReadMe on your Github
Removed “and above” from page and instead added a note to always get the latest version if your version isn’t listed as supported explicitly.
Thanks for all your hard work on this. I’ve used lasim to transfer my subscriptions to my other accounts on other instances when the lemmy.world downtimes happened last week. I love the portability of the tool.
Fwiw, sh.itjust.works is a horrible name, but a great instance lol.
What’s funny though, I’m getting beehaw posts in my all feed since yesterday. No idea if they’ve refederated with us, or if it’s an artifact of connect (my app of choice), or what,
Interesting. You are still on the list of their blocked instances, so I’m not sure: https://beehaw.org/instances
Must be some kind of weirdness with the app then. Thanks for looking at that!
geddit.social is a another good server, I have alt there. It’s run by @stux@geddit.social who has his own hosting company and also hosts mstdn.social.
The DB migration at the end of this upgrade is significant, I was surprised how long it took when I upgraded my instance. Lots of room for things to go wrong considering the size of their DB.
That makes sense, especially how large the instance is. Just curious, how long did the migration take for you? Half an hour?
Took me the whole day. The new migrations require PostgreSQL version 15, and my Akkoma and Lemmy are using a shared database server of version 13. First shut down both services, then update Debian from 11 to 12, PostgreSQL from 13 to 15 and after all this, redeploy Lemmy to start the migrations. The new Lemmy queries use more RAM compared to the previous version, so the database was getting OOM and I needed to upgrade to a bigger instance.
Not fun, but everything works now and is stable.
