<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: The Homelab Files</title>
    <description>The latest articles on DEV Community by The Homelab Files (@thehomelabfiles).</description>
    <link>https://dev.to/thehomelabfiles</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4244713%2F15435b5d-1903-4fd6-999a-433f2443344c.png</url>
      <title>DEV Community: The Homelab Files</title>
      <link>https://dev.to/thehomelabfiles</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thehomelabfiles"/>
    <language>en</language>
    <item>
      <title>Agent guidance now ships in the members' repo</title>
      <dc:creator>The Homelab Files</dc:creator>
      <pubDate>Sun, 15 Nov 2026 19:23:30 +0000</pubDate>
      <link>https://dev.to/thehomelabfiles/agent-guidance-now-ships-in-the-members-repo-3nbg</link>
      <guid>https://dev.to/thehomelabfiles/agent-guidance-now-ships-in-the-members-repo-3nbg</guid>
      <description>&lt;h1&gt;
  
  
  Agent guidance now ships in the members' repo
&lt;/h1&gt;

&lt;p&gt;The AGENTS and SKILL markdown files are in the Evidence Locker — workflow rules and repeatable skills, so an AI agent can implement what's there without guesswork.&lt;/p&gt;

</description>
      <category>homelab</category>
      <category>selfhosted</category>
      <category>ai</category>
    </item>
    <item>
      <title>Welcome to the Fediverse</title>
      <dc:creator>The Homelab Files</dc:creator>
      <pubDate>Sat, 14 Nov 2026 16:00:21 +0000</pubDate>
      <link>https://dev.to/thehomelabfiles/welcome-to-the-fediverse-40bi</link>
      <guid>https://dev.to/thehomelabfiles/welcome-to-the-fediverse-40bi</guid>
      <description>&lt;p&gt;The Homelab Files has joined the Fediverse!!&lt;/p&gt;

&lt;h2&gt;
  
  
  Joining the Fediverse
&lt;/h2&gt;

&lt;p&gt;The Homelab Files is now on the Fediverse. You can find it at &lt;em&gt;@&lt;a href="mailto:blog@thehomelabfiles.org"&gt;blog@thehomelabfiles.org&lt;/a&gt;&lt;/em&gt;, or open it directly at &lt;a href="https://md.thehomelabfiles.org/@blog" rel="noopener noreferrer"&gt;https://md.thehomelabfiles.org/@blog&lt;/a&gt;. This allows us to notify and expose our content via the Fediverse in a way that we hope makes consuming it convenient, as well as sidestepping concerns of algorithmic suppression or counter-narrative stomping.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why This Matters
&lt;/h2&gt;

&lt;p&gt;It is indisputable that many platforms modulate viewpoints. Nothing is more dangerious. Couple that with engineered narratives that obscure the truth and honest reality breaks. A handful of companies, often pressured by governments, now sit between a writer and a reader, a podcaster and a listener, a video and its audience. This arrangement is presented as convenience; it is nothing of the sort. It is custody and control. An account can be closed, a reach can be quietly reduced, a topic can be labeled, and the person on the other end is given no recourse and no explanation. When the pipe is owned by the people who also decide what flows through it, "free speech" becomes a policy they revise whenever it costs them something.&lt;/p&gt;

&lt;p&gt;These are the entities who bring to life terms like malinformation.&lt;/p&gt;

&lt;p&gt;Decentralized communication is the corrective. Not a different platform - the same idea the internet was built on. Independent servers, speaking a common protocol, each with its own rules and its own owner(s). Nobody has to like the arrangement. Nobody has to approve my account, and I do not have to approve theirs. That is what a commons looks like when it is working.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Voltaire? François-Marie Arouet? S. G. Tallentyre? Evelyn Beatrice Hall? Ignazio Silone? Douglas Young? Norbert Guterman?&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Making It Available To You
&lt;/h2&gt;

&lt;p&gt;We want the content to be reachable by as many people as possible, in whatever way they already consume things.&lt;/p&gt;

&lt;p&gt;The Fediverse is not one website. You do not need an account on my server. You do not need an account on any particular server. If you already use Mastodon, GoToSocial, Akkoma, Misskey, Firefish, Friendica, or one of the publishing tools that speak ActivityPub, paste the address into your search field and follow from there. Your feed stays yours, in the client you already use, next to the people you already follow.&lt;/p&gt;

