Sorry, I completely didn’t read all of your comment. You’re right about resistance but then again the filament won’t need to touch the enclosing coil at a large surface. In the usual bowden tubes, you have a lot of contact surface between tube and filament but this would not need to be the case in the drying coil. In the end it would all depend on the application. I’m not interested in very high speed printing (yet) because my machines are all pretty slow :).

You “just” need a longer distance inside the drying chamber. This could be achieved by coiling up the space where the filament travels through and guide hot and dry air through that space, ideally from the outlet towards the inlet. That air could maybe be pulled from the hotend cooler.

Argh finally someone tries the obvious solution. I was already considering it but was demotivated since it seemed so obvious and nobody seemed to have done it before.

This device could also probably be printed in PLA. I can’t wait until I get my lab power supply so I can give this a try with a wire coil heater.

Edit: you could even mount some PTFE tubing mounted below a heated bed and pass air through it. That way you could potentially get away without a heating element and re-use some power usually lost.

Not only this. It’s also old news.

Full agree!! I use the dev version too!

The 1.0 release is around the corner. It’s only a matter of a few weeks. It has the toponaming problem fixed and a built in assembly toolbox!

I’m interested to hear how it turns out!

Nice work! What does the optics look like? Do you have a picture of the whole thing?

KDE Connect is amazing. Also works without KDE.

Not true about xmpp in general. There are modern clients out there.

What’s your problem with xmpp?

Thanks for the interesting point! I learned something today. I guess it all depends on your use-case, whether flatpaks make sense or not.

A floss project’s success is not necessarily marked by its market share but often by the absolute benefit it gives to its users. A project with one happy user and developer can be a success.

I’m not against probabilistic models and the like. I merely try to capture part of the reason they are not always well received in the floss community.

I use LLMs regularly, and there is nothing rivalling them in many use cases.

Flatpaks won’t get their libs updated all at once by just updating a library. This can be very bad in cases like bugs in openssl. Instead of just updating one library and all other software benefiting from the fix, with flatpaks, you need to deal with updating everything manually and waiting for the vendor to actually create an update package.

I’m not 100% sure about this. Flatpak has some mechanisms that would allow to manage dependencies in a common fashion.

This and on top of being inexact, it’s not understandable and un-transparent. These are two of the top reasons to push for free software. Even if the engine executing and teaching models are free, the model itself can’t really be considered free because of its lack of transparency.

I think it’s a short term vs long term debate. In the short term snaps are nice. They might help you get that software you want right now. In the long term though, it will only take away some of your rights and make you into a product.

There are also some interesting things to say about wording. Specifically consumer vs user. Software is not consumed, it’s used and depending on the specific software, the user might be abused by the people producing and controlling the software.

I totally agree about rate limiting, mostly against bad passwords that you are not in control of. But banning failed attempts is mostly not interesting if you ask me. It feels like the right thing to do, but IP addresses can change and other measures are better.

It’s debated whether software like fail2ban actually helps or if it just makes attacks visible that would anyways fail if you have up to date software. Oftentimes, defensive software adds attack-surface because it adds more software that can be targeted by attackers.

Fail2ban might help with protecting against exploiting of bad passwords though.

I like the looks of them