1. Control and privacy. The server does exactly what I choose, not somebody’s business model.
2. Once you have other users, it’s not a hobby anymore. People are not amused by downtime.
3. The w3schools.com tutorials have been good for me.

Ooh. Extra bitter with your bitter.

Just made one of these. I probably got the recipe wrong, but can confirm, it’s delicious.

Seems like we always have cans of condensed milk left over from some holiday dessert, I want to try this one too. Sort of like the affogato except already melted.

Mmm, going to try that

I drink it. That’s a nice tin, though. I have lots of beans, tea and mate that would feel honored to be in that tin.

Guatemala Proyecto Xinabajul Dos Villatoros from Sweet Maria’s, roasted just a little past medium, ground in a Hario Skerton by hand, about 5 clicks on the grinder setting, brewed pour over in a Melitta single serving ceramic cone. Bloom it first, pour splashy the second time. It takes about 2 minutes for the brew to finish.
I play with beans and roast a lot, I am pretty fixed with brew technique.
I found some instant in a Vietnamese market once that was interesting. I usually avoid instant.
Like I said, I keep brew the same so as to evaluate playing with roasting, but I am open to ideas, I could probably do it better.

Two things, one you care about and one you might not. The one you care about: you can set up a service in isolation. You can then test it, make sure it works, and switch over to it once you are sure, with almost no downtime. This is important for things you actually need to use. Once you do something like breaking your primary email server, you will understand. Also, less important, you can set up a service on, say, a VM at home, and move it to a VPS, without having to transfer the entire image, and it will work the same. The one you don’t care about. That last bit about moving servers around is important for cloud providers who turn these things on and off all the time.

name.com. I don’t remember why I picked them, but they do no BS and the service is fine.

I do believe blooming is good, the first pour should be gentle and get the grounds wet, and the second pour should be from higher up, to agitate the grounds. There are probably other ways to get the same results. People tend to mess around with whatever techniques they can, do something that makes a better cup, and settle on that as the way to do it. There’s more than one good way.

Likewise. I have been running it for years, almost no problem that I can think of. My setup is pretty vanilla, Apache, MySQL. It’s running in a container behind a reverse proxy. I keep it as up to date as possible. Only 3 people use mine, and I don’t use very many apps: files, notes, bookmarks, calendar, email.