&lt;p&gt;And if none of that appeals, nothing here changes for you. The blog stays where it is, readable without a login. This is an addition, not a migration.&lt;/p&gt;

&lt;h2&gt;
  
  
  On Algorithms and Narrative
&lt;/h2&gt;

&lt;p&gt;We have no interest in competing for a ranked slot from a tech deity. When you follow this account, you see what gets posted, in the order it gets posted. There is no auction deciding whether it reaches you, no model deciding it is off-message, no throttling of a link because it points off-platform. If the material is not for you, unfollow - that is a cleaner mechanism than being quietly filtered and never told.&lt;/p&gt;

&lt;p&gt;We will not pretend the Fediverse is free of argument or bad actors. It is a room full of people, and rooms full of people are messy. But messy and open beats tidy and controlled ... &lt;em&gt;any day&lt;/em&gt; ... &lt;strong&gt;every day&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does Not Change
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://blog.thehomelabfiles.org/" rel="noopener noreferrer"&gt;The Blog&lt;/a&gt; is still home to prose.&lt;br&gt;&lt;br&gt;
Videos stay on &lt;a href="https://www.youtube.com/@TheHomelabFiles" rel="noopener noreferrer"&gt;YouTube&lt;/a&gt;.&lt;br&gt;&lt;br&gt;
&lt;a href="https://github.com/TheHomelabFiles/TheHomelabFiles" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; still holds the assets.&lt;/p&gt;

</description>
      <category>fediverse</category>
      <category>selfhosted</category>
    </item>
    <item>
      <title>Welcome - Sweet Mercy, a Blog?</title>
      <dc:creator>The Homelab Files</dc:creator>
      <pubDate>Sat, 14 Nov 2026 16:00:17 +0000</pubDate>
      <link>https://dev.to/thehomelabfiles/welcome-sweet-mercy-a-blog-5543</link>
      <guid>https://dev.to/thehomelabfiles/welcome-sweet-mercy-a-blog-5543</guid>
      <description>&lt;p&gt;I have spent years, decades really, architecting, engineering, building, razing, deploying, decommissioning technology stacks and software at the enterprise datacenter/cloud scale as well as for my own uses: a rack in a closet, a stack of containers, a DNS server the whole house quietly depends on, and a backup routine I trust slightly less than I would like. You see, I've had the pleasure of operating in both leadership capacity as well as a direct executor in the various spaces in which I've worked - Wall St., Main St., Defense/Intel, Federal/Civilian, Big Tech, and more ...&lt;/p&gt;

&lt;p&gt;The Homelab Files is where I thought I might start to capture much of the lessons learned, relationships made, and various takeaways and share them. There is no shortage of amazing content creators online, but I am hoping that The Homelab Files does something a bit different.&lt;/p&gt;

&lt;p&gt;I'm hopeful much of the content will be worth watching to you. An automation or build, a debrief on an architecture and why, conversations with industry peers - those are easier to show than to describe. Those become content on our &lt;a href="https://www.youtube.com/@TheHomelabFiles" rel="noopener noreferrer"&gt;YouTube Channel&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Some things just read better. An editorial or an opinion piece on some recent news or event, a follow-up to a discussion, a whitepaper that I, or perhaps with a colleague, may be working on or have produced, etc. Video can be a poor container for such material. You cannot skim it, you cannot copy a line out of it, and you cannot search it eighteen months later with ease (although AI is indeed changing this). So the written side goes here.&lt;/p&gt;

&lt;p&gt;This gives the project three places to live. Videos on &lt;a href="https://www.youtube.com/@TheHomelabFiles" rel="noopener noreferrer"&gt;YouTube&lt;/a&gt;, where you need to watch a thing happen or enjoy a long-form conversation. Code, scripts and similar assets on &lt;a href="https://github.com/TheHomelabFiles" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; (which does require a Membership to access). Lastly, this blog for the material that does not fit either: written posts that never needed a video, and companion notes for the videos that did, and more.&lt;/p&gt;

&lt;p&gt;This journey is always subject to change, but for now everything on the blog is public. There is no paywall, no gated section, no members-only tier. If it is worth writing, it is worth reading without a login. That isn't to say there won't be premium content that requires revenue to support it in the future, but we'll cross that bridge if we need to.&lt;/p&gt;




