<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>reilyh</title>
    <link>https://pen.blahaj.zone/reilyhh/</link>
    <description>Reilyh&#39;s little corner where she writes her stuff!</description>
    <pubDate>Tue, 28 Apr 2026 09:02:13 +0000</pubDate>
    <item>
      <title>On Content Warnings and Spoilers</title>
      <link>https://pen.blahaj.zone/reilyhh/on-content-warnings-and-spoilers</link>
      <description>&lt;![CDATA[I take content warnings and spoilers very seriously. I think they protect the user themselves, and not just the users around them. I&#39;ve had many times where I vented about something traumatic, or said some bad news, only for my eyes to slightly go up and read that all over again. So by having spoilers, I was able to protect myself from re-reading sensitive content. &#xA;&#xA;!--more--&#xA;The key thing about content/trigger warnings I think is &#34;Readiness&#34;. Yes, sure, it is to protect some folks from being triggered by the content due to having bad past experiences with it. But I also think that it&#39;s there to give users a choice, do you want to read something that might upset you or not? Like you might not have any bad past experiences with X, Y, and Z, but what if you just woke up, and the first thing you were greeted with was a bad case of X, Y, or Z? Or if you expected to see a wholesome chat room with kitty cuddles and meows only to see unspoilered sensitive content. That surprise, that shock, I don&#39;t like that.&#xA;&#xA;Here&#39;s a post on how to spoiler things on Matrix chatting clients, and the last two sections cover the internet in general.&#xA;&#xA;pemAll writing is licensed under a href=&#34;https://creativecommons.org/licenses/by-nd/4.0/&#34; rel=&#34;nofollow&#34;CC-BY-ND/a with attribution to a href=&#34;https://blahaj.zone/@reilyh&#34; rel=&#34;nofollow&#34;REILYH!/a. The FSF recommends a href=&#34;https://www.gnu.org/licenses/license-list.html#OpinionLicenses&#34; rel=&#34;nofollow&#34;this license/a for opinion pieces./em/p]]&gt;</description>
      <content:encoded><![CDATA[<p>I take content warnings and spoilers very seriously. I think they protect the user themselves, and not just the users around them. I&#39;ve had many times where I vented about something traumatic, or said some bad news, only for my eyes to slightly go up and read that all over again. So by having spoilers, I was able to protect myself from re-reading sensitive content.</p>



<p>The key thing about content/trigger warnings I think is “Readiness”. Yes, sure, it is to protect some folks from being triggered by the content due to having bad past experiences with it. But I also think that it&#39;s there to give users a choice, do you want to read something that might upset you or not? Like you might not have any bad past experiences with X, Y, and Z, but what if you just woke up, and the first thing you were greeted with was a bad case of X, Y, or Z? Or if you expected to see a wholesome chat room with kitty cuddles and meows only to see unspoilered sensitive content. That surprise, that shock, I don&#39;t like that.</p>

<p><a href="https://pen.blahaj.zone/reilyhh/matrix-tips-and-tricks" rel="nofollow">Here&#39;s a post</a> on how to spoiler things on Matrix chatting clients, and the last two sections cover the internet in general.</p>

<p><em>All writing is licensed under <a href="https://creativecommons.org/licenses/by-nd/4.0/" rel="nofollow">CC-BY-ND</a> with attribution to <a href="https://blahaj.zone/@reilyh" rel="nofollow">REILYH!</a>. The FSF recommends <a href="https://www.gnu.org/licenses/license-list.html#OpinionLicenses" rel="nofollow">this license</a> for opinion pieces.</em></p>
]]></content:encoded>
      <guid>https://pen.blahaj.zone/reilyhh/on-content-warnings-and-spoilers</guid>
      <pubDate>Sat, 25 Apr 2026 16:45:37 +0000</pubDate>
    </item>
    <item>
      <title>Matrix Tips and Tricks!</title>
      <link>https://pen.blahaj.zone/reilyhh/matrix-tips-and-tricks</link>
      <description>&lt;![CDATA[Spoilers!&#xA;&#xA;For spoilering you could use the following format:&#xA;&#xA;!--more--&#xA;&#xA;Double Pipes&#xA;&#xA;If your client support this syntax ||spoilered text|| you should write like this:&#xA; CW/TW: Description Of The Warning ||Actual Content||&#xA;&#xA;The /spoiler Command&#xA;&#xA;If your client does not support that syntax, check if your client provides a /spoiler command: &#xA;in that case you should send a message that details the CW/TW then reply to it using the /spoiler command&#xA;&#xA;Long Text and Other Forms of Media&#xA;&#xA;An excellent way would be to use https://trggr.link/ you could write CW/TWs for any kind of media: images, videos, large text, etc.&#xA;&#xA;Although keep in mind that trggr isn&#39;t a file hosting service, it only supports text. To send sensitive media, upload to an external file host, like https://catbox.moe or other file hosting services.&#xA;&#xA;Stickers&#xA;&#xA;I am known as the sticker girl, I&#39;ve been mostly collecting images on the internet, cropping them, sometimes editing them slightly to fit my needs. I even drew some stickers. So here&#39;s what I learned:&#xA;&#xA;[This section is under construction]&#xA;&#xA;pemAll writing is licensed under a href=&#34;https://creativecommons.org/licenses/by-nd/4.0/&#34; rel=&#34;nofollow&#34;CC-BY-ND/a with attribution to a href=&#34;https://blahaj.zone/@reilyh&#34; rel=&#34;nofollow&#34;REILYH!/a. The FSF recommends a href=&#34;https://www.gnu.org/licenses/license-list.html#OpinionLicenses&#34; rel=&#34;nofollow&#34;this license/a for opinion pieces./em/p]]&gt;</description>
      <content:encoded><![CDATA[<h2 id="spoilers">Spoilers!</h2>

<p>For spoilering you could use the following format:</p>



<p><strong>Double Pipes</strong></p>

<p>If your client support this syntax ||spoilered text|| you should write like this:
 CW/TW: Description Of The Warning ||Actual Content||</p>

<p><strong>The <code>/spoiler</code> Command</strong></p>

<p>If your client does not support that syntax, check if your client provides a /spoiler command:
in that case you should send a message that details the CW/TW then reply to it using the /spoiler command</p>

<p><strong>Long Text and Other Forms of Media</strong></p>

<p>An excellent way would be to use <a href="https://trggr.link/" rel="nofollow">https://trggr.link/</a> you could write CW/TWs for any kind of media: images, videos, large text, etc.</p>

<p>Although keep in mind that trggr isn&#39;t a file hosting service, it only supports text. To send sensitive media, upload to an external file host, like <a href="https://catbox.moe" rel="nofollow">https://catbox.moe</a> or other file hosting services.</p>

<h2 id="stickers">Stickers</h2>

<p>I am known as the sticker girl, I&#39;ve been mostly collecting images on the internet, cropping them, sometimes editing them slightly to fit my needs. I even drew some stickers. So here&#39;s what I learned:</p>

<p>[This section is under construction]</p>

<p><em>All writing is licensed under <a href="https://creativecommons.org/licenses/by-nd/4.0/" rel="nofollow">CC-BY-ND</a> with attribution to <a href="https://blahaj.zone/@reilyh" rel="nofollow">REILYH!</a>. The FSF recommends <a href="https://www.gnu.org/licenses/license-list.html#OpinionLicenses" rel="nofollow">this license</a> for opinion pieces.</em></p>
]]></content:encoded>
      <guid>https://pen.blahaj.zone/reilyhh/matrix-tips-and-tricks</guid>
      <pubDate>Sat, 25 Apr 2026 15:11:35 +0000</pubDate>
    </item>
    <item>
      <title>FINALLY!</title>
      <link>https://pen.blahaj.zone/reilyhh/finally</link>
      <description>&lt;![CDATA[NO MORE DEALING WITH CSS DEMONS! AAAAAAAH I CAN WRITE STUFF NOW!&#xA;&#xA;pemAll writing is licensed under a href=&#34;https://creativecommons.org/licenses/by-nd/4.0/&#34; rel=&#34;nofollow&#34;CC-BY-ND/a with attribution to a href=&#34;https://blahaj.zone/@reilyh&#34; rel=&#34;nofollow&#34;REILYH!/a. The FSF recommends a href=&#34;https://www.gnu.org/licenses/license-list.html#OpinionLicenses&#34; rel=&#34;nofollow&#34;this license/a for opinion pieces./em/p]]&gt;</description>
      <content:encoded><![CDATA[<p>NO MORE DEALING WITH CSS DEMONS! AAAAAAAH I CAN WRITE STUFF NOW!</p>

<p><em>All writing is licensed under <a href="https://creativecommons.org/licenses/by-nd/4.0/" rel="nofollow">CC-BY-ND</a> with attribution to <a href="https://blahaj.zone/@reilyh" rel="nofollow">REILYH!</a>. The FSF recommends <a href="https://www.gnu.org/licenses/license-list.html#OpinionLicenses" rel="nofollow">this license</a> for opinion pieces.</em></p>
]]></content:encoded>
      <guid>https://pen.blahaj.zone/reilyhh/finally</guid>
      <pubDate>Sat, 25 Apr 2026 14:55:00 +0000</pubDate>
    </item>
    <item>
      <title>Hello world!</title>
      <link>https://pen.blahaj.zone/reilyhh/hello-world</link>
      <description>&lt;![CDATA[I did an oopsie again and forgot my password for &#34;reilyh&#34; for pen.blahaj.zone. Oh well :P&#xA;!--more--&#xA;&#xA;pemAll writing is licensed under a href=&#34;https://creativecommons.org/licenses/by-nd/4.0/&#34; rel=&#34;nofollow&#34;CC-BY-ND/a with attribution to a href=&#34;https://blahaj.zone/@reilyh&#34; rel=&#34;nofollow&#34;REILYH!/a. The FSF recommends a href=&#34;https://www.gnu.org/licenses/license-list.html#OpinionLicenses&#34; rel=&#34;nofollow&#34;this license/a for opinion pieces./em/p]]&gt;</description>
      <content:encoded><![CDATA[<p>I did an oopsie again and forgot my password for “reilyh” for pen.blahaj.zone. Oh well :P
</p>

<p><em>All writing is licensed under <a href="https://creativecommons.org/licenses/by-nd/4.0/" rel="nofollow">CC-BY-ND</a> with attribution to <a href="https://blahaj.zone/@reilyh" rel="nofollow">REILYH!</a>. The FSF recommends <a href="https://www.gnu.org/licenses/license-list.html#OpinionLicenses" rel="nofollow">this license</a> for opinion pieces.</em></p>
]]></content:encoded>
      <guid>https://pen.blahaj.zone/reilyhh/hello-world</guid>
      <pubDate>Sat, 18 Apr 2026 16:36:42 +0000</pubDate>
    </item>
  </channel>
</rss>