D.eSystem 6.0.6 features an important bugfix for the desktop and the graphics,and it also got a new icon design on the desktop with D.UI 11.1

you can find it here: https://github.com/D-electronics-scratch/all_D.eSystem_versions/releases#release-v.6.0.9

Github main page from D.eSystem: https://github.com/D-electronics-scratch/all_D.eSystem_versions

wrote CLI in C++ to sort files. it's very simple, just download and use. if you a photographer, video editor or just need to sort some files, you welcome (link in post)

First thing since this is Lemmy I want to say up front this is in regards to a Windows app.

I like to make things sometimes, but I'm terrible at showing them off, is there anyone with a passion for making little demos that could help me out? I'm really proud of this little tool I made but I don't feel like I can really explain it to people well and a demo I could have in the GitHub description would really take it to the next level.

Thanks for taking the time to even read this!

I've been testing VPN services and somehow every one with a client has written their own. Proton, Windscribe, IVPN, Mullvad, AirVPN, NordVPN, and the list goes on.

Don't these services all do the same thing? Connect to a server to get a list of servers, then use WireGuard or OpenVPN to make a connection, and have some fancy stuff like split tunneling or a killswitch. It should just take configuration by adding profiles per service and it should be possible to use the same client.

What am I missing?

See also: Parse, don't validate (referenced early in the talk)

Ran into a situation last week that got me thinking about how most teams handle visual changes in production.

We pushed a CSS update that was supposed to fix button alignment on one page. Looked fine in staging. Looked fine in the PR preview. Got merged, deployed, and broke the card layout on three other pages because of a shared utility class.

Caught it about four hours later when a customer mentioned it in a support ticket. Not a great look.

What we tried

After that incident we talked about adding visual regression testing to CI. Looked at a few options:

• Percy — solid, but the pricing gets steep once you have more than a handful of pages and multiple PRs a day

• Playwright screenshots in CI — free, but you need to maintain baseline images and the diffs are noisy. Every font rendering difference across runners triggers a false positive

• Manual spot checks after deploy — what we were doing. Obviously not sufficient

We ended up going with Playwright screenshot comparisons but with a pretty generous diff threshold (0.3%) to cut down on false positives. It catches big layout shifts but ignores sub-pixel rendering differences. Good enough for now, but not ideal.

The production monitoring gap

CI-based visual testing only covers what happens before deploy. It doesn't catch things that break after — CDN caching serving old assets, third-party scripts injecting unexpected elements, A/B test variants rendering wrong.

Some teams run synthetic monitoring that takes periodic screenshots of production pages and compares them. That covers the post-deploy gap but it's a separate system to set up and maintain.

Curious what others do

How are you handling visual verification in production? Specifically:

• Do you run any visual checks post-deploy, or only in CI?

• If you use screenshot comparison, how do you deal with dynamic content (dates, user-specific data, ads)?

• Anyone running continuous visual monitoring on production pages on a schedule?

Feels like there should be a simpler answer than "maintain 200 baseline images and pray the CI runner has the same font rendering as last time."

Would be a terrible shame if lots of people opted out.

If you are a EU citizen you might also want to write a complaint to privacy@huggingface.co because they are collecting your personally identifiable information in machine-readable form which they are distributing to third parties.

Now that there's way more trash out there it feels irresponsible not to check for client side security