### Add Discord ID to profile under Connect Services

06:31 am

Title:
Add Discord ID to profile under Connect Services

Area:
profiles, third party integration

Summary:
Adding a new option for Discord to the Connect section of user profiles.

Description:
Discord (https://discordapp.com/) has been gaining popularity particularly among RPers in recent months as an alternative to AIM for a central messaging system. It'd be really nice if we could add our Discord user ID the same way we can add our AIM screen names to our profiles.

Their formats are CHOSENNAME#4DIGITS where the 4 digits are randomly assigned, but consistent, and the whole thing becomes your actual username - so if you chose the username "Penguin", Discord will give you "Penguin#2792" and that is your username.

Discord doesn't host profile pages outside of the chat app itself, so I don't think you could do the <user name=name site=discord> function, but it's not needed. Just the ability to list the username itself is really the useful bit.

Poll #18124 Add Discord ID to profile under Connect Services
Open to: Registered Users, detailed results viewable to: All, participants: 101

This suggestion:

Should be implemented as-is.
82 (81.2%)

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

Shouldn't be implemented.
1 (1.0%)

(I have no opinion)
17 (16.8%)

0 (0.0%)

### entries serving as "events" with dates in future

04:02 pm

Title:
entries serving as "events" with dates in future

Area:
entries

Summary:
Allow a special class of entry, an "event", with in addition to posting time, a start and finish in the future. Allow a special class of comment saying that one is/is not attending such an event. Facilitate display of upcoming events amongst one's watchlist.

Description:
<user name="liv"> (who has nothing to do with this specific proposal) and I were discussing the depressing popularity of Facebook in spite of its universally acknowledged awfulness.

It seems to me that one of the main drivers behind it is familiar; it's the reason Exchange crops up so widely in a corporate context in spite of its awfulness. Shared calendaring, or similar.

I suggest that something of a similar nature could piggyback on the existing entry infrastructure. An "event" would have additional metadata in the form of start and end times (ideally conveniently organised so that a one-day event can be created without saying "00:00 on Monday 24th July ... 24:00 on Monday 24th July"), and the creation interface would strongly encourage adding a meaningful title to the entry. There's some obvious wishlist stuff for repeating events, but none of that is really necessary. Other than that, they'd be normal entries, with users free to enter what text they pleased, make them public or fiendlocked, etc. (The interface might, wishlist, warn about the creation of public events).

In addition, there'd be a format for metadata in comments which would indicate that a given user was or was not attending an event. Comments consisting purely of such metadata would not be ordinarily displayed. An "event" entry would still permit conventional comments or comments with both text and attendance metadata.

The tricky bit would be in the display; in making this facility as convenient to use as possible. I would suggest, for example, that (optionally) when viewing a watchlist (including a custom view), I would see at the top of the page a list of upcoming events in the next n days posted by users on that list, including their titles and radio buttons to mark my intent to attend them, perhaps mentioning how many others in my Circle are attending. Viewing the entry for an event might present the attendees list in a convenient format assembled from the comment metadata.

Poll #13638 entries serving as "events" with dates in future
Open to: Registered Users, detailed results viewable to: All, participants: 40

This suggestion:

Should be implemented as-is.
5 (12.5%)

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

Shouldn't be implemented.
13 (32.5%)

(I have no opinion)
21 (52.5%)

0 (0.0%)

### Support MathJax in Entries

09:43 am

Title:
Support MathJax in Entries

Area:
MathJax JavaScript support at site level

Summary:
I suggest that (in due time!) dw support MathJax <a href="http://www.mathjax.org/">MathJax</a> for mathematical/technical formatting in dw entries.

Description:
This suggestion is intended to make it easy for dw people to write beautiful and useful mathematical/technical content in our entries. MathJax is now a mature and well-supported FOSS extension of html via javascript, with healthy user and developer communities. We've been experimenting with MathJax for the Stanford Encyclopedia of Philosophy, and we've been very pleased with it so far. (This is not an official SEP endorsement.) Code can be written or displayed rendered or in TeX or MathML. This makes it useful also for gacking and modifying, and even for learning more about those markup languages. Anyone who has tried to do serious mathematical or technical typesetting in html will agree, I think, that html is *not* a typesetting language. MathJax goes a long way toward allowing decent technical typesetting in an html context.

If MathJax can be permitted as a tightly controlled JavaScript layer at the dw site level, which I think it can, then users will be able to write mathematical and technical fragments into their journal entries as easily as any other html. I don't envision putting MathJax support into the rich text editor -- I anticipate that anyone who wants to use MathJax will be comfortable editing their own markup. This is rather an extension of html markup into a wider domain.

It is possible that I'm overestimating the ease of implementing this suggestion, but I've experimented with MathJax support in my personal webpages and at the SEP site, and it looks as though MathJax makes this as easy as possible. Furthermore, the social/political aspects look promising, insofar as the MathJax user and developer communities look like just the sorts of folks dw wants to make alliance with, as far as I can tell.

Poll #12341 Support MathJax in Entries
Open to: Registered Users, detailed results viewable to: All, participants: 46

This suggestion:

Should be implemented as-is.
14 (30.4%)

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

Shouldn't be implemented.
3 (6.5%)

(I have no opinion)
26 (56.5%)

2 (4.3%)

### Allow mailto: links in the Links module

09:33 am

Title:
Allow mailto: links in the Links module

Area:
Journal modules

Summary:
It is not possible to add a mailto: link to the "Links" module. I would like to be able to do so.

Description:
At present, if I fill in "mailto:my@email.com" as a link target for the Links module, it gets rewritten to "http://my@email.com", which is obviously something entirely different.

I don't know whether there is a reason for not allowing email links, and thus whether it is intentional that it can't be done, or whether this is an unintended side-effect of tidying up URIs. If it's not a deliberate choice, I think that email links should be allowed.

Poll #11748 Allow mailto: links in the Links module
Open to: Registered Users, detailed results viewable to: All, participants: 53

This suggestion:

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

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

Shouldn't be implemented.
5 (9.4%)

(I have no opinion)
22 (41.5%)

0 (0.0%)

### Enable Embedding GitHub Gists as Media in Posts

04:57 pm

Title:
Enable Embedding GitHub Gists as Media in Posts

Area:
posting, media

Summary:
Enable adding GitHub Gists, which are embedded as scripts, in posts, via the 'add media' option so that DW users can post short blocks of formatted source code for discussion and review.

Description:
Gists are text files hosted on GitHub enabling developers to post short snippets of code for review and comment.

GitHub provides a way to embed a gist on a site, as a script file:

&lt;script src="https://gist.github.com/3290622.js?file=foo.js"&gt;&lt;/script&gt;

However, DW wisely prevents scripts from being embedded as either media or post content because XSS :)

