Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

Avatar by @[email protected]

  • 49 Posts
  • 662 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle









  • I don’t see what people’s problem with this is. It’s not like it’s anyone can just buy a blue check (unlike X). It’s just confirming that the account belongs to who it claims to be (like old Twitter verified users). I don’t know if that requires any payment, but it’s definitely not “Here’s $5 – okay, here’s your blue check”.

    • During this initial phase, Bluesky is not accepting direct applications for verification," the company said.
    • “As this feature stabilizes, we’ll launch a request form for notable and authentic accounts interested in becoming verified or becoming trusted verifiers.”

    If I remember correctly, that’s pretty much exactly how old Twitter rolled out its original user verification.

    From a de-centralized perspective, I’m not sure how that would work. I guess each instance would be in charge of verification and setting the “verified” flag for the account? The alternative would be some kind of central authority. Granted, I know little of Bluesky (microblogging is not my cup of tea), so I may be way off on my guesses there.









  • Is there a way I can get Let’s Encrypt to dole out a wildcard certificate

    Yep. Just specify the domains yourdomain.com and *.yourdomain.com in the certbot request. Wildcard domains require the DNS-based challenge, but you’ve said you’re already good there. You don’t technically need the apex domain (yourdomain.com) but I always add it since I do have services running there.

    Any subdomains under the wildcard can use internal DNS or internal IPs on the public DNS (I do the former, but the latter works too).

    I used to run an internal CA, and it wasn’t too hard to setup a CA and distribute my root cert. Except on mobile devices. On Android it was easy, but there was a persistent warning that my network traffic could be intercepted (which is true when there’s a custom root cert installed), but it since it was my cert, it got annoying seeing that all the time. Not sure if Apple devices can even do that, but regardless, it wasn’t practical for friends who wanted to use my self-hosted services to install a custom cert when they were over.