excess0680

@excess0680@lemmy.world

• ⁨Comment⁩ on ⁨If you have one, how much do you pay for a domain name? Any cheap registrar recommendations?⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

  I’ve read that if you or your family depend on some kind of firewall provided by a company (and removing or disabling it is not allowed), then that firewall might outright refuse to connect to such a domain, even if the domain was never used. (Basically outright blocking .xyz at the root.) It’s not applicable in most cases but it is definitely a case of overzealous “protection” software. It’s just an unpredictable outcome and a risk. If you don’t plan on hosting email and don’t use a firewall like that, then it would be marginally acceptable.

  I would still strongly recommend a .com or .net. The only advantage of using lesser known (or of low reputation) TLD is that more domains will not have been taken. I’d rather just try to be creative or pick something longer with .com.

• ⁨Comment⁩ on ⁨If you have one, how much do you pay for a domain name? Any cheap registrar recommendations?⁩ ⁨⁨6⁩ ⁨days⁩ ago⁩:

  Beyond just the registrar you pick, try not to pick some vanity TLDs. The ubiquitous ones (e.g. .com and .net) are fine. For example .xyz has a bad reputation (due to its initial low price to register, it became used for many spammers) and might be blocked in unexpected places. Others might lure you in with a cheap first year but charge much higher for subsequent years.

  In addition to that, ccTLDs (country code) can be a wildcard, especially if you don’t live in the region served by it. Although rare, the country registry can seize your domain. Most commonly though, many, including .us, do not allow you to mask your personal information (WHOIS privacy). I’ve had a .me for a long time and even though they haven’t been much of a problem, they are also raising the price for renewal faster than an equivalent .com, and so I’ve been thinking of letting that domain go.

  If you trust your country’s ccTLD registry and they’re reputable, that’s less of an issue, however.

• ⁨Comment⁩ on ⁨rootless backup or rootless podman volumes?⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  In addition to podman unshare (which you would just prefix in front of commands like chmod), you can just temporarily do podman unshare chown -R root: <path> if you backup while the container is down. Don’t try that command on live containers.

  For a more permanent solution, you can investigate which user is the default in the container and add the option –user-ns=“keep-id:uid=$UID. This does not work with all images, especially those that use multiple users per container, but if it works, the bind mount will have the same owner as the host.

• ⁨Comment⁩ on ⁨What else should I self-host?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  I haven’t looked much into the differences, but from my brief research, it appears that Forgejo has just recently updated such that migration from Gitea is no longer possible. I knew that they had become a “hard” fork last year but it has now diverged.

  From a feature standpoint, I know that Forgejo is working on Fediverse integration. Beyond that, I think the differences are less apparent.

  So to answer your question, I use Gitea and have for a long time. They’ll still remain MIT-licensed even if it’s no longer fully open source. However, the owning company can (and may) cease open source development. If I had known of Forgejo breaking away earlier, or if I were a new user, I would have probably started with Forgejo. That’s my recommendation.

• ⁨Comment⁩ on ⁨The Way Ubuntu Boots on Raspberry Pi is Changing⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  It sounds like you’ve found your ideal distro. Great! Not everyone will have the same exact use case for their Pi’s.

  I’m just a little disgruntled because I like treating my Pi’s as headless servers, often with a single purpose, and I don’t want to have to erase the SD cards to upgrade versions.

• ⁨Comment⁩ on ⁨What else should I self-host?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Absolutely! I have used multiple origins for posting my projects to Gitea/Forgejo and GitHub. You can also mirror repositories from one site to another, too, although it requires a clean slate for setup.

  The biggest use case for me is documenting (as code) my home network setup on my private forge.

• ⁨Comment⁩ on ⁨What else should I self-host?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  You may or may not be a developer, but I would like to vote for Gitea/Forgejo. Should you ever get a grasp of git, a git forge is great for keeping code and even plain text documents recorded. It’s my favorite self-hosted service by far.

  It can even operate as an OIDC server, so you can create a single login for all your services (that support OIDC).

• ⁨Comment⁩ on ⁨The Way Ubuntu Boots on Raspberry Pi is Changing⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  That’s very fair. Everyone has a different use for Pi’s, and I just happen to favor long-lived devices that can be updated easily. I wish more of the pi internals were upstreamed too.

• ⁨Comment⁩ on ⁨The Way Ubuntu Boots on Raspberry Pi is Changing⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  The devs have started releasing 64-bit builds since then, yes. However, they still push people to the 32-bit builds: www.raspberrypi.com/software/operating-systems/

  I understand their thinking. They want a unified build experience, to simplify their development and user experience.

• ⁨Comment⁩ on ⁨The Way Ubuntu Boots on Raspberry Pi is Changing⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  I believe you may have found your ideal OS. Debian will always lag behind ever so often. And that’s okay. We all use the Pi’s for different reasons.

• ⁨Comment⁩ on ⁨The Way Ubuntu Boots on Raspberry Pi is Changing⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  This is probably a hot take, but:

  I disagree. The OS doesn’t run a mainline kernel, and the Raspberry Pi devs recommend a clean slate on OS upgrades. Granted, they do some trickery for performance with their Zero (not 2) line, using armhf instead of the slower armel, but this doesn’t excuse the fact that Raspberry Pi OS is so brittle. The builds are also still on 32-bit, even though every Pi since 3B can run 64-bit OSes.

  I just run Debian on mine. Can’t be assed to clean flash my devices each major update.

• ⁨Comment⁩ on ⁨Is it normal to not have any malicious login attempts?⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Incredible yet accurate analogy

• ⁨Comment⁩ on ⁨TIL - Caddy⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  If you’re using git to version Caddy configuration, you can use a pre-commit hook to test it, ensuring that you’ll never have invalid configuration. That’s what I do.

  caddy --validate
  

  There’s some extra command arts that may be necessary but that should be an adequate first step.