<?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 x00/</title><link>https://fleax.codeberg.page/tags/python/</link><description>Recent content in Python on x00/</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 21:20:00 +0200</lastBuildDate><atom:link href="https://fleax.codeberg.page/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 3 — Running a Local LLM on a Potato (LocalAI on a Celeron)</title><link>https://fleax.codeberg.page/2026/07/part-3-running-a-local-llm-on-a-potato-localai-on-a-celeron/</link><pubDate>Fri, 03 Jul 2026 21:20:00 +0200</pubDate><guid>https://fleax.codeberg.page/2026/07/part-3-running-a-local-llm-on-a-potato-localai-on-a-celeron/</guid><description>&lt;p&gt;&lt;em&gt;Part 3 of the &lt;a href="https://fleax.codeberg.page/series/homelab-telemetry/"&gt;Homelab Telemetry&lt;/a&gt; series. Part 2 got&#10;logs into VictoriaLogs; now something has to read them.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Where this sits in the series:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Part 1 — Overview: the whole pipeline, decision by decision.&lt;/li&gt;&#10;&lt;li&gt;Part 2 — Logs: journald → VictoriaLogs, zero agents on the laptops.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Part 3 — A local LLM triages the logs on a four-core Celeron.&lt;/strong&gt; &lt;em&gt;(keep reading?)&lt;/em&gt;&lt;/li&gt;&#10;&lt;li&gt;Part 4 — Notifications: ntfy, and the two rabbit holes that ate an evening.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The brief: a local model reads the day&amp;rsquo;s notable logs and returns a verdict. The&#10;constraint: it runs on an Intel N5105 that already shares its four cores with&#10;Immich. Everything interesting here is a consequence of that constraint.&lt;/p&gt;</description></item><item><title>Developmenting a Slack Command with python</title><link>https://fleax.codeberg.page/2021/11/developmenting-a-slack-command-with-python/</link><pubDate>Wed, 24 Nov 2021 00:00:00 +0000</pubDate><guid>https://fleax.codeberg.page/2021/11/developmenting-a-slack-command-with-python/</guid><description>&lt;h1 id="the-idea"&gt;The idea&lt;/h1&gt;&#10;&lt;p&gt;&lt;em&gt;afk&lt;/em&gt; is a well-known aslias to let others know that you will not available on the chat for a while. Slack has a status on your profile. But for some reason we still keep using the afk appreviation, at least this is the case in my team. So why not make it a slack command which will store each afk, optionally with a message and it could also tell you all the ppl who are afk at the moment until they make their present available again.&lt;/p&gt;</description></item></channel></rss>