jokeyrhyme

Howdy, folks!

I'm teetering on the brink of connecting my Sovol3D S06 ACE to my wireless network, but I'm pausing because this device can make physical real-world actions like:

• record photos and videos using its built-in camera
• shaking so much that it manages to knock itself on the floor
• melting so much plastic that it dribbles all over itself and then all over everything around and beneath it
• consume lots of electricity and cost me a fortune on my utilities bill
• burn the house down

None of this happens in normal usage, of course, but watching it self-calibrate did make me wonder:

• how safe the firmware is?
• is it retrieving instructions from Sovol3D or some other party by itself?
• is it sending records of my print jobs to a 3rd party?
• is it sending photos and videos to a 3rd party?
• how safe the firmware is once its receiving arbitrary network traffic?

All IPv4 traffic from the internet goes through a NAT/firewall that I conceivable control, but my devices all get public-facing IPv6 addresses, and the default SSH password on all of these printers is publicly-documented

It looks like the Sovol3D S06 ACE firmware is https://www.klipper3d.org/ + https://www.obico.io/ + some unknown amount of stuff that Sovol3D adds on top, and it doesn't seem like they've kept the public source code up-to-date: https://github.com/Sovol3d/SV06-ACE

I do already self-host https://www.home-assistant.io/ and plan to integrate the 3D printer with it, avoiding any cloud behaviour as much as possible, but I'm wondering if anyone else has already done this and has any advice on what to avoid?

Cheers! <3

After immersing myself in 3D printer content on YouTube and Lemmy, I'd talked myself all the way up to spending AU$2000 which is just absurd for a first timer, but then talked myself into the Sovol3D S06 ACE as a decent starting point, haha

Anyhow, I'll be running this in my garage (garage door open) and I think the first batch of filament in the pack is either PLA or PETG, which seems beginner friendly

I've been wondering about 3D printer profiles and calibration in slicer apps... is there a way to print as many benchies that will fit on the bed, but each which different profile parameters, so I can see which profiles do or don't work best? Or do current slicer apps always produce a plan that uses the same parameters for the entire job?

Note that I'm 100% on Linux (no Windows here), so I'm probably limited to https://github.com/prusa3d/PrusaSlicer or https://github.com/SoftFever/OrcaSlicer (or maybe https://github.com/GladiusSlicer/GladiusSlicer if I'm in the mood for contributing my own code)

I've consumed probably too much YouTube at this point, but any especially important hints and tips for a first timer would be appreciated!

P.S. oh, just noticed, https://lemmy.ml/post/23597074 thanks!

My desktop PC is the only machine in the house having Wi-Fi connectivity issues (connects fine, but drops out randomly after a few minutes or sometimes a few hours)

I think wpa_supplicant is getting confused and thinks signal strength is poor (I have a Netgear mesh, but this seems increasingly common, so it's weird for that to be the issue)

I did pick up a TP-Link USB Wi-Fi adapter, but can reproduce the same connectivity issues

The fix was switching away from wpa_supplicant in favour of iwd, which seems rock solid in comparison

I'm sure there's a way to fix wpa_supplicant, but it's man pages only seem to list the options without actually describing what they do, which seems sort of poor considering how old the project is 🤷

cross-posted from: https://lemmy.ml/post/1073275

Great explainer / FAQ

I'll probably still use my Precursor and Yubikeys for the most part, but I'll definitely enable Passkeys wherever they are an option

That’s why later this summer, we're launching a refreshed Find My Device experience that makes it easier than ever to locate your devices and belongings quickly and securely by ringing compatible devices or viewing their location on a map in the app – even when they’re offline. The new Find My Device network will harness over a billion Android devices across the world to help you locate your missing belongings like headphones, tracker tags, or even your phone via Bluetooth proximity.

This earlier announcement about a joint effort with Apple to work out how stop stalkers and other criminals from abusing these networks now makes a bit more sense: https://security.googleblog.com/2023/05/google-and-apple-lead-initiative-for.html

We can take a few guesses as to why things are so big. First, Samsung is notorious for having a shoddy software division that pumps out low-quality code. The company tends to change everything in Android just for change's sake, and it's hard to imagine those changes are very good.

...

Unlike the clean OSes you'd get from Google or Apple, Samsung sells space in its devices to the highest bidder via pre-installed crapware. A company like Facebook will buy a spot on Samsung's system partition, where it can get more intrusive system permissions that aren't granted to app store apps, letting it more effectively spy on users.

Urgh, it's so frustrating that Samsung is the leading Android manufacturer, the market is rewarding greed and incompetence

Huh, I have mixed feeling about Google doing this

Yay that Apple isn't the only game in town for this functionality

But then it's this functionality in particular with all the horrible stalking that it facilitates

I switched over to the completion plugin that is part of https://github.com/echasnovski/mini.nvim and I'm impressed with how suitable it is for my use case without any configuration

Sure, it's not as extensible, but it's so set-and-forget and still gives suggestions from LSP

On the whole, I would rate the Poco F1’s bull**** level as follows:

• Initial setup: miserable
• Ongoing problems: minor

Interesting look at UX for decentralised systems