• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: December 22nd, 2023

help-circle








  • three primary things.

    Fucking coax, literally the bane of anybody anywhere, fucking horrible standard. Works well, which is the only reason anybody uses it, it’s just a nightmare. (if you have ever dealt with a coax cable, you know exactly what i mean)

    Offices were already wired up with phone lines, which often had redundant lines running to each endpoint, meaning you could just hook straight into the existing wiring infrastructure, and convert it to ethernet (very accessible and cheap)

    twisted pair comes with the advantage of noise reduction over longer distances, cheaper construction, and significantly simpler wire structure, making it easier to route, manage, terminate, and just generally exist around. (basically the same as the first one lmao)

    It was actually so much of a problem, that the original ethernet standard, based on RG-6? I think, don’t quote me on it, ended up moving to a smaller coax standard and was referred to as “thinnet” as it was thinner coax and easier to work with.








  • it’s definitely cool that we have the capability of things like thread/matter zigbee and zwave now.

    I would be more ok with local IoT devices being IP based if they were intended on being used with an “offline” network. Though that’s a little funky to setup, and causes interference issues, so i think i prefer the zigbee and zwave solution of using a different protocol entirely, especially since it mandates offline handling.

    My two biggest concerns with IP connected devices are most home networks are not properly delegated, so people aren’t creating a second subnet specifically for IoT devices for example, and they most definitely aren’t properly providing access controls through that network as well. So if someone manages to get into one of the devices, you basically have the entire network at that point.

    One of the big advantages of non IP based systems is that you have a “point of relay” or gateway between all of your IoT devices and your network, which becomes the attack vector, making it a lot easier to secure, and manage. Even if you managed to hack into a zwave/zigbee network, it would only be locally, and IoT devices only, so it’s not going to be hugely problematic.

    theoretically you can do all of this on a traditional IP based network, i just don’t think it’s the correct approach. Sort of like making a carboat, or a boatcar. You could, but why?

    I think at minimum, a standalone IoT device should not be capable of connecting to the global internet, period. Through something like a gateway or “point of relay” sure, that’s fine by me, but even then i would prefer open standards and documentation on that specific feature set.




  • networking standards were a mess before ethernet really fucking cooked with twisted pair wiring.

    Ethernet had already existed for a little bit prior to this, and most other alternatives were actively being worked on at the time, and relatively similar to ethernet, save for the general technical implementation, token ring as opposed to the funny broadcast meta. But when ethernet was able to just barely get ahead and use twisted pair, the entire thing came crumbling down and everyone agreed that ethernet over twisted pair, with switched star topology was the best.