So, #Smithereen no longer requires a username when signing up. You instead get assigned one automatically, of the form "idXXX" where XXX is the ID for your user record. You can change it later in settings if you wish. Current Mastodon versions handle this change no problem.
The username is only visible in two places:
The URL of your profile
When someone mentions you
So it's not very important. Definitely not important enough to be a required field when you register.
I saw a post today about another Mastodon API endpoint that is kind of in a zombie state (I looked into Featured Profiles awhile back).
This one is a “Mastodon Wrapped" end of year review.
On m.s. it's accessible but as expected doesn't return any data. Currently, the admin would have to jump to the console and run a task to populate the reports.
Like other "wrapped" end of year summaries, it's only available to the user.
@newsmast is the Social Media Feed (@socialmedia) just boosting everything under the mastodon hashtag?
It might be wise to filter out posts also tagged with #MastoDev and #MastoAPI since these are intended for developer audiences rather than the general public.
Just did a test, and I think we may be able to implement FedCM in Mastodon. It seems that you can actually create Doorkeeper Applications with a client_id that's a URL, rather than having it generate a unique client_id for you.
However, where it fails is that you don't get a unique client_id, so registering the same client again fails with a duplicate record error (maybe this is intentional?)
I guess FedCM client_id's don't have a client_secret at all to use…