beeb
Here are the same queries with Kagi (I was interested to see the difference)
Something like this is a good start! I use transmission as the torrent client instead of deluge. Also added a service for my vpn and use that as the network for the tranmission service so all traffic is routed through the vpn. https://ochoaprojects.github.io/posts/PlexAutomation/
Personally love Piped and the LibreTube app. I'm using the smnz.de instance for steaming and adminforge.de for authentication. Been super stable over the last few months. AFAIK Piped acts as a proxy between you and the yt servers so they have no chance to gather data about you. Not sure invidious works the same.
Just use an alias, it's anyway a good idea to find a provider that lets you create unique aliases for each account.
Been using DuckDuckGo for a long time but I recently trialed Kagi and have been quite impressed! It's not free but hopefully it keeps the enshittification away for a bit longer.
Got in touch with ProtonVPN support and asked about this. Here's their reply:
Our engineers have conducted a thorough analysis of this threat, reconstructed it experimentally, and tested it on Proton VPN.
We concluded that:
- The attack can only be carried out if the local network itself is compromised
- Our Windows and Android apps are protected against it
- For iOS and macOS apps, you are completely protected from this as long as you're using a Kill Switch and a WireGuard-based protocol (our apps use them by default, and if a user wants to use something other than WireGuard derivates, they'd have to manually set it up). Note that Stealth, WireGuard TCP and Smart protocol on iOS/macOS are all WireGuard-based.
- For our Linux app, we're working on a fix that would provide full protection against it.
Interesting, that would confirm the pressure advance as the likely culprit (speed and acceleration are taken into account in the algo). Maybe your slicer has a bug related to this? If changing the value wildly does not improve or worsen it, then it might not be calculating what it's supposed to. Can you try another slicer?
All seems to indicate something related to pressure advance, whereby the printer thinks it needs to extrude less because of some pressure buildup but it underestimates how much is really needed. Does it happen if you print slowly? E.g max 15 mm/s or less.
Here (didn't find the right one, almost)