<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>Pizza's server updates</title>
<author>Pizza2d1</author>
<link>index.xml</link>
<lastBuildDate>24 Oct 26 16:30 -0600</lastBuildDate>
<description>Pizza's server updates</description>
	<item>
		<title>Testing out RSS</title>
		<link>index.xml</link>
		<pubDate>24 Oct 26 16:30 -0600</pubDate>
		<guid>index.xml/01_First-post</guid>
		<description><![CDATA[<p>This is the first rss bit that Im putting out that should be able to just be converted to xml format, but we&rsquo;ll see</p>

<h2>Plans on how this should work</h2>

<p>I mostly just wanna use this as a way to put out updates for my server, whether it be for things with jellyfin or for the website or just some nerd stuff that nobody else will care about, the main reason is mostly just to have a way to both document and to let people know what is going on</p>

<h3>Other things</h3>

<p>Here&rsquo;s a test to see if your rss feeder can render images (or if my markdown -&gt; xml tool can convert this successfully)
<img src="https://copyparty.happylizard.me/media/images/memes/17846245858425546572319761338929.jpg?k=ymcf" alt="" /></p>

<h1>Big</h1>

<h2>Biggish</h2>

<h3>Medium</h3>

<h4>Smaller</h4>

<h5>Smaller</h5>

<p>Testing out LaTeX:</p>

<p>Native markdown:
<span class="math inline">\(\pi \ne 3.14\)</span></p>

<p>Online tool:
<img src="http://latex.codecogs.com/png.latex?y=x^2" alt="penisballs" /></p>
]]></description>
	</item>
	<item>
		<title>Jellyfin server is updating to 12.0</title>
		<link>index.xml</link>
		<pubDate>19 Oct 26 15:17 -0600</pubDate>
		<guid>index.xml/02_Jellyfin-update-to-v12</guid>
		<description><![CDATA[<p>The newest version of Jellyfin is out and with the appeal of better performace and sercurity patches, I really wanted to update to it asap, but the first time I did it, everything broke and I didn&rsquo;t have a proper backup of the jellyfin instance so a lot of data was lost and I had to go back to regular 10.11.11, which was fine since it still had compatibility with third-party apps like JellyMusicDiscovery + ytmusicserver.</p>

<h2>New movies and shows</h2>

<p>Sadly I don&rsquo;t think I will be spending much more time adding content and will instead be working on trimming down the fat, so that people who might wanna mirror or people who worry about bandwidth don&rsquo;t have to worry as much. Notable shows and movies being The Big Bang Theory and most of the Spider-man films, which were uneccessarily big. With this trimming of most shows we should be able to save about 500 GB - 1 TTB of storage which would be really nice considering that I am running low on storage, the process of trimming down has already started and we have already saved over 300 GB</p>

<h2>Performance</h2>

<p>Jellyfin also switched back to using a proper GPU on a laptop rather than using 90% of the server rack&rsquo;s CPU when transcoding in real-time, making loading speeds of shows and movies take almost half as much time, from a consistent 4-7 sec to about less that 3 sec, and that&rsquo;s just with the hardware switch, I haven&rsquo;t tested Jellyfin version 12.0 performance yet</p>
]]></description>
	</item>
	<item>
		<title>File organization</title>
		<link>index.xml</link>
		<pubDate>20 Oct 26 14:10 -0600</pubDate>
		<guid>index.xml/03_file_renaming</guid>
		<description><![CDATA[<p>The server media files have now been updated to be standardized and better organized so that when browsing and indexing files they are easier to identify.</p>

<h3>Shows</h3>

<p>A big issue that was happening was that there would be many different season folders that would be fragmented and in different names that made it impossible for things like Jellyfin and the rstack to be able to read the files correctly, leading to incorrect episode listings e.g.:</p>

<p>Regular Show - Season 1<br>
Regular Show - Season 2<br>
Regular Show - Season 3<br>
Regular Show - Season 4<br>
Regular Show - Season 5<br>
Regular Show - Season 6<br>
Regular Show - Season 7<br>
Regular Show - Season 8<br>
Season 3<br>
Season 4<br>
Season 6<br>
Shorts</p>

<p>The issue is that you would have things like episodes S03E05 - S03E08 in the &ldquo;Season 3&rdquo; folder with all the other season episodes in the proper &ldquo;Regular Show - Season 3&rdquo; folder, but Sonarr wouldn&rsquo;t see it as an issue and would just keep them separated, leading to there being multiple folders and incorrect indexing in Jellyfin and somewhat in copyparty</p>

<hr>

<p>The fixed way would look more something like this:</p>

<p>Regular Show - Season 1<br>
Regular Show - Season 2<br>
Regular Show - Season 3<br>
Regular Show - Season 4<br>
Regular Show - Season 5<br>
Regular Show - Season 6<br>
Regular Show - Season 7<br>
Regular Show - Season 8<br>
Specials</p>

<p>Since Jellyfin will identify folders named as &ldquo;Special&rdquo; as a dedicated folder for extra files, rather than &ldquo;Shorts&rdquo; or &ldquo;Extras&rdquo;</p>

<h3>Movies</h3>

<p>Movies didn&rsquo;t have much of a change since many of them were already fomatted correctly manually a while ago, the main changes were getting rid of video files that had simple names with no parse-able data for Jellyfin and Radarr, making it so that even though there was a valid video file, Jellyfin would mix up movies and Radarr wouldn&rsquo;t count it as a valid file to index e.g.:</p>

<p>In the &ldquo;Django Unchained&rdquo; folder:
- django.mkv</p>

<p>Django wouldn&rsquo;t be properly indexed, and radarr would show it as unavailable unless it was renamed</p>

<p>Fixed:
- Django Unchained (2012) 1080p BrRip x264 -YIFY.mp4</p>
]]></description>
	</item>
	<item>
		<title>Storage News</title>
		<link>index.xml</link>
		<pubDate>24 Oct 26 16:24 -0600</pubDate>
		<guid>index.xml/04_Storage-news</guid>
		<description><![CDATA[<h3>Running out</h3>

<p>Unfortunately as the server keeps growing, the storage that it&rsquo;s has isn&rsquo;t, making it so that things like movies and shows will slow down for how many are added to the server and suggestions that are added to the server won&rsquo;t be considered as much as before when I would just add whatever people asked for</p>

<p>For reference on the large things taking up storage space that might need to be reconsidered:
<br>
<strong>Top Gear</strong> - 183.5 GiB
<br>
<strong>South Park</strong> - 134.5 GiB
<br>
<strong>The Amazing World of Gumball</strong> - 109 GiB
<br>
<strong>Brooklyn  Nine-Nine</strong> - 101.7 GiB
<br>
<strong>Futurama</strong> - 100.8 GiB
<br>
<strong>Psych</strong> - 91.4 GiB
<br>
These are <strong><em>OBSURDLY</em></strong> big shows that do not need to be as such when they have not and are not being watched. So as time goes on it is very likely that these shows will either receive a downgrade from 1080p to 720p, will only include the first couple seasons until more is requested, or will be removed entirely.
<br></p>

<h3>Plans on adding more storage</h3>

<p>As of now there&rsquo;s not much that I can do when wanting to upgrade the storage of the server other than to just buy more expensive drives, get a dedicated storage server, or turn to cloud storage, all of which are very expensive and is something I would rather not do, especially since I don&rsquo;t have an actual income<br>
I have had suggestions that maybe some people would be willing to mirror my server so that there is better availability in case of a server crash, and to alleviate the storage issues, but honestly I don&rsquo;t think I can reliably offload these issues yet until I have a proper storage standard (which is currently being worked on) and I can teach them how to use tools like radarr and sonarr and whatnot appropriately so that there&rsquo;s no accident that involves downloading a 100 GB season of Scooby-Do or whatever.</p>
]]></description>
	</item>
</channel>
</rss>
