I think this sort of attitude towards hardware devices will massively limit the potential for attacks on our hardware via our ports. We should push for protocols that verify the hardware on the other end is either a known or approved device.
What sort of imaginary attacks are you talking about? Also, removing your ability to use your devices with this device arbitrarily makes this device less "our hardware" and more 'Microsoft's Hardware".
These kind of attacks are pretty rare in general, and for X-Box machines even more so (if they even exist at all). It's not really a huge deal for most people, and locking everything down for everyone is a huge price to pay. It also seems to me that most actors deploying these kind of attacks can bypass these limits them without too much trouble.
If you really want this protection then you can just lock it down yourself.
any plans to generate something for the server side? What I've been prototyping macros which wrap functions to ensure that they adhere to the behavior of an openapi spec.
There is a lot more nuance to law/regulation than “if you don't like my draconian privacy and/or freedom reducing laws then you deserve no property rights!”
Property rights are not possible without a monopoly on force. Property rights are inherently broken because it means someone is giving you rights over some __property__ that you're defending with some arbitrary rules.
Not really. You surely know what the mob thinks about property and privacy rights.
100% of intellectual property rights requires a government. It's not really a right. It's manufactured. Patents user to he called monopolies. It takes a government to enforce such a regime.
Without a government there's no agreed upon, or forced upon, authority to prevent violence.