An annoying trend I've been seeing recently, which the GitHub repo behind this does, is having better documentation for the robots than there is for the users.
Compare the README.md to the skills/pay-for-http-request/SKILL.md
The chances are, if you live somewhere like that, somewhere that actually has a low noise floor for RF, then you likely also have a lot of space to cover with your wifi - and that means sacrificing range (via additional access points) for the second network..
For me: Wifi is great! But, whenever it's practical, I avoid it... Everything with it is a tradeoff!
If the current setup can't, plugging the cameras and the NVR into a separate switch and none of that traffic will go near the rest of your LAN.
Wifi on the other hand, there's really no (practical) segregation to speak of - the spectrum has limited bandwidth, it doesn't matter if it's a different SSID / wifi network, it'll affect your Wifi!
While technically, yes, you are correct. It kinda misses the point - developers are more and more working with containers. Doing this on a Mac is an awful experience compared to doing it on Linux (or, Windows - I hear docker + WSL2 is pretty decent - but I've not tried it!)
> this device can handle a lot: firewalls, user management and access control for home media and file servers, and even some traffic control in data centers – without the need for a stand-alone router.
It's definitely got home networks as a target market. It's one of the suggested use cases.
I'm sure they are perfectly capable of signing up. But, I'd bet they are expressly forbidden from doing it.
Signups typically involve agreeing to some terms, and you absolutely don't want company employees working their official job duties agreeing to random T&C's.
> 1. Since 2020, it's illegal to send PII (personally identifiable) data to the US because of the removal of the Privacy Shield Framework [2]
Minor nit - "PII" really isn't the right term to use, because it suggests the info itself must be personally identifiable to an individual. The GDPR covers much more than this, and uses the term "Personal Data".
In reality, as a service provider, you have no ability to determine if the client IP belongs to an individual or not - so you have no choice but to assume it does identify an individual.
Honestly, it's not that big a leap to reach this interpretation.
1) Your IP address is considered personal data, as it can be used to identify you. In general, everyone can see and agree with this.
2) In the absence of additional protections and/or contract terms[1], the transfer of personal data out of the EU is an offense under the GDPR (well, technically it's not out of EU, but transfer to a country without GDPR equivalence).
So - embedding code / data from a 3rd party into your website results in a transfer of personal data.
[1] The idea of additional protections/contract terms is even questionable, but that's a whole other thing...
That's not strictly true - or at least - it's missing a piece.
When a company decides to use a product, it needs to ensure that product is legal to use in their jurisdiction(s).
If it gets to a court, it's likely that the consumer/client is the claimant and the Company who chose to use US Product X is the defendant. The company who makes US Product X is likely nowhere to be seen.
> but from my experience with Jenkins, I've seen using passwords in plaintext so many times, even in big companies
I reckon this has to do with how the CI tools are configured.
Everyone knows you shouldn't commit a secret to Git, so tools like GitLab CI which require all their config be in git naturally will see less of this specific issue.
> This article ignores the most common problem I have with DNS these days which can roughly be construed as: What is actually handling resolution on my system?
This does my nut in too - even just narrowing the Q down to modern Linux Desktops with e.g. chrome/firefox, and I have absolutely no idea what the query path is. So many components have been added to the path over the last few years :(
That's not always possible & wise, e.g. the example given is the Kubernetes search/ndots values. Changing this would break the expected "API" between the applications in Kube and the Kube cluster, which is bound to cause some pain and suffering down the line :)
Using a FQDN (as in, a DNS name with the trailing dot) is the only reliable way to avoid this without breaking other things!
They got it back in the day (prob mid-90's) because they asked for it - IP space used to handed out like candy on Halloween.. Now that it's a valuable asset - they are very unlikely to just hand it back.
I'm not 100% sure of all the details, but archive.org has some exceptions[1] to the DMCA & thanks to California, it's officially considered a library - which again, I believe gives it some more leeway on the DMCA.
Compare the README.md to the skills/pay-for-http-request/SKILL.md