inherentlee/siblinghood-deprecated
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add a bunch of newlines for readability

Browse Source
This commit is contained in:
inherentlee
2026-09-10 11:32:23 -07:00
parent 24cfe068b4
commit 94c68cae4e
1 changed files with 56 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
index.html
+56 -26
View File
@@ -41,29 +41,44 @@
<p><a target="_blank" href="https://flipping.rocks/@inherentlee/115645750535211187">originated on the fediverse</a> with an idea from <a target="_blank" href="https://scholar.social/@noctiluca">noctiluca@scholar.social</a>.</p>
<h2>objective</h2>
<p>send a greeting card around the world. maybe more than one. we'll see.</p>
<p>send a greeting card around the world. Maybe more than one. We'll see.</p>
<h2>outline</h2>
<p>from a group of participants, a random list will be formed. every person is given the address of the next person in the list (the last person receives the first person's address). first person picks a greeting card, signs it, and sends it to their designated recipient; that person receives, signs, sends on, etc.</p>
<p>this continues on to the last person, who finally signs and sends back to the first, closing the loop and ending the adventure. the first person gets to keep the card they originally sent out.</p>
<p>if we want to, this can be easily re-run - add folks who want to be added, drop folks who want to be dropped, scramble the list, and start again.</p>
<p>from a group of participants, a random list will be formed. every person is given the address
of the next person in the list (the last person receives the first person's address). First
person picks a greeting card, signs it, and sends it to their designated recipient; that person
receives, signs, sends on, etc.</p>
<p>this continues on to the last person, who finally signs and sends back to the first, closing
the loop and ending the adventure. The first person gets to keep the card they originally sent
out.</p>
<p>if we want to, this can be easily re-run - add folks who want to be added, drop folks who want
to be dropped, scramble the list, and start again.</p>
<h3>timeline</h3>
<p>applications for round one (cards one and two) closed on <time datetime="2025-12-15">December 15th, 2025</time>.
Round two (card three) closed on <time datetime="2026-05-01">May 1st, 2026</time>.
You may still put in for future rounds, but be aware future rounds are not confirmed yet and will not be confirmed for at least 6 months.</p>
<p>assignments (recipient address, order in loop) for cards one and two have been sent out as of <time datetime="2025-12-26">December 26th, 2025</time>.
Assignments for card three have been sent out as of <time datetime="2026-06-04">June 4th, 2026</time>.</p>
<p>applications for round one (cards one and two) closed on <time datetime="2025-12-15">December
15th, 2025</time>. Round two (card three) closed on <time datetime="2026-05-01">May 1st,
2026</time>. You may still put in for future rounds, but be aware future rounds are not
confirmed yet and will not be confirmed for at least 6 months.</p>
<p>assignments (recipient address, order in loop) for cards one and two have been sent out as of
<time datetime="2025-12-26">December 26th, 2025</time>. Assignments for card three have been
sent out as of <time datetime="2026-06-04">June 4th, 2026</time>.</p>
<h3>participants</h3>
<p>any number, but in the case of signups reaching 26 or greater people, the cohort will be split. Why 26? I'd like this to not run significantly longer than a year, and I'm very loosely estimating that each person will add 2 weeks to the timeline.</p>
<p>for the round beginning <time datetime="2026-01-01">January 1st, 2026</time>, we have 32 participants and will have two cards in circulation.</p>
<p>each cohort will be 16 people. When signups for the next round hit 16, I will confirm with
all folks that they are still in; if so, we'll kick it off (if not, we'll wait for another
person or two).</p>
<p>for the round that began <time datetime="2026-01-01">January of 2026</time>, we have 32
participants and will have two cards in circulation. All following rounds will kick off when
16 signups have been reached.</p>
<h3>on randomization</h3>
<p>I will edit the list as needed to accommodate any mailing restrictions. I will also re-roll if I am placed first on the list.</p>
<p>I will edit the list as needed to accommodate any mailing restrictions. I will also re-roll
if I am placed first on the list.</p>
<h3>card guidelines</h3>
<p>4x6 inches/10x15 centimeters minimum size recommended so there is space for everyone to sign. Must not require an unusual envelope e.g. square or similar. Must meet letter rates so nothing too heavy.</p>
<p>4x6 inches/10x15 centimeters minimum size recommended so there is space for everyone to sign.
Must not require an unusual envelope e.g. square or similar. Must meet letter rates so nothing
too heavy.</p>
<h3>address privacy</h3>
<p>the only people who will see your address are:</p>
@@ -76,8 +91,12 @@
<h2>what I'll need from participants</h2>
<h3>signing the card</h3>
<p>sign in any way you find meaningful. Please don't hog the card space - remember that as many as ~2 dozen people will be signing it!</p>
<p><strong>IMPORTANT!</strong> Only put a name, nickname, doodle, fedi handle, etc. on the card that you are comfortable having displayed publicly. In any posts that I make, it will not be directly connected to you. However, as there are only 16 signers per card, please be aware that how you sign could be tied back to your fedi account.</p>
<p>sign in any way you find meaningful. Please don't hog the card space - remember that as many
as ~2 dozen people will be signing it!</p>
<p><strong>IMPORTANT!</strong> Only put a name, nickname, doodle, fedi handle, etc. on the card
that you are comfortable having displayed publicly. In any posts that I make, it will not be
directly connected to you. However, as there are only 16 signers per card, please be aware that
how you sign could be tied back to your fedi account.</p>
<h3>mailing the card</h3>
<p>this will require a fresh envelope and stamp(s) as needed for postage.</p>
@@ -85,27 +104,38 @@
<h3>status checks</h3>
<p>this is, at the end of the day, pretty flexible, but what I would really, really like is:</p>
<ul>
<li>2 emails, one on receipt and one on re-sending. This allows me to check in on progress and ensure the card doesn't get too stalled, or lost.</li>
<li>more optionally, but fun for seeing how things are going: a picture of the card (not the envelope!)</li>
<li>2 emails, one on receipt and one on re-sending. This allows me to check in on progress and
ensure the card doesn't get too stalled, or lost.</li>
<li>more optionally, but fun for seeing how things are going: a picture of the card (not the
envelope!)</li>
</ul>
<p>feel free to post your card pictures using the hashtags #siblinghoodOfTheTravelingGreetingCard or #sottgc.</p>
<p>feel free to post your card pictures using the hashtags #siblinghoodOfTheTravelingGreetingCard
or #sottgc.</p>
<h2>what I'll send participants</h2>
<h3>guidelines</h3>
<p>summary/highlights of these guidelines will be repeated over email. Full guidelines will always be available here.</p>
<p>summary/highlights of these guidelines will be repeated over email. Full guidelines will
always be available here.</p>
<h3>recipient and loop order assignment</h3>
<p>each participant will be sent the name and address of the next person in the loop. They will also be sent their place in the loop, numbered from 0.</p>
<p>each participant will be sent the name and address of the next person in the loop. They will
also be sent their place in the loop, numbered from 0.</p>
<h3>reminders</h3>
<p>I'll be doing my level best to track the card's movement, so as it is sent around (assuming I get check-ins from y'all! please help me out here!). I will send out reminders to folks to either check their mail or make sure the card gets sent out again. Some folks have specifically asked for this support and I don't want to let them down, so more communication is always better.</p>
<p>I'll be doing my level best to track the card's movement, so as it is sent around (assuming I
get check-ins from y'all! please help me out here!). I will send out reminders to folks to
either check their mail or make sure the card gets sent out again. Some folks have specifically
asked for this support and I don't want to let them down, so more communication is always
better.</p>
<h2>I want in!</h2>
<p>as stated above, signups for the rounds beginning <time datetime="2026-01-01">January 1st, 2026</time>
and <time datetime="2026-06-04">June 4th, 2026</time>are
<strong>closed</strong>. However, you may still sign up in case of future rounds.</p>
<p><a target="_blank" href="https://airtable.com/appdoHZsRDUzgYu9q/pagsr9LVAqKx29gDl/form">sign up for the siblinghood of the traveling greeting card</a>.</p>
<p>if airtable is in any way inaccessible to you, please <a target="_blank" href="https://leecat.art/contact">reach out directly to lee</a>.</p>
<p>as stated above, signups for the rounds beginning <time datetime="2026-01-01">January 1st,
2026</time> and <time datetime="2026-06-04">June 4th, 2026</time>are <strong>closed</strong>.
However, you may still sign up in case of future rounds.</p>
<p><a target="_blank" href="https://airtable.com/appdoHZsRDUzgYu9q/pagsr9LVAqKx29gDl/form">sign
up for the siblinghood of the traveling greeting card</a>.</p>
<p>if airtable is in any way inaccessible to you, please <a target="_blank"
href="https://leecat.art/contact">reach out directly to lee</a>.</p>
</main>
<footer id="footer"><!-- auto populated by nav.js --></footer>