LOL OK

Would like to have known your questions, though. All I have is your edit.

I wrote a blog article about this a while back with references to what this meme is actually quoting.

https://netmonkey.net/2023/06/03/nobody-wants-to-work-anymore/

Also, the point isn’t whether people want to work or not, but rather that the moral panic keeps coming up.

Thank you for reminding me. 😛 I’m camping this weekend.

Those paws. ❤️

You probably would be, but that depends on the law where the server is hosted. This isn’t a good place for legal advice like that.

What kind of server do you want to host?

Since AP servers both accept incoming connections and make outgoing connections, both sides need valid certificates to do HTTPS.

Good luck getting the server connecting to you to trust it!

I can’t imagine it’d work without a domain, as your instance will need to talk HTTPS with other instances.

That’s pretty much been my experience, as well.

It’s a timeline approach. So, I just enter notes for each day. I’ve developed a habit of just putting things down when I need, including random stuff, links to Slack conversations, etc. I then use tags to bind things together, and there are a couple of plugins in use.

I’ve been using Logseq at work and I LOOOOVE it.

It’s something that Linux users have been saying for 20 years and it’s outdated. It makes sense when maybe your computer came with less than a GB of RAM, but these days I usually configure a server with a small amount of swap (like a couple of GB), and I set swappiness to something very low like 5.

No.

What are the potential point of failures for having your own domain?

Forgot to answer this. My advice would be to pick a good DNS provider.

It doesn’t have to be the company which registered your domain. A good provider will generally have more than authoritative DNS servers, will generally have them in separate top-level domains (e.g., .com, .net, .uk, etc.), and may even be running Anycast, which makes them even more resilient.

There’s a difference between your domain registrar and the authoritative DNS servers for your domain. For example, I register domains with Hover, but host the DNS at AWS. If Hover were to go down, I don’t see how that would have any impact on my DNS. If AWS’s Route53 were to go down, then my DNS is only as good as what’s cached out there on the Internet.

Depends on the context, I think. For me, I rarely do it for personal stuff. If I wanted to be perfect, I could do it, assuming a signature is available to verify, but I’m lazy. I would venture to say most folks don’t do it either.

With that being said, where I have been consistent about doing it has been writing config management code at work. If I need to have it download an installer from an untrusted source, I can verify that I’m installing the same package on all servers by verifying the signature before installation. This doesn’t always work well in all circumstances, though.

I tend to prefer installing Debian on a server, but recently I did install Ubuntu’s recent LTS on a box because I was running into an issue with the latest version of Debian. I didn’t want to revert to an earlier version of Debian or spend a bunch of time figuring out the problem I was having with Python, so I opted to use Ubuntu, which worked.

Ubuntu is based on Debian, so it’s like using the same operating system, as far as I’m concerned.

Yup, I’ve read something similar. Hopefully they’re able to get things sorted out soon!

I’ve not personally noticed any federation issues with Beehaw on my instance. Glad to hear things are better tonight.