Post

Is there anything preventing to link multiple domain names to the same account? If we go with the idea that verification is done via domain name you might want to verify that you both are part of the Bluesky team (with paul.bsky.team) and that you own your personal domain

Shouldn't it be as easy as to remove the DNS entry or the .well-known page from the directory? Like, if say _dan.ign.com gets laid off, ign should just need to remove that subdomain and then they just get the invalid domain for the account.

If the domain owner tries to re-verify an arbitrary account with the revoked subdomain then that triggers the check, they can do it with a dummy account if they wish

To help with this it would be suuuper helpful if the original handle was reserved (with option to release) when you add a custom domain. I naively assumed it would be and now I *can’t* change back because someone else nabbed it before I realised. They now post on my old handle so I can’t change back

Please clarify one key-point : what happens to posts where your ID is mentioned ? Are they updated too ? If you changed from Jack to Joe, will my old post forever keep mentioning you as Jack ?

Nick Fuentes is still on Bluesky. bsky.app/profile/nick...

I understand you don't lose the account - but do you lose verification?

They’re building something intended to outlast the company itself; so solutions that rely on Bluesky the company are inherently flawed. Domain based verification is used in the SSL certificate world too, see the DNS challenge here letsencrypt.org/docs/challen...

paul, please marry me

Yes - I went and snagged mine right away after I switched to a domain and put a link to my domain.

Nice! Hey, any news about letting us send photos on DM? We are being obligated to use Instagram DMs and it's a chore switching apps. Thanks!

Yes. It gets back into the pool and will be claimed by someone else, unless you create a second account and lock it for yourself. I lost my firstname handle here thanks to this mess.

But weblinks to your profile can (and sometimes already do?) use your DID instead. There should be a setting for that, actually, because I sometimes link posts in my notes for reference, and having a link with a DID instead of handle makes it hardened against "handle rot".

The employee would have to also choose to migrate to the new handle but yeah, no problems there. If you just change it and nobody does anything on the account you’d get an [invalid handle] situation

Great!!!

If it resolves the DID to the current association could things be out of context? Or is the handle that resolved at post time preserved on the post?

Ah, I know this one! In the current Bluesky code base, your posts show your current handle and address, for all posts past and current.

Bunch of tools here, see skytools on the list for that specifically github.com/fishttp/awes...

Hmm wonder if it's worth adding a "share permalink" or some equivalent to the menu for profiles. It's not super easy to get a did link to a profile otherwise

Orgs should always set up org-specific accounts, to be honest. If your PR guy leaves, do you really want to lose all the eyeballs, too? Typically, you'd have your own email domain, etc. so that when someone leaves, you retain control of that data - why wouldn't you do the same for Bluesky?

This is another good reason to support employer-subdomain alts that'll give you an [institution] icon without affecting backlinks

Is there a reason why the bluesky webapp and native apps prefer handle name based links instead of DID based links? I feel like defaulting to DIDs would help protect against linkrot and name hijacking abuses. Especially for users like journalists who's handles are subdomains of their employers.

Is there a way to avoid this, like if you link to posts with a did identifier rather than username-based link? I feel like this could become a big issue, and why Twitter links to posts rendered based on status id no matter what username was used in the link.

(of course, aliases - allowing you to keep your .bsky.social as a permalink - would also help mitigate that)

Alias usernames might be a good idea so that nobody can steal your handle in the meantime

Yes, exactly

So I need a way to monitor the content put up by the users in my org to make sure they are staying within the law of, err, the country that's hosting my pds?

I work with Fedica - it lets you save drafts, cross post and schedule up to 10 posts at a time for free. bsky.app/profile/fedi...

This feature is being worked on. See https://github.com/bluesky-social/social-app/pull/6055

Use buffer.com for drafts for now

That's my point about web links, yes

maybe effectively true enough today, but worth noting: any valid at-uri can have a handle instead of a did: atproto.com/specs/at-uri... uris i’ve see so far in the firehose are always dids, but

Are there any plans to fix the links breaking issue? It's not ideal considering it seems like, with domain validation being the main form of validation, one's username could change relatively often.

I read a post on Bsky, then go to the website to confirm the legitimacy of the person who posted it, then go to whois.com and confirm the legitimacy of the website (assuming that the information there is correct)? So many scenarios that even these checks do not guarantee authenticity...

If I were to switch to a domain name is my current handle auto-squatted on or can it be lost before I change back?

I’ll admit though I have my own domain it’s been difficult for me to switch my account. 🥲 I’ll keep trying tho haha

Fine. I still believe Mastodon has a better solution though. Hey, one thing they’re doing right :))

If you go from handle A and change it to handle B, does that mean someone else can go and recreate handle A?

cname would be a good solution to link multiple usernames, especially for company subdomains, your main could still be your private, but your company could link to it

Google's Blogger (for one) does that. If you change to a custom domain, your original myname.blogspot.com forwards to your custom url in perpetuity.

*assuming that you reserved pfrazee.bsky.social so that someone didn't grab it after you relinquished it during the initial change to paul.bsky.team.

The best solution is owning a domain because no one can't disrupt it, it's all yours anyway.

that does feel like it would be a good change. if nothing else it would be handy for people who forget who has custom domain handles so if they try to look you up they can be redirected and still find you.

So where exactly do I do this change?