Where is antifa? Is it here in this room right now? Point at where antifa is….

Paige, no, no, no, no, no!

MoCA is a way to send wired Ethernet up to (300mb/s, at least the version i have) over coax. Verizon fios would provide these devices to send internet to set top boxes over existing coax cabling, but you can get a pair of these devices and send Ethernet in on one side, and Ethernet out the other side.

I have noticed however, it adds a bit of latency to the connection, which may be trouble.

⟋etc⟋passwd ⧸etc⧸passwd ／etc／passwd

Depending on your use cases and apps, file locking can be problematic when sharing across SMB and NFS simultaneously, their locking semantics are slightly different

I think it’s not widely front-and-center because it’s kinda fiddly, especially with folks with customized printers and there are caveats that can damage the machine or ruin the print if you are not careful. Sadly, I think that some of the more ‘closed’ slicer/printer systems could support it more reliably because the dimensions of the head + arm are much better known and the tool path can be planned much more precisely.

https://help.prusa3d.com/article/sequential-printing_124589 <-- explains how to set up the sequential printing in Prusa.

https://www.klipper3d.org/Exclude_Object.html <-- Explains the exclude object function in Klipper/Mainsail

https://docs.mainsail.xyz/overview/slicer/prusaslicer#enable-exclude-object <-- how to configure Prusa to label objects so mainsail/klipper can individually select and skip them.

Like I mentioned, I have the most experience with Prusa + my Ender3 ( w/ a RPi3/Kilpper & mainsail; and a crtouch sensor) . I’d wager that other slicers could do this too, but I"m not sure of their setup.

Keep in mind that if you slice multiple parts to be printed at a time, then a failure on one part means the whole batch is potentially compromised.

I have the most experience with PrusaSlicer, and have used the multiple part one at a time option to print multiple parts at once. You have to tell it the dimensions of your extruded head, so it doesn’t crash the part , and if you have a bed slinger, you have to be careful of your x axis bar (ie, order it so it starts at the front if the bed and works it way to the back)

With mainsail and klipper, you can cancel one failed part mid print and keep going on the rest of the parts.

It’s not the Muslims, it’s the evil Christians. Same problem, but different names.

It’s uncommon for ‘public use’ ethernet ports to exist, unless they are clearly labeled. The ethernet ports might grant access to the internal network, which, is easy to accidentally do. A non-profit library with a limited budget might overlook all the extra protections on open ports (enable/disable ports as needed, use 802.11x port-based authentication, internal SSL, etc), that would be necessary to secure it. Or, even better; that RJ45 port might be wired up to an old PBX, and you may have fried their telephone system, or your own hardware.

The Germans have Russians. :-/

Passkeys are great, and generally a plus for security; but (a) all the most popular implementations have not implemented key export and transfer to alternate implementations (b) It includes an implementation ID + hardware attestation feature which can be used to disable ‘unapproved’ implementations by key consumers. Considering the most common device with a ‘secure’ environment, and can implement this are your cell phones, and they are made by Apple + Google, this effectively locks your identity to either of these platforms. © All the public signals smell and look like the providers (apple, google, Microsoft) are doing everything they can to implement the features to make lock in all but inevitable, including mandating that implementations user-hostile features, or risk being rejected by sites.

It’s a great idea, and it could be awesome, but things are not being addressed. Or being handwaved as “we can address them later”. This recent discussion from last month (both the discussion in the linked github issue, and in the HN thread both including some key players in the PassKey system) is pretty telling: https://news.ycombinator.com/item?id=39698502

In fact, it can be better: having root means you can arrange additional ‘firewalls’ between apps and your data , or omit/falsify sensor data the the banking app should not need, that the Google is unwilling to implement.

https://pairdrop.net is FOSS, cross platform, realtime, peer-to-peer, and only needs a browser. You can host your own version if you prefer. In contrast, Firefox Send (also FOSS) was ‘asynchronous’ (you could upload, and then email a link), but it was shut down due to abuse. https://github.com/timvisee/send is a fork of the archived github project that you can self host with many improvements, notably authentication, so only yourself and trusted users can upload. (edit: wrong link for ff send)

Here’s the REAL reason: Apps grant Developers/Content owners more control/metrics/data about the user to feed their advertisers, which translates to more revenue. It’s way easier to hoover up data about the user outside of the browser sandbox, and in apps.

I wish I knew, but the ad industry LOVES this tech: https://duckduckgo.com/?q=smart+tv+ACR&t=ffab&ia=web Every other result is “How ACR is going to be awesome for advertisers/marketers”. the ones in between are “How to shut off ACR” :-/

No.

Smart TV’s run automatic content detection on all their inputs. You will also be nagged to put the device online relentlessly, and some models will not let you skip internet connectivity.

Giulia Wylde is not amateur, but she is all those other things and more

I see this said every time this comes up.

Are there any efforts starting or even attempting this? Or even taking an existing printer and replacing it’s main board?

These hips don’t lie