Thank you! I just upgraded the lemmy version. I thought it would be difficult but it was more painless than I thought.

Ah, I did not know this was a problem. The only reason I haven’t upgraded yet is because it could break the current config. In any case, I’ll try doing it as soon as possible.

I’m working on it. Apologies for the downtime. I added enough resources to keep this from happening for another year, although I’ll try to migrate to 0.19 this week.

Yes, I’ll upgrade this week at latest. Sorry for keeping us back. Historically that used to be the safest decision for Lemmy, but I do realize it’s been a long time.

Thank you. I’ll add that to the status monitor. Do you have experience in system administration? I am basically unable to take proper care of yiffit at the moment, often being out of town and I need some help :(

I’m sorry. Apparently the Lemmy server component went down but because the frontend was still responsive my downtime monitor didn’t detect it as down.

It should now work again! Apologies!

I’m still around, but busy. I’ll try to enable push notifications.

Thank you for letting me know. I’ll have a look into it as soon as possible!

It can be made easily via their API, but depends on what features you’re looking for. What is it that you miss from the web version?

Yes, but It’s pretty hands off since 99% of security stuff is managed for you by the Lemmy software, including rate limiting. Just make sure you use a secure password and if you want put the instance behind cloudflare which is super easy to do.

Don’t buy Apple. As simple as that. You know when a company gives you the creeps? That’s how I feel about Apple.

Good idea! And yes, the idea is to edit it or strike things through as they get done.

I’d say to start with CF tunnels unless you need non-web based applications. Cloudflare tunnels require you to have a domain, though.

It has the added benefit that you have network monitoring, logging and some filtering for security that they do on top and you get to manage everything from their web interface.

be warned that the first time can be a bit confusing, but since it’s done using their web interface it’s easier than if you have a problem making wireguard work.

1. Create a tunnel with a public hostname that will be the url to access that service. During the creation of the hostname specify you want it protected by L7 application firewall.
2. Create a new self-hosted application in cloudflare application section and for starters use the default login email and in rules specify the list of emails that are allowed to login

you should now be able to access your application from anywhere.

Alternatively, if you have a DNS server in your home network you can add a private IP range to your tunnel. Let’s say 192.168.0.0/24. Then when you connect with their pseudo-VPN (cloudflare warp or cloudflare ONE) you can directly use your home network’s ip address from that device. If you tell your device to use a local DNS server that resolves your internal services, you’ll be able to connect to them that way.

Original idea by: @[email protected] . Thank you!

Cool, I’m already working on something. Used @[email protected]’s pythorhead library to keep it populated.

That’s not a bad idea, but maybe we could have a link to [email protected] instead? Or it could be a link to a static page with a list of all communities. I think that’s more feasible since it wouldn’t clutter the comment section with a very long post.

She’ll have to get a computer and use it in her free time instead of a phone. It’s the best way

I need to have a look at this. Thank you!

Joplin I think, or Trillium but that one could be less user friendly.