Email or username:

Password:

Forgot your password?
Top-level
Athena L.M.

@dotnet Hello. Before you get going too far with this handle, may I point out: If your server is on a subdomain of a domain you're known to own, everyone can know without having to check that it's yours.

If this account was "@dotnet@dot.net" or "@dotnet@social.dot.net", I wouldn't have to check for a verified checkmark on the blog entry in your profile.

Just a particular advantage of federation that isn't automatically obvious.

3 comments
Athena L.M.

@dotnet (Or, to reduce the amount of servers being run by the same company, @dotnet@social.microsoft.com)

David August

@alilly @dotnet do a lot of software companies try to minimize their own use of software?

clacke: looking for something πŸ‡ΈπŸ‡ͺπŸ‡­πŸ‡°πŸ’™πŸ’›
@davidaugust @alilly @dotnet They should. Software is a liability, not an asset. We accept software because it solves a problem at lower cost than the alternatives.

In this particular case it seems dotnet.social wants to be independent from Microsoft, so it wouldn't make sense for the instance to move.

For the dotnet account though it makes sense to ask whether the account as a Microsoft account should signal that it is part of the community and be on dotnet.social, or that it should signal that it represents Microsoft and be on a Microsoft server. Both choices make sense depending on what the purpose with the account is.
@davidaugust @alilly @dotnet They should. Software is a liability, not an asset. We accept software because it solves a problem at lower cost than the alternatives.

In this particular case it seems dotnet.social wants to be independent from Microsoft, so it wouldn't make sense for the instance to move.
Go Up