squaresinger

But if you enable "Avoid crossing perimeters" this problem will still not occur.

Since OP mentioned a switch from Marlin to Klipper, it could also be acceleration settings or something like it.

Might be. I'm neither Brit nor American, so I learned both.

Hopefully. Because right now this is not a simple bug but engrained in the core concept of how Lemmy works.

Sure the designers of this monstrosity thought, "There are only black people living there, so it's a win-win" -.-

Lemmy is setup quite ok to scale users and traffic, since the users are (theoretically) distributed over many instances. In reality it doesn't work out perfectly, since people generally are more likely to join the biggest instances, so there's quite an imbalance there.

But what's worse is content replication. As soon as an user requests to look at a community for the first time, the whole community will get completely replicated on that user's instance. So any decently sized instance will pretty much replicate almost all communities, at least all that have content.

There is no scaling or storage balancing mechanic here. Even if no user ever touches that replicated community again, it will continue to be replicated, will fetch all new posts/comments and store them in the instance.

There is also currently no workaround to this (like there is for users/traffic, which you can just tell to join a different instance).

So if Lemmy ever gets to the point where gigabytes of data gets posted every day (which is only about 1000 pictures a day) storage demand will get so high, that hosting an instance will be seriously costly, which will probably lead to instances without any kind of cash flow shutting down, which will in turn lead to more users and thus traffic on the remaining instances.

I guess, that's one of the biggest technical (and conceptual) roadblocks that need to be addressed if Lemmy ever grows that big.

Potential solutions:

• Coasting/Wiping before travel
• Linear Advance
• Tuning retraction
• Or completely side-step the issue by turning on "Avoid crossing perimeters"

The last one should really be default-activated. It avoids so much stringing and ugly outside surfaces.

Yeah, it's really hard to pinpoint such simple inventions.

Correct :)

Maintaining Open Source without being paid by a company to do so is terrible. I made a few Open Source projects and never will I do it again. I do contribute a fix or something every once in a while if the issue really annoys me in my usage, but I will never again take any active role in an open source project.

People take your work for free and then attack you for not doing everything they ask for, equally for free. It's just not sustainable.

The U2 metro line. No way in hell would I use the highway parallel to it in rush hour. There are many nicer parking spots than that highway.

Both Dr and Dr. are possible.

But shouldn't "w/o" then be written as "w/o/"?

And "N/A" omits more than one sylable in "applicable".

I guess it's a grown system.