<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Invites questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Invites design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>Invite budget model?</title>
      <link>https://flove.org/making-of.html#nety-spec_q14</link>
      <guid isPermaLink="false">nety-spec_q14</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Scales with Social facet — Allowance grows with standing; Sybil-resistant.
• Fixed small allotment — Everyone gets the same few; egalitarian but flat.
• Earned per good invite — More invites as your invitees mature.
• Scales + accountability — Scales with standing AND invitees' fates reflect back — invite someone who's slashed, your budget+score drop.

★ decided: Scales + accountability</description>
    </item>
    <item>
      <title>How does abuse become a slash?</title>
      <link>https://flove.org/making-of.html#nety-spec_q15</link>
      <guid isPermaLink="false">nety-spec_q15</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Weighted peer reports — Reports weighted by reporter's score auto-slash; needs anti-brigading.
• Reports + trusted jurors — A quorum of high-trust jurors confirms; harder to brigade.
• Staked reports — Reporting costs staked stars; false reports burn the stake.
• Defer — just show the slash — Mock only shows 'reported→slashed'; design real adjudication later.

★ decided: Defer — just show the slash</description>
    </item>
    <item>
      <title>Shape of the invite web?</title>
      <link>https://flove.org/making-of.html#nety-spec_q16</link>
      <guid isPermaLink="false">nety-spec_q16</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Multi-sponsor web (DAG) — A peer can be co-vouched by several; stronger entry.
• Strict tree (one sponsor) — Exactly one inviter each; clean accountability.
• Tree entry, web later — Enter via ONE invite (clean lineage tree), then accumulate vouches that add web edges for scoring without changing your parent.

★ decided: Tree entry, web later</description>
    </item>
    <item>
      <title>Invite code issuance?</title>
      <link>https://flove.org/making-of.html#nety-spec_q17</link>
      <guid isPermaLink="false">nety-spec_q17</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Single-use only — One code → one person, pre-committed.
• Reusable capped link — One link good for N joins.
• Both (multi-use needs per-registrant validation) — Single-use code OR a capped multi-use link where you approve each registrant before they're in.

★ decided: Both (multi-use needs per-registrant validation)</description>
    </item>
    <item>
      <title>Revocation?</title>
      <link>https://flove.org/making-of.html#nety-spec_q18</link>
      <guid isPermaLink="false">nety-spec_q18</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Revoke unused only — Refund before use; joined lineage is permanent.
• Revoke + disown — Also sever a joined invitee — costs Social score + leaves a public 'disowned' mark.
• No revocation — Immutable once created.

★ decided: Revoke + disown</description>
    </item>
    <item>
      <title>Invite-graph scoring: depth vs breadth?</title>
      <link>https://flove.org/making-of.html#nety-spec_q19</link>
      <guid isPermaLink="false">nety-spec_q19</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Favor depth — Deep thriving lineage is the strongest, hardest-to-fake signal.
• Balance both — Wide-and-good scores like deep-and-narrow; steeper decay, higher breadth cap.
• Favor breadth — Reward many good direct invitees; more gameable.

★ decided: Balance both</description>
    </item>
    <item>
      <title>What makes an invitee 'matured' (counts for subtree credit)?</title>
      <link>https://flove.org/making-of.html#nety-spec_q20</link>
      <guid isPermaLink="false">nety-spec_q20</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Independent verify + outside vouch — ≥ Telegram-verified on their own AND ≥1 vouch from someone OTHER than their inviter — so sponsors can't self-manufacture matured nodes.
• Score threshold + time — Reach a min score sustained for a period; still gameable.
• Contribution-based — Must have actually contributed/published.

★ decided: Independent verify + outside vouch</description>
    </item>
    <item>
      <title>Resisting mutual-vouch rings / collusion?</title>
      <link>https://flove.org/making-of.html#nety-spec_q21</link>
      <guid isPermaLink="false">nety-spec_q21</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Diversity-weighted vouches — A vouch counts less from your own dense cluster, full from distant independent peers — rings self-cancel.
• Reciprocity discount only — Just down-weight directly mutual A↔B; misses 3+ rings.
• Defer it — Note as a limitation; rely on maturation + slashing for now.

★ decided: Diversity-weighted vouches</description>
    </item>
    <item>
      <title>Slash severity &amp; reach?</title>
      <link>https://flove.org/making-of.html#nety-spec_q22</link>
      <guid isPermaLink="false">nety-spec_q22</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Graduated + bounded cascade — Severity scales with the offense; cascades to inviter/vouchers but decayed and only to those who didn't disown in time. Proportional.
• Hard reset, no cascade — Zero the facet, contained to the offender; removes accountability pressure.
• Flat penalty + full cascade — Fixed slash propagated undecayed to all ancestors; harsh, collateral-heavy.

★ decided: Graduated + bounded cascade</description>
    </item>
    <item>
      <title>Who signs the invite-lineage edge (builds the public tree)?</title>
      <link>https://flove.org/making-of.html#nety-spec_q23</link>
      <guid isPermaLink="false">nety-spec_q23</guid>
      <category>nety-spec</category>
      <category>Invites</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Co-signed by both — Inviter + invitee both sign — mutual, non-repudiable, hard to forge or deny.
• Inviter publishes — Ties to budget, but invitee hasn't attested their own lineage.
• Invitee publishes — Natural in a feed model, but a parent could be falsely claimed.

★ decided: Co-signed by both</description>
    </item>
  </channel>
</rss>
