Custom Bluesky Handles for Domain users

eddiewebb

This extension allows users of your site to set their bluesky domain to <slug>.<yourdomain> replacing the commonplace bsky.social domains all users are assigned by default.

Installation

Install with composer:

composer require webbinaro/flarum-bluesky-handles:"*"

Updating

composer update webbinaro/flarum-bluesky-handles:"*"
php flarum migrate
php flarum cache:clear

Screenshots

User settings to provide their DID

Updating domain/handle in Bluesky

Requirements and Configuration

This extension uses fof/masquerade to define the new User Profile field.
You DNS settings will need to send wildcard domain to your webserver
Your webserver will need to route wildcard domains to the newly exposed endpoint /api/bluesku/<slug>
Your SSL cert will need to be updated to support wildcards.

Example Nginx config is included in GH repo

clarkwinkelmann

eddiewebb excellent initiative !

Wouldn't it make more sense to return a 404 error in the wildcard config and only redirect the .well-known path? Or redirect to the Flarum user profile page when trying to open the subdomain in a web browser.

I was a bit intrigued while reading the Bluesky documentation myself, they didn't put any suggestion on what to do with the subdomains homepage. I feel like it could have adverse SEO effect if it returns a 200 status.

I don't understand why they didn't create a system that didn't rely on multiple subdomains. They could have specified a special DNS record that refines a single authoritative REST API endpoint, or allow the apex domain to list multiple key-values in a single .well-known endpoint. I feel like it would have been a lot more practical.