Coopr8

I looked around a bit more, seems to be regional which is growing faster. UK Meshcore is growing fast, which makes sense since core devs are there. I haven’t found a good statistics source for node numbers, probably for the best given the network goals. Meshtastic of course is older so has the inertia lead, but the security and routing of Meshcore definitely is appealing to me and seems better for emergency situations where text messaging reliability is top priority.

Meshcore is currently considered superior in most respects to Meshtastic, and as a result has a faster growing user base.

https://meshcore.co.uk/

Windat

If only I were the king of the world!

I think what you are arguing for is hardcoding requitement for signatures with an “age appropriateness” ranking into the OS. How does this change the current situation where adult sites and apps are legally required to have an age verification popup/warning? Whether signature based or graphically based, what is at issue here is age verification which means referring to some “repository of truth” outside the will of the user. The problem is that the effect of this is to link government ID directly to web traffick, as to truly verify age requires verifying identity meaning abolishing anonymity on the web and enabling complete tracking of dissent.

I could see a version of what you are describing akin to the way physical cryptographic keys are used to manage DRM on high end enterprise software, where identity/age verification would need to be done by the hardware vendor and not the software/site, the problem with that however is the aftermarket and multiple-user devices. You could say that the “age key” would be a hardware device sold to adults using physical ID akin to spirits or tobacco, something like a SIM Card but preferably with NFC rather than having to be installed in the device. “Adult Access” would then be enabled on sign-in by scanning the “age key”, enabling onboard software to serve software and sites that don’t have an “all ages signature”.

Honestly as I write this, it isn’t the worst solution, the main thing would be keeping the Age Key as an interchangeable, replaceable device that only interacts with the OS and isn’t referenced by other software, so it doesnt just become another Digital ID proxie.

Nice, shame the assistant isn’t on Windows.

Don’t go giving them ideas. That way leads to Digital ID at birth, which should be avoided at all costs.