This seems like a lot of text for saying “unless you can predict all the specific ways a bad thing could happen, I think putting all your eggs in one basket is fine.” And under some circumstances you’d be right.
This seems like a lot of text for saying “unless you can predict all the specific ways a bad thing could happen, I think putting all your eggs in one basket is fine.” And under some circumstances you’d be right.
That’s why I said I don’t trust them to not fuck up, not that it’s something that should ordinarily be expected. Additionally, especially considering how the rule of law in their jurisdiction is going recently I wouldn’t assume it will always be this way.
Your registrar (the place you buy your domains) is where you update your nameservers. If Cloudflare have locked you out then you won’t be able to change them. Other standard registrars will have far less cause, legitimate or not, to lock or disable your account, since they don’t host/proxy your content.
I wouldn’t buy domains from Cloudflare from a risk mitigation perspective. At work I direct six figures of budget their way annually, but as a free-tier customer in my personal life I don’t trust them not to fuck up at some point and lock my account. If I register my domain elsewhere I can bring myself back online by moving the nameservers. If it’s registered at Cloudflare I’m fucked.
The fuck is Forejo. I’m running a personal Forgejo instance and have contributed to the project. It is not for-profit.
I don’t know what you’re running there mate, Forgejo is a golang app.
They took private investment.
Just curious because I’m thinking about self-hosting, if you self-host an instance why are you not posting from your account there?
Is port 22 accessible and pointed at it? You could also run it on an alternate port and specify that port in your ssh config.
I’m still in the middle of a K8s migration. It’s overkill for a home user, but I want the upskilling.
I’ve got a QNAP NAS with self-managed linux for storage, and a MS-01 with an RTX A2000 for compute. They’re connected over 10Gb SFP+. I’m more than half way done, especially considering I mostly know what I’m doing now.
I still need to figure out the idiomatically right way to schedule pods with their storage, but I got GPU workloads going recently. Next up is migrate the last of the docker-compose from the storage node.
It’s not open source, unavailable on non-apple platforms, and (ironically) needs something like Plex for remote playback.
One of the big selling points of Linux to me was I can automate my install from end to end. I haven’t bothered automating the installer, but once it boots I run a playbook to set everything up and restore most of my homedir from backup. Everything down to setting my custom keyboard shorts, extensions and wallpaper is covered.
These days I run Silverblue and I’m trying to find the time to put together my own build pipeline to build my own images on top of Silverblue’s.
Either way, I have no fear of reinstalls.
💯 I see it the same way.
Yes, that’s one half of what I was getting at. The other half is that it doesn’t prioritise aesthetics.
Listen prioritises aesthetics, but is lacking in function. For me, the missing functionality isn’t important.
There’s no single right answer.
The official app could be described as “functional”. This is a native android app and (imo) looks better.
Decent list and plan overall. Since you enjoy self hosting and seem systems oriented, I’d add Python on the curriculum somewhere. That would round things out nicely for you.
I’m sorry you feel that way, but you literally started off by doing that.