SoylentNews - User contributions [en]

Editors

2018-03-09T00:23:02Z

Chromas: /* Who we are */

The editorial team is responsible for checking and revising (if required) user submitted stories. Prospective editors should be prepared to devote a significant amount of time to checking stories, have a good grasp of the English language, and be familiar with slash's formatting options. Contact: '''editors@soylentnews.org''', or join #editorial in [[SoylentNews:IRC |irc]].

==Who we are==
<section begin=whoweare />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| janrinok
| editor
| UTC+1 (CET)
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| n1
| editor
| UTC
|-
| martyb
| editor
| UTC-4 (EST/EDT)
|-
| CoolHand
| editor
| UTC-4 (EST/EDT)
|-
| NotSanguine
| editor
| UTC-4 (EST/EDT)
|-
| Cmn32480
| editor
| UTC-4 (EST/EDT)
|-
| takyon
| editor
| ?
|-
| charon
| editor
| UTC-4 (EST/EDT)
|-
| Fnord666
| editor
| UTC-4 (EST/EDT)
|-
| Snow
| editor
| ?
|-
| mrpg
| editor
| ?
|-
| chromas
| editor
| UTC-8 (PST; -7 PDT)
|-
| fyngyrz
| editor
| ?
|-
| GreatOutdoors
| editor
| ?
|-
| Xyem
| editor
| GMT
|}
<section end=whoweare />

==Retired Members==
Former editors that have lost their roles due to inactivity or retirement
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Retired members]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Subsentient
| editor
| UTC-7 (MST)
|-
| LaminatorX
| Team Leader
| UTC-5 (CST/CDT)
|-
| Dopefish
| editor
| UTC-8 (PST)
|-
| mattie_p
| editor
| UTC-7 (MST)
|-
| zizban
| editor
| UTC-4 (EST/EDT)
|-
| Azrael
| editor
| ?
|-
| Woods
| editor
| UTC-5 (CST/CDT)
|-
|}

==Projects==

*Continue to develop editorial process (see Documentation below)
*Maintain static pages (FAQ.shtml, about.shtml, and moderation.shtml)

==Documentation==
<section begin=documentation />
*A [[Story_Style|Story Style]] document outlines editorial guidelines, it may need additional refining and ratification eventually.
* [[Editing_Process|The Editing Process]] - builds on the Story Style and Submission Guidelines to describe <b>how</b> the editing process is carried out.
* [[Submission_guidelines|Submission Guidelines]] - Notes to all users regarding the formatting of submissions and relevant rules.
* [[Editorial_Policy|Editorial Policy]] - Policy Statement of the Editorial Team
* [[EditorialHTML|Editorial HTML]] - HTML useful in Story Editing
<section end=documentation />

==Dependencies==
*Main Website (slash)
**[[EditorPrivileges|editor privileges]]

[[Category:Teams]]
[[Category:Editorial team]]

Editors

2018-03-09T00:21:37Z

Chromas: /* Who we are */ update tz

The editorial team is responsible for checking and revising (if required) user submitted stories. Prospective editors should be prepared to devote a significant amount of time to checking stories, have a good grasp of the English language, and be familiar with slash's formatting options. Contact: '''editors@soylentnews.org''', or join #editorial in [[SoylentNews:IRC |irc]].

==Who we are==
<section begin=whoweare />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| janrinok
| editor
| UTC+1 (CET)
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| n1
| editor
| UTC
|-
| martyb
| editor
| UTC-4 (EST/EDT)
|-
| CoolHand
| editor
| UTC-4 (EST/EDT)
|-
| NotSanguine
| editor
| UTC-4 (EST/EDT)
|-
| Cmn32480
| editor
| UTC-4 (EST/EDT)
|-
| takyon
| editor
| ?
|-
| charon
| editor
| UTC-4 (EST/EDT)
|-
| Fnord666
| editor
| UTC-4 (EST/EDT)
|-
| Snow
| editor
| ?
|-
| mrpg
| editor
| ?
|-
| chromas
| editor
| UTC-7 (PST)
|-
| fyngyrz
| editor
| ?
|-
| GreatOutdoors
| editor
| ?
|-
| Xyem
| editor
| GMT
|}
<section end=whoweare />

==Retired Members==
Former editors that have lost their roles due to inactivity or retirement
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Retired members]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Subsentient
| editor
| UTC-7 (MST)
|-
| LaminatorX
| Team Leader
| UTC-5 (CST/CDT)
|-
| Dopefish
| editor
| UTC-8 (PST)
|-
| mattie_p
| editor
| UTC-7 (MST)
|-
| zizban
| editor
| UTC-4 (EST/EDT)
|-
| Azrael
| editor
| ?
|-
| Woods
| editor
| UTC-5 (CST/CDT)
|-
|}

==Projects==

*Continue to develop editorial process (see Documentation below)
*Maintain static pages (FAQ.shtml, about.shtml, and moderation.shtml)

==Documentation==
<section begin=documentation />
*A [[Story_Style|Story Style]] document outlines editorial guidelines, it may need additional refining and ratification eventually.
* [[Editing_Process|The Editing Process]] - builds on the Story Style and Submission Guidelines to describe <b>how</b> the editing process is carried out.
* [[Submission_guidelines|Submission Guidelines]] - Notes to all users regarding the formatting of submissions and relevant rules.
* [[Editorial_Policy|Editorial Policy]] - Policy Statement of the Editorial Team
* [[EditorialHTML|Editorial HTML]] - HTML useful in Story Editing
<section end=documentation />

==Dependencies==
*Main Website (slash)
**[[EditorPrivileges|editor privileges]]

[[Category:Teams]]
[[Category:Editorial team]]

Story Style

2018-02-24T09:32:34Z

Chromas: /* Serial Comma */ Splelign erros

Note: Whereas some languages, like French and German, have standardized forms governed by regulatory bodies, English is in many ways a free-for-all. Let this be a collection of information on which we english-speakers (typers?) agree.

Parent: [[Editors|Editors Team]]

=What is a Manual of Style=

This document is intended to form a manual of style that dictates the way stories are written, mainly in matters of format, punctuation, and grammar. The Manual of soylent Style will hopefully create a uniform presentation that is in line with journalistic practices, while leaving many matters open to the personal preferences of editors and submitters.

=Why a Manual of Style?=

As we develop our own unique process, this will inform on common editor practices, and help guide new editors to the conventions that have been established thus far.

=Story Structure=

Stories begin with:<br>
*"[$submitter] writes:"<br>
*or "[$submitter] informs us of [a link]" (when the submission contains little or no summary)<br>
The colon and structure signifies the following text is the summary, and quotes are '''not''' necessary surrounding the entire text. [$submitter] should be a link to their site profile if available. The next component should be a summary of the article with in-line links, and any direct quotes from the article(s) using quotation marks normally. HTML formatting should use <nowiki><p> and </p> tags. Block-quoting is done with the <blockquote> and </blockquote></nowiki> tags.<br>
<br>Example:

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
<nowiki>
<p><a href="http://soylentnews.org/~soylent+bob/">Soylent Bob</a> writes:</p>

<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur massa elit, pharetra sed lacus vitae, vehicula porta elit. Nulla ac porta nibh. "Quisque adipiscing sem 'nisi', sit amet pulvinar velit vestibulum in", says Soylent Mel. Morbi luctus aliquet erat quis tempor. Nulla facilisi:</p>

<blockquote>Morbi leo purus, fermentum non felis vitae, mattis tempus mauris. Nunc bibendum neque non dolor pharetra, quis dignissim tortor semper. Phasellus sed nisl sit amet elit rutrum interdum. Ut rutrum pellentesque tempus.</blockquote>

<p>Integer id nisl vel ante sodales consectetur nec nec tortor. Suspendisse a congue est. Donec ut consectetur mauris. Duis hendrerit nibh nec quam consequat dapibus. Aenean luctus iaculis magna, aliquet aliquam nisi consectetur eget.</p>

<p>[ED's note: the quick brown fox jumps over the lazy dog.]</p>
</nowiki>
</pre>

=US/UK Spelling=

The site is endeavouring not to be a US-centric site, and by doing so wishes to encourage members, casual-readers and interest from english-speakers around the world. As the dialects of English differ between the US and many other English speaking regions, it is essential that the site remains inclusive to all but provides clearly written stories that are easily understandable. Each submission contains 2 essentially different elements at the most basic level: the linked source material and the summary (TFS).

== Linked Material ==

The linked material (the information source) must be in English but can be in '''any''' English dialect. It is reported exactly as printed to remove the possibility of an editor changing the meaning accidentally. Having two or more linked sources in different English dialects is acceptable.

== Summary ==

The summary can be written in any commonly-used English dialect but must be consistent throughout. Other than quoted material (which is always quoted exactly as written) only one dialect can be used throughout the summary. Mixing US and UK spelling, for example, in a single summary is unacceptable. It does not have to be written in the same dialect as the source material - indeed, if there are 2 different sources it might be impossible to do so.

=Headline Capitalization=

# Except for function words, all words are regularly capitalized in headlines, e.g. "'Moon Made of Soylent Green Cheese', Says NASA."
# Function words are:
## Prepositions, e.g. in, at, and on.
## Conjunctions, e.g. and, if, and but.
## Articles, i.e. the, an, and a.
## Pronouns, e.g. who, you, they, who, and which. The single exception is of course the pronoun I, which is always capitalized.
## The copula ("the verb <i>to be</i>"), e.g. is, am, and are.
# But when headline-initial, even function words are capitalized, 'Is Soylent Green Made of People?" (cf. [[Story_Style#Betteridge.27s_Law_of_Headlines]]).

=Serial Comma=
In a series of three or more items, place a comma between the second-to-last item and the conjunction that follows, e.g. "Soylent Green, Soylent Purple, and Soylent Yellow" instead of "Soylent Green, Soylent Purple and Soylent Yellow".

This is commonly referred to as the Harvard or Oxford Comma, and it reduces ambiguity. Its usefulness is often illustrated with the (non-Oxford-Comma-conforming) phrase "To my parents, Ayn Rand and God," as this sentence reads that the parents in question are actually "Ayn Rand and God". [http://en.wikipedia.org/wiki/Serial_comma#Ambiguity (wikipedia reference)].

=Dashes=

=Betteridge's Law of Headlines=
Betteridge's Law explains: Any headline that ends in a question mark can be answered with one word -- <i>no</i>. The use of such questions in headlines is a journalistic device that is used when the story has little proof, no basis at all, or describes events that did not actually occur at the time of writing, i.e. not news. This should be avoided whenever possible. Note: this axiom naturally applies only to yes/no questions rather than wh-prefixed questions.

=Possessive S=
# The possessive form of singular nouns is marked with 's, except for some archaic proper nouns that end in -es or -is, e.g. Moses' law (http://www.bartleby.com/141/strunk.html#1).
# The possessive form of plural nouns ending in "s" does <i>not</i> require an additional "s", e.g. pirates'.

=Apostrophes=
# Apostrophes are used in the possessive form of nouns, e.g. soylent's (singular) and news' (plural).
# Apostrophes are not used to form the plural ending of nouns, e.g. the plural form of apple is apples, and its possessive form is apples'. Apple's is the possessive form of the singular apple, while apples' is the possessive form of the plural apples.
# Apostrophes are likewise not used with decades, when written in numbers, e.g. 1980s rather than 1980's.
# The form <i>it's</i> is a contraction of <i>it is</i>. The word <i>its</i>, on the other hand, is the possessive form of the pronoun <i>it</i>. This can be easily remembered by comparing the other third person pronouns: <i>he's</i> has an apostrophe because it is a contraction of <i>he</i> and <i>is</i>, whereas <i>his</i> never has one. The same also applies to <i>hers</i> and <i>she's</i>.

=Hyper-Prescriptivism: Split Infinitives and Stranded Prepositions=
# The use of adverbs between the word <i>to</i> and its following infinitive is allowed, e.g. <i>to boldly go</i> is just as acceptable as <i>boldly, to go</i> and <i>to go boldly</i>.

=Weasel Words=
Weasel words include a variety of terms that can mislead and and deceive readers. Examples include use of: non sequitur statements, [http://en.wikipedia.org/wiki/Passive_voice passive voice], vague expressions (e.g. "some people think," and "experts agree"), and adverbs that weaken a statement through ambiguity (e.g. "probably").

=Source Needed=

=Titles of Works=
# The titles of books, films, albums, etc. are rendered in italics rather than quotation marks, e.g. <i>Planet of the Apes</i> instead of "Planet of the Apes".
# The names of websites and products receive no such marking, e.g. "CNN reports that Charlton Heston has discovered the secret ingredient in Soylent Green." Contrast this to the following sentence, in which Soylent Green is the film rather than the product: "CNN reports that Charlton Heston has discovered the secret ingredient in <i>Soylent Green</i>."

=Quotations=
Punctuation marks appear before closing quotation marks. Example:
: "Moon is Made of Soylent Green Cheese," says NASA.
Instead of:
: "Moon is Made of Soylent Green Cheese", says NASA.
<br>
Punctuation should follow the format of presented material, even if it differs from source material. Example:
: "Moon is Made of Soylent Green Cheese," says NASA.
Source material:
: "Moon is Made of Soylent Green Cheese."

=Editor's Notes=
Editor's notes should be used sparingly. They should never be used to add the editor's opinion, that can be done as a comment on the story. One accepted case would be in notifying readers that a story was updated or changed, or informing the readers of important information ex: [Editor's Note: The live-stream appears to be inaccessible at this time.]

Editor's notes can also be used to link to previous stories on the subject or related subjects, where adding the links to the story would be obtrusive or change the submission drastically.

[[Category:Editorial team]]

IRC:MrPlow

2017-03-02T23:53:35Z

Chromas: Created page with "MrPlow is TheMightyBuzzard's IRC bot, currently written in [https://www.rust-lang.org/en-US/ Rust]. The sauce is [https://github.com/TheMightyBuzzard..."

MrPlow is [[User:TheMightyBuzzard|TheMightyBuzzard]]'s IRC bot, currently written in [https://www.rust-lang.org/en-US/ Rust]. The sauce is [https://github.com/TheMightyBuzzard/RustBot on GitHub].

=fite=
The '''#fite''' command instigates a fite between you and another user. It's currently restricted to the channel #fite to reduce mental abuse of anyone who doesn't give continuous affirmative consent.

