That is not how it is supposed to look, the end result should be at least a couple of inches wide.

Maybe you don’t need to ‘fix’ your retraction settings?

If it looks good enough, why bother?

Wasn’t aware of the test (SuperSlicer user here), and found this.

The tower has multiple notches, each one corresponding to a different retraction length. By looking at the tower after printing, you can see how each retraction length affects the print quality.

So check your surface finish and select the retraction value with the best looks.

Gonna recommend this to all my co workers.

It is not vulnerable to Windows viruses.

:-)

Blowtorch will heat this up way too hot.

Try to get it to a high enough temperature to insert filament to do a cold pull and repeat…

Electrical heat gun (paint stripper) is hot enough. Gas based torches will change the stiffness of your material and you will regret it.

Yes, physically getting bigger.

Dell XPS had a batch laptops going crazy and pushing the touchpad up.

You will recognize it :-)

This.

Using a CEC link will make things even more simple, but that might involve additional hardware. Those raspberry thingies have native CEC on hdmi. For x86 you might have to look at some extra hardware.

And of course, Kodi is an example of a 10 foot interface.

NetApp makes storage devices, just like Dell’s DataDomain.

Looks like the ad is referring to a ST6000NM0034, a drive from Seagate. Personally, I like to stay away from that brand as far as possible.

Have had good experiences with WD.

https://tukaani.org/xz-backdoor/

Check the links on that page.

Thanks for the pointer.

This is really huge, but people don’t quite understand that yet.

If this wasn’t caught, every system -running public sshd- could be hacked or abused/misused.

And I completely agree with the last words, corporate should pay foss projects!

Vlans firewall rules and something to route between the different networks.

This can all be achieved with pretty much every Linux installation.

Easydns.ca, no privacy issues. Nothing about me personally in the who’s db (.net tld)

Depending on the size, but I’ve had success with super glue and baking soda.

https://www.instructables.com/Baking-Soda-Reinforcing-Glue-Repair/

Exactly this. Foolish ideas from someone behind a desk.

Nerds and hackers will win this easily.

You got me there… :-)

Ender 3v2 as starter here, doubled the price with a lot of upgrades/modifications. Got it running rock solid with Klipper and a microswiss direct drive.

Grabbed the piggy bank and am now really satisfied with my voron 2.4.

But very pleased with the fact I started with the Ender and got to learn then basics.

As far as I can suggest anything; start with something with a large installed base, so it will be easy to find answers or (hardware) solutions to your problems. I can tell you, the installed base for Ender is large, but the quality of the hardware, is what you pay. And they are cheap…

Totally agree. People using cli are probably more skilled and their knowledge has been fed into these ai models.

So we will all end up with some mediocre level of knowledge, because the next input for the LLM 's will be more of the some old stuff. Flattening the curve and less innovation and smart ideas.

These kind of “solutions” are for a non existing problem. Looking at the investors, this is only about making money.

Forgejo ftw!

Self hosting here, also with runners to create a complete ci/cd line.

Still testing and fiddling, but I’m using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:

on:
  schedule:
    - cron: '5 2 * * *'
    - cron: '5 14 * * *'

jobs:
  build:
    runs-on: docker
    container:
      image: renovate/renovate:37.140-full
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Run renovate
        env:
          PAT: ${{ secrets.PAT }}
          GITHUB_COM_TOKEN: ${{ secrets.GITHUB }}
        run: |
          echo "Running renovate"
          cd ${GITHUB_WORKSPACE}
          renovate --token ${PAT}          

The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.

Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.

Absolutely!

Running local, self hosted forgejo with a few runners.

Now my code is neatly checked with pre-commit and linters, build when new tags are pushed, renovate is scheduled every 24 hours to check for new releases of stuff etc.

Just a few containers and a happy user :-)