<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Circles questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Circles design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>What does the permissions layer govern?</title>
      <link>https://flove.org/making-of.html#nety-spec_q29</link>
      <guid isPermaLink="false">nety-spec_q29</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Content / pages — Who can read your published pages, posts, files.
• Shared resources — Who can draw on the compute/storage/AI you offer.
• Profile data — Field-level visibility of your profily.
• Interaction / social — Who can message you, request to join via you, add you to their MyNet.

★ decided: Content / pages · Shared resources · Profile data · Interaction / social</description>
    </item>
    <item>
      <title>What are permissions granted to?</title>
      <link>https://flove.org/making-of.html#nety-spec_q30</link>
      <guid isPermaLink="false">nety-spec_q30</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• MyNet + named circles — Your whole MyNet and/or named sub-circles. Most expressive.
• Per-peer only — Individual grant/deny; precise but tedious.
• By trust tier — Grant by network trust level; leans on the score.
• Hybrid: circles + tiers — Circles AND tiers in one rule.

★ decided: MyNet + named circles</description>
    </item>
    <item>
      <title>Default audience for a new peer?</title>
      <link>https://flove.org/making-of.html#nety-spec_q31</link>
      <guid isPermaLink="false">nety-spec_q31</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Private-first, opt-in to share — Everything starts private; you deliberately widen each area. Safest, FOSS-aligned.
• Sensible per-area defaults — Reasonable defaults per area; friendlier but some things visible early.
• Public-first, opt-in to restrict — Open by default; lock down what you want private.

★ decided: Private-first, opt-in to share</description>
    </item>
    <item>
      <title>Circle model?</title>
      <link>https://flove.org/making-of.html#nety-spec_q32</link>
      <guid isPermaLink="false">nety-spec_q32</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Flat subsets of MyNet — Each circle a subset; a peer in several; no nesting.
• Nested tiers — Concentric rings close⊆friends⊆MyNet; outer grant includes inner.
• Flat independent tags — Labels with no MyNet relationship; can include non-MyNet peers.
• Nested tiers + independent tags (both) — Tiered rings for graded trust AND flat tag circles for project/context groups, coexisting.

★ decided: Nested tiers + independent tags (both)</description>
    </item>
    <item>
      <title>Which layers do circles span?</title>
      <link>https://flove.org/making-of.html#nety-spec_q33</link>
      <guid isPermaLink="false">nety-spec_q33</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Both nety + appy, parallel &amp; connectable — nety circles and appy circles are the same circles, running in parallel and easily linked across the bridge.
• Upper (appy) only — Circles live only in the apps layer.
• Lower (nety) only — Circles live only in the infrastructure layer.

★ decided: Both nety + appy, parallel &amp; connectable</description>
    </item>
    <item>
      <title>How visible are your facet scores to others?</title>
      <link>https://flove.org/making-of.html#nety-spec_q34</link>
      <guid isPermaLink="false">nety-spec_q34</guid>
      <category>nety-spec</category>
      <category>Circles</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Owner-controlled per facet — Default private; you reveal each facet (exact or coarse tier) to public/MyNet/circles. The protocol still computes with true scores.
• Public tier badges, exact private — Others see coarse tiers; exact numbers private to you.
• Fully public exact — All four facet values visible to everyone.
• Fully private — Nobody sees scores; only capability outcomes observable.

★ decided: Owner-controlled per facet</description>
    </item>
  </channel>
</rss>
