@mauve A lot of the problems I've had to solve involve coordinating rich interactions between multiple programs that have a separation of concerns that is intuitive to people (to avoid permissions and therefore permission fatigue) while also allowing maximum functionality.

@mauve For example, the SUIS handles interaction among multiple independent objects with their own unique multimodal interactions while only giving as much data as may be necessary in a form that's both convenient and unlikely to infer other sensitive data.

The pulse senders and receivers are also very powerful, they act as spatial tags and generic communication.

Zones are able to manipulate other objects spatially while not having a sense of anything else.

@mauve Items are ways to send data or handles to other clients, they're the backbone of the Wayland compatibility in Stardust.

@mauve I would love to talk with you more about this, I think Stardust is one of the only platforms that has had to solve these issues so far even though it's fully local

@technobaboo Yeah absolutely! I think your work on stardust is some of the most exciting in terms of VR environments. :o

I'm not sure if you've been attending the omi scripting group meetings, but that might be a good place to discuss standards with others so we can make objects more interoperable (assuming that's a shared value in the first place 🤪).

Might also find a way to get funding from Protocol Labs or something to work on loading interactive objects from IPFS via WASM or the such.

@mauve I've been busy and disorganized so I haven't been in the scripting group lately but I have mentioned it in there several times

@technobaboo Yeah, maybe once you have some of the foundations stabilized you'll have more time to look into what sort of stuff can be built on top of them. :o

Luckily the state of VR/AR hardware still sucks (especially with open platforms) so there's plenty of time to iterate before people can actually start depending on this stuff. :P