codus

Sounds like you need some more hobbies to throw at it. :-)

You could always inflate the numbers by giving it artificial load but I imagine that breaks a ToS somewhere.

I use Steam + Proton in an LXC so I can share the graphics card among several other containers. It works quite well with streaming once I got it set up.

I was going to recommend Logseq as well. I use the git plug-in on laptops and Working Copy (git on iOS) and some automations to sync it on mobile.

Nostr gets rid of the notion of servers and admins. At a high level everyone on nostr owns their own account (no central instance). When you want to post something you send your content to a list of relays you choose.

Other people can choose what relays they want to subscribe to.

Relays can block people from subscribing or posting.

Everything is cryptographically secured so there is no way for someone to pretend to be you.

Lemmy is different where the instance admin has complete control. Admins can post as you and users cannot easily migrate to a different server.

What do your logs say?

In a similar vain, enabling ssh and using that for config or moving files around has saved me a lot of typing.

Similar to how there are Mastodon hosting providers, I imagine Lemmy providers will eventually appear to make being your own admin even simpler.

If there is a vulnerability in the software, it’s entirely possible for a single attack to take everyone down. All the instances are known and easily discovered.

It’s not great but if you copy the URL into your instance’s search, you can get to the post that way.

I also have around 3GB used for pictrs and I’m not really sure the best way to see what all content is in there.

I’ve never been able to successfully sync posts from a kbin Magazine to Lemmy. I also haven’t seen Lemmy users show up in kbin communities so I assumed that subscriptions were unilateral (kbin users have access to Lemmy but not vice versa).

The instance settings now includes a private instance option, which if turned on, will only let logged in users view your site. Private instances was one of our first issues, and it was a large effort, so its great to finally have this completed.

From the release notes.

I haven’t tried it but I think that making an instance private disables federation.

If you aren’t attached to Ansible, I suggest using Docker to host Lemmy. I found it’s instructions, using Docker Compose, to be quite straight forward.

My other 2 cents is that hosting on Windows isn’t worth the hassle and there will be a lot less to debug on Ubuntu if you’re already comfortable with it.

+1 to using a subdomain. You’ll probably have a much better time even if you get a path working.

It’s not the cheapest but I use a DigitalOcean instance to do what you are describing. I’ve been burned by VPS hosts and I’ve enjoyed the complete lack of drama or downtime with DigitalOcean.

For port forwarding I’m using Private Internet Access and gluetun. I don’t really recommend Private Internet Access and, like you, I’m interested in a better solution. It’d be nice if I could use ProtonVPN’s port forwarding but it looks like that only works if you use their app.