I went through the exact problem 2 days ago on my U1.
I was trying to print a very thick cylinder, with pctg directly on the bed (no pla support). Extremely simple and it kept failing. Glue stick and upping the bed temp didn't seem to help. I also slowed acceleration. Oddly fewer wall loops helped so it made me think it was warping. I tried z hop and finally got it printing but it could have been a combo of doing the previous steps too.
It could also be a bed leveling problem. The mesh is only for head 1 and I was printing with head 4. Bed mesh is possible because I first tried printing 4 at once and 1 was good, 2 had a severe layer line but finished, and one failed. I then couldn't re print that last one and kept having the failures where I tried everything above.
I'll try an analogy to explain better. The firewall is a lock on the door to your house. Vlans are a rule that to go from one room to another, you must go back out the locked door and back in.
So an attacker tries to come in and can't pick the lock. You are safe.
Another attacker can pick the lock and get into a room. But if they can pick the lock for one room, they can pick the same lock again and get into any other rooms because it's the same lock protecting every room in the house.
Lithium is pretty much the best possible chemical to build batteries out of.
Nickel iron batteries, while heavier and less energy dense have virtually infinite lifespan. As such it is a far better battery for home power walls than lithium.
if you allowed that to happen you either did not set firewall rules strict enough
The argument was that the vlans force a device through the firewall so that the firewall can protect it. But for that to happen, like you said the firewall wasn't strick enough or didn't have a defense against a 0 day.
So the vlan doesn't do anything either way. Either the firewall works in which case you don't need vlans to force local traffic through them a second time or they don't work in which case again the vlan did nothing.
The title of the article is extraordinary wrong that makes it click bait.
There is no "yes to copilot"
It is only a formalization of what Linux said before: All AI is fine but a human is ultimately responsible.
" AI agents cannot use the legally binding "Signed-off-by" tag, requiring instead a new "Assisted-by" tag for transparency"
The only mention of copilot was this:
"developers using Copilot or ChatGPT can't genuinely guarantee the provenance of what they are submitting"
This remains a problem that the new guidelines don't resolve. Because even using AI as a tool and having a human review it still means the code the LLM output could have come from non GPL sources.
To compromise a device on a vlan it had to get through the firewall. If your firewall couldn't stop it then it can attack any other device by going through the firewall because again the firewall didn't stop the device from being compromised in the first place.
haven't really found any personal need for VLAN segregation
I feel like many setup vlans "because it exists", not for actual need. The security reason generally doesn't exist for home labs because most need to setup bridging or you can't access the devices on the secure vlan at all.
Won't help now but only deal with contractors that have a contractor license. That license number means they paid insurance into a fund so if they take the money and run, you can recover your money from the state insurance fund even if they personally don't have any money.
It took like 3 years for the process to work through but I got back all my money from a contractor that took a payment and disappeared.
I believe many office environments have customer service reps using only web apps. They don't run an .exe, they go to a webpage that has the corporate web apps.
Personally I had to spend a lot time getting my raspberry PI to autoload Firefox at boot because I have a custom html home automation panel. A distro that had the option of "boot to web page" at start up would have saved me an hour of googling.
I went through the exact problem 2 days ago on my U1.
I was trying to print a very thick cylinder, with pctg directly on the bed (no pla support). Extremely simple and it kept failing. Glue stick and upping the bed temp didn't seem to help. I also slowed acceleration. Oddly fewer wall loops helped so it made me think it was warping. I tried z hop and finally got it printing but it could have been a combo of doing the previous steps too.
It could also be a bed leveling problem. The mesh is only for head 1 and I was printing with head 4. Bed mesh is possible because I first tried printing 4 at once and 1 was good, 2 had a severe layer line but finished, and one failed. I then couldn't re print that last one and kept having the failures where I tried everything above.