<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fediverse on Notes from the Rabbit Hole</title><link>https://magnus919.com/tags/fediverse/</link><description>Recent content in Fediverse on Notes from the Rabbit Hole</description><generator>Hugo</generator><language>en</language><copyright>© [Magnus Hedemark](https://github.com/magnus919)</copyright><lastBuildDate>Wed, 29 Jan 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://magnus919.com/tags/fediverse/index.xml" rel="self" type="application/rss+xml"/><item><title>GoToSocial on a Raspberry Pi Zero 2 W: Will it work?</title><link>https://magnus919.com/notes/gotosocial-on-raspberry-pi-zero-2-w/</link><pubDate>Wed, 29 Jan 2025 00:00:00 +0000</pubDate><guid>https://magnus919.com/notes/gotosocial-on-raspberry-pi-zero-2-w/</guid><description>&lt;p>I didn&amp;rsquo;t keep good notes as I went, honestly. I did a first pass on this &amp;ldquo;shooting from the hip&amp;rdquo; a bit to just see if I could get it to work.&lt;/p>
&lt;p>Instead of using Docker-CE, I used &lt;code>podman&lt;/code> which created a little bit more work (not much at all really). Ultimately the service did start up, did run. It was even usable &lt;em>until&lt;/em> the moment it started federating. As soon as I started following external accounts from the instance, and the federated traffic started coming in, I could see that the system was hitting high &lt;code>loadavg&lt;/code> numbers (like in excess of 5.0). But the CPU cores still had plenty of idle capacity.&lt;/p></description></item></channel></rss>