Commands:
{| class="wikitable"
|#fite ''$nick''|| Start a fite with someone.
|-
|#fitectl status||Show your character 'sheet'.
|-
|#fitectl weapon ''$string''||Set your weapon.
|-
|#fitectl armor ''$string''||Set your armor.
|}

=sammich=
You can order an internet sammich with the '''#sammich''' command. Note this only works if you sexually identify as a male. It otherwise redirects you to the kitchen.
#sammich ''$nick''

=socialist=
Use '''#socialist''' if you want to start an in-depth libertarian debate.
#socialist ''$nick''

IRC

2017-03-02T22:55:12Z

Chromas: /* Bots */ Updated MrPlow and monopoly; removed superfluous linebreaks.

Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC, and the [[IRCVision|IRC vision]] is worth checking out.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:juggs|juggs]] (AKA Deucalion)
| Team leader
| UTC+1 (BST)
|-
| [[User:paulej72|paulej72]]
| Member
| UTC-4 (EDT)
|-
|}
<section end=whoarewe />

==Retired Members==
Former members of the IRC team that have lost their roles due to inactivity or retirement
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|Former members]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:xlefay|xlefay]]
| Co-team leader
| UTC+2 (CEST)
|-
| [[User:FunPika|FunPika]]
| Member
| UTC-4 (EDT)
|-
| [[User:Landon|Landon]]
| Member
| ?
|-
|}

[[IRC links]]

==Current Projects==

