[personal profile] swaldman

Title:
Set default country according to IP

Area:
Shop

Summary:
When making purchases in the shop, it would be nifty if your country could be defaulted to a best guess based on IP.

Description:
It would be a minor convenience feature, and might involve quite a lot of work/hassle/complexity... but I thought I'd throw it out there in case somebody says "oh, that'd be easy actually" :-)

Drawbacks: Slowdown as the lookup is done; don't know whether this would be significant. Maybe there are some situations in which people would be offended by an incorrect guess?

Poll #13460 Set default country according to IP
Open to: Registered Users, detailed results viewable to: All, participants: 46


This suggestion:

View Answers

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

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

Shouldn't be implemented.
23 (50.0%)

(I have no opinion)
16 (34.8%)

(Other: please comment)
0 (0.0%)

[personal profile] swaldman

Title:
Review the countries that are at the top of the "country" dropdown in the shop

Area:
Shop

Summary:
When paying by credit card in the DW shop, one specifies one's country in a drop-down. This drop-down is alphabetically sorted except for United States, which appears at the top.

Suggestion is to review which countries appear at the top.

Description:
It is fairly common for such dropdowns to promote a few most-common countries out of their alphabetical order and put them at the top of the list.

The Dreamwidth Shop does this with United States.

My suggestion is to review which countries appear at the top in this way: are there others that hold a sufficiently large proportion of the DW paid userbase to merit this treatment? I suggest that 3-5 of the most common countries should appear here, and that a separator should then be inserted in the list to make it clearer what is going on.

Poll #13459 Review the countries that are at the top of the "country" dropdown in the shop
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
23 (51.1%)

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

Shouldn't be implemented.
5 (11.1%)

(I have no opinion)
15 (33.3%)

(Other: please comment)
1 (2.2%)

twigletzone: (Default)
[personal profile] twigletzone

Title:
A new revenue model: pay-per-awesome?

Area:
Payment/revenue/keeping DW ad-free.

Summary:
After reading <user name=synechdochic>'s essay on the flaws in Web 2.0, I've had an idea for a potential new revenue stream for sites like Dreamwidth. I'd love to know what you guys think.

Description:
I recently re-read <user name=synechdochic>'s <a href="http://synecdochic.dreamwidth.org/234496.html">essay</a> on Web 2.0, and why the advertising model is doomed to failure. It made me think. I'm not an economist and have no experience of running an Internet business but the basic idea I had seems like common sense, so I'm throwing it out there for more experienced minds to consider.

<user name=synechdochic> suggests that the basic problem with the subscriber model is achieving sustainable revenue as the site grows over time. DW is young, and therefore small, and hasn't hit this problem yet. <user name=synechdochic> further suggests that the centralised model of revenue generation, in which the user is the product being sold to advertisers, quite rightly alienates users and creates a downward spiral of ever more intrusive advertisements.

Livejournal has attempted to generate extra revenue by allowing users to purchase gifts for other users - but all this provides for the user receiving it is an image to display on their profile page. The Archive Of Our Own has kudos points, which are free social status you can hand out to creators of content you enjoy. DW has a "Gift a random user" function that lets you donate paid time. What if all these ideas were linked up and taken one step further?

Imagine an opt-in system where users could pay to buy kudos points or something like them, which they can then donate to whoever created any piece of DW content they find particularly awesome. Kudos points could then be exchanged for site services like paid account time. Perhaps, if a user acquires a very high level of points in a certain time period, the excess could even be converted back into real-world money.

DW, as the provider of the platform that publishes this awesome content, could take a percentage from purchases of points - say that spending $10 buys 900 points instead of 1000, or something (where each point represents $0.01 worth of site services the recipient could buy with it). Or perhaps users could even choose what percentage of their point buy to pass to DW directly to help run and improve the site, and what percentage they want to convert into points they can donate to other users.

DW isn't meant to be a crowd-funding site so there would have to be some mechanism in place to stop users begging for points for content that hasn't yet been created. That's essentially a social problem, so the solution would probably have to be about DW's culture; policing anyone abusing the system, and clearly explaining the intentions of the system to start with. It would seem sensible to run it alongside the current subscriber model, so that people still have the option of contributing both socially and financially to DW without being dependent on other users' goodwill. Nobody should be denied a voice, after all.

The idea here is to stop the user becoming the product, and make the content the valuable thing instead; the financial model behind the site becomes more democratic since each individual user can be both a seller and a buyer. The users who produce the best content are materially rewarded for it by the community, and even those who don't have a lot to contribute in terms of content have a way of getting involved and showing their appreciation. Since DW contains a lot of fanfic, anonymous donations of kudos could even be made possible so that less family-friendly content can be appreciated without the donation being traceable to a particular account name. Any author who wants to keep their content free could simply opt out of receiving kudos for a particular post or a whole journal - whether that's because they believe information should be free to all or because the idea of being paid for writing adult fiction skeeves them out!

