<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Python on forrestcook.net</title>
		<link>https://forrestcook.net/tags/python/</link>
		<description>Recent content in Python on forrestcook.net</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Apr 2025 00:00:00 -0700</lastBuildDate>
		
			<atom:link href="https://forrestcook.net/tags/python/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Varints - because this wasn&#39;t complicated enough already</title>
				<link>https://forrestcook.net/posts/varint/</link>
				<pubDate>Mon, 21 Apr 2025 00:00:00 -0700</pubDate>
				<guid>https://forrestcook.net/posts/varint/</guid>
				<description>&lt;p&gt;While working through the potato chat BLOBs, I was introduced to the varint concept. Effectively, a varint is a flexible way to communicate positive integers through one or more byte of data, dynamically.&lt;/p&gt;&#xA;&lt;p&gt;Instead of an application always requiring an integer use &lt;em&gt;one&lt;/em&gt; byte of data to convey a number (and thus being limited from 0-255), or the application always requiring some larger number of bytes to convey a larger span of integers, a varint can be used.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Potato Chat pt. 2; Starchy Boogaloo! 🥔💬</title>
				<link>https://forrestcook.net/posts/potato_chat_pt_2/</link>
				<pubDate>Thu, 17 Apr 2025 00:00:00 -0700</pubDate>
				<guid>https://forrestcook.net/posts/potato_chat_pt_2/</guid>
				<description>&lt;h3 id=&#34;update---08222025&#34;&gt;Update - 08/22/2025:&lt;/h3&gt;&#xA;&lt;p&gt;Christian Peter has continued this research into areas I have not addressed - his post is worth a read and the coming LEAPP parser is exciting news!&#xA;Check out his writeup here: &lt;a href=&#34;http://cp-df.com/en/blog/potato.html&#34;&gt;http://cp-df.com/en/blog/potato.html&lt;/a&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;In the last post I brought up some behaviors that I was able to test and observe within the potato chat application. While I am not done testing the application&amp;rsquo;s behaviors (there are many&amp;hellip; so many), I have also been attempting to process the various databases and logs to make some meaningful headway into documenting user activity through the app. The two main databases I have been working with are:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Case Management Utility</title>
				<link>https://forrestcook.net/posts/case_mgmt/</link>
				<pubDate>Mon, 10 Mar 2025 00:00:00 -0700</pubDate>
				<guid>https://forrestcook.net/posts/case_mgmt/</guid>
				<description>&lt;p&gt;I often find myself happily exploring rabbit holes in digital forensics, time discipline is not a strength of mine. So in order to better manage my time and enhance my productivity, the clear choice was to spend (many) hours learning Python to automate some of my day to day activities. The &amp;ldquo;Case management script&amp;rdquo; (which doesn&amp;rsquo;t manage anything, btw&amp;hellip; I&amp;rsquo;m not good at naming things) was my first real undertaking with Python.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Warrant Builder</title>
				<link>https://forrestcook.net/posts/warrant_builder/</link>
				<pubDate>Sun, 17 Nov 2024 21:11:54 -0700</pubDate>
				<guid>https://forrestcook.net/posts/warrant_builder/</guid>
				<description>&lt;p&gt;Creative names aside - I took it upon myself recently to attempt to streamline the warrant writing process at my agency. This endeavor took place over many months and several iterations as I stumbled forward learning Python and some pertinent libraries. Moving from quality of life automations based on command line inputs for myself, I began to learn to put together a GUI based application to modify a .docx template file. Features piled up in my brain faster than I could accomplish them through code but eventually I have gotten to a stage where the program is functional enough to share.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
