Login

u/Savenz

r/projects r/ender3v2
▲ 2 r/ender3v2

Help with potential leveling issue

Hi everyone,

I just got the Ender 3 v2 second hand and it’s my first 3d printer.

I noticed during some prints that after leveling each corner with the paper method the purge line seems to place well but when going to the middle the skirting seems to get stringy and lift off. I am using the stock glass plate but notice marks from old prints on it not sure if that would impact it that much.

On my last print I changed the offset -0.06 and it seems to be better.

Do I have to consider having to change the z offset everytime when the skirting is placed to ensure I get a good first level? Or do I need to replace the plate?

I appreciate some advice 👍

reddit.com
u/Savenz — 22 hours ago
▲ 1 r/projects

Hi everyone,

I’ve been using LLMs a lot for projects recently, and I noticed a recurring issue: they love to hallucinate dependencies. They’ll suggest a packages that sounds perfectly plausible, but simply doesn’t exist.

The real danger isn't just the 404 error, it’s the supply chain risk. If a developer blindly installs a hallucinated package and an attacker realizes that name is "trending" in LLM outputs, they can register it and you’ve just invited malware into your build pipeline.

I built SlopShield to automate the cleanup of this "AI Slop."

It’s a CLI tool written in Go that scans your project manifests and runs them through a few detection layers:

  1. Registry Truth: It hits the official registries to verify existence.

  2. Typosquatting Detection: It uses Levenshtein distance to flag packages that look suspiciously like popular libraries (e.g., lodsh vs lodash).

  3. Reputation Check: It flags packages created suspiciously recently (e.g., < 14 days old), which is a common pattern for supply chain attacks.

I tried to make it as robust as possible for actual production use:

* Fast: Uses a thread-safe in-memory cache so it doesn't re-check the same deps in large monorepos.

* Polite: Implements token-bucket rate limiting per ecosystem so you don't get your IP banned.

* Clean: Full context.Context propagation so you can cancel it with Ctrl+C and it won't hang.

* CI-Friendly: Can output SARIF for GitHub Security tabs or raw JSON for custom scripts.

I also included a "prober" tool that can hit OpenAI, Anthropic, Gemini, and Ollama simultaneously to harvest new hallucinations and build a local database of known bad actors.

It’s open source and I’d love to get some eyes on the code or hear about any hallucination-based close calls you've had.

Repo: https://github.com/savisaar2/slopshield (https://github.com/savisaar2/slopshield)

u/Savenz — 2 months ago