pauamma: Cartooney crab wearing hot pink and acid green facemask holding drink with straw (Default)
[personal profile] pauamma

Title:
Display unregistered and renamed-without-redirect usernames as struck through

Area:
site-specific markup, renaming, registration, usability

Summary:
<user name="thisusernamedoesntexist"> is displayed with no strike through when the username was never registered, or was renamed to something else without redirection. This makes it harder to spot typos, and may have minor privacy consequences in the latter case. It should be made consistent with the way usernames of deleted accounts display.

Description:
Drawback: This would introduce an incompatible change for people who relied on the current behavior to display made-up generic usernames without having to register them or find ones already registered for that purpose, like "exampleuser". Finding one suitable for that purpose - eg, not that of an actual site user or community which might feel singled out - would become harder, and maybe even impossible without actually registering it, for languages other than English.

Poll #13088 Display unregistered and renamed-without-redirect usernames as struck through
Open to: Registered Users, detailed results viewable to: All, participants: 50


This suggestion:

View Answers

Should be implemented as-is.
2 (4.0%)

Should be implemented with changes. (please comment)
18 (36.0%)

Shouldn't be implemented.
16 (32.0%)

(I have no opinion)
11 (22.0%)

(Other: please comment)
3 (6.0%)

pne: A picture of a plush toy, halfway between a duck and a platypus, with a green body and a yellow bill and feet. (Default)
[personal profile] pne

Title:
Page showing recently-purged usernames

Area:
newpage

Summary:
Create a new page showing purged usernames, as inspiration for people considering a rename.

Description:
LiveJournal has a page that shows purged usernames: http://www.livejournal.com/misc/expunged_list.bml

That page "is updated every day with new usernames that are up for grabs". There's a short list of usernames that became available in the last 24 hours and a big long list of random usernames that start with a particular letter or digit. You can then choose a different initial letter or digit, or click "See more random results" to get some more ideas. The order of the names on a given page seems to be roughly arbitrary.

It might be useful to have such a list on Dreamwidth, too, with similar features: show a list of usernames that are available for renaming to due to a purge.

The exact details might vary, but LiveJournal's implementation might be taken as a starting point.

Except that I'd like a bit more randomness if this is easily possible - when I first load the page (without applying a filter), I usually get names starting with "a0" or "a1"; a mix of "a0..a9, aa..az" would be nicer if this is easily possible. (Perhaps just a "select username from usertable where status = 'purged' limit 100" with no "order by" clause? Then for "see more random results", repeat the query with a "start at 101", "start at 201", etc.? Then they'd be in quasi-random order, presumably the order in which they were created.)

In http://dw-news.dreamwidth.org/31382.html?thread=3770518#cmt3770518, Denise said that purges happen comparatively rarely and the number of accounts that gets purged at each go is lower, so perhaps it's not quite as useful here as on LJ, but I wanted to suggest it anyway.

Perhaps one *can* find a nifty username from it!

Poll #8859 Page showing recently-purged usernames
Open to: Registered Users, detailed results viewable to: All, participants: 84


This suggestion:

View Answers

