SoylentNews is people
SoylentNews
Assuming everything went well with our upgrade (and thus we're running the new and shiny slashcode 14.04), you might have noticed a new bar at the top of the page which looks like this: "SoylentNews is powered by your submissions, so send in your scoop. Only 13 submissions in the queue."
This is our cue to the community that the queue is running low, and acts as a request to "please submit your stories if you want to keep the flow of news coming." We've previously had to run stories asking for submissions, so this will prevent us from having to spam the index for help. A lot of you left good comments in the previous "need stories" post, so I'm going to take take a moment and address that.In the comments on our last plea, two things were identified. First, too many moderators can limit community involvement due to moderate^post. I've gotten tons of good feedback already (and I ask you guys to keep it coming), and I'll have a writeup of what we're doing based on that feedback soon.
The second one was, in my opinion, a more serious failing on our part; specifically that we don't communicate on why a story is rejected. This is a side-effect of simply not having a way to send a notification to a submitter short of an editor going to a user's profile, getting their email, and sending them mail. That being said, I promised you guys transparency, and we're going to deliver. The other site often frequently worked in a void, and while Firehose let everyone see the submission queue, it didn't provide any insight on what does (or doesn't) make it onto the main page.
We don't have it now, but we will implement a way for editors to easily communicate about rejections to submitters via the messaging feature on the site. I've flagged this as critical for the 14.06 release, but I hope to get it backported and live before then. Until then, please bear with us. I've asked the editorial team to send messages to the email addresses included in submissions (or the email on a user's profile) so we can communicate why we're rejecting a story.
This is our cue to the community that the queue is running low, and acts as a request to "please submit your stories if you want to keep the flow of news coming." We've previously had to run stories asking for submissions, so this will prevent us from having to spam the index for help. A lot of you left good comments in the previous "need stories" post, so I'm going to take take a moment and address that.In the comments on our last plea, two things were identified. First, too many moderators can limit community involvement due to moderate^post. I've gotten tons of good feedback already (and I ask you guys to keep it coming), and I'll have a writeup of what we're doing based on that feedback soon.
The second one was, in my opinion, a more serious failing on our part; specifically that we don't communicate on why a story is rejected. This is a side-effect of simply not having a way to send a notification to a submitter short of an editor going to a user's profile, getting their email, and sending them mail. That being said, I promised you guys transparency, and we're going to deliver. The other site often frequently worked in a void, and while Firehose let everyone see the submission queue, it didn't provide any insight on what does (or doesn't) make it onto the main page.
We don't have it now, but we will implement a way for editors to easily communicate about rejections to submitters via the messaging feature on the site. I've flagged this as critical for the 14.06 release, but I hope to get it backported and live before then. Until then, please bear with us. I've asked the editorial team to send messages to the email addresses included in submissions (
mrcoolbp adds: Please include an email in your submission if you'd like to receive feedback in the case that the submission is rejected until we can implement a better solution.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
If bankers can count, how come they have eight windows and only four tellers?
(Score: 1) by paulej72 on Tuesday April 01 2014, @05:44PM
We are planning on putting it back in. When the nagger does not need to nag, it will display the "this page was generated" message. I think I'll add some new items to the two lists though to make it more interesting.
In the new version it will not disrupt the layout of the three main elements below the header.
Team Leader for SN Development
(Score: 2, Insightful) by ticho on Tuesday April 01 2014, @06:04PM
Maybe make it configurable, so that those of us who think it is stupid can disable it? :)
(Score: 2, Insightful) by spxero on Tuesday April 01 2014, @06:34PM
Honestly I found it kind of funny in a grass roots kind of way. That kind of thing would never show up on a major news site and made the site feel more like a community than just a news roll.
(Score: 1) by Buck Feta on Tuesday April 01 2014, @06:59PM
> I think I'll add some new items to the two lists though to make it more interesting
Oh boy, Mad-libs!
Adjectives: tasty, fatty, savory, spattering porcine, scrumptious, delectable, heavenly, toothsome.
Nouns: bacon, pigs, hogs, breakfast meats, rashers, porkbellies, swine, boars, porkers.
- fractious political commentary goes here -
(Score: 2) by Koen on Tuesday April 01 2014, @07:24PM
The truly nerdy thing to do would be to take the adjectives and nouns from the original Elite game [alioth.net], such as "Fierce Bug-Eyed Lizards", "Red Slimy Lobsters" and "Small Blue Horned Humanoids".
/. refugees on Usenet: comp.misc [comp.misc]
(Score: 1) by Yog-Yogguth on Wednesday April 02 2014, @02:35AM
It needs a kitchen sink, please add one :)
E.g.: "this page was generated for $user by a kitchen sink full of bacon".
Bite harder Ouroboros, bite! tails.boum.org/ linux USB CD secure desktop IRC *crypt tor (not endorsements (XKeyScore))