As I said, I'm neither an economist nor an experienced Web business person - just a left-leaning person with a reasonably good mind. And I do understand that implementing this would be a massive project. But - does this fit DW's philosophy, and could it be a model for the future?

Poll #9394 A new revenue model: pay-per-awesome?
Open to: Registered Users, detailed results viewable to: All, participants: 90


This suggestion:

View Answers

Should be implemented as-is.
10 (11.1%)

Should be implemented with changes. (please comment)
9 (10.0%)

Shouldn't be implemented.
53 (58.9%)

(I have no opinion)
15 (16.7%)

(Other: please comment)
3 (3.3%)

azurelunatic: Vivid pink Alaskan wild rose. (Default)
[personal profile] azurelunatic

Title:
Vanity promo (invite) code

Area:
invitations, paid features

Summary:
Pay a small but reasonable fee to automatically create a custom promo code, suitable for printing on business cards and the like. (Regular promo codes would still be available for free at site admins' discretion, by filing a support request in the Account Payments category.)

Description:
Site administrators can already generate promo codes, which can be given to people needing bulk invitations (migrating an entire community, attending a conference, in response to Greater Internet Events). Promo codes are currently issued for free, at site administrators' discretion; individual extra invitations are also issued for free at site administrators' discretion. Promo codes can be preloaded with paid time, and to avoid abuse, are not bottomless, and can also be cut off if it becomes apparent they are being misused.


There are more situations that could be suited to promo codes than there is necessarily staff availability to grant and oversee them.

Perhaps you'd like to hand out cards to friends and new contacts, and would like to invite at least some of them to Dreamwidth. Printing up individual invitation codes is not only tedious, but runs the chance that someone wouldn't use the code you gave them, and then you'd have to make the call to either leave it unused or re-issue the code (and then if the person you gave it to was saving it until they had the spare time and motivation, they're out of luck).

Perhaps you want to migrate the users from that community *now*, and you know that staff are on vacation until a little too late to help you.


Users would be able to spend points to create a custom promo code without needing site admin intervention. This would require a promo code control interface visible to the user, while not limiting site administrators' ability to monitor the activity of user-controlled promo codes to prevent abuse and anticipate site growth.

How many points per invite? There would need to be a reasonable minimum limit needed to create the promo code, and a reasonable maximum number of invitations the promo code may hold at one time. (For development, the price per invite, the minimum, and the maximum should probably be set as a cap, so it may be modified on the back end on other installations. On other sites, site administrators could set the points-per-invite cap at 0 for all users or certain users if they wanted those users to be able to invite their friends freely but without completely open registration.)

Should users be able to withdraw unused invitations that they'd spent points on (decreasing the number available in the promo code), and get points back?

Limiting the number of invites that may be held in a promo code at one time would limit the possible damage if a spammer got their hands on someone's promo code, or if a spammer bought an account and created a promo code.

If spammers did get into a legitimate user's promo code, could the points spent to create the codes be refunded to the user upon the destruction of the spammers' journals? In case of a spammer purchasing a promo code, nuke from orbit.

Users should be able to set their own promo code within certain reasonable restrictions (must be at least a certain number of characters, not more than another certain number of characters); it might be a good idea to allow users to automatically generate a promo code in case they aren't feeling particularly clever about creating one, and/or don't want to claim good namespace.

