Dreamwidth Suggestions

Description:
As we know, remote site user name linking works for any site where users can be found at www.[service.tld]/users/[name], even if it isn't set up so there's a site-specific user-head to link there. [Edit: the proper location is 'users', not 'user'. My bad.]

Etsy's user URLs take the form of www.etsy.com/shop/[name], and their profile URLs www.etsy.com/people/[name].

Are there enough Etsy crafters, and people who know Etsy crafters, that it would be useful to be able to easily link to Etsy crafters before someone gets to bug 23 (http://bugs.dwscoalition.org/show_bug.cgi?id=23) ?

Description:
It's not always necessary or desirable to broadcast one's website address as being associated with one's journal to the whole internet. Yet it would still be helpful to list it with one's journal, viewable to those who have been granted access -- or sometimes, merely to all registered users, rather than to all the spammers the internet has to offer.

Since the website is also used in building the journal page itself, it might take a bit more doing than simply restricting who may view it on the profile page.

One can of course approximate the effect by putting a public link in the bio to a secured entry listing the website, although this method is roundabout and makes one's readers click a few more times to reach their destination.

Description:
The current success message for profile edits is: "Edit Profile Success. Your profile has been revised." This does not appear to differentiate between one editing one's own profile as the logged-in user, and editing the profile of a community one administrates.

One can, of course, look at the URI of the page to see that one is currently working as a community and what the community is, as the page has authas=community, but it's not as nice as it could be.

This looks like it might be good for a beginning developer.

Description:
This isn't yet an issue, so I thought I'd suggest it while it still isn't. As we know, staff accounts are issued to staff to make authoritative statements in official venues. Once upon a time Denise expressed a preference that in the case of a staff member becoming no longer staff, their staff account should revert to being a regular user.

This could, of course, make historical discussions lose some of their context, with seemingly non-authoritative users making authoritative statements.

To mitigate that for the people who take the time to investigate these things, if an account is stripped of its Staff status, the account's profile should show that it was previously a staff account, and possibly even what dates its Staff status was in effect.

This is inspired by LiveJournal's display for Early Adopter accounts that enjoy a better status now, such as "Permanent Account, previously an Early Adopter".

If dates of time on staff are mentioned, the system should allow for someone who leaves and returns an arbitrary number of times, although that does sound like a really weird use case.