Powerline ethernet dumps an utterly horrifying amount of electrical noise into both the wiring and the surrounding area. Please don't use powerline unless you have no other solution.
Note: Powerline ethernet should not be confused with Power Over Ethernet which is perfectly fine.
Don't have any to link off hand, but the basic gist is this:
Electrical wiring of any sort are all antennas to varying degrees, transmitting and receiving electromagnetic signals. Most mains electrical wiring is also unshielded, meaning they readily transmit and receive electromagnetic signals.
Powerline ethernet basically puts ethernet data on mains electrical wiring by utilizing the bands that aren't used for carrying power. This data is very, very noisy in electrical noise terms, and because most wiring also acts as an antenna that noise also gets broadcast everywhere.
Simple electronics like your coffee machine or microwave oven won't care, but more sensitive electronics like radios can in turn receive interference from both the power line and the noise broadcast into the air.
The issue, I think, is that you're extrapolating from the usecase where high bandwidth ethernet is carried over the power lines. Protocols' like X10 bandwidth use and needs are so low (dozens of bits per second) that the interference is indistinguishable from the regular power fluctuations.
I speak from experience. I tried powerline ethernet because wifi signals traverse the house walls very poorly, to say the least. The sheer noise the powerline adapters generated into the line, regardless traffic, was unacceptable.
I have a box of old X10 devices here, one of the most reliable home automation systems I ever set up. I only switched to WiFi when my iobridge X10 controller failed and I couldnt work out the RS232 protocol for a different controller.
No. Powerline ethernet was pretty obviously going to have security issues along these lines from the go considering the lack of clear boundaries inherent in sending data over wires connecting to a public grid and included cryptography from the go. I know Homeplug devices have been on AES since the mid-2000s using either passwords or push button config and G.hn had something similar going on.
To elaborate, the power conditioning circuits in flat screen (often plasma) TVs would interfere with the non-60hz signaling of the powerline ethernet. That's certainly not the same as breaking into the network, but it may have been enough to knock devices offline.
No BS here.
The _average_ house price in Auckland is 1 million dollars. How long does it take to save a 20% deposit on 150k in a HCOL country?
And 150k is generally a senior level wage, no one in NZ is starting on 150k
Plenty of places OP could look at if they were serious but they aren't. I'm not saying housing isn't in a bad spot as it definitely needs serious attention as a key (perhaps "THE") political issue. But hyperbole and lies doesn't help anyone or anything.
Also keep in mind although Firefox containers is made by Mozilla it's a plugin that you have install, which was very counter intuitive when I first wanted to use it.
The plugin is technically just a management interface for functionality that is already in the browser. FF just doesn't surface it by default, because devs think it would scare casual users.
That's not the only reason. The other reason is that although it's pretty obvious to any one person how it should work, no two people's ideas are the same. Depending on how you are using containers, the answer to a number of questions can be completely opposite to someone else's usage. The theory was that Firefox would provide the underlying functionality, and specialized addons would specialize it to a style of usage.
In practice, it feels like that has hurt adoption. You can't pave the cowpaths if the cows aren't venturing out of the corner of the field.
Honestly the implementation seems half baked, it's very hard to move sites to new containers, there is no list of sites with containers they belong to, etc. I don't know why you'd add a feature in the first place and then decide to hide it for vast majority of users instead of going the extra mile of making it user friendly and intuitive.
Probably because it's a bit of a difficult thing to explain to users in the first place. Instead, by providing just "primitives", they opened the doors to focused add-ons (like the one that isolates Facebook, effectively the first large-scale deployment that used it) without spending too much time on a feature that folks might have found difficult and might result in increased support issues. The status quo is that power-users can make it work, add-ons can use it if they wish, and the overwhelming majority of users can carry on happily ignoring its existence; not a terrible trade-off. But I agree that the management add-on could be better.
I believe Apple is doing something similar with their virtualization API - it's there, some folks can use it, but they don't want to surface it to the masses.
I mean relative to the effort put into building this feature making the UI intuitive shouldn't be a huge task. Think when FF released "tabs" for the first, super intuitive and instant adoption. I wonder if FF is short on UI/UX contributors.
I think I've commented before on this but I've had great success using VSCode Remote Containers. Essentially using the M1 as a frontend to an x86 environment.
Works great and I can move between a local and cloud servers depending on requirements
Location: New Zealand (UTC+12-13, can work within the range [UTC+10 - UTC-08])
Remote: Yes
Willing to relocate: Not at this time
Technologies:
- Python, JavaScript, ReactJS, TypeScript
- Serverless Framework, Ansible, GitLab CI
- AWS, Docker, Linux, KVM, ESX
Dabbling in:
- Electron, NextJS, Kubernetes, Pulumi, Go
Résumé/CV: On request
Email: ezra AT bn0.io
I'm a full-stack/devops generalist with 20+ years experience weighted more towards DevOps/Backend development. I believe knowledge across a broad range of technologies brings a deeper vertical understanding of each specific stack. More than happy to learn new technologies.