But adding gist.github.com to a whitelist would enable coders of all skill levels to quickly post nicely formatted snippets of code for review, discussion, and comment.

Poll #11553 Enable Embedding GitHub Gists as Media in Posts
Open to: Registered Users, detailed results viewable to: All, participants: 53

This suggestion:

Should be implemented as-is.
13 (24.5%)

Should be implemented with changes. (please comment)
5 (9.4%)

Shouldn't be implemented.
5 (9.4%)

(I have no opinion)
30 (56.6%)

0 (0.0%)

### Using "Tell Someone About This" should be included in Sent mail.

10:33 pm

Title:
Using "Tell Someone About This" should be included in Sent mail.

Area:

Summary:
When I use the envelope icon to email a link to a Dreamwidth entry, it should show in the sent mail in my inbox.

Description:
When I use the envelope icon to email a link to a Dreamwidth entry to someone who doesn't have a Dreamwidth acct, it should show in the sent mail in my inbox. I can't always remember who I've sent what. I looked at the site map, and I can't see anywhere else reasonable to track these. ( I suppose I might be looking right at and not seeing it. If so, please let me know where.)

Poll #10626 Using "Tell Someone About This" should be included in Sent mail.
Open to: Registered Users, detailed results viewable to: All, participants: 57

This suggestion:

Should be implemented as-is.
31 (54.4%)

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

Shouldn't be implemented.
1 (1.8%)

(I have no opinion)
25 (43.9%)

0 (0.0%)

### Thread Logging (or "Dreamwidth Journal History")

11:00 am

Title:
Thread Logging (or "Dreamwidth Journal History")

Area:

Summary:
It can be hard to track down all the posts you've made or threads you've started or replied to -- even with tags, commenting in your journal, other people's journals, communities, etc, can make it hard to have any kind of record of your own experiences on the site. If the site can record every one of your posts/top level comments (or the top-level comment you replied to) and report it (somewhere on your console, or into a specific entry in your journal) it will be much easier for people to reread their old posts/threads and track their life on DW.

