this post was submitted on 22 Nov 2025
309 points (99.4% liked)

Selfhosted

61425 readers
551 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] tofu@lemmy.nocturnal.garden 4 points 8 months ago (2 children)

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

[–] Andres4NY@social.ridetrans.it 5 points 8 months ago* (last edited 8 months ago)

@tofu @Deceptichum I haven't had problem with concrete walls, but the walls with metal lathe (& plaster) really do a number on wifi and cell signal. I'm guessing different kinds of metal lathe probably makes a difference, too; my prior house literally had chicken wire in the ceilings, my current house has more like a metal sheet with smaller holes punched out.

[–] GreenCrunch@piefed.blahaj.zone 2 points 8 months ago

it seems like the brick walls in my case really impede signal. connection across the sides of the chimney, which is brick, seem to suffer a lot.