this post was submitted on 22 Nov 2025
217 points (99.1% liked)

Selfhosted

53090 readers
776 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Someone on another Lemmy instance raised the question of whether an old wifi router could make a usable server of some sort, specifically a decade-old Google AC-1304. Since I happened to have a couple hanging around, I decided to give it a try.

I wrote a little about my experience in my blog but to summarize, I thought it would be fun to se if I could run a GoToSocial instance entirely on the router. It has an ARMv7 processor, 4GB of storage, and 512MB of RAM, so it falls a smidge short of the recommended minimum specs, but I figured that I might be able to get by if I kept the instance simple.

Surprisingly, GTS seemed to run fine after some basic configuration tweaks. The biggest issue I encountered was actually with ffmpeg, rather than GTS itself. The only GTS build available for ARMv7 is a nowasm build, meaning that it's missing the built-in media handling components, and instead relies on ffmpeg being proveded by the host system. The version of ffmpeg that ships with the OS I'm using (OpenWRT) didn't have the needed codecs to create webp files, which GTS requires when dealing with media. Using the OpenWRT SDK, I tried to build an ffmpeg package with the correct codecs, but it still failed to properly convert files to webp. My goal was just to run GTS, though, so I that digging deeper into ffmpeg felt like a tangent I didn't want to pursue.

But I digress. The instance is now online and running (though without media), and I created a simple bot account, named Gale, who will post a random fact about wifi and networking each day. Feel free to give 'em a follow in your favorite Mastodon client at @gale@gts-googlewifi.k3can.us or you can view past toots here

Just wanted to share!

you are viewing a single comment's thread
view the rest of the comments
[–] qbit@lemmy.sdf.org 13 points 10 hours ago (1 children)

Nice! I just picked one of these up from the thrift store and flashed openwrt.

[–] GreenCrunch@piefed.blahaj.zone 6 points 9 hours ago (1 children)

Oooh, they work with it? ... my family still has these as actual WiFi routers. the coverage kinda sucks.

[–] Deceptichum@quokk.au 2 points 6 hours ago (1 children)

I still use them and the 3 of them cover my entire house without issue?

[–] tofu@lemmy.nocturnal.garden 1 points 4 hours ago (1 children)

Idk how large your house is, but our house (3 stories + basement) and garden are easily covered by a single wifi router, so needing 3 doesn't sound so great

[–] Deceptichum@quokk.au 2 points 4 hours ago (1 children)

It's not about the size, it's the walls. Signal barely travels more than 2 rooms over without being dog-shit. All routers have been like this for me, it's only a mesh set-up that's helped mitigate it.

[–] tofu@lemmy.nocturnal.garden 2 points 4 hours ago

Hm, weird, our concrete walls and ceilings aren't that bad