Description:
Right now it's difficult to find everywhere you've posted or commented to and thus track your 'life' on this site. Basically, if someone wishes to do "thread logging", it all needs to be done manually -- you can track threads which sort of does it a little, but that again is a manual task. There's no automatic record, no recorded history, of where you've commented and what you've said.

Especially as the roleplay community gets larger this is something I feel will be more in demand (as rpers frequently like to reread the character development they go through, but sometimes this can be months or years of posts to wade through -- with an RP like CFUD, you've got six years of roleplay! Or, even if they're not fans of rereading, a lot of sites request you turn in your activity every month, which involves wading back through posts trying to find it, using tags liberally to help yourself keep track (but again, tags are added manually, which means human error). Thread-logging is standard but usually involves manual work.

Perhaps there can be an option on the site which outputs (into a console box or an entry that you set up and somehow mark as a "history" entry) the links for your comments/posts. Obviously doing every comment would be frustrating, so I'm thinking:
A) Any post you make, the post link would go in here.
B) If you make a comment, the History console identifies the top level comment in that thread (whether you started the thread or replied to it) and links it, discarding anything after. (Obviously in the case of B it would also check if it has already linked this thread and not link again if so).

Additional thoughts, details, and concerns:

- It would need to be arranged by date somehow, whether just a chronological order (top-down) or with datestamps of the toplevel comment beside them.

- Since what's just a list of links could become unwieldy fast it would be good for the user to either be able to convert into linktext instead of a plain URL, or at least have a field where the user could add a comment beside the link to identify the content if they choose to (ex: (LINK) - "Umeda and Akiha have a picnic. Mood crab sings them a song.")