===Chat bot (Python)===
* ELIZA module that uses Futurama personalities (to match the bot's current nick)
* Modify bot logging to match existing formats (mIRC preferably)

===Services (C)===
* Single sign on against the website (coordinate with NCommander)
* Get the web IRC to use the website's sessions to sign in

===Documentation===
* Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)

===Misc bots===
* Anyone wanting to join existing bot development projects should contact the developer(s) noted below.

===IRC Games===
* NerdRPG

[[Category:Teams]]
[[Category:IRC]]

==Channels==

===Official channels===

* Unless otherwise noted, channels are NOT considered "safe for work"

{| class="wikitable" style="width:100%;"
|-
! Channel !! Description !! Maintained by
|-
| #soylent || General chat/lobby || All SoylentNews Staff
|-
| #staff || Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel || All SoylentNews Staff.
|-
| #editorial || The home of the SoylentNews editors, here you can volunteer for duty, report typo's & ask for submission tips and the like. || Editors & IRC Staff.
|-
| #dev || The home of and for developers that help develop our fork of SlashCode. || Development team & IRC staff.
|-
| #help || This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. || IRC Staff.
|-
| #sysops || This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. || Sysops & IRC Staff.
|-
| #wiki || This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! || IRC Staff.
|-
| #irpg || This is our "nerdRPG"'s (our fork of idleRPG) channel, feel free to idle along! || IRC Staff.
|-
| #test || Main testing chambers, feel free to test anything in here (just be friendly & be considerate) || IRC Staff.
|}

===Private establishments (unofficial)===

{| class="wikitable" style="width:100%;"
|-
! Channel !! NSFW !! Description !! Maintained by
|-
| ## || yes || mostly about bacon and stuff || [[User:crutchy|crutchy]]
|-
| # || yes || the batcave; bot testing/borking, random chaos, exec's home || [[User:Alberto|Alberto]]
|-
| #derp || || aqu4bot's origin and the portal to Universe 2. Bring own peanut butter. || [[User:Subsentient|Subsentient]]
|-
| #sublight || || Sublight's bot home ground || [[User:xlefay|xlefay]]
|-
| #rss-bot || no || various rss/atom feeds || [[User:juggs|juggs]]
|-
| #debug || no || bot error spew || [[User:chromas|chromas]]
|-
| #comments || yes || soylentnews.org comments feed || [[User:crutchy|crutchy]]
|-
| #github || no || ~github-list repos push feed - checked every 5 mins || [[User:crutchy|crutchy]]
|}

* NSFW = not safe for work / kids /family (contains adult themes and profanity)

