I use Proton Mail for my primary domain and then addy.io for redirects to it. It costs $10 a year or something like that and it’s all I actually need.

Replying to emails is as easy as just hitting reply, the only thing that’s slightly harder is sending entirely new email (as in not replying) but even that can either be remembered, or the special email address copied from the addy.io app.

Avahi basically broadcasts to the whole network “hello there, my name is some-cool-domain.local”. When you request that address, your router checks if someone broadcasts that name and uses their IP if so.

Yes, indeed, it’s your local timezone.

store all of the documents, desktop, downloads, etc. on a couple computers

Why use SSHFS for that? I recommend using Syncthing, it’s great for synchronizing stuff across multiple PCs (local and remote).

You need to host your domain somewhere, meaning some DNS provider needs to be the authority on what gets routed where when someone accesses your domain.

The provider will give you a list of nameservers when you make the domain part of their DNS.

I don’t know if there are any that are free (if you don’t also buy a domain from them), so you’ll have to check on your own. You can also self-host a bind9 server and do your DNS there.

Ah, I’ve only ever seen it in combination with a tunnel, so I assumed it’s part of that.

It makes a tunnel through to you and links to that.

True. But pretty much the same applies for dynamic DNS services, except you have to trust your dynamic DNS provider.

I meant more because people generally don’t have as much time to spend on IT security as companies, but yeah, it works for privacy as well.

My recommendation: host OpenVPN, change the default port and only access your NAS from the internet using your VPN. Also only allow the VPN port on your router firewall.

Note that I only did a brief evaluation of baby buddy, compared to that:

• better looking and less confusing
• snappier user interface
• fully end-to-end encrypted

I don’t know about other features, like sharing etc., but my reason to create this was that I wanted something modern looking without security compromises.

Yep, that’s planned, as it has already been requested.

Well, technically speaking you can use it for that.

I’ll whip up some docker image during the next week!

Well, managing servers is part of my job. So stuff like what you mention doesn’t really make it easier for me and it adds unnecessary overhead.

In theory, though in this particular case you’re giving them to an open source app which you can check the source code of. Of course there is the possibility that I’ve modified the code that I’m hosting, you’re gonna have to trust me that I didn’t.

I’m an author of many open source libraries and apps and I have no need to steal your credentials. Though that of course doesn’t have to mean anything to you.

But if you’re giving your credentials to a mobile app or any other frontend, you’re doing pretty much the same thing. And technically speaking, even trusting your instance admins is the same thing - they might have modified the code to log your credentials.

In general, yes, you should be worried where you put your credentials. In ideal scenario Lemmy would support OAuth or something like that, but that’s not the case currently.

You can also use the hosted version, if you wish so. I’m also the author of the client library for Lemmy that this uses and just two days ago I’ve updated the library to work with 0.19 (though it’s not updated in Lemmy Schedule yet).

Yes, currently swamped with work so I have to prioritize. I’ll get to it, though no promises on when.

That sounds like a wrong metric to use. Better than nothing, but upvote and comment times seem like a much better one.

It would probably need a direct access to the database (which I want to avoid), there currently aren’t apis for that. Best I could do is based on comment times but that can be inaccurate (lurkers are not taken into account).

If you want, raise it as a feature request either at the Github repo or at !schedule@lemmings.world.