Comment by stackghost 1 day ago I tried to grab @SecDef just now, they appear to have it blocked/internally reserved 2 comments stackghost Reply arduanika 1 day ago Huh. Maybe they just do that automatically when a verified account renames itself, to keep the old one reserved? Who knows. stackghost 1 day ago I got a "something went wrong" error and then it auto assigned me @SecDef48372 or something similar.Sad.
arduanika 1 day ago Huh. Maybe they just do that automatically when a verified account renames itself, to keep the old one reserved? Who knows. stackghost 1 day ago I got a "something went wrong" error and then it auto assigned me @SecDef48372 or something similar.Sad.
stackghost 1 day ago I got a "something went wrong" error and then it auto assigned me @SecDef48372 or something similar.Sad.
Huh. Maybe they just do that automatically when a verified account renames itself, to keep the old one reserved? Who knows.
I got a "something went wrong" error and then it auto assigned me @SecDef48372 or something similar.
Sad.