Site Update
A few interesting features of the site where silently introduced over the past year (like notifications), while others have long since been shrouded in mystery (like the stream). We also haven't had a meta update for while, so lets dig into some of the new changes:
Notification System
When someone replies to one of your comments or journals, you will now get a notification instead of a text message. These new notifications show comment replies in-line and can be used for other events that where not covered by the old system.
Numerous Small Pages
A summary page ([username].pipedot.org/summary) is now available for every user that shows you a brief overview of their activity. You can now monitor the computers/devices that have an active login cookie to the site on your "Logins" ([username].pipedot.org/login/) page. You can now see all feeds on the browse page. Feeds are also now organized into topics. Your published story submissions ([username].pipedot.org/submissions) now have their own page as well.
RSS Reader
Although the feed page ([username].pipedot.org/feed/) was added pretty early, many users may not realize that a full feed reader ([username].pipedot.org/reader/) is now built into the site. You can add your own RSS/Atom feed by URL, or select one of the existing feeds from the list of topics. You can even comment on articles or vote for your favorites.
The Stream
The stream is an attempt at simplifying the "link sharing" process. The traditional method of sharing a story is a rather involved process that may turn off some contributors:
Upcoming Pipe Changes
Speaking of story submissions and contributions, special thanks goes out to evilviper and zafiro17. Together, they have performed the entire submission process (detailed above) on nearly 500 of their own stories, as well as the laborious task of rewriting hundreds of poorly written (or incomplete) submissions to an acceptable quality level. The amount of effort required for these tasks is not inconsequential.
Suggestions to help relieve the burden of the editors mainly involve changing how the pipe operates:
Notification System
When someone replies to one of your comments or journals, you will now get a notification instead of a text message. These new notifications show comment replies in-line and can be used for other events that where not covered by the old system.
Numerous Small Pages
A summary page ([username].pipedot.org/summary) is now available for every user that shows you a brief overview of their activity. You can now monitor the computers/devices that have an active login cookie to the site on your "Logins" ([username].pipedot.org/login/) page. You can now see all feeds on the browse page. Feeds are also now organized into topics. Your published story submissions ([username].pipedot.org/submissions) now have their own page as well.
RSS Reader
Although the feed page ([username].pipedot.org/feed/) was added pretty early, many users may not realize that a full feed reader ([username].pipedot.org/reader/) is now built into the site. You can add your own RSS/Atom feed by URL, or select one of the existing feeds from the list of topics. You can even comment on articles or vote for your favorites.
The Stream
The stream is an attempt at simplifying the "link sharing" process. The traditional method of sharing a story is a rather involved process that may turn off some contributors:
- Find an interesting article for a story.
- Write up a short synopsis including a link to the article, maybe a quote or two, and possibly even a bit of editorial.
- Submit your scoop to the pipe.
- Wait as users vote up your submission.
- An editor reviews your story, makes any spelling/grammar/etc corrections they notice, and publishes the story to the front page.
Upcoming Pipe Changes
Speaking of story submissions and contributions, special thanks goes out to evilviper and zafiro17. Together, they have performed the entire submission process (detailed above) on nearly 500 of their own stories, as well as the laborious task of rewriting hundreds of poorly written (or incomplete) submissions to an acceptable quality level. The amount of effort required for these tasks is not inconsequential.
Suggestions to help relieve the burden of the editors mainly involve changing how the pipe operates:
- Submissions could automatically be published after a certain number of up-votes in the pipe.
- Submissions could get instantly published, but then have +/- vote buttons on each story to provide a "moderation" of stories. Stories with low scores could shrink to a smaller size or hide completely (similar to the comment moderation.)
- The pipe could be populated with automatically created stories generated from popular stream articles.
- Many browsers (Firefox/Chrome/nearly all mobile browsers) now support custom "share this page" buttons. These "Pipedot" share buttons could be an easy way to automatically create a story submission for interesting articles.
Unless I'm missing something, the only way I can access the reply to my comment (and I'm fairly sure there was one...) is by finding it in my notifications.
What's the point in even having Pipedot if it won't show our conversations?
Unless I'm missing something, thing isn't configurable. The vanishing-comments 'feature' is just set in stone. (A reminder: Pipedot isn't exactly overflowing with comments. There's no need for this.)