Oh, I didn’t mean to come off as dissing Prusa in general. I ponied up for an XL and it’s night-and-day better than any previous printer I’ve owned.

If this was during an auto level, it’s my humble opinion that this is a manufacturer’s defect in the machine that caused the damage. There should be proper coding to ensure that any increase in sensor pressure by (delta p) halt that machine and that there should be a pressure offset in the sensor such that a loss of signal or anomalous zero reading or lack of reading is done prior to levelling to ensure that a sensor failure has not occurred. My XL freaks out if a fan isn’t spinning at the right speed, so they clearly know that a nominal operational check before the print starts is proper engineering design.

Of course you won’t get anywhere. Unfortunately, a lot of 3D print failures really are user error so I suspect that’s their default response and it takes them a good deal of proof to push them of that mark.

XL feels like using cheat codes.

If you print with incompatible filaments (materials which don’t bond/adhere) you can get cheap, nearly perfect breakaway supports. I’ve done some rocket parts on my PrusaXL and it’s certifiably magic.

But Meta can already do that through user accounts or through a honeypot/passive instance, correct? All public conversations are open, as are all public user profiles.

The only solution is to fight it and kill it.

That’s like saying the only way to get out of being hit by flying debris is to eliminate all wind on the planet. As much as we like to think of Threads as some corporate being, it’s not. It’s a hundred million people that are made of meat and have day jobs like you and me - the wind - and a few million bots and controlled accounts which attempt to influence [whatever their master wishes] - the debris. The debris is already here, and it’s people too - just people with nefarious or profiteering intent. It (debris) happens whenever there are enough people (enough wind) to stir things up.

Cutting yourself off from people is the only way to prevent it because it’s an inherent function of humanity.

My issue is that it’s an inefficient use of human resources because it clutters the interface. If you’re looking for the answer to a question, you have to post in multiple places and/or search/review multiple communities to see if the question has already been answered. For low-traffic communities the replies get split, suppressing topic participation. For high traffic communities, stories/links that get posted to the “same” community on multiple instances clog up personal home pages and - in the case of large participation - clog up the top feed.

Again, imho, there should be a way for communities to aggregate or sync across instances and be shown as a single feed, like a symlink to multiple folders that is treated as a single location for end users. I realize this causes moderation concerns. I still think its better for the participants.

Oh no, a new discussion board is neither as robust nor as polished as one with over a decade of use and revision.

Most of the complaints are just whining that Lemmy isn’t a perfect drop-in replacement for his love of endless, constant time wasting on Reddit. OTOH, the issue of multiple, nominally identical communities on Lemmy is a true weakness of the platform (imho, of course).

They’re wrong, of course.

You don’t have to enter a license key.