Should be implemented as-is.
35 (41.7%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
10 (11.9%)

(I have no opinion)
39 (46.4%)

(Other: please comment)
0 (0.0%)

deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah

Title:
make a more direct link to support request from feed profile page

Area:
support

Summary:
Somebody who is requesting a changed URL for a feed doesn't need to read the FAQs for support, they need to go directly to the link for making a support request.

Description:
On the profile page for a feed account, we have the text "If this feed has stopped updating because its location has changed, please contact Support to have the location updated instead of creating a new feed." "Support," in this case is a link to the support portal (http://www.dreamwidth.org/support/), which rightfully starts with all of the FAQs, Known Issues, etc., and has "make a support request" way down on the bottom.

However, somebody who clicks on the link "please contact support to have the location updated" doesn't need to read all the FAQs; they just need to contact support. It should take them directly to the form.

In fact, ideally, it should take them to a pre-populated version of the form, which says something like "the URL for the syndicated feed sample_feed has been changed. Please paste the new URL below."

(And if we do all that, then the linked part of the above text shouldn't just be the word "support" but the more informative link text "contact support to have the location updated". That's just a change of where the [/a] those.)

Poll #8832 make a more direct link to support request from feed profile page
Open to: Registered Users, detailed results viewable to: All, participants: 60


This suggestion:

View Answers

Should be implemented as-is.
54 (90.0%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (10.0%)

(Other: please comment)
0 (0.0%)

[personal profile] zaluzianskya

Title:
Allow new users to purchase purged usernames outright

Area:
journal creation, renames

Summary:
We can buy purged usernames now. This is awesome! But if you want to use a purged username for a new journal, you have to register a throwaway name and then rename that. Not so awesome.

Description:
Let's say you have a username you really like -- let's call it "loveandkittens". You really want to register "loveandkittens" for your new journal, but it's been deleted and purged! Luckily, Dreamwidth now has journal renaming, which is highly nifty. But in order to rename to "loveandkittens", you need a journal to actually rename.

So, you register a journal to rename. It can have whatever name you want -- if you're savvy about how renames work, you'll probably register something like "sldjcw982198nfckj", something no one would be likely to ever pick in the future. But, alas, not everyone is so savvy. A lot of users, especially new ones, would pick something like "hateandkittens", and then rename that to "loveandkittens". This, however, causes a problem if someone else wants to come along and register "hateandkittens" later on: It's either now a deleted and purged username, and the whole process starts aaaall over again, or it's a permanent redirect to "loveandkittens", which is even worse.

I'm not suggesting that we do away with having to pay for purged usernames; obviously, that's necessary. However, there should be a way for brand new journals to register these usernames without having to register a throwaway name first. They would be asked for payment up-front, and then some behind-the-scenes process would do whatever it has to do to move all of "loveandkittens"'s former activity over to "ex_loveandk123" so the new journal can be "loveandkittens". My suggestion is to register a journal with a username of the form "ex_123456789", and then apply the rename to it without the user ever seeing it.

And, obviously there'd have to be a link to some page explaining why you have to charge $15 for a brand new journal, and explaining that they're free to pick a different username instead if they don't want to fork out the money, but that's just standard for all rename-related shenanigans.

Poll #5132 Allow new users to purchase purged usernames outright
Open to: Registered Users, detailed results viewable to: All, participants: 82


This suggestion:

View Answers

Should be implemented as-is.
71 (86.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
10 (12.2%)

(Other: please comment)
1 (1.2%)

tenkuu: Tenkuu no Touma (Default)
[personal profile] tenkuu

Title:
No rename token for purged communities

Area:
communities, rename tokens

Summary:
A purged username that someone wants to use as a community should not require a rename token.

Description:
Communities shouldn't need rename tokens because they're not a newly created username like someone would have for their own personal journal. Once purged, if a username can be used as a community, it should be as easy to claim it as for any newly created community. After all, purged should mean that it no longer has any association with its previous owner, and in this way it's like any regular unclaimed username.

Poll #2674 No rename token for purged communities
Open to: Registered Users, detailed results viewable to: All, participants: 47


This suggestion:

View Answers

Should be implemented as-is.
6 (12.8%)

Should be implemented with changes. (please comment)
1 (2.1%)

Shouldn't be implemented.
32 (68.1%)

(I have no opinion)
8 (17.0%)

(Other: please comment)
0 (0.0%)

ex_xo956: (Default)
[personal profile] ex_xo956

Title:
Importing Dreamwidth journals into Dreamwidth journals

Area:
Import Content, Entries

Summary:
It would be uberly, superly awesome if you could import a DW journal into another DW journal. For example, I created ABC as a public journal and XYZ as a private friends only journal and eventually, I decide I'd like to import ABC into XYZ so I can have all my entries in one place.

Description:
I'm really surprised no one has suggested this yet and so now I'm wondering if it's one of those things that just can't be done and I'm the village idiot standing around waiting for everyone to breathe water. :P Or worse, it's some kind of cyber-faux-pas to request such a thing...

One drawback to this thing that I am suggesting is that, if someone combines their journals but leaves the original one still standing, it takes up superfluous server space. It could be implemented such that, if you combine DW journals, the one being imported is automatically queued for deletion...but there could be a reason someone would want to combine and leave the original standing. I don't know.

The reason I came up with this at all is because I'm consolidating ALL of my online journals into one journal and I would like to add my DW journals to this one.

OOO! I just thought of something else actually...MOVING entries from one DW journal to another. So it would be a totally different feature from the Import Content because would be A.) importing entries and B.) deleting the entries from the place they were imported. That could get really tricky though - if there were any glitches at all, entries could be lost forever...

Well, I think I'm done brainstorming this one. :P I'll go ahead and turn this over to the people who know what they're talking about and I'll wait to see if I've invented the wheel or if I'm suggesting we all start breathing water. ;)

Poll #1925 Importing Dreamwidth journals into Dreamwidth journals
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
18 (40.0%)

Should be implemented with changes. (please comment)
21 (46.7%)

Shouldn't be implemented.
4 (8.9%)

(I have no opinion)
2 (4.4%)

(Other: please comment)
0 (0.0%)

Profile

Dreamwidth Suggestions

December 2018

S M T W T F S
      1
23 45678
9101112131415
16171819202122
23242526272829
3031     

Style Credit

Expand Cut Tags

No cut tags

Syndicate

RSS Atom