&lt;h2&gt;
  
  
  What To Expect
&lt;/h2&gt;

&lt;p&gt;The blog carries the written side. Some posts will stand alone. Others will follow a video and cover what the video could not: the part cut for time, the approach that failed and the reason it failed. When a post follows a video it will link to it, and any associated code lives on &lt;a href="https://github.com/TheHomelabFiles" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Who This Is For
&lt;/h2&gt;

&lt;p&gt;Frankly anyone interested! That said, it is likely to be quite technical in its content at times, so some level of understanding is expected. For example, if I'm referencing Docker containers, I'm not going to author much text about what they are ... I'm likely to go right into the strategic and tactical elements of what I'm trying to convey, or show how I execute.&lt;/p&gt;

&lt;p&gt;What I will do is take feedback seriously and make an honest effort to adopt some compromise as needed for the audience, which is likely to shape how things are posted, albeit more so on &lt;a href="https://github.com/TheHomelabFiles" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; than this blog.&lt;/p&gt;




&lt;h2&gt;
  
  
  How This Will Go
&lt;/h2&gt;

&lt;p&gt;This is early. This is the first post (arguably pre-launch) and there is no backlog to read through.&lt;/p&gt;

&lt;p&gt;Going forward, I would rather publish something that took a week to get right than keep a schedule for its own sake. If that means two posts this month and none the next because work moves to video production, so be it. The alternative is padded posts that waste your time and mine, and I have read enough of those for a lifetime.&lt;/p&gt;

&lt;p&gt;I will also correct things. If a post turns out to be wrong, or a step stops working because the project changed underneath it, I would rather update the post and say so at the bottom than leave a broken recipe sitting here looking authoritative.&lt;/p&gt;

&lt;p&gt;If you want new posts by email, subscribe. That is all the signup does: when a newsletter goes out, it lands in your inbox, and there is no other use for your address. You can also unsubscribe at your whim.&lt;/p&gt;




&lt;h2&gt;
  
  
  On Carlin and &lt;a href="https://www.youtube.com/results?search_query=george+carlin+soft+language" rel="noopener noreferrer"&gt;Soft Language&lt;/a&gt; (Warning)
&lt;/h2&gt;

&lt;p&gt;George warned of the sterilization of the American language:&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;  &lt;span class="ltag-quote__identity"&gt; &lt;span class="ltag-quote__author"&gt;George Carlin&lt;/span&gt; &lt;/span&gt;  &lt;blockquote class="ltag-quote__body"&gt; &lt;div class="ltag-quote__text"&gt;I don't like words the hide the truth. I don't like words that conceal reality. I don't like euphemisms or euphemistic language. And American English is loaded with euphemisms because Americans have a lot of trouble dealing with reality. Americans have trouble facing the truth. So they invent the kind of a soft language to protect themselves from it. And it gets worse with every generation.&lt;/div&gt; &lt;/blockquote&gt;  &lt;cite class="ltag-quote__source"&gt;Doin' It Again (1990)&lt;/cite&gt;  &lt;p&gt;&lt;/p&gt;

&lt;p&gt;I'm a kid born and bred of the streets of Brooklyn &amp;amp; Queens, New York. &lt;em&gt;Rough-and-tumble&lt;/em&gt; neighborhoods steeped in ethnicity, flair, and phrases or word choices that would make the non-New Yorker take notice or blush. There was no "Soft Language" growing up. People spoke plainly, directly, and largely without high-societal moderation. If you are sensitive to this sort of language, this is a destination you might want to skip. I'll try to tag posts with "RANT" when they contain such flair, but you've been warned. This is truly a free-speech venue for myself and any collaborators that wind up contributing.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Important Part
&lt;/h2&gt;

&lt;p&gt;Enjoy the videos, the blog posts, the &lt;a href="https://github.com/TheHomelabFiles" rel="noopener noreferrer"&gt;GitHub repo&lt;/a&gt;, and our shared journey! ...but more importantly enjoy life. Step away from the keyboard more often. Play Frisbee with your dog, take your kid out for a malted. Hug your husband or wife and take them out for lunch. I fell in love with these devices decades ago ... and if I've learned anything it is that stepping away from them from time to time has allowed me to continue loving them.&lt;/p&gt;

</description>
      <category>homelab</category>
      <category>selfhosted</category>
    </item>
  </channel>
</rss>
