<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>rule-based &#8211; Gig City Geek</title>
	<atom:link href="https://gigcitygeek.com/tag/rule-based/feed/" rel="self" type="application/rss+xml" />
	<link>https://gigcitygeek.com</link>
	<description></description>
	<lastBuildDate>Wed, 15 Apr 2026 16:21:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://gigcitygeek.com/wp-content/uploads/2026/01/cropped-GigCityGeek_Logo-32x32.png</url>
	<title>rule-based &#8211; Gig City Geek</title>
	<link>https://gigcitygeek.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Taming Your Plex Library: A Smarter Cleanup Solution?</title>
		<link>https://gigcitygeek.com/2026/04/20/plex-jellyfin-automation-cleanup/</link>
					<comments>https://gigcitygeek.com/2026/04/20/plex-jellyfin-automation-cleanup/#respond</comments>
		
		<dc:creator><![CDATA[Laronski]]></dc:creator>
		<pubDate>Mon, 20 Apr 2026 13:00:00 +0000</pubDate>
				<category><![CDATA[Smarter Not Harder]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[cleanup]]></category>
		<category><![CDATA[digital library]]></category>
		<category><![CDATA[Jellyfin]]></category>
		<category><![CDATA[media management]]></category>
		<category><![CDATA[Media Server]]></category>
		<category><![CDATA[plex]]></category>
		<category><![CDATA[Radarr]]></category>
		<category><![CDATA[rule-based]]></category>
		<category><![CDATA[Sonarr]]></category>
		<guid isPermaLink="false">https://gigcitygeek.com/?p=3644</guid>

					<description><![CDATA[Feeling overwhelmed by your Plex or Jellyfin library? This post explores a new tool that automates cleanup, flagging unwatched, low-rated, or rarely-touched ...]]></description>
										<content:encoded><![CDATA[<p>The other night I was scrolling through a <a href="https://www.reddit.com/r/radarr/comments/1sl8stf/release<em>reclaimerr/&#8221;>Reddit thread</a> where someone casually mentioned their <a title="" href="https://en.wikipedia.org/wiki/Server" target="</em>blank&#8221; rel=&#8221;noopener&#8221;>home server</a> had hit nearly 100 TB, then in the same breath admitted they were scrambling to delete things to make room. That combination of pride and mild panic felt way too familiar.</p>
<p>My library is much smaller, but I have had my own sessions of halfheartedly browsing <a title="" href="https://www.plex.tv/" target="<em>blank&#8221; rel=&#8221;noopener&#8221;>Plex</a> and <a title="" href="https://jellyfin.org/" target="</em>blank&#8221; rel=&#8221;noopener&#8221;>Jellyfin</a>, wondering why on earth I downloaded half of what is sitting there. My wife just wants the shows to play without stuttering and could not care less which version of a movie we have, only that it works when she hits play.</p>
<p><h4>A Promising Kind Of Automation</h4>
</p>
<p>In that thread, a new tool popped up that tries to take the tedium out of this mess by handling cleanup in a more systematic way. It hooks into Plex and Jellyfin, and it can optionally talk to <a title="" href="https://sonarr.tv/" target="<em>blank&#8221; rel=&#8221;noopener&#8221;>Sonarr</a>, <a title="" href="https://radarr.tv/" target="</em>blank&#8221; rel=&#8221;noopener&#8221;>Radarr</a>, and request tools if you want everything coordinated across your stack.</p>
<p>The main idea is <a title="" href="https://en.wikipedia.org/wiki/Rule-based<em>system&#8221; target=&#8221;</em>blank&#8221; rel=&#8221;noopener&#8221;>rule based scanning</a>: you define conditions like “unwatched for X days,” “low rated,” or “barely touched since it was requested,” and the tool flags those titles for potential removal rather than pretending everything is equally precious.</p>
<p><h4>A Careful Approach To Safety</h4>
</p>
<p>What I liked is that it does not jump straight to deleting everything it thinks is useless. Automatic deletion is deliberately disabled while the project is in beta, so you have to approve anything it wants to remove through the UI. There is also a protection system that lets you mark certain shows or movies as untouchable, and users can request that protection too, with admins deciding what sticks. My son’s favorite <a title="" href="https://en.wikipedia.org/wiki/Manga" target="_blank" rel="noopener">Manga</a> films would live under that umbrella without question.</p>
<p>Because of those choices, I would still classify this whole idea as a net positive for people running home media servers, even if the tooling is not perfect yet.</p>
<p><h4>Here Comes The Skepticism</h4>
</p>
<p>Once you read a bit deeper into the comments, the excitement gets tangled with a good amount of distrust. Some people are just tired of “yet another tool” that seems to redo what an older project already tried, worried that the developer enthusiasm will vanish in a few months and leave behind another orphaned <a title="" href="https://en.wikipedia.org/wiki/Container<em>(software)&#8221; target=&#8221;</em>blank&#8221; rel=&#8221;noopener&#8221;>container</a>.</p>
<p>Others jumped straight into accusing the project of being “<a title="" href="https://en.wikipedia.org/wiki/Artificial<em>intelligence&#8221; target=&#8221;</em>blank&#8221; rel=&#8221;noopener&#8221;>AI vibe coded</a>” the moment they saw clean bullet points and structured text in the release post. The developer pushed back and said the code is hand written, and that <a title="" href="https://en.wikipedia.org/wiki/Large<em>language</em>model&#8221; target=&#8221;_blank&#8221; rel=&#8221;noopener&#8221;>large language models</a> are used sparingly as a helper.</p>
<p>That nuance is easy to lose when the default assumption has become that anything polished must have been generated rather than crafted.</p>
<p><h4>What It Says About The Community</h4>
</p>
<p>Reading through it all, I ended up less focused on the specific tool and more on what the whole exchange revealed about the community itself. People running <a title="" href="https://haveibeenpwned.com/arr/" target="<em>blank&#8221; rel=&#8221;noopener&#8221;>Plex, Jellyfin, and *arr setups</a> are dealing with more data, more integrations, and less tolerance for failure than ever, because a single <a title="" href="https://en.wikipedia.org/wiki/Configuration</em>management&#8221; target=&#8221;_blank&#8221; rel=&#8221;noopener&#8221;>misconfiguration</a> can wipe out a lot of time and bandwidth.</p>
<p>At home, my wife and son only see whether their shows are there when they click; I am the one thinking about <a title="" href="https://en.wikipedia.org/wiki/Disk<em>space&#8221; target=&#8221;</em>blank&#8221; rel=&#8221;noopener&#8221;>disk space</a> graphs and cleanup rules in the background.</p>
<p>Tools like this are trying to bridge that gap, making it easier to keep things lean without accidentally nuking the favorites, but they have to fight through a wall of skepticism around AI, project abandonment, and trust before most of us will let them anywhere near the delete button.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://gigcitygeek.com/2026/04/20/plex-jellyfin-automation-cleanup/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