- Having a list of the number of your total comments in the thread/post would probably be super useful to RPers (obviously this would mean that either it would have to dynamically update with each reply like the comment section in your profile OR the user could manually run to check for all updates you've made with that username).

- If this WAS going to be planned anyway, obviously the fact that people imported journals would make it difficult to have a 'full' list of their journal's history, unless there were a way to run the function to comb back through all appearances of the relevant username on DW (using their ID) and do a link dump. (This would be ideal for me, as a CFUDer who really wants to reread old threads). Since DW has such a strong search function I think this would theoretically be possible using something similar to the search functionality using the journalname ID, but I'm no programmer.

- Privacy issues -- if in a console you need to be logged into to see this isn't a concern, but if not, whatever journal entry this output into might need to be private by default (with the user able to make it public if they chose to?) in case you didn't want the whole world to see what that journal had been up to.

- This obviously wouldn't track anonymous comments, so if users can manually add extra threads (as in an editable entry) for any 'anon posts' they participate in, or if they did a 'bodyswap' with journals or so on, they could help keep track of these extra things as well. Not totally necessary as long as the journal name's history is added but it'd be a nice bonus for completion's sake.

- If this is impossible to do on the site itself, are there any programmers on the suggestions team or reading this otherwise who may be able to draw up an associated client that could run a similar function of outputting posts/the top comment of threads with a journal name? It's currently difficult to get full thread logs without having to manually keep track of things yourself, which is doubly difficult if you have multiple computers you thread from, if your game doesn't use tags, etc.

Poll #9801 Thread Logging (or "Dreamwidth Journal History")
Open to: Registered Users, detailed results viewable to: All, participants: 57

This suggestion:

Should be implemented as-is.
11 (19.3%)

Should be implemented with changes. (please comment)
5 (8.8%)

Shouldn't be implemented.
18 (31.6%)

(I have no opinion)
21 (36.8%)

2 (3.5%)

04:56 pm

Title:

Area:
Crossposting

Summary:
Allow me to link to my Twitter account and post the subject line and link when I post.

Description:
The one thing I really miss from LJ is Twitter posting. I don't think comments should be crosspostable or anything from a journal that you don't own. But when posting a new item to your journal (or maybe to a public community?) I would really like the option to send a Twitter notice. I have lots of friends who used to read journals and have stopped, but they will follow a link from Twitter and read if it's right in their face.

I'd post the subject line and a condensed link only.

Poll #9488 Twitter notifications of new posts
Open to: Registered Users, detailed results viewable to: All, participants: 56

This suggestion:

Should be implemented as-is.
17 (30.4%)

Should be implemented with changes. (please comment)
6 (10.7%)

Shouldn't be implemented.
9 (16.1%)

(I have no opinion)
24 (42.9%)

0 (0.0%)

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

03:46 pm

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

Area:

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:

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

3 (3.3%)

### Editable Module Headers

03:51 pm

Title:

Area:
styles / customization

Summary:
User input fields to control the text headers of all modules, not just the custom text module.

Description:
Currently, the the Custom Text module allows for the user to change the module heading from the Text customization options for your journal. (The same page where you might edit other default page text such as metadata labels and navigation links). Though you can hide module headers entirely with css, other modules have no such customization options other than order and page placement. It would be exceedingly helpful to both users and communities who use their journals, and the modules available to them, differently if all other modules allowed for the user to alter the default module headings to text of their own choosing.

This might logically be implemented either from the Text page, as it already exists for the with the Custom Text module, or from the Modules page where order and organization of your modules takes place.

Poll #9210 Editable Module Headers
Open to: Registered Users, detailed results viewable to: All, participants: 68

This suggestion:

Should be implemented as-is.
39 (57.4%)

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

Shouldn't be implemented.
2 (2.9%)

(I have no opinion)
26 (38.2%)

0 (0.0%)

### Browse Wikimedia Commons for photos to insert into new posts

02:02 pm

Title:
Browse Wikimedia Commons for photos to insert into new posts

Area:
entries

Summary:
On the New Post and Edit pages, give the user the ability to browse freely licensed photos from Wikimedia Commons to insert into their posts. Use the MediaWiki API https://www.mediawiki.org/wiki/API:FAQ and the example of http://www.mediawiki.org/wiki/PhotoCommons as a prototype (it's a WordPress extension).

Description:
It would be nice to give users the ability to dress up their more text-heavy posts with graphics. Wikimedia Commons is a useful source of freely licensed graphics.

I don't know how this should be implemented in the UI. I imagine there would be some kind of search functionality, to search Commons for photos matching a keyword and then to display thumbnails and then choose them for insertion. Inserting the photo should probably also automatically add a caption with attribution.

Poll #8850 Browse Wikimedia Commons for photos to insert into new posts
Open to: Registered Users, detailed results viewable to: All, participants: 64

This suggestion:

Should be implemented as-is.
5 (7.8%)

Should be implemented with changes. (please comment)
4 (6.2%)

Shouldn't be implemented.
26 (40.6%)

(I have no opinion)
27 (42.2%)

2 (3.1%)

### Instant Feedback Button

08:06 am

Title:
Instant Feedback Button

Area:
Posts

Summary:
Similar to the Facebook 'like' button, have a 'favorite' button, kudos, etc. Some sort of button, where if a person likes an entry but doesn't want to comment, they can leave some sort of feedback.

Description:
As somewhat of an author, it's frustrating when one doesn't get reviews. I may not get reviews but I do see when people favorite one of my stories on another site. That site keeps track of how many have favorite your work. Since many authors might be coming here, I think having some kind of like/favorite/kudos button would be great. Fanfiction.net and DeviantArt.com have similar options.

Poll #6525 Instant Feedback Button
Open to: Registered Users, detailed results viewable to: All, participants: 267

This suggestion:

Should be implemented as-is.
161 (60.3%)

Should be implemented with changes. (please comment)
46 (17.2%)

Shouldn't be implemented.
38 (14.2%)

(I have no opinion)
16 (6.0%)

6 (2.2%)

### Standardize color selection throughout site

04:24 pm

Title:
Standardize color selection throughout site

Area:
Customization, circle management

Summary:
I want an improved color picker, and all places on the site that pick colors to be the same.

Description:
Right now, I can think of two places on Dreamwidth that have color selection:

http://www.dreamwidth.org/customize/options?group=style
http://www.dreamwidth.org/manage/circle/edit

I want us to pick out a jQuerified plugin, such as ColorPicker, and use it on both of those pages instead of the current disparate systems.

This suggestion has a caveat, however, in that it changes the way the circle colors work--right now, those colors seem to be artificially limited to a given set in the front end. However, I don't think giving people more options with a (possibly better) UI would be amiss here.

Any implementation would have to consider users who do not use Javascript, however, and make sure they have a usable interface still.

Poll #3752 Standardize color selection throughout site
Open to: Registered Users, detailed results viewable to: All, participants: 32

This suggestion:

Should be implemented as-is.
17 (53.1%)

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

Shouldn't be implemented.
1 (3.1%)

(I have no opinion)
13 (40.6%)

0 (0.0%)

## Profile

Dreamwidth Suggestions

S M T W T F S
1
23456 7 8
9 101112131415
16171819202122
23242526272829
30

No cut tags