==Bots==
There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.<br />
Anyone wishing to develop bots should use #test or # for testing.<br />
Please avoid flooding in private establishments and official channels (except #test and #). The #debug channel is used by bots for public error reporting (if dumping errors to #debug, bots should ideally be set to not respond to commands in that channel to prevent race/infinite loop conditions).

{| class="wikitable" width="100%"
|-
! nick !! channels !! triggers !! devs/ops/hosts !! source !! tasks !! usage/notes
|-
| [[Aqu4bot|aqu4]] ||
* #
* ##
* #Soylent
* #derp
* #test
||
* $
* aqu4:
||
* [[User:Subsentient|Subsentient]] (dev/op)
|| http://github.com/Subsentient/aqu4bot ||
* Memos ($sticky)
* Messaging ($tell)
* Logging/user tracking
* Channel control (in #derp)
||
* $sr
* $seen
* $tell
* $help
* $burrito
|-
| [[IRC:Bender|Bender]] ||
* #Soylent
* ##
* #
||
* <nowiki>!</nowiki>
||
* [[User:paulej72|paulej72]] (op)
|| ||
* karma
* todo
||
* coffee++
* <nowiki>!</nowiki>whoup
* <nowiki>!</nowiki>todo stuff
* <nowiki>!</nowiki>uid
|-
| [[IRC:ciri|ciri]] ||
* #
|| ||
* [[User:arti|arti]]
|| ||
* Entertainment
||
* <nowiki>!</nowiki>decide yes "other stuff"
* 8ball (your question)
* <nowiki>.</nowiki>country (2 digit code) - country lookup.
* <nowiki>.</nowiki>bin2dec <binary value>
* <nowiki>.</nowiki>binary2decimal <binary value>
* <nowiki>.</nowiki>decimal <binary value>
* <nowiki>.</nowiki>dec2bin <decimal value>
* <nowiki>.</nowiki>decimal2binary <decimal value>
* <nowiki>.</nowiki>binary <decimal value>
* <nowiki>.</nowiki>calc <Equation> - Calculates a mathmatical equation.
* <nowiki>.</nowiki>f2c <Fahrenheit> - Fahrenheit => Celsius.
* <nowiki>.</nowiki>c2f <Celsius> - Celsius => Fahrenheit.
* <nowiki>.</nowiki>ft2m <Feet> - Feet => Meters.
* <nowiki>.</nowiki>m2ft <Meters> - Meters => Feet.
* <nowiki>.</nowiki>mi2km <Miles> - Miles => Kilometers.
* <nowiki>.</nowiki>km2mi <Kilometers> - Kilometers => Miles.
* <nowiki>.</nowiki>lb2kgl <Pounds> - Pounds => Kilograms.
* <nowiki>.</nowiki>kg2lb <Kilograms> - Kilograms => Pounds.
* <nowiki>!</nowiki>word - word scramble game.
* <nowiki>!</nowiki>idle - see who is idle.
* <nowiki>!</nowiki>g (term) - google something.
* <nowiki>!</nowiki>google (.countrycode) (term) - google something.
* <nowiki>!</nowiki>google [.google.country.code] [define:|spell:]
* <search terms> <1+1> <1 cm in ft> <patent ##>
* <weather city|zip> <??? airport>
* <nowiki>!</nowiki>images [.google.country.code] <search terms>
* <nowiki>!</nowiki>groups [.google.country.code] <search terms>
* <nowiki>!</nowiki>news [.google.country.code] <search terms>
* <nowiki>!</nowiki>local [.google.country.code] <what> near <where>
* <nowiki>!</nowiki>book [.google.country.code] <search terms>
* <nowiki>!</nowiki>video [.google.country.code] <search terms>
* <nowiki>!</nowiki>fight <word(s) one> vs <word(s) two>
* <nowiki>!</nowiki>trans region@region <text>
* <nowiki>!</nowiki>gamespot <search terms>
* <nowiki>!</nowiki>gamefaqs <system> in <region>
* <nowiki>!</nowiki>blog [.google.country.code] <search terms>
* <nowiki>!</nowiki>ebay [.ebay.country.code] <search terms>
* <nowiki>!</nowiki>ebayfight <word(s) one> vs <word(s) two>
* <nowiki>!</nowiki>wikipedia [.2-digit-country-code] <search terms>[#subtag]
* <nowiki>!</nowiki>wikimedia [.www.wikisite.org[/wiki]] <search terms>[#subtag]
* <nowiki>!</nowiki>locate <ip or hostmask>
* <nowiki>!</nowiki>review <gamename> [@ <system>]
* <nowiki>!</nowiki>torrent <search terms>
* <nowiki>!</nowiki>best <system>
* <nowiki>!</nowiki>worst <system>
* <nowiki>!</nowiki>rgb2hex (r:XXX g:XXX b:XXX) - converts rgb value to hex.
* <nowiki>!</nowiki>hex2rgb (XXXXXX) - converts hex color value to rgb.
* <nowiki>!</nowiki>roll (1dX) - rolls a X sided die (1d4, 2d6).
* <nowiki>!</nowiki>disc - discworld quotes
* <nowiki>!</nowiki>dict (word) - dictionary, word lookup via princeton.edu.
* <nowiki>!</nowiki>dailymotion <search terms>
* <nowiki>!</nowiki>ign <search terms>
* <nowiki>!</nowiki>myspace <search terms>
* <nowiki>!</nowiki>trends [.google.country.code] <YYYY-MM-DD>
* <nowiki>!</nowiki>dawn - random dawn of war quote.
* <nowiki>!</nowiki>bofh - random BOfH quote.
* <nowiki>!</nowiki>duke - random duke nukem quote.
* <nowiki>!</nowiki>coffee - order coffee for you or someone.
* <nowiki>!</nowiki>coke - order coffee for you or someone.
* <nowiki>!</nowiki>icecream - shows menu.
* <nowiki>!</nowiki>order (nick) (something) - shows menu.
* <nowiki>!</nowiki>pizza - shows menu.
|-
| [[IRC:exec|exec]] ||
* #
* #comments
* #debug
* #github
||
* ~
||
* [[User:cmn32480|cmn32480]] (op)
* [[User:Crutchy|crutchy]] (admin/dev)
* [[User:chromas|chromas]] (admin)
|| http://sylnt.us/execsrc || ||
* SN comments feed (in #comments)
* GitHub events feed (in #github)
* refer to [[IRC:exec#Quick_start|quick start guide]]
|-
| [[IRC:Loggie|Loggie]] ||
* #Soylent
|| ||
* [[User:xlefay|xlefay]]
|| ||
* logging to logs.sylnt.us
||
* /invite Loggie
|-
| [[IRC:monopoly|systemd]] ||
* #
* #Soylent
||
* =
||
* [[User:chromas|chromas]] (dev/op)
|| ||
* Nothing. It's dead inside.
||
|-
| [[IRC:NerdRPG|NerdRPG]] ||
* #irpg
|| || || ||
* outputs game data
||
|-
| [[IRC:MrPlow|MrPlow]] ||
* #Soylent
* #fite
* #test
||
* #
||
* [[User:TheMightyBuzzard|The Mighty Buzzard]] (dev/op)
|| ||
* Translate to Klingon
* Get help with commands
* Get local weather
* Set #weather location
* Get time/date/channel/message of the last time someone spoke
* Have a libertarian debate
* Instigate fites between users
||
* #bnk
* #fite
* #g
* #help
* #join
* #klingon
* #part
* #roll
* #sammich
* #sammichadd
* #seen
* #smake
* #smakeadd
* #socialist
* #submit
* #tell
* #weather
* #weatheradd
* #youtube
|-
| [[IRC:PlowKing|PlowKing]] || || ||
* [[User:TheMightyBuzzard|The Mighty Buzzard]] (dev/op)
|| || ||
|-
| [[IRC:Regurgitator|Regurgitator]] ||
* #rss-bot
* #soylent
||
* !rss
||
* [[User:juggs|juggs]] (op)
||
Eggdrop v1.8.0+fixbotnetloop http://www.egghelp.org/files.htm <br />
rss-synd v0.6 plugin https://github.com/eggtcl/rss-synd
||
* various rss / atom feeds
* logging only in #soylent for pisg stats
||
* #rss-bot !rss to see all feeds. !<feed> to see individual feed contents. Idle in channel to see all feeds.
* #soylent see pisg output here: http://stats.sylnt.us/pisg/index.html
|-
| [[SedBot]] || || ||
* [[User:FoobarBazbot|FoobarBazbot]] (dev/op)
|| https://github.com/FoobarBazbot/sedbot ||
* message correction
||
* s/old/new/
* nick: s/old/new/
|-
| [[IRC:tama|tama]] ||
* #
|| ||
* [[User:arti|arti]] (op)
|| || ||
|-
| [[WikiRC|WikiRC]] ||
* #wiki
|| ||
* [[User:FunPika|FunPika]]
|| ||
* wiki events feed
||
|-
| [[IRC:exec|x]] ||
* #debug
* #crutchy
||
* ~
||
* [[User:Crutchy|crutchy]] (op/dev)
* [[User:chromas|chromas]] (admin)
|| http://sylnt.us/execsrc || ||
* exec development
|}

===Bot projects / task ideas===

* [[IRCiv]] is currently under development for the exec bot and is intended to be a civilization-like building game played on IRC.
* a Soylent PBC board meeting assistant script is currently under development for the exec bot, intended for minute taking and publishing on the wiki. See [[IRC:exec#Meeting_assistant]] for more details.
* an IRC voting system. refer to [[IRC:exec#Proposed_IRC_voting_system]] for details.
* returning data from the SoylentNews using the [[ApiDocs|SlashCode API]]
* [[IRC:exec suggestions]]

[[Category:IRC]]

URLShortener

2015-11-17T01:48:38Z

Chromas: Updated with pointer to existing shortener.

SoylentNews has a [http://sylnt.us/ URL shortener] which shortens links to these domains:
*soylentnews.com
*soylentnews.org
*soylentnews.net
*altslashdot.org
*altslashdot.com
*altslashdot.net
*slashdot.org
*github.com

IRC

2015-03-03T22:53:27Z

Chromas: /* Bots */

Template:Spam

2014-11-25T07:07:35Z

Chromas: Created page with "<div style="border:1px solid red;"> This page is a candidate for '''spammy deletion''' because it's spam. </div> <noinclude> Any pages this template is placed onto will be add..."

<div style="border:1px solid red;">
This page is a candidate for '''spammy deletion''' because it's spam.
</div>
<noinclude>
Any pages this template is placed onto will be added to [[:Category:Candidates for spammy deletion]].
</noinclude>
<includeonly>
[[Category:Candidates for spammy deletion]]
</includeonly>

Talk:SoylentNews

2014-09-18T12:26:35Z

Chromas: Undo SPAM by LisabethBitters (talk)

"You have followed a link to a page that does not exist yet. To create the page, start typing in the box below"

Okay, let's see if that works.

And help kill beta by joining the Slashcott

February 10th -17th

unitron

Slashdot UID 5733

== Teething pains? ==

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

John@AltSlashdot.org
SMTP error from remote mail server after RCPT TO:<John@AltSlashdot.org>:
host mail.altslashdot.org [66.147.244.192]: 550 No Such User Here

...

Is this an "only if Slashdot doesn't back down on beta" contingency, or =
"going to happen no matter what Slashdot does"?

...

== Hot Grits ==

I have poured them down my pants. Thank you. [[Special:Contributions/86.50.93.164|86.50.93.164]] 10:16, 6 February 2014 (MST) Iskender (1040286)

*Why are they down your pants? They should be on Natalie Portman - naked and petrified..

== Group or Business ==

Okian Warrior seems to want to be CmdrTaco all over again. While I am a very, very pro-business sort of person, I don't think we want to just push reset and do Slashdot over again as another build it up and cash out endeavor. It seems like that's exactly what would happen, and on the backs of volunteers no less. The only way I could see supporting this endeavor as a business would be with some sort of codified protection like a charter, whereby certain attributes of the way the site functions would be guaranteed, and those guarantees could only be changed if (the charter could only be modified if) the users were polled and agreed to it. In this way the business could operate but be ultimately accountable to and restrained by the userbase. This seems like a good hybrid solution. ~ElectricTurtle

You could solve this by managing it similar to the debian project.

^ Agree with both sentiments. I'm a bit skeptical of Okian Warrior's business mindset... we need this to resemble a non-profit FOSS project. Can that really be so hard to do (in the beginning, especially, and also with all the cloud services now available to avoid slashdotting?). Some will balk at the Debian-like structure as too codified and rigid, but let's at least discuss this as a FOSS project first, and *maybe* some ad revenue down the line to support it. Although, donations/crowdfunding seems better to me. ~ [[User:Seandiggity|Seandiggity]] ([[User talk:Seandiggity|talk]]) 08:52, 7 February 2014 (MST)

I agree that we shouldn't trade corporate overlord for a new master with the prospect of becoming a corporate overlord. I am not opposed to the project manager making money off the site though. Instead of an exit strategy how about a transitional strategy wherein the founder makes a fixed amount of money and/or profits for a fixed time? Eg $100k or 5yrs, whichever comes first.

As far as monetization, premium accounts with little or no ads is easy. Couple this with paid postings to receive a higher start moderation eg. 5¢ for 0,nuetral if you don't have an account. It shouldn't be hard to get the money to buy the site from the founder. Especially if coupled with annual wikipedia donation drives to cover the site overhead.

:Non-profit or volunteer org is a good approach. If it's owned by a business or corporation, I will not use it. [[User:Mfnickster|Mfnickster]] ([[User talk:Mfnickster|talk]])

==Stories==
*Could there be [[Open Hardware FPGAs]]? http://www.electronicsweekly.com/mannerisms/fpga/will-expiring-patents-boost-fp-2007-03/

== Barrapunto ==

People here should be familiar with the Spanish language version of Slashdot,
Barrapunto.com. It looks like it was forked from older Slashcode, and it does
not appear to be a dice holding. This is the most durable SlashClone with which
I'm familiar. I seem to recall reading about it more than 5 years ago. If nothing
else, we could learn a lot from them about running a successful SlashClone.

We should make a list of any currently running clones.
*http://slashcode.com/www.slashcode.com/

Thanks for posting the link. That looks a lot more like /. Classic. Now we certainly
don't want to knock over the server that discusses SlashCode, so we shouldn't be
posting there... but they seem like an ideal candidate for a bunch to form a non-profit
org. IMHO, that's the answer. We need to form a non-profit dedicated to serving the
users. Worst case scenario we replace ads with something like the annual Wikipedia
begging; but it might be worth it.

The Wikipedia begging beats having advertizes dictating the content of your site or selling the users info for $$$ Wikipedia I believe does it right. [[User:Script Cat|Script Cat]] ([[User talk:Script Cat|talk]]) 14:28, 6 February 2014 (MST)
<br>(The advertising on barrapunto.com looks fine and unobtrusive to me. My 2 cents, but no, I don't know much about advertising paying the bills, sadly.)(Gaaark)
== Alternate domain ideas? ==

It's come up elsewhere online that a name including slashdot might get this project into hot water with DICE

== Hosting and collaboration ==
make it foss with gpl2<br>
is there any reason why the site can't be directly hosted by https://github.com/<br>
ultra-nerdy, with plenty of linuxy flavor<br>
no need to worry about dedicated infrastructure, and domain doesn't matter that much if it's something like "github.com/altslash" nerds are gunna find and remember it
: I don't trust Github. I don't think they really care about their community any more than Dice cares about Slashdot's. [[User:Mfnickster|Mfnickster]] ([[User talk:Mfnickster|talk]])
:: I don't think that's a problem, since every repository clone is essentially a full backup, so if they pull something sinister, we can simply stop using them. [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 06:31, 10 February 2014 (MST)
::: Like we "simply stopped using" Slashdot? :) [[User:Mfnickster|Mfnickster]] ([[User talk:Mfnickster|talk]])
:::: There are some similarities, yes. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 07:27, 10 February 2014 (MST)
::::: Yeah, that's the beauty of git, you can move elsewhere in minutes. But at least having the updated Slash code on github is a good advertisement as well, and would allow lurkers (like me!) who are not directly involved with the new codebase clone the repo and try it out. ~ [[User:Seandiggity|Seandiggity]] ([[User talk:Seandiggity|talk]]) 08:05, 10 February 2014 (MST)

== Journals ==
I hope journals are included and hope people use them.

: and wiki home pages too (good for introducing yourself). [[User:Crutchy|here's mine]] if anyone is curious. it also has links to my soylent journal entries. ~ crutchy

== AGPL licensing ==
If no one's said it yet, I think we need to move the updated version of SlashCode to AGPL and get it in a git repo for people to hack on (preferably github). I'm happy to put it up there under that license but I don't want to see (yet another) fork. Any objections to that license? It's recommended by the FSF for any Web software, or really any that runs primarily over a network. In my view, it will protect us from seeing the fruit of our labors be turned into another locked up DiceDot... how nice would it have been to have at least the updated "Slashdot Classic" interface available now to hack on instead of the circa 2009 version? The AGPL would have made that possible. ~ [[User:Seandiggity|Seandiggity]] ([[User talk:Seandiggity|talk]]) 09:22, 7 February 2014 (MST)
: Can you just re-license someone else's code? How is that legally possible? Also, it might make sense to fork it anyway just to have control over the code base. It could also be ported to another language (don't say .NET or PHP please!). [[User:Mfnickster|Mfnickster]] ([[User talk:Mfnickster|talk]])

:: You can license a modified version of a program under a compatible license, depending upon the terms that the original authors released the source. Many forks end up under a different license through some new mix of code. If the original Slash is licensed "GPL v2.0 or any later version" there's a clear path to GPLv3 and then AGPL. If not, the authors must be the ones to do it, and we might think about asking them (all of whom left Slashdot a while ago AFAIK) rather than stay on GPLv2 forever. Whatever the case, we should be thinking about licensing, esp. because direct competition between this and /. is bound to raise Dice's ire. ~ [[User:Seandiggity|Seandiggity]] ([[User talk:Seandiggity|talk]]) 20:43, 9 February 2014 (MST)

::: FYI, take a look at my [[SoylentNews#Licensing.3F|better-written frontpage post]]... we also should be thinking about things like CLAs and discussing them. Joining the Slashcott now... ~ [[User:Seandiggity|Seandiggity]] ([[User talk:Seandiggity|talk]]) 21:14, 9 February 2014 (MST)

== Slashcott, Week 2 ==

Did I mention that I've officially extended the Slashcott?

Week 2 runs from February 17th, 2014, to February 23rd, 2014.

And of course what Dice will probably never understand is that it really is a Valentine to Slashdot

-unitron

== Some features ==
How about Unicode support, a basic feature Dice never got around to implement? Or HTTPS to everyone. Possibly a Twitter feed to tell about new stories, like /. has. Just throwing some ideas around. :) [[Special:Contributions/80.223.182.224|80.223.182.224]] 07:42, 16 February 2014 (MST)

== newsbot ==
Maybe develop some kind of distributed bot for scraping the web for tech news (including inconspicuous stories lurking on the web in hard to reach places).

IRC:exec

2014-05-02T05:30:13Z

Chromas: /* Weather script */

'''IRC Script Executive'''

"'''exec'''" is a script that runs in a CLI that connects to the Soylent [[SoylentNews:IRC|IRC server]] (irc.sylnt.us:6667) and executes other programs for output to an IRC channel.

Input to a script/program is via command line arguments only (stdin is not supported).

stdout of an executed script/program may be passed to an IRC channel or output to exec's stdout (terminal), depending on the value of ''auto-privmsg'' in the exec line. If ''auto-privmsg=0'', stdout from the script/program must begin with "privmsg " for it to be sent to the IRC channel.

Programs executed may be anything accessible from the CLI of the machine running the exec script. They may be shell programs (such as ''cowsay'' and ''fortune''), php scripts (executed using the CLI ''php'' command) or scripts in any other language executable by their respective CLI interpreters (python, perl, etc).

==Bot development==

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test

Files:
*https://github.com/crutchy-/test/blob/master/irc.php
*https://github.com/crutchy-/test/blob/master/exec

Download above files from [https://github.com/crutchy-/test/blob/master/ github], open a terminal and change to that directory, and run "php irc.php".

Scripts may be stored anywhere that is accessible to the bot script for CLI execution. If stored in a different location, the script path must be included in the exec file line.

===Buckets===

"Buckets" are a feature of exec that allow scripts to store data in a common location which is accessible from any script and is retained/persistent between script executions. Each bucket consists of an array element in the main bot program that is read, written and cleared using IRC-like commands (see below) passed through stdout/stdin pipes from/to executed scripts - buckets are filled by pipes hahaha :-P

Currently having difficulty reading large amounts of data and use of gzcompress is hampered by control characters, but you can store complex data in array form by using php's serialize/unserialize (or equivalent in other languages).

Buckets are referenced by an index string, which is encoded/decoded by the bot.
<pre>
:exec BUCKET_GET :index
:exec BUCKET_SET :index data
:exec BUCKET_UNSET :index
</pre>

Tested PHP functions for reading/writing bucket data can be found here: https://github.com/crutchy-/test/blob/master/scripts/irciv_lib.php

==Exec file==

===Example exec file===
<source lang="dot">
# alias|timeout(sec)|auto-privmsg(1|0)|empty-trailing-allowed(1|0)|cmd
# available templates: %%trailing%%, %%dest%%, %%nick%%, %%start%%, %%alias%%, %%cmd%%, %%data%%, %%exec%%, %%params%%
# %%trailing%% excludes alias

# EXEC ON ALL LINES (ONLY ONE EXEC LINE ALLOWED SO ADD TO COMMAND USING &&
*|5|0|0|php scripts/grab.php %%trailing%% %%nick%% && php scripts/cmd.php %%cmd%% %%trailing%% %%data%% %%dest%% %%params%% %%nick%%

~|5|1|1|php scripts/about.php
cowsay|5|1|0|cowsay %%trailing%%
snake|5|1|1|echo %%trailing%% | cowsay -f elephant-in-snake
test|5|0|0|php scripts/test.php %%trailing%% %%dest%% %%nick%%
ps|5|1|1|ps fl
moo|10|1|1|apt-get moo
fortune|5|1|1|fortune -s
cowsay-fortune|5|1|1|sh cowsay-fortune.sh
define|10|0|0|php scripts/definitions.php %%trailing%%
php|5|0|0|php scripts/php.php %%trailing%%
smile|5|1|0|php scripts/smile.php %%trailing%%
uptime|5|1|1|uptime
rofl|5|1|1|fortune -s
exec-up|5|0|1|php scripts/up.php %%start%%
bsod|10|1|1|php scripts/bsod.php
~join|5|0|0|php scripts/join.php %%trailing%%
~part|5|0|1|php scripts/part.php %%dest%% %%trailing%%
~recurse|5|0|1|php scripts/recurse.php
~bucket|5|0|1|php scripts/buckets.php

weather|10|0|1|php scripts/weather.php %%alias%% %%trailing%%
weather-add|10|0|1|php scripts/weather.php %%alias%% %%trailing%%

civ|5|0|1|php scripts/irciv.php %%nick%% %%trailing%% %%dest%%

# non-php scripts
haskell|5|1|1|runhaskell scripts/haskell.hs
perl|5|1|1|perl scripts/perl.pl
</source>

===Available exec templates===

TODO: describe these in more detail

*%%trailing%%
*%%dest%%
*%%nick%%
*%%start%% # microtime(True) result when bot was started
*%%alias%%
*%%cmd%%
*%%data%%
*%%exec%%
*%%params%%

<source lang="dot">:<prefix> <command> <params> :<trailing></source>

==Script development==

===Example script===
<source lang="php">
<?php
# test|5|0|0|php scripts/test.php %%trailing%% %%dest%% %%nick%%
echo "when auto-privmsg=0 this shows on terminal (stdout) only\n";
echo "privmsg msg=".$argv[1]."\n";
echo "privmsg chan=".$argv[2]."\n";
echo "privmsg nick=".$argv[3]."\n";
?>
</source>

If anyone is interested in adding their own script, do a github fork/pull and/or let crutchy know (crutchy usually hangs out in #soylent and #test).

==Usage in IRC==

To invoke a script in IRC client:
<source lang="dot">alias [msg]</source>
Example:
<source lang="dot">
<crutchy> define atlantic ocean
<exec> 1 | noun | the 2nd largest ocean; separates North and South America on the west from Europe and Africa on the east\n2 | adjective | relating to or bordering the Atlantic Ocean
</source>
In the above example, "define" is the command alias, "atlantic ocean" is passed to the script as %%msg%%

==Weather script==

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test/blob/master/scripts/weather.php

Available commands:
*weather location
*weather-add code location

'''note:''' ''weather-add code location'' will change the location of the code if the code has already been entered. Currently, codes cannot be deleted.

A few thousand ICAO and IATA/FAA airport codes have been imported into the codes file thanks to [["http://openflights.org/data.html"|OpenFlights]].

===Usage examples===
<source lang="dot">
<crutchy> weather
<exec> SOYLENT IRC WEATHER INFORMATION BOT
<exec> usage: "weather location" (visit http://wiki.soylentnews.org/wiki/IRC#weather for more info)
<exec> data courtesy of the APRS Citizen Weather Observer Program (CWOP) @ http://weather.gladstonefamily.net/
<exec> by crutchy: https://github.com/crutchy-/test/blob/master/weather.php
</source>

<source lang="dot">
<crutchy> weather JFK
<exec> Weather for Brooklyn, NY US at 2014-04-14 03:36:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 66°F (18.9°C) dewpoint = 56.3°F (13.5°C)
<exec> barometric pressure = 1017.3 mb ~ change of 0 mb over past 0.2 hrs relative humdity = 71%
<exec> wind speed = 1 mph (1.6 km/h) wind direction = 336°
</source>

<source lang="dot">
<kobach> weather vostok, aq
<exec> Weather for Vostok Station (RUS), -, Antarctica (the territory South of 60 deg S) at 2014-04-14 12:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = -83.7°F (-64.3°C) dewpoint = -90.9°F (-68.3°C)
<exec> barometric pressure = 948.9 mb ~ change of 1.6 mb over past 6 hrs relative humdity = 57%
<exec> wind speed = 10 mph (16 km/h) wind direction = 200°
</source>

<source lang="dot">
<crutchy> weather-add crutchy melbourne australia
<exec> code "crutchy" set for location "melbourne australia"
</source>

<source lang="dot">
<crutchy> weather crutchy
<exec> Weather for Melbourne Regional Office, VIC, Australia at 2014-04-14 11:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 60.4°F (15.8°C) dewpoint = 50.2°F (10.1°C)
<exec> barometric pressure = 1023.5 mb ~ change of -1.4 mb over past 3 hrs relative humdity = 68%
<exec> wind speed = (no data) wind direction = 0°
</source>

Historic:MainSiteFAQPage

2014-04-30T03:41:20Z

Chromas: /* FAQ */ hyphenated "community driven"

'''This is for review purposes only.''' This page is an html document that will be integrated into slash.
Feel free to make edits, please bold them (by using <nowiki>''' surrounding the text, i.e. '''this text would be bold'''</nowiki>) so I can easily integrate improvements back into the html doc. [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 16:17, 28 April 2014 (UTC)

==FAQ==

What is this site?

This is a community'''-'''driven news and discussion site, where you can submit interesting stories, and everyone can comment on them.

Where did it come from?

We had become dissatisfied with existing 'news for nerds' solutions but contrary to other project forks, we couldn't just change 'open' to 'libre'." In the spirit of Open Source, we set out to make a community-centric news site rather than just complain about corporate overlords. We forked a rather old public release of Slash, the code that runs Slashdot, and proceeded to modernize and improve upon it.

Who runs it?

It is currently managed by a small group of volunteers who maintain and operate the site. There are plans underway to replace this ad-hoc structure with a proper not-for-profit legal entity.

How can I get involved?

The simplest way to help the site is by submitting quality stories and leaving interesting comments. Without these, the site has little to offer the community. If you'd like to become more directly involved, visit the team pages and contact a team directly. Beyond that, hop on to our IRC channels and get to know the staff and learn about what needs doing. Volunteering is how this site was brought about, and there is likely something that meshes with your talents.

Can anyone submit a story?

Yes, of course anyone can submit a story. Please read the submission guidelines to increase the quality of your submission and subsequently improve its chances of being accepted.

Can I submit a story anonymously?

Yes.

Do you only want tech news?

We aim for around 70% technology and science stories with the remainder being a mix of content with general interest to our community.

Why didn't you post my story?

This is a tough one.

We get many submissions every day. Our editors constantly go through these submissions, and try to select the most interesting, timely, and relevant items to post. There are probably as many reasons for stories to get rejected as there are stories, but here are some of the more common ones:

Badly worded or incorrect submissions
Broken or missing URLs
Confusing or hysterical sounding writeup
It might be an old story
It might just be a busy day and we've already posted enough stories
Someone already submitted your story
Your story just might not be interesting
Although the editing team works hard to clean up some of the messier and incomplete submissions (we get many with just a link or two and no summary), editors do not wish to put words in the mouth of the submitter. If the article is interesting but the summary is terribly written, it puts the editors in a difficult position, we may choose to reject it in this case rather than writing up a whole new summary. In other cases we may add significantly to the summary, though we try to indicate when we do that to avoid confusion.

Why is your grammar/spelling so bad?

We're more interested in getting the stories out quickly than we are in making sure every post passes the white glove test. We attempt to catch most of the spelling and grammar mistakes by having an additional editor sign off on each story, but with our limited resources that doesn't always happen, and certainly things do sometimes slip through. Feel free to point it out, we may even make corrections depending on the case.

Why hasn't my story been accepted or rejected yet?

Usually stories are examined within a few hours of their submission. Sometimes, however, it might take longer before it closes. Usually with things that aren't time dependent...there may be some delay there. So be patient.

My story submission was "accepted"; how come I never saw it?

Usually it's because you just need to be patient. Many stories are accepted, but not posted for a few hours (for a variety of reasons: to give existing stories some time to be read and commented on, or to have a second author give a second opinion on some detail).

I submitted that a month ago!

A lot of times, we don't use a particular story on a particular day, but at some later point, someone else submits it, and it ends up getting used. We have many people from across the globe working together to post things on here. What one of us finds stupid, the others might find interesting. Or it just might be the rest of the stuff that's going on that day. There are a variety of factors: the personality of the post, the quality of the submission, or even the quantity of stories already posted when your submission entered the queue.

Where do I submit corrections or updates to previous stories?

The best way to submit followups is just as if you were submitting any other news item: please use the web submission form (rather than email). However, if your story ties closely to a specific story that's already run (for instance, if you have an update about a situation which has changed since the last time it was mentioned), please include a link to the previous story to which you're referring, rather than merely alluding to it.

I don't wish to log in because my tinfoil hat is very comfy, what am I missing?

Logged in users have a variety of benefits on SoylentNews that are unavailable to users who don't bother logging in. Among these benefits are:

The ability to save user preferences from visit to visit.
Your own Journal in which to share your innermost feelings.
The ability to define Friends & Foes to aid in reading discussions.
A chance to participate in the Moderation System.
Posting in Discussions at Score:1 instead of Score:0 means twice as many people will see your comments.

Why is someone else's User Name appearing on my User Page's Menu?

This is not a bug. This is a feature! That name is the last user page (besides your own ;) that you have visited. This is useful when you want to hop around between your user info, and someone else's: to compare friends and foes for example. Your account has not been hacked, this is totally by design.

How do I submit bugs?

The bugs are tracked on github. You'll need a github account to submit a new bug. You can also email admin@soylentnews.org and we can submit one on your behalf. Either way, please include as much relevant detail as you can (i.e. UID, time, browser and version, OS, error message, and screenshots).

Why can't I log into the Wiki?

The wiki uses a separate account system from the main page, you'll need to create separate accounts on each site.

I have a question that is not answered in this FAQ. What should I do?

Email your questions to admin@soylentnews.org. We will get you an answer, and if it's a question we've seen before, we'll consider adding it to the FAQ.

IRC

2014-04-26T04:13:32Z

Chromas: /* exec */ Moved details to new page

IRC:exec

2014-04-26T03:37:35Z

Chromas:

'''IRC Script Executive'''

"'''exec'''" is a script that runs in a CLI that connects to the Soylent [[SoylentNews:IRC|IRC server]] (irc.sylnt.us:6667) and executes other programs for output to an IRC channel.

Input to a script/program is via command line arguments only (stdin is not supported).

stdout of an executed script/program may be passed to an IRC channel or output to exec's stdout (terminal), depending on the value of ''auto-privmsg'' in the exec line. If ''auto-privmsg=0'', stdout from the script/program must begin with "privmsg " for it to be sent to the IRC channel.

Programs executed may be anything accessible from the CLI of the machine running the exec script. They may be shell programs (such as ''cowsay'' and ''fortune''), php scripts (executed using the CLI ''php'' command) or scripts in any other language executable by their respective CLI interpreters (python, perl, etc).

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test

Files:
*https://github.com/crutchy-/test/blob/master/irc.php
*https://github.com/crutchy-/test/blob/master/exec

==Usage==
Download above files from [https://github.com/crutchy-/test/blob/master/ github] into the same directory, open a terminal and change to that directory, and run "php irc.php".

Scripts may be stored anywhere that is accessible to bacon for CLI execution. If stored in a different location, be sure to include a path in the exec file line.

To invoke a script in IRC client:
<source lang="dot">alias [msg]</source>
Example:
<source ="dot">
<crutchy> define atlantic ocean
<bacon> 1 | noun | the 2nd largest ocean; separates North and South America on the west from Europe and Africa on the east\n2 | adjective | relating to or bordering the Atlantic Ocean
</source>
In the above example, "define" is the command alias, "atlantic ocean" is passed to the script as %%msg%%

About:
<source lang="dot">~</source>

Exec file:
<source lang="dot">
# timeout(sec)|auto-privmsg(1|0)|empty-msg-allowed(1|0)|alias|cmd
# available templates: %%msg%%, %%chan%%, %%nick%%, %%start%%, %%alias%%
# %%msg%% excludes alias

5|1|0|cowsay|cowsay %%msg%%
5|0|0|test|php test.php %%msg%% %%chan%% %%nick%%
5|1|1|ps|ps
5|1|1|moo|apt-get moo
5|1|1|fortune|fortune -s
5|1|1|cowsay-fortune|sh cowsay-fortune.sh
10|0|0|define|php definitions.php %%msg%%
5|0|0|php|php php.php %%msg%%
5|1|0|smile|php smile.php %%msg%%
5|1|1|uptime|uptime
5|1|1|rofl|fortune -s
5|0|1|bacon-up|php up.php %%start%%

5|1|1|haskell|runhaskell haskell.hs
5|1|1|perl|perl perl.pl

10|0|1|weather|php weather.php %%alias%% %%msg%%
10|0|1|weather-add|php weather.php %%alias%% %%msg%%

5|0|1|civ|php irciv/irciv.php %%nick%% %%msg%%

# EXEC ON ALL LINES (ONLY ONE EXEC LINE ALLOWED SO ADD TO COMMAND USING &&
5|0|0|*|php grab.php %%msg%% %%nick%%
</source>

Available exec templates:

*%%msg%%
*%%chan%%
*%%nick%%
*%%start%% # microtime(True) result when bot was started
*%%alias%%

Example script:
<source lang="php">
<?php
# 5|0|0|test|php test.php "%%msg%%" "%%chan%%" "%%nick%%"
echo "when auto-privmsg=0 this shows on terminal (stdout) only\n";
echo "privmsg msg=".$argv[1]."\n";
echo "privmsg chan=".$argv[2]."\n";
echo "privmsg nick=".$argv[3]."\n";
?>
</source>

If anyone is interested in adding their own script, do a github fork/pull and/or let crutchy know (crutchy usually hangs out in #soylent, ## and #test).

===weather exec script===

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test/blob/master/weather.php

Available commands:
*weather location
*weather-add code location

'''note:''' ''weather-add code location'' will change the location of the code if the code has already been entered. Currently, codes cannot be deleted.

A few thousand ICAO and IATA/FAA airport codes have been imported into the codes file thanks to [["http://openflights.org/data.html"|OpenFlights]].

===Usage examples===
<source lang="dot">
<crutchy> weather
<exec> SOYLENT IRC WEATHER INFORMATION BOT
<exec> usage: "weather location" (visit http://wiki.soylentnews.org/wiki/IRC#weather for more info)
<exec> data courtesy of the APRS Citizen Weather Observer Program (CWOP) @ http://weather.gladstonefamily.net/
<exec> by crutchy: https://github.com/crutchy-/test/blob/master/weather.php
</source>

<source lang="dot">
<crutchy> weather JFK
<exec> Weather for Brooklyn, NY US at 2014-04-14 03:36:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 66°F (18.9°C) dewpoint = 56.3°F (13.5°C)
<exec> barometric pressure = 1017.3 mb ~ change of 0 mb over past 0.2 hrs relative humdity = 71%
<exec> wind speed = 1 mph (1.6 km/h) wind direction = 336°
</source>

<source lang="dot">
<kobach> weather vostok, aq
<exec> Weather for Vostok Station (RUS), -, Antarctica (the territory South of 60 deg S) at 2014-04-14 12:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = -83.7°F (-64.3°C) dewpoint = -90.9°F (-68.3°C)
<exec> barometric pressure = 948.9 mb ~ change of 1.6 mb over past 6 hrs relative humdity = 57%
<exec> wind speed = 10 mph (16 km/h) wind direction = 200°
</source>

<source lang="dot">
<crutchy> weather-add crutchy melbourne australia
<exec> code "crutchy" set for location "melbourne australia"
</source>

<source lang="dot">
<crutchy> weather crutchy
<exec> Weather for Melbourne Regional Office, VIC, Australia at 2014-04-14 11:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 60.4°F (15.8°C) dewpoint = 50.2°F (10.1°C)
<exec> barometric pressure = 1023.5 mb ~ change of -1.4 mb over past 3 hrs relative humdity = 68%
<exec> wind speed = (no data) wind direction = 0°
</source>

Template:FULLPAGENAME

2014-04-26T03:34:24Z

Chromas: Created page with "{{#if:{{{1|}}}|{{FULLPAGENAME:{{{1|}}}}}|{{FULLPAGENAME}}}}"

{{#if:{{{1|}}}|{{FULLPAGENAME:{{{1|}}}}}|{{FULLPAGENAME}}}}

IRC:exec

2014-04-26T03:32:47Z

Chromas: Created page with "{{DISPLAYTITLE:IRC SCRIPT EXECUTIVE}} "'''exec'''" is a script that runs in a CLI that connects to the Soylent IRC server (irc.sylnt.us:6667) and executes..."

{{DISPLAYTITLE:IRC SCRIPT EXECUTIVE}}

"'''exec'''" is a script that runs in a CLI that connects to the Soylent [[SoylentNews:IRC|IRC server]] (irc.sylnt.us:6667) and executes other programs for output to an IRC channel.

Input to a script/program is via command line arguments only (stdin is not supported).

stdout of an executed script/program may be passed to an IRC channel or output to exec's stdout (terminal), depending on the value of ''auto-privmsg'' in the exec line. If ''auto-privmsg=0'', stdout from the script/program must begin with "privmsg " for it to be sent to the IRC channel.

Programs executed may be anything accessible from the CLI of the machine running the exec script. They may be shell programs (such as ''cowsay'' and ''fortune''), php scripts (executed using the CLI ''php'' command) or scripts in any other language executable by their respective CLI interpreters (python, perl, etc).

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test

Files:
*https://github.com/crutchy-/test/blob/master/irc.php
*https://github.com/crutchy-/test/blob/master/exec

==Usage==
Download above files from [https://github.com/crutchy-/test/blob/master/ github] into the same directory, open a terminal and change to that directory, and run "php irc.php".

Scripts may be stored anywhere that is accessible to bacon for CLI execution. If stored in a different location, be sure to include a path in the exec file line.

To invoke a script in IRC client:
<source lang="dot">alias [msg]</source>
Example:
<source ="dot">
<crutchy> define atlantic ocean
<bacon> 1 | noun | the 2nd largest ocean; separates North and South America on the west from Europe and Africa on the east\n2 | adjective | relating to or bordering the Atlantic Ocean
</source>
In the above example, "define" is the command alias, "atlantic ocean" is passed to the script as %%msg%%

About:
<source lang="dot">~</source>

Exec file:
<source lang="dot">
# timeout(sec)|auto-privmsg(1|0)|empty-msg-allowed(1|0)|alias|cmd
# available templates: %%msg%%, %%chan%%, %%nick%%, %%start%%, %%alias%%
# %%msg%% excludes alias

5|1|0|cowsay|cowsay %%msg%%
5|0|0|test|php test.php %%msg%% %%chan%% %%nick%%
5|1|1|ps|ps
5|1|1|moo|apt-get moo
5|1|1|fortune|fortune -s
5|1|1|cowsay-fortune|sh cowsay-fortune.sh
10|0|0|define|php definitions.php %%msg%%
5|0|0|php|php php.php %%msg%%
5|1|0|smile|php smile.php %%msg%%
5|1|1|uptime|uptime
5|1|1|rofl|fortune -s
5|0|1|bacon-up|php up.php %%start%%

5|1|1|haskell|runhaskell haskell.hs
5|1|1|perl|perl perl.pl

10|0|1|weather|php weather.php %%alias%% %%msg%%
10|0|1|weather-add|php weather.php %%alias%% %%msg%%

5|0|1|civ|php irciv/irciv.php %%nick%% %%msg%%

# EXEC ON ALL LINES (ONLY ONE EXEC LINE ALLOWED SO ADD TO COMMAND USING &&
5|0|0|*|php grab.php %%msg%% %%nick%%
</source>

Available exec templates:

*%%msg%%
*%%chan%%
*%%nick%%
*%%start%% # microtime(True) result when bot was started
*%%alias%%

Example script:
<source lang="php">
<?php
# 5|0|0|test|php test.php "%%msg%%" "%%chan%%" "%%nick%%"
echo "when auto-privmsg=0 this shows on terminal (stdout) only\n";
echo "privmsg msg=".$argv[1]."\n";
echo "privmsg chan=".$argv[2]."\n";
echo "privmsg nick=".$argv[3]."\n";
?>
</source>

If anyone is interested in adding their own script, do a github fork/pull and/or let crutchy know (crutchy usually hangs out in #soylent, ## and #test).

===weather exec script===

Developer(s): [[User:Crutchy|crutchy]]

Source: https://github.com/crutchy-/test/blob/master/weather.php

Available commands:
*weather location
*weather-add code location

'''note:''' ''weather-add code location'' will change the location of the code if the code has already been entered. Currently, codes cannot be deleted.

A few thousand ICAO and IATA/FAA airport codes have been imported into the codes file thanks to [["http://openflights.org/data.html"|OpenFlights]].

===Usage examples===
<source lang="dot">
<crutchy> weather
<exec> SOYLENT IRC WEATHER INFORMATION BOT
<exec> usage: "weather location" (visit http://wiki.soylentnews.org/wiki/IRC#weather for more info)
<exec> data courtesy of the APRS Citizen Weather Observer Program (CWOP) @ http://weather.gladstonefamily.net/
<exec> by crutchy: https://github.com/crutchy-/test/blob/master/weather.php
</source>

<source lang="dot">
<crutchy> weather JFK
<exec> Weather for Brooklyn, NY US at 2014-04-14 03:36:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 66°F (18.9°C) dewpoint = 56.3°F (13.5°C)
<exec> barometric pressure = 1017.3 mb ~ change of 0 mb over past 0.2 hrs relative humdity = 71%
<exec> wind speed = 1 mph (1.6 km/h) wind direction = 336°
</source>

<source lang="dot">
<kobach> weather vostok, aq
<exec> Weather for Vostok Station (RUS), -, Antarctica (the territory South of 60 deg S) at 2014-04-14 12:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = -83.7°F (-64.3°C) dewpoint = -90.9°F (-68.3°C)
<exec> barometric pressure = 948.9 mb ~ change of 1.6 mb over past 6 hrs relative humdity = 57%
<exec> wind speed = 10 mph (16 km/h) wind direction = 200°
</source>

<source lang="dot">
<crutchy> weather-add crutchy melbourne australia
<exec> code "crutchy" set for location "melbourne australia"
</source>

<source lang="dot">
<crutchy> weather crutchy
<exec> Weather for Melbourne Regional Office, VIC, Australia at 2014-04-14 11:00:00 (UTC) ~ 0.8 hrs ago:
<exec> temperature = 60.4°F (15.8°C) dewpoint = 50.2°F (10.1°C)
<exec> barometric pressure = 1023.5 mb ~ change of -1.4 mb over past 3 hrs relative humdity = 68%
<exec> wind speed = (no data) wind direction = 0°
</source>