The 3DS on the other hand…

https://github.com/zoeyjodon/moonlight-N3DS

What is the advantage of this over just dropping HTML files onto a USB drive?

Not often, but there’s a niche. I wish I could remember the details, but I saw someone earlier this year that was hosting a public BBS on a c64.

Same experience. 🫤

Personally, whenever I need to process anything text-based, I use perl.

Read the json into a hash, parse the values if desired, then plug the values into an html template.

It’s pretty quick to write, much easier to learn than python (in my opinion), and super powerful.

I’m a bit torn on the hardware bit, myself.

On one hand, hardware is a fundamental aspect of self hosting. There’s already a portion of the community who considers self-hosting to include using commercially-hosted cloud services (as long as it’s not Google), so prohibiting hardware discussion just reinforces that concept. Plus, it can be really fun to see what creative hardware people come up. I’m pretty sure I posted about my Fediverse server running on a WiFi router here, for example. The focus was on the unusual hardware, but it was also clearly related to self-hosting.

On the other hand, looking at what is posted in other communities, I don’t think there’s a ton of value in seeing a dozen photos of a bone-stock rpi or a closed laptop sitting on a desk. Same with the nth post asking if their 30-year-old 1u would be a good choice for Jellyfin; so I see why the rule exists.

Overall, though, I think hardware should be allowed, but maybe add a rule along the lines of “if you’re posting a question, please include what resources you’ve already reviewed or troubleshooting steps you’ve already taken.”

Heck, that might be a good rule for all questions, regardless of topic…

The first one. The service is owned by root, but the application is running as an unprivileged system user.

Quadlets work like any other systemd service.

You create the user/group you want to run as on the underlying system, then just specify that user/group in the quadlet file.

If you look at my *arr examples, you can see the user and groups they’re running as.

Podman quadlets can also auto-update and auto rollback, if needed.

It’s a function of a “pod” within podman.

I wrote the podman examples for AudioMuseAI using a pod: https://github.com/NeptuneHub/AudioMuse-AI/tree/main/deployment/podman-quadlets

And I have an example *arr suite on my GitHub page: https://github.com/K3CAN/podman-arr-quadlets

I’ll second podman quadlets. Good security, full integration with systemd, pods allow applications to easily share a namespace, and you can manage graphically through Cockpit if you really want to.

Correct. Full-upgrade is the new term. It’s an alias, though, so using either will accomplish the same thing.

The computer itself isn’t the only element that makes up a centralized social media platform. Reddit, for example, isn’t just a random giant server in the middle of a desert; it requires tons of additional costs and inefficiencies to run that business, like entire buildings and hundreds or thousands of people.

When it comes to the electrical impact, concentration matters a lot, too. 100MWH consumed by a single data center stresses the infrastructure far more than the same total amount of power being consumed by 10,000 locations spread around the world.

I don’t know the source, but this user uses it for a lot of their websites.

hashtagsafety.getinfotoyou.com imageslim.getinfotoyou.com holidaysync.getinfotoyou.com and so on.

Quadlets. Auto update and auto rollback if the new image fails to start. Plus easier management overall, too.

Yeah. I just needed to provide a US-based mailing address.

Debian on my servers. No drama, it just works.

Fedora on my laptop and desktop. Still solid, but quicker updates.

Which is exactly what is demonstrated in the post. 🙃

Thanks! I like to keep things simple. The colors are based on Counter Strike 1.6. 😁

And if you’re into the classic styling, my homepage is a direct homage to my old 2000s sites.

True, but this is specifically about scripts you think you know, and how curl bash might trick you into running a different script entirely.