Users should be able to load invite codes they received (assigned to their account? what about assigned to other accounts under control? If that, then what's to stop someone from wandering about and snagging up other codes people have publicly posted?) into their promo code, and should be able to generate individual invite codes out of the pool in their promo code.

Promo codes could be loaded with initial paid time for the new journals (first month, perhaps) if the user setting it up wants to shell out for that.

There should be notifications that could be subscribed to for various activity -- codes getting low, new account creation, possibly more.

The purchase page should have a link to create a support request in the Account Payments category, and a note explaining that promo codes are also available for free upon request, something like: "Invite codes and promotional codes for group invites, can often be obtained for free by opening a request in the Accounts category and speaking with an administrator about the specific situation. Free invite and promo codes are distributed generously but with respect to keeping current site growth controlled and sustainable."


Advantages:

* Fun
* Revenue for the site
* Automatic - no need to ask for something
* Immediate - no need to wait for an administrator to check the requests and grant more codes/a promo code
* Feature that daughter sites might be able to use


Possible disadvantages:

* Shameless moneygrubbing.
* Could discourage people from asking for free promo codes
* Supposing a spammer got in there, eww

Poll #7848 Vanity promo (invite) code
Open to: Registered Users, detailed results viewable to: All, participants: 54


This suggestion:

View Answers

Should be implemented as-is.
25 (46.3%)

Should be implemented with changes. (please comment)
2 (3.7%)

Shouldn't be implemented.
3 (5.6%)

(I have no opinion)
22 (40.7%)

(Other: please comment)
2 (3.7%)

jumpuphigh: Pigeon with text "jumpuphigh" (Default)
[personal profile] jumpuphigh

Title:
Communities to Receive Points

Area:
Accounts

Summary:
Communities currently cannot receive points. I suggest allowing them to do so.

Description:
Currently, communities don't have the ability to receive points from users. I suggest that we change this. Instead of allowing users to only buy time for communities, it would be awesome if we could transfer points now that we have the points system.

Examples of ways it could be useful:
-Two people want to share the cost of a month's membership. Each person transfers 15 points.
-The community is holding a contest. People give 5 points to participate. Community now has points for prizes.
-You love a post made by a community. You want to give points as kudos. You can transfer as many points as you feel is appropriate.

Poll #7552 Communities to Receive Points
Open to: Registered Users, detailed results viewable to: All, participants: 54


This suggestion:

View Answers

Should be implemented as-is.
20 (37.0%)

Should be implemented with changes. (please comment)
15 (27.8%)

Shouldn't be implemented.
1 (1.9%)

(I have no opinion)
18 (33.3%)

(Other: please comment)
0 (0.0%)

cheyinka: A sketch of a Metroid (Default)
[personal profile] cheyinka

Title:
Hide never-completed orders after n days

Area:
Payments

Summary:
It's disconcerting to see a "waiting for payment" order sitting around for months. It would be less disconcerting if older orders could be hidden.

Description:
The Order History page shows old orders, completed or not. I initially thought that that was a bug, but learned today that it's intentional behavior. However, it's really disconcerting to see an order that will never be completed still showing up as pending, especially when it's been there for over a year.

Denise suggested that I suggest that the system could hide carts older than some number of days, and only show them if explicitly requested. (So here I am.)

I'm imagining something like "One or more orders that aren't completed are hidden because they were opened more than 30 days ago. Show all orders?" with a counterpart "Currently, all orders are visible. Hide never-completed orders more than 30 days old?" (30 seems like a good minimum number of days before a cart won't display by default anymore. 60 or 90 would work too.)

Poll #4944 Hide never-completed orders after n days
Open to: Registered Users, detailed results viewable to: All, participants: 39


This suggestion:

View Answers

Should be implemented as-is.
24 (61.5%)

Should be implemented with changes. (please comment)
2 (5.1%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (33.3%)

(Other: please comment)
0 (0.0%)

azurelunatic: Vivid pink Alaskan wild rose. (Default)
[personal profile] azurelunatic

Title:
Community points

Area:
communities, points, great ideas that could go badly wrong

Summary:
It could be interesting to allow communities to receive points, and to allow community admins to distribute points belonging to the community.

Description:
So yesterday I decided to hand out a few of the points that I happened to have on hand, and since it was related to a community sort of thing, I wondered if it would be possible to hand them out through the community. Of course, I then learned that one can't do this through a community -- one may only give points to an active personal journal (which, incidentally, means no giving points to OpenID users).

This could be great if people wanted to give points to a community to perhaps contribute toward a paid community, or for the administrators of that comm to give out as they saw fit, say to community members who contributed to the community, or as prizes, or what have you.

This could be seriously problematic, of course, if one admin of the community saw fit to transfer all the community's points to one of their spare accounts in the night and run overseas (or at least stop answering their e-mail). Or give them all to a friend. And when real money gets involved, drama can be right behind sometimes.

Do the possibilities for good outweigh the possibilities for evil?

Poll #3656 Community points
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
15 (33.3%)

Should be implemented with changes. (please comment)
13 (28.9%)

Shouldn't be implemented.
9 (20.0%)

(I have no opinion)
5 (11.1%)

(Other: please comment)
3 (6.7%)

yvi: Kaylee half-smiling, looking very pretty (Default)
[personal profile] yvi

Title:
Attach a note when transferring points

Area:
Shop

Summary:
It would be good to be able to attach a note when transferring points to another user.

Description:
I would really like to attach notes when transferring points. "Thanks for the help with X" or "Have fun with this little gift!" or "Happy Birthday".

Poll #3035 Attach a note when transferring points
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)
8 (9.8%)

Shouldn't be implemented.
1 (1.2%)

(I have no opinion)
2 (2.4%)

(Other: please comment)
0 (0.0%)

[personal profile] galateus

Title:
anonymous, delayed points-giving

Area:
purchases, transferring points

Summary:
Allow buying and transferring Dreamwidth points for someone else as an anonymous gift and/or with a future delivery date.

Description:
In the Dreamwidth Shop, when you "Buy paid services for..." someone else's account, there's a field for "Delivery date" and a ticky box asking "Do you want to make this an anonymous gift?" But if you "Buy Dreamwidth Points for..." someone, there's no Delivery date or anonymous ticky box options, and there really should be.

And I don't actually know what transferring points-you-already-have looks like, since I don't *have* any, but (if the options aren't there already,) there should also be delivery-date/anonymous-gift options in that case, too.

Poll #3030 anonymous, delayed points-giving
Open to: Registered Users, detailed results viewable to: All, participants: 64


This suggestion:

View Answers

Should be implemented as-is.
55 (85.9%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
8 (12.5%)

(Other: please comment)
0 (0.0%)

ninetydegrees: Art: self-portrait (Default)
[personal profile] ninetydegrees

Title:
Points: e-mail notification when transferring

Area:
notifications, payments

Summary:
You're notified by e-mail when you're buying points but not when you're transferring them. I'd like to be.

Description:
I'd really like to be. :)

Poll #3024 Points: e-mail notification when transferring
Open to: Registered Users, detailed results viewable to: All, participants: 50


This suggestion:

View Answers

Should be implemented as-is.
44 (88.0%)

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

Shouldn't be implemented.
1 (2.0%)

(I have no opinion)
4 (8.0%)

(Other: please comment)
0 (0.0%)

ninetydegrees: Art: self-portrait (Default)
[personal profile] ninetydegrees

Title:
Points: historify purchase, use and transfer

Area:
payments

Summary:
Let users see a history of whatever they've done with their points. This would probably involve revamping 'Order History'.

Description:
Since you're now buying points and not directly stuff, it makes sense to me to let users keep track whatever they've done with them (buying, using, transferring). Something like:

* date - bought x points for $x - paid with method x - status - details
* date - used x points - status - details
* date - transferred x points - status - details

Poll #3023 Points: historify purchase, use and transfer
Open to: Registered Users, detailed results viewable to: All, participants: 58


This suggestion:

View Answers

Should be implemented as-is.
53 (91.4%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (8.6%)

(Other: please comment)
0 (0.0%)

yvi: Kaylee half-smiling, looking very pretty (Default)
[personal profile] yvi

Title:
Allow paid account users to upgrade to premium paid accounts

Area:
accounts, shop

Summary:
Paid account users should be able to pay the point difference between their current account level and a 6/12 month premium paid account to get upgraded.

Description:
If you have a 'normal' paid account on Dreamwidth right now, but would like to have a premium paid account (maybe someone else gifted you the paid account time, maybe you suddenly realized you need those 500 extra notifications, whatever), it would be good if you could just pay the difference in Dreamwidth points and convert your account to a premium paid account.

I admit I have no idea what would happen now if I just purchased a premium paid account in the store right now and because I am not interested in having one at the moment, I am not going to try. However, it looks like someone who has a few months left of regular paid account time pays the same price as someone who has a free account. Since from looking at another bug in the bugtracker I just learned that there is currently no downgrading from a premium to a regular paid account, it obviously won't be the case that you would have a premium paid account for 6/12 months and then be downgraded to a regular paid account. So I think the system should calculate how many points the remaining regular paid time you have on your account is worth and subtract that from your order.

Examples of how I think it would work:

A regular paid user has two months left on their paid account. That's 60 Dreamwidth points. They go into the shop and select 6 months of premium paid account time, which is worth 250 points. The system should ask the user whether they want to upgrade their account level and then tell the user that they need 190 points to perform the upgrade.

A regular paid user has 10 months left on their paid account. 6 months paid time is 175 points, 12 months is 350, and from there on the system should probably make some sensible calculations and rounding and so on, so I'd gather 10 months is worth about 290 points. The user goes into the shop and selects 12 months of premium paid account time, which is worth 500 points. The system should ask the user whether they want to upgrade their account level and then tell the user that they need 210 points to upgrade their account.

The calculations with rounding are probably going to be a bit tricky to implement - rounding down to the nearest full month and then having fixed values for those would probably be easiest, but with the points system, there can also be smaller steps. There can also be situations where the users gets Dreamwidth points back - which isn't bad, in my opinion, as that doesn't mean Dreamwidth will have to pay back money, it just means the points can be used for something else. But I think it's worth it so that users can upgrade their account without having to wait or feeling like they are losing something.

(And I certainly know that I have been hesitant to gift paid account in the past because I didn't know whether the user would maybe want a premium account)

Poll #2939 Allow paid account users to upgrade to premium paid accounts
Open to: Registered Users, detailed results viewable to: All, participants: 36


This suggestion:

View Answers

Should be implemented as-is.
16 (44.4%)

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

Shouldn't be implemented.
6 (16.7%)

(I have no opinion)
14 (38.9%)

(Other: please comment)
0 (0.0%)

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%)

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

Title:
Escrowed Dreamwidth points

Area:
shop

Summary:
Allow escrowing points to earmark them for work on specific features

Description:
Example use case: I'll give 271828 points to whoever implements an "electrocute commenter" client-server protocol feature inspired from the "electrocute webmaster" option some browsers support. I know that feature is complex and you may be reluctant to work on it with no guarantee of payment, so I'm putting those points in escrow, and I can't touch them or use them for the next 3 years except to transfer them to you.

This may overlap with the Dreamwidth baazar idea that I think someeone suggested long ago, or be a component of it. It may also work at cross-purposes with it.

The main problem is likely handling disputes on releasing points to recipient vs. reclaiming them for sender.

Poll #2673 Escrowed Dreamwidth points
Open to: Registered Users, detailed results viewable to: All, participants: 36


This suggestion:

View Answers

Should be implemented as-is.
7 (19.4%)

Should be implemented with changes. (please comment)
7 (19.4%)

Shouldn't be implemented.
7 (19.4%)

(I have no opinion)
15 (41.7%)

(Other: please comment)
0 (0.0%)

cesy: "Cesy" - An old-fashioned quill and ink (Default)
[personal profile] cesy

Title:
Add link to Circle Gifts from the Shop

Area:
shop, shameless money-grubbing

Summary:
Add a link from the shop page to circle gifts.

Description:
Add a link from http://www.dreamwidth.org/shop to the Circle Gifts page, http://www.dreamwidth.org/shop/gifts

Currently the Circle Gifts page appears in the menu, but not in the actual shop. I'd suggest adding "Buy a Paid Account ... For someone in your circle" between the first two "For" links.

Poll #1430 Add link to Circle Gifts from the Shop
Open to: Registered Users, detailed results viewable to: All, participants: 26


This suggestion:

View Answers

Should be implemented as-is.
24 (92.3%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (7.7%)

(Other: please comment)
0 (0.0%)

cesy: "Cesy" - An old-fashioned quill and ink (Default)
[personal profile] cesy

Title:
Add date to shop receipts

Area:
shop

Summary:
Add the date to order history detail pages.

Description:
If you go to the Order History page, http://www.dreamwidth.org/shop/history.bml, you can click on "View" to see the details of an order. On this "Receipt" page, the date the order was made isn't mentioned, although it is shown in the history page, and the delivery date is usually listed as "Today", even when it isn't, if you chose to have your order delivered immediately. The actual date of the order would be useful to add.

Open to: Registered Users, detailed results viewable to: All, participants: 40


This suggestion:

View Answers

Should be implemented as-is.
40 (100.0%)

Should be implemented with changes.
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(Other: please comment)
0 (0.0%)

yvi: Kaylee half-smiling, looking very pretty (Default)
[personal profile] yvi

Title:
Split 'give a gift' page into personal accounts and communities

Area:
Shop

Summary:
The 'shop/gifts.bml' page should have two separate lists of free accounts, one for personal accounts and one for community accounts.

Description:
Since most people (I guess), when they visit the Gift page will look for personal accounts to give paid time to, it would be nice if the list could be split so that the alphabetically-sorted free personal accounts come first and then the alphabetically-sorted free community accounts.

This will make the page more ordered, as many people have quite a lot of communities in their circle and right now need to 'sort it in their heads'.

The 'Expiring Soon' section can be left untouched or can be split as well. I assume that there's way less communities showing up there for most users, since having a paid account for communities isn't that much of an advantage yet.

I honestly can't think of drawbacks/problems right now, as three sections won't make the page less clear than two sections, in my opinion.

Implementation shouldn't be too much of a problem and I even volunteer to do it should the suggestion be chosen for implementation ;)

And now I am just hoping this is clear and I didn't forget anything.

Open to: Registered Users, detailed results viewable to: All, participants: 35


This suggestion:

View Answers

Should be implemented as-is.
34 (97.1%)

Should be implemented with changes.
1 (2.9%)

Shouldn't be implemented.
0 (0.0%)

(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