LibreOffice Draw?

All of the services that I host are for private use:

• Nextcloud
• FreshRSS
• Immich
• Jellyfin
• RSSBridge

And they are all behind Caddy, which reverse proxies and handles HTTPS. I’m not sure if it really counts as self-hosting, but I also use my server as a host for my backups with Borg. I also use it as a sort of central syncing point for Syncthing.

I did have a Pi-Hole at one point, but I kept running into issues with it — I may look into it again in the future.

At some point I’d like to try implementing some ideas that I’ve had for Homeassistant (a camera server with Frigate and some other automation things). Once federation has been implemented, I would like to host a Forgejo instance. I may also host a Simplex relay server, depending on how the app progresses. I’ve been considering hosting a Matrix instance, but I’m not sure yet.

Are you looking for something for a headless server or something for a system with a GUI (eg a desktop)?

It entirely depends on how you want your homelab to work. I use a reverse proxy to set up subdomains for my publicly facing services because I find it easier and cleaner to assign a subdomain to each service, and I also like having HTTPS managed by a single point — a sort of single point of entry to the rest of the services. You’d have to decide what you want out of your homelab, and find and set up the services that yield the outcome that you want.

+1 for Factorio.

I honestly forgot that this game existed. I remember it being very well made, but I could never fully get into it for some reason.

Yeah, take a look at the solution at the top of the post.

Local Only Communities

Local communities are an interesting concept, though I am concerned about unintended side effects. I have noticed many times that people from other instances chime in to meta-communities to provide some alternative viewpoints and context when instances are discussing interactions with the rest of the network. I worry that some will become too isolated/sheltered. But I suppose, in the end, that’s ultimately up to the individual instances to decide.

Lemmy can now federate with Wordpress, Discourse and NodeBB.

Increased federation capabilities is always awesome to see!

In order to improve interoperability with Mastodon and other microblogging platforms, Lemmy now automatically includes a hashtag with new posts. The hashtag is based on the community name, so posts to /c/lemmy will automatically have the hashtag #lemmy. This makes Lemmy posts much easier to discover.

This is a clever solution. I think this is a good way to go about it.

RSS feeds now include post thumbnail and embedded images.Security

I really appreciate the continued attention given to keep RSS alive.

A security audit was recently performed on Lemmy.

Awesome! And congrats!

• Added Community local_subscribers count
• Support for custom post thumbnail
• Indicate to user when they are banned from community
• Added alt_text for image posts

Great features for improving the polish and user experience on Lemmy!

Would you mind pointing out examples of them boycotting the software? From what I saw in their comment history, it was mostly them talking about moving away from centralization on lemmy.ml.

That only exports settings (general account config, saved posts and comments, blocked users, communities, and instances, etc.). That won’t export all of the user’s own posts and comments.

There’s no need to port the game. Just make sure that the Windows version is compatible with Wine/Proton.

EDIT: Nvm — at the end of the article, it states that it’s probable that part of the reason why the Linux version was cancelled was because proton already works well.

On the Linux side, it’s also not overly surprising given that we have Proton now which enables the game to run with a tick of box on Steam. I even showed it previously running really nicely on Steam Deck with Proton using the demo.

You’re welcome 😊

There’s already an issue open for this.

so might run into more roadblocks with its use.

This has been my experience with Podman. That’s not to say that these roablocks aren’t without reason, nor merit, but there is always a trade off of convenience when optimizing for security.

Podman is […] “better” because it doesn’t run as root, but other than that I don’t know of any advantages to it that are not a derivation of “it runs as a regular user”.

Podman can run in rootless mode (with some caveats), but it is still able to run as root — it doesn’t only have the capability to run as a “regular user”.

I am curious what kind of performance you’re seeing for DNS requests considering how old and anemic the first gen Pi is

I haven’t done any rigorous tests to gather empirical data for an accurate comparison, but, annectdotally, it, at least, doesn’t feel any slower than when I had my router (Linksys E8450) resolving to Cloudflare.

I could be misunderstanding your comment, but you don’t seem to have answered my question of why I don’t see my rules anymore.

Now that it is up and running, do you think it’s is a good service?

That’s a good question. The service itself is well made — it functions as advertised, it has satisfactorily intuitive UX, a sizeable community, and a good amount of documentation. I’m not sure, yet, if it’s a service that I personally need — I set it up mostly for the benefit of others.

While you may not like the setup

The main pain points were the sparse, vague, and misleading documentation that I encountered — I understand that documentation is difficult, but for a company like Raspberry Pi, my standards, and expecations are quite a bit higher. I probably won’t use Podman anymore, as I don’t find its setup overly user friendly, currently, as compared to something like docker. I had never used Podman before, and I was considering switching my existing services over to it, so this was sort of meant to be a trial run on something with little impact. I will keep an eye on Podman, but I will stick with Docker for the time being.

do you enjoy the results?

I personally don’t notice its effects as much, but I do like what I’m seeing for others. It has also made me aware of some other issues that I’ll have to look into, so that is good.

It’s a raspberry pi 1. Those things have 256mb of RAM

The exact model that I am using, which I referenced in my post, actually has 512MB of RAM.

Given the extremely limited resources: why bother with containers?

While, from what I can see, containers virtually don’t add any resource overhead, it’s honestly moreso that I favor consistency. Containerization is well documented, it is well supported, and its behaviour (if one is familiar with the platform) tends to be more predictable than running a service natively.