<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permission Design on Fondsites</title><link>https://fondsites.com/tags/permission-design/</link><description>Recent content in Permission Design on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 May 2026 18:32:29 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/permission-design/feed.xml" rel="self" type="application/rss+xml"/><item><title>Permission Boundaries in Full Dive VR: What a World Should Be Allowed to Do</title><link>https://fondsites.com/full-dive-vr/guidebooks/permission-boundaries/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/full-dive-vr/guidebooks/permission-boundaries/</guid><description>&lt;p&gt;Permissions sound like a software problem until the software reaches the body. A phone app asks for the camera, the microphone, location, contacts, or notifications. A full dive world might ask for touch, balance cues, emotional adaptation, body transformation, session memory, synthetic companionship, voice proximity, and the right to keep running while the user rests. The vocabulary looks familiar, but the stakes are not.&lt;/p&gt;
&lt;p&gt;&lt;img
 src="https://fondsites.com/full-dive-vr/images/guidebooks/full-dive-vr-permission-boundaries.avif"
 alt="A participant in a full dive chair surrounded by abstract permission layers while a facilitator monitors unreadable controls."
 loading="lazy"
 decoding="async"&gt;
&lt;/p&gt;</description></item></channel></rss>