Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JU
Posts
4
Comments
464
Joined
2 yr. ago

  • There was a thread about that on c/selfhosted a few weeks ago. Created by a particular wild-cat-inspired sysadmin, I might add.

    But on a more serious note, the interactions between a sysadmin and their servers (that they have enough responsibility for to be able to name) are much more intimate than the interactions between a dev and their variables. The server names also exist in a much larger namespace, so they need to be more unique.

  • I really like that bluetooth devices can still work at distances farther than a typical cable would allow. I have a decently-sized studio apartment and I can see my computer screen from most places. It's nice to continue watching a video as I move around the apartment to clean, get up to stretch, play with my cat, etc.

    You could probably get wired headphones that long, but then you'd be dealing with that giant cable all the time. Or you'd have to constantly swap cables and interrupt the audio during that time. My AirPods work reliably from 15ft away. I can't argue with that convenience.

  • Pi-hole works by giving clients non-routable addresses in response to DNS queries of known ad-serving domains. If the client (web browser, phone, smart device, etc) doesn't let you set its DNS server (as many no longer do) and doesn't obey DHCP, then you can't feed them those addresses. You could block outbound DNS traffic from all clients except your Pi-hole, but in response some clients will just refuse to work entirely. And if they require DNSSEC (or DoT/DoH with a pinned certificate), there's nothing you can do.

  • Customers have more power than companies would like you to believe. Politely explain the situation to customer support, and ask for a refund. If they refuse, mention that you purchased a game that was promised to work for at least several months, and you haven't received the product you paid for. Because of that, you're considering charging back through your bank. If that doesn't work, say you'll charge back if they don't refund. If that doesn't work, actually charge back through your bank. Banks are surprisingly cool about it as long as you don't do it too often. Of course, you need to buy the game directly (no account balance) from a credit card.

    Just don't be a jerk to the support person, because it's almost certainly not their fault. It's also less likely to get you what you want. They'd rather give you what you want so you go away, and you just need to give them reasons that they can relay to their supervisor if necessary.

  • Business decisions are almost always influenced by the personal preferences of people in charge. While OP probably can't change the existing infrastructure right now, when the infrastructure is eventually changed, OP's pro-Linux input could make a big difference.

  • With the right algorithm (upvotes and downvotes, top, hot), the majority of posts you would see would be real and also interesting. I guess it would also need to be less exclusive by default, so that the highest rated posts are always the most interesting ones.

  • Just connecting to the internet on various networks can be confusing. And they're going to need to periodically upgrade system packages, or they'll be vulnerable to various exploits. Even if you set up auto-upgrades, occasionally some things will need manual intervention.