azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Expiration warning for feed account comments sections

Area:
feeds

Summary:
Display a notice in the comments section of feed accounts about the 14 day expiration of the entry. This would serve as a reminder that all things are ephemeral, and if the user wanted their comment saved, they could go to the original (settings allowing) or manually save it somewhere.

Description:
There's been some previous discussion around comments on feed accounts. Currently, comments are enabled on feed accounts as a courtesy to Dreamwidth users who would like a forum, however ephemeral, to discuss the feed amongst themselves, particularly when the source does not allow comments (such as XKCD).

However, it's not immediately obvious to someone who is unfamiliar with feed accounts that the comments won't be sent back to the original source of the feed, and that the comments will vanish when the feed entries vanish after 14 days.

I suggest a notice, to be displayed on the entry page above the comments section (so it's visible to readers and to people using quickreply), and on the reply page. It would say something like: Only feed entries from the last 14 days are displayed on Dreamwidth. Comments left on feed entries will not be saved after the entry is gone.

(People using quickerreply from their reading pages probably wouldn't have that notice visible.)

Users would be given enough information to decide for themselves whether to try to leave their comment on the source, or whether it's more appropriate for the comments on the feed. It could feel unnecessary or annoying to users who are already aware, and would introduce another little delay for screen reader users to try to skip over.


(If implemented cleverly, this could possibly be reused to support comment policy notices for communities and personal journals.)

Poll #16990 Expiration warning for feed account comments sections
Open to: Registered Users, detailed results viewable to: All, participants: 47


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
3 (6.4%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (10.6%)

(Other: please comment)
0 (0.0%)

dredmorbius: Dr. Edward Morbius (Default)
[personal profile] dredmorbius

Title:
Provide OPML feed import/export options

Area:
Reading Page

Summary:
Providing OPML support would allow for a standards-compliant improvement in the ability to manage RSS/Atom feeds on user's Reading Pages.

Description:
DW offers users the ability to add and manage feeds of RSS/Atom sources as a "Reading Page" feature, effectively a Web-based Newsreader.

Management of feeds (adding, removing, organizing, modifying) is done through a series of Web interfaces, principally http://www.dreamwidth.org/feeds/, http://www.dreamwidth.org/manage/circle/edit, http://www.dreamwidth.org/manage/subscriptions/filters, and http://username.dreamwidth.org/read.

Some of these tasks, as well as archival and distribution or sharing of lists, would be much easier if feeds could be exported in OPML format, a standard data exchange format for RSS and Atom feeds used by many feed readers. Providing import/export for Dreamwidth feeds would avoid a significant amount of front-end and back-end redesign to improve the feeds management process while providing for much greater user flexibility and ease in management.

https://en.wikipedia.org/wiki/Opml

This is *not* a request to allow re-syndication of feeds (though people would be able to share the feeds lists they subscribe to). E.g., request #9210 is an entirely different matter: http://dw-suggestions.dreamwidth.org/9210.html

Among challenges:

- DW feeds are based on local feeds, not the original source. Translating between these would have to be provided for.
- Allowing both feeds *and* filters to be exported/imported would be most useful. This would require some design and planning.

There's an earlier (2009) suggestion which mentions OPML though it's not clear where it is access or what the files contain: http://dw-suggestions.dreamwidth.org/133555.html

Poll #15785 Provide OPML feed import/export options
Open to: Registered Users, detailed results viewable to: All, participants: 35


This suggestion:

View Answers

Should be implemented as-is.
8 (22.9%)

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

Shouldn't be implemented.
1 (2.9%)

(I have no opinion)
26 (74.3%)

(Other: please comment)
0 (0.0%)

msilverstar: (Default)
[personal profile] msilverstar

Title:
Feed journals should show the source

Area:
user interface, feeds

Summary:
Put the feed source link into the feed journal view for clarity.

Description:
New feeds and broken feeds have very blank journal pages, which are a bit off-putting. Even feeds with lots of content can be confusing, depending on the format of that content. Right now the source information is only on the profile page. Because there's no original content in the journals, showing the feed source right there in the journal view would make them easier to understand.

Poll #9374 Feed journals should show the source
Open to: Registered Users, detailed results viewable to: All, participants: 57


This suggestion:

View Answers

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

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

Shouldn't be implemented.
2 (3.5%)

(I have no opinion)
21 (36.8%)

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

aedifica: Me looking down at laptop (off screen).  Short hair. (Default)
[personal profile] aedifica

Title:
Wording fix when creating a feed

Area:
Feed creation

Summary:
Wording on the "subscribe to this feed you've just created?" page refers to a checkbox that doesn't exist; let's change the wording.

Description:
When one creates a feed, the "subscribe?" page has this text:

[checkbox] Subscribe: display the entries to which you have access on your reading page.

Optional: Include in one or more subscription filters. You must subscribe to the user by selecting the _second_ box above in order to add them to any subscription filters. (emphasis mine)

But there is no second box, there's only the one box. I think this wording is carried over from the "add someone to your Circle" page, where it makes sense (there's a "grant access" box and a "subscribe" box, unlike here where there's just a "subscribe") box. Let's change the wording here so it makes sense in context.

Poll #8414 Wording fix when creating a feed
Open to: Registered Users, detailed results viewable to: All, participants: 51


This suggestion:

View Answers

Should be implemented as-is.
45 (88.2%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (11.8%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Protect outbound feeds from reader-breaking characters

Area:
feeds, the greater internet, making things make sense

Summary:
Automatically detect characters that are likely to break offsite software attempting to read journal feeds, and strip those characters/truncate the feed with a notice that this has been done. This would help offsite readers get feeds from Dreamwidth more reliably, even if they would occasionally have to click through to read the whole entry on the site.

Description:
Every now and then someone gets an unusual character in their entry and that character screws up the feed of that journal or community on LJ and probably other places.

One of the answers to this problem would be for LJ and other places to get feed readers that could deal with the occasional weird character, but that's not within our control.

If we could detect characters likely to break things, and replace them with something like [character that will break things was here] (there has got to be a better way to phrase that) only for the syndicated feed, so people reading the entry on their reading page or directly at the entry would see the whole thing, then feed readers on other sites wouldn't get jammed up as often from that problem.

If the feed generator has to replace something, or has to cut off an entry early, it should provide a notice at the bottom of the entry that the version in the feed is incomplete, that to read the original format one should click through to the DW version, and why the feed is incomplete: we detected characters that might break readers.

Poll #8413 Protect outbound feeds from reader-breaking characters
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

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

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

Shouldn't be implemented.
4 (8.9%)

(I have no opinion)
31 (68.9%)

(Other: please comment)
0 (0.0%)

[personal profile] melia244

Title:
Adding Feeds

Area:
feeds

Summary:
Option for adding feeds inside the manage circle page. Alternatively add a separate "manage feeds" entry on the organize tab.

Description:
This is related to http://dw-suggestions.dreamwidth.org/87376.html

Every time I decide to add a feed to my reading list I seem to fumble around a lot before I can remember how it is done. My intuitive response has always been:
1. Click on "Manage circle". From there I can add people/communities, and I can also modify my relationships to them. I can also unsubscribe from feeds, but I cannot add them. That seems incongruous.
2. Go to the home page and click on the "organize" tab, where all the other "manage" options reside.
For me "read->feeds" would probably mean the page where I get to read the feeds I subscribe to.

Thus my suggestion is to add the option for adding feeds to the manage circle page. Alternatively, add a separate "manage feeds" entry on the organize tab.

Poll #7895 Adding Feeds
Open to: Registered Users, detailed results viewable to: All, participants: 48


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
14 (29.2%)

Shouldn't be implemented.
1 (2.1%)

(I have no opinion)
14 (29.2%)

(Other: please comment)
3 (6.2%)

ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
[personal profile] ninetydegrees

Title:
Feeds: provide link to feed account when account already exists

Area:
rss, site interface

Summary:
When creating a feed account with a name which is already in use, link users to the account so that they can check whether the account is for the same feed or something else.

Description:
So here's what happened: I tried to create a feed which already existed except I didn't know that and because the URL I entered was a bit different the feed wasn't recognized as a duplicate. I therefore was asked to enter an account name as if it was a new feed. The name I entered was actually the same one as the one of the existing feed account (yay universe!) so I got this error message:

That account name is already in use.

That account name is already in use.

(Yeah, twice).

Oh cool, I thought, this probably means the feed account already exists. And then I exclaimed: "But why not link me to it?!" and made a sad face. No more sad face, please?

Poll #7087 Feeds: provide link to feed account when account already exists
Open to: Registered Users, detailed results viewable to: All, participants: 83


This suggestion:

View Answers

Should be implemented as-is.
75 (90.4%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
8 (9.6%)

(Other: please comment)
0 (0.0%)

erik: A headshot of me! (Default)
[personal profile] erik

Title:
Correct embedded content from syndicated LJ feeds

Area:
RSS

Summary:
Videos seem not to show up correctly in posts that are part of syndicated feeds from LJ.

Description:
When a community on LJ is syndicated here through RSS, any YouTube (and I assume other) videos posted on LJ are not visible on DW (At least to me). For instance:
http://vintage-ads-feed.dreamwidth.org/1360519.html
shows me a blank space (which seems to be the right size) instead of the video in Firefox and Chrome. But when I follow the link back to LJ, the video is shows up just fine in the same browser. And videos in other RSS feeds also show up correctly.

Poll #6497 Correct embedded content from syndicated LJ feeds
Open to: Registered Users, detailed results viewable to: All, participants: 35


This suggestion:

View Answers

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

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

Shouldn't be implemented.
3 (8.6%)

(I have no opinion)
15 (42.9%)

(Other: please comment)
1 (2.9%)

ratcreature: RatCreature's toon avatar (Default)
[personal profile] ratcreature

Title:
add the poster information to community rss feeds

Area:
communities, rss

Summary:
When I read a feed of a community I would like to be able to see the user who posted as well as the community name. It seems that this info is not in the RSS feed, and I guess DW can't do anything to make it appear in the LJ feeds, but it doesn't seem to be included in the community feeds originating on DW either, and I think it should be, so people reading communities offsite could see the posters.

Description:
In other feeds from blogs I've sometimes seen a "posted by" line, and in addition to the feed name I don't know whether that is a formal field in the format, but something like that would be nice to have in community feeds, so that readers could tell the poster.

Currently community feeds are for me more like alerts, because I always have to click to see who the poster was, even if I don't want to comment. So I suppose a drawback might be that people like me who like to know the poster are less likely to click to the original feed to find out, but communities concerned about their traffic can change the feed setting to just a teaser blurb or summary iirc, so that would be more straightforward to attract clicks, and otherwise I can't think of anything negative to come from this.

Poll #6470 add the poster information to community rss feeds
Open to: Registered Users, detailed results viewable to: All, participants: 46


This suggestion:

View Answers

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

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

Shouldn't be implemented.
1 (2.2%)

(I have no opinion)
13 (28.3%)

(Other: please comment)
1 (2.2%)

sofiaviolet: drawing of three violets and three leaves (Default)
[personal profile] sofiaviolet

Title:
Feed creation: allow user to select if multiple possible feeds

Area:
Feeds

Summary:
Sometimes, when creating a feed account, Dreamwidth picks the wrong feed from the source site (e.g. comments instead of posts). Allow users creating feed accounts to select which feed to use.

Description:
Currently, a user enters the site whose content they would like to see on their reading page and Dreamwidth makes its best guess as to which feed it should create the account for.

Suggested workflow:
1. User enters the URL and clicks "Add Feed."
2. On the next page, Dreamwidth displays the URL entered by the user and a list all the feeds it can pull from that site.
3. The user selects one feed using radio-tickies. If only one feed is available, it is auto-selected, If multiple feeds are available, the radio-tickies could be left blank or Dreamwidth could fill in its best guess.
4. The user enters a name for the new feed.

Bonus: If the user enters a URL that offers multiple feeds, some of which have been added to Dreamwidth already, they should receive a page that lists all available feeds and, where applicable, provides linkified usernames for the existing feed accounts.

Poll #6469 Feed creation: allow user to select if multiple possible feeds
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
3 (6.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (24.4%)

(Other: please comment)
0 (0.0%)

ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
[personal profile] ninetydegrees

Title:
Add interest keywords to feed accounts

Area:
feeds

Summary:
It's been suggested to make feeds searchable, which is a very good idea. However, I'd also like to be able to use interests to search for them because I think it would be more helpful when you want to find feeds pertaining to a certain topic.

Edit: see this comment for an alternative suggestion which doesn't use interest keywords.

Description:
I have no idea how many feed accounts they are on the site or how many are created per day so, to be honest, I don't know if this is a nice idea or a crazy one and how to implement it. Ideas and discussions are really welcome.

First, who would be able to add interests? Any user? A dedicated team of volunteers? Should users only be able to add interests from a pre-approved list? Could new ones be suggested? How?

Should the interests remain general (e.g. news, comics, music, science, technology, food,...) to be more manageable or would that would make the feature less useful/too restrictive?

What about personal blogs? I can see the potential for drama there. OTOH, it'd be like letting people assign interests to one's profile. OTOH, Neil Gaiman's blog is the feed with the greatest number of subscribers on DW so if we leave these out how useful is the feature?

Anything else?

Poll #6451 Add interest keywords to feed accounts
Open to: Registered Users, detailed results viewable to: All, participants: 41


This suggestion:

View Answers

Should be implemented as-is.
9 (22.0%)

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

Shouldn't be implemented.
3 (7.3%)

(I have no opinion)
21 (51.2%)

(Other: please comment)
3 (7.3%)

matgb: Artwork of 19th century upper class anarchist, text: MatGB (Default)
[personal profile] matgb

Title:
Allow crosspost footers to also be put in the footers of RSS feeds

Area:
RSS

Summary:
The crosspost footer can be used in a more flexible way, by allowing it to be put at the base of posts that leave the site in other ways, such as RSS feeds.

ETA: NB, we're not talkinag about feeds syndicated to DW, we're talking about the RSS feeds our journals/comms release to other sites.

Description:
Many users use the crossposter to other sites, and look forward to it working with other platforms as well.

Others still have their content syndicated in some way, for example imported into Facebook notes or onto a Livejournal feed.

I have kept my notes import for Facebook coming from Livejournal, as that way the crosspost footer stays. In the comments to this suggestion:
http://dw-suggestions.dreamwidth.org/435390.html

it's come up that some people comment on syndicated content on Livejournal thinking it's going to go to the author, which is obviously not true. Allowing a footer displayed within the feed would help solve this problem.

Some sort of feed footer seems to be a fairly standard feature of other platforms, they definitely exist for some Blogger and Wordpress powered feeds I read, and this would definitely help cross site interoperability.

Drawbacks: Optional opt in, with wording editable by the user, apart from coding time and possible extra server load for the comment # image, I see none.

Poll #4510 Allow crosspost footers to also be put in the footers of RSS feeds
Open to: Registered Users, detailed results viewable to: All, participants: 38


This suggestion:

View Answers

Should be implemented as-is.
22 (57.9%)

Should be implemented with changes. (please comment)
3 (7.9%)

Shouldn't be implemented.
1 (2.6%)

(I have no opinion)
12 (31.6%)

(Other: please comment)
0 (0.0%)

willow: Red haired, dark skinned, lollipop girl (Default)
[personal profile] willow

Title:
Feeds Don't Need A Reply Function

Area:
feeds

Summary:
Stop making feeds seem like original DW content

Description:
Content that is imported to be read on DW, via RSS aka Feeds, should NOT have a reply function. The content creator never sees any replies made to a feed (it is not an account, there is no associated email), and entries and comments are not permanent on a feed anyway.

When individuals do not realize that, because there's a reply function, they can end up commenting and being ignored.

There is really no need for feeds to have a reply function - especially when there's a link to the direct entry itself.

Poll #4436 Feeds Don't Need A Reply Function
Open to: Registered Users, detailed results viewable to: All, participants: 73


This suggestion:

View Answers

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

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

Shouldn't be implemented.
29 (39.7%)

(I have no opinion)
9 (12.3%)

(Other: please comment)
2 (2.7%)

aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] aveleh

Title:
Put links to original articles at the bottom of every feed entry

Area:
feeds, entries

Summary:
A link to the original source for a feed article would be convenient if located at the bottom of the article instead or as well as at the top.

Description:
Right now, any journal that imports a feed from an external source displays the original link, and then the article (or portion of the article provided by the feed). This means that I often read the article or article summary, and if I find it interesting, I have to scroll back up to find the link to the source so that I can read the comments provided there or the remainder of the article.

I think that having an additional link at the bottom would be more convenient. While for shorter articles or feeds that only provide a headline or summary having two links so close together might be confusing, the dual placement would allow convenient reading both for those people who like to follow the link right away or those who like to read the text before choosing to follow the link.

Poll #3746 Put links to original articles at the bottom of every feed entry
Open to: Registered Users, detailed results viewable to: All, participants: 48


This suggestion:

View Answers

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

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

Shouldn't be implemented.
1 (2.1%)

(I have no opinion)
9 (18.8%)

(Other: please comment)
0 (0.0%)

juniperphoenix: Fire in the shape of a bird (Default)
[personal profile] juniperphoenix

Title:
Automatically cut entries from syndicated feeds

Area:
entries

Summary:
I would like to be able to set a preference whereby all entries from syndicated feeds (or all those over a certain length) would be automatically placed behind a cut on my Reading page.

Description:
I subscribe to a lot of syndicated feeds. Many of these feeds come from blogs where cut tags are not used at all, and the posts are often very long and/or contain multiple photos. I would like a way to reduce the amount of space taken up by these posts on my Reading page.

I don't know how this could be accomplished from a coding perspective, but as an end user what I'd like to see is a preference somewhere in my account settings that would let me automatically place all entries from feeds behind a cut. It would be even better if it were sensitive to the length of the entry -- if, for example, it could leave the first 100 words uncut as a teaser and place the rest behind a cut.

Now that we have expandable cut tags, it would be very easy for users to expand and read the entries if they wanted to, and it would save a lot of clutter on Reading pages.

It would be awesome if any solution to this could apply to Network pages as well as Reading pages.

Thanks for your consideration!

Poll #3497 Automatically cut entries from syndicated feeds
Open to: Registered Users, detailed results viewable to: All, participants: 48


This suggestion:

View Answers

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

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (22.9%)

(Other: please comment)
0 (0.0%)

trouble: Sketch of Hermoine from Harry Potter with "Bookworms will rule the world (after we finish the background reading)" on it (Default)
[personal profile] trouble

Title:
Feed of "Latest Things"

Area:
Latest Things

Summary:
I would love to be able to add a "latest things" feed to my greader for specific tags.

Description:
Being able to subscribe to specific feeds on the "latest things" page would be awesome. I don't know what else to describe! :D

Poll #3407 Feed of "Latest Things"
Open to: Registered Users, detailed results viewable to: All, participants: 38


This suggestion:

View Answers

Should be implemented as-is.
21 (55.3%)

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

Shouldn't be implemented.
1 (2.6%)

(I have no opinion)
12 (31.6%)

(Other: please comment)
0 (0.0%)

green_grrl: (Default)
[personal profile] green_grrl

Title:
Preserve cuts on RSS feeds / auto-cut RSS feeds on Reading page

Area:
Reading page - cuts

Summary:
RSS feeds on a DW Reading page should respect the LJ text cut or "Read more" cut of the source posting. If this is not technically feasible, long posts should be auto-cut (or you should have the option of your reading page having an auto cut).

Description:
When my DW Reading page loads an RSS feed I've subscribed to, it loads the entire thing, even though the original blog/journal post had a cut. Some feeds, this is no big deal—posts are short. But if someone is subscribed to the RSS feed of a fic community on LJ, or to another lengthy source (538, I'm just sayin'), the Reading page can get looong.

Is it even technically possible to get cuts to come in with RSS? (Because with the new little AJAX triangle? That would be beyond awesome!)

If there's no way to do it with RSS, then I think azurelunatic's suggestion for auto-cuts (http://dw-suggestions.dreamwidth.org/298397.html) would be the second best option.

Poll #3368 Preserve cuts on RSS feeds / auto-cut RSS feeds on Reading page
Open to: Registered Users, detailed results viewable to: All, participants: 56


This suggestion:

View Answers

Should be implemented as-is.
30 (53.6%)

Should be implemented with changes. (please comment)
8 (14.3%)

Shouldn't be implemented.
3 (5.4%)

(I have no opinion)
15 (26.8%)

(Other: please comment)
0 (0.0%)

mecurtin: Doctor Science (Default)
[personal profile] mecurtin

Title:
Make automatic cuts in feeds

Area:
Feeds

Summary:
Make it possible to force cuts in feeds (or other entries, but feeds in particular)

Description:
I've been consolidating my feeds on DW, and while some of them (e.g. http://alistapart-feed.dreamwidth.org/ ) use excerpts for their feeds, others (e.g. http://smashing-feed.dreamwidth.org/) do not. I know that the difference is in the way they've set up their feeds, but I'd like to be able to force cut tags for certain journals, or for a class of journals such as feeds.

Poll #3305 Make automatic cuts in feeds
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
19 (42.2%)

Should be implemented with changes. (please comment)
10 (22.2%)

Shouldn't be implemented.
6 (13.3%)

(I have no opinion)
8 (17.8%)

(Other: please comment)
2 (4.4%)

lamashtar: Shun the nonbelievers! Shun-na! (Default)
[personal profile] lamashtar

Title:
Comment feeds

Area:
comments

Summary:
A comment feed like that used on blogs, so you can receive all the comments made to a community without having to track all the individual posts and clog your email.

Description:
Many blogs now offer comment feeds, in addition to entry feeds. Feed readers offer quick ways of zooming through content to see what you might be interested in. One of the drawbacks to the journal thread system is that if you are not the original poster you won't receive all the comments on a post. People tend to visit the post a few times and then assume the conversation has died and move on. You lose out on participating in conversation you might've been interested in.

With comment feeds, you immediately know when someone has commented on an old post. You can respond and engage them. You can also do searches if you're looking for a specific conversation in the feed, which can be useful for mods. Using this system for blogs has saved me a lot of surfing loading time and I can swiftly determine whether or not a post or comment is worth participating in.

While tracking a post does similar things for specific posts or comments of interest, it requires prognosticating that an interesting conversation will develop and it sends the notification straight to your email box, often filling it up with nonsense you have to open and check each individually. A possible answer is to allow the tracking feature to be set up for feeds, which would allow almost all the features of regular comment feeds, though it would not allow you to know if someone commented on very old posts if the journal you're following has a large archive.

Poll #2724 Comment feeds
Open to: Registered Users, detailed results viewable to: All, participants: 36


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
3 (8.3%)

Shouldn't be implemented.
5 (13.9%)

(I have no opinion)
16 (44.4%)

(Other: please comment)
0 (0.0%)

Profile

Dreamwidth Suggestions

April 2017

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

Style Credit

Expand Cut Tags

No cut tags

Syndicate

RSS Atom