Our great sponsors
-
unicast-extensions
The IPv4 unicast extensions project - Making class-e (240/4), 0/8, 127/8, 225/8-232/8 generally usable - adding 419 million new IPs to the world, and fixing various other slightly broken pieces of the IPv4 world
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
-
They have a github that is accepting issues, i would suggest sending the pitch forks over there. https://github.com/schoen/unicast-extensions
Today, ARM9 processors with MMUs capable of running Linux cost roughly $1 on SIPs with RAM. Though most non-Unix embedded networking stacks support IPv6, we've found that in at least 80% of cases, any embedded device with IPv6 support is running it through a Linux kernel. It's boringly monotonous.
I have the locking of accounts setup in code. It sounds complicated, but I set it up in just a few minutes. I already have a Home Assistant installation connected to a Node-Red instance for my home automation. There is a device for each kid in HA, which communicate to a node in Node-Red. NR then hosts a Rest API that reports if accounts should be locked or not (seriously easy in Node-Red, you can create a simple API like that in under a minute). The DC runs a script every minute to check if kids accounts should be locked or not. If they should be locked, the account is locked and forcefully logged off all kids devices. If the account should be unlocked, it's unlocked. Overall time to setup was under half an hour. I've got a dashboard then in Home Assistant where you give/revoke kids access with just a tap of a switch.
I have the locking of accounts setup in code. It sounds complicated, but I set it up in just a few minutes. I already have a Home Assistant installation connected to a Node-Red instance for my home automation. There is a device for each kid in HA, which communicate to a node in Node-Red. NR then hosts a Rest API that reports if accounts should be locked or not (seriously easy in Node-Red, you can create a simple API like that in under a minute). The DC runs a script every minute to check if kids accounts should be locked or not. If they should be locked, the account is locked and forcefully logged off all kids devices. If the account should be unlocked, it's unlocked. Overall time to setup was under half an hour. I've got a dashboard then in Home Assistant where you give/revoke kids access with just a tap of a switch.