SoylentNews - User contributions [en]

Hacktivist Википедия

2026-01-31T10:41:30Z

Janrinok: Blanked the page

Editorial Policy

2026-01-31T08:36:55Z

Janrinok: /* Editorial Policy (DRAFT) */

Parent: [[Editors|Editors Team]]

== Editorial Policy==

=== Team Leader - Editor-in-Chief (EiC) ===

The editorial team for SoylentNews.org is led by an experienced editor, referred to in this document as the Editor-in-Chief (EiC). He is responsible to the Management Group (MG) for providing editorial advice, ensuring that all editors are following the direction given by the MG, and for the day-to-day running of the editorial team. He is also responsible for ensuring that all editors are trained to an acceptable level. In any debate within the editorial team on how it should conduct itself or carry out its primary duties then the decision of the EiC is final.

For periods of extended absence of the EiC (more than 48 hours?), an Acting EiC can be nominated by the EiC before his departure, or by the MG. This should be confirmed to all members of the editorial team in writing (usually via email) in order to prevent any confusion or apparent loss of leadership from occurring.

=== Acting Editor-in-Chief (AEiC) ===

While filling the role as TL in a temporary capacity, the AEiC should fulfil all the duties of the EiC and he has the same authority as the EiC for the period of his appointment. However, he should resolve problems within the team without making long-term commitments or instigating major changes to procedures until the EiC has resumed his
post. The EiC can then assess and approve, modify or reject the proposed changes.

=== Status of Editors ===

All members of the editorial team (ET) are volunteers. However, as the site depends on the stories displayed for information and discussion, the ET is responsible for ensuring that the stories are edited and displayed 24 hours a day, 7 days a week. This places a burden upon editors that might not be found in all other support areas of the site. Additionally, as the stories influence significantly the public view of the site, it is necessary that the editorial standards are maintained at a high level and that all editors are trained to an acceptable standard before being allowed to release stories without supervision.

While there will be varying levels of expertise and experience among the members of the ET, there is no formal distinction made to reflect this. All editors are in this respect considered equal and they can all be expected to carry out all the duties of an editor at any time, with the exception of editor training.

===Training ===

Before a new volunteer is accepted into the ET they must complete a period of training. While the responsibility for this rests with the EiC, he can nominate other editors to assist in this task. Editors must not assume that they can conduct training without having first been informed by the EiC that he is content for this to happen. There is no limit to the number of editors that can be nominated to assist in training.

=== Access to the SoylentNews System. ===

Only the EiC can request that the necessary access to the system be given by a member of the System Team to a new member of the editorial team.

The EiC can also have access removed from a member of the editorial team should he decide that this is necessary for security, disciplinary or other reasons. Such action must be taken immediately that it is required and no prior approval from the Board is necessary. The EiC's reasons for his actions must be conveyed to the Board at the earliest opportunity and the editor affected must be given a copy of the reasoning in writing, usually via email. The subject of such action has the right to appeal to the Board
within 28 days of the email being sent. In the event of an appeal, the Board's concurrence or otherwise with the EiC's actions must also be given in writing, usually by email, to the subject. If no appeal is received, the subject will be assumed to have accepted the action with no additional right of appeal. Appeals to the Board should be directed to ....(?)

=== Cooperation with Other Teams ===

Editors are not to simply consider their role in isolation. For some tasks, e.g. security, SPAM prevention etc, it is not possible for the ET to operate without the assistance of other teams. Editors should be prepared to notify the appropriate members of other teams and to cooperate with them to ensure that the site operates efficiently and securely at all times, while maintaining a professional appearance to the community.

=== Interfacing with the Community.===

Any qualified editor may field questions from the community and help to resolve any disputes that may arise between community members or between a member and the SoylentNews Team. Editors must take care that they are able to do what they promise to community members or, if not, they should seek the assistance of the EiC or other appropriate Teams to help with resolution of the problem.

Editors are to take special care that they do not themselves become embroiled in a dispute with a community member. Such animosity can severely damage the community's perception of the site and could make an editor's position untenable. Tact, diplomacy and humour should all be employed as appropriate to defuse situations that occur in story discussions.

Editors should be quick to acknowledge to the community when a mistake has been made and, if possible, to take the appropriate action to remedy the mistake. They are not to make promises, assurances or take actions on behalf of others that they are not explicitly authorised to do. Editors can and should promise that the matter will be reported through the appropriate reporting chain for resolution if they are personally unable to remedy a mistake.

=== Financial Remuneration and Compensation ===

Because of the burden of 24/7 working in support of the site, the EiC can request that the Board consider some level of financial (or other) remuneration or compensation be considered for editors who achieve a certain level of effort and/or achievement.

=== Problem Management ===

Any problems that arise during the day-to-day working of the ET should be notified to the EiC as quickly as possible, commensurate with the severity of the problem. Editors are encouraged to exercise initiative in resolving problems wherever possible but, nevertheless, the EiC should be informed of the nature of the problem and the method of its resolution at the first reasonable opportunity.

Where new procedures are introduced to resolve a problem, an editor should be tasked by the EiC to document the process in the appropriate section of the wiki in order that it can become a standard procedure used by the ET.

=== Internal Dispute Resolution ===

Serious disagreements between editors should be a rare occurrence. Any such disagreements should be referred to the EiC immediately, or to another MG Member if the EiC or Acting EiC is not available. Disputes should be resolved within the Editorial Team wherever possible.

In the event of a disagreement between the EiC and 2 or more editors, and which cannot be resolved within the team, any of the editors involved may request that another MG Member intervene to assist in the resolution of the dispute. Such action is not to be taken lightly and must be reserved for only the most serious of disputes.

Where agreement regarding routine editing procedures or the editing of a specific story cannot be reached by discussion between members of the ET, the EiC has the authority to seek the advice of his experienced editors and to resolve the matter to their mutual satisfaction, regardless of whether this receives unanimous support. In such instances it would be wise for the EiC to seek the advice of an even number of senior editors so that no stalemate over the final outcome can occur. This requirement will
also help overcome the difficulty in bringing all senior editors together at the same time resulting from their geographic spread. However, ultimately, it is for the EiC to decide with whom he consults on any particular matter.

2025年最佳SoundCloud播放量计算器与增长方案

2026-01-31T08:11:13Z

Janrinok: Blanked the page

2025年7月SMM金属产量数据发布上海有色网

2026-01-31T08:11:00Z

Janrinok: Blanked the page

2025 Is The Year Of Arkadium Bubble Shooter

2026-01-31T08:10:49Z

Janrinok: Blanked the page

2025: Al Mejor Sonido

2026-01-31T08:10:30Z

Janrinok: Blanked the page

2024 年最好的 XXX 個免費同性戀色情網站，作者為 MrPornGeek

2026-01-31T08:10:11Z

Janrinok: Blanked the page

2019年十大男性增强药: Customer Review

2026-01-31T08:09:57Z

Janrinok: Blanked the page

10种最好的增强性功能的药物介绍障碍是一种男性

2026-01-31T08:09:22Z

Janrinok: Blanked the page

10 Trendy Concepts For Your Arkadium Bubble Shooter

2026-01-31T08:08:58Z

Janrinok: Blanked the page

10 Most Wonderful Chaturbate Mature Changing Exactly How We See The World

2026-01-31T08:08:43Z

Janrinok: Blanked the page

10 Most Incredible Bisexual Porn Changing How Exactly We Start To See The World

2026-01-31T08:08:20Z

Janrinok: Blanked the page

10 Easy Ways To Figure Out The Tassimo Drinks Machine In Your Body.

2026-01-31T08:07:50Z

Janrinok: Blanked the page

User:SaraBlodgett2

2026-01-31T08:05:48Z

Janrinok: Blanked the page

A Guide To Gilf Porn

2026-01-28T19:49:18Z

Janrinok: Blanked the page

Best-handjob Videos

2026-01-28T19:47:01Z

Janrinok: Blanked the page

Japansex: In 5 Easy Steps

2026-01-28T19:46:21Z

Janrinok: Blanked the page

Cast Teenager Young Porn Videos 18

2026-01-28T19:46:08Z

Janrinok: Blanked the page

Hot Blondes In Free People Wind Up Tubing Videos In HD On PornDig

2026-01-28T19:45:38Z

Janrinok: Blanked the page

Dubbel Penetration Porno Video s Pornhub Com

2026-01-28T19:45:15Z

Janrinok: Blanked the page

Approaches To Use Top Porn Movies Site

2026-01-28T19:44:54Z

Janrinok: Blanked the page

An Unbiased View Of Japan Porn Video

2026-01-28T19:42:52Z

Janrinok: Blanked the page

Milf Smut Videos

2026-01-28T08:12:22Z

Janrinok: Blanked the page

Toys Disengage Porn Videos Porn For Women

2026-01-28T08:11:19Z

Janrinok: Blanked the page

Do We Need Best Premium Porn Sites Reddit Since We ve

2026-01-28T08:11:00Z

Janrinok: Blanked the page

The Fundamentals Of New Free Porn Video Sites Revealed

2026-01-28T08:10:43Z

Janrinok: Blanked the page

Unidentified Details About Porn Famous Websites Made Known

2026-01-28T08:10:27Z

Janrinok: Blanked the page

An Observational Study On The Popularity And Perception Of The "We The People" Graphic Cotton Tee

2026-01-28T08:10:06Z

Janrinok: Blanked the page

Roughly Sex Search

2026-01-28T08:08:20Z

Janrinok: Blanked the page

Blond Little Girl Porn Videos

2026-01-28T08:07:59Z

Janrinok: Blanked the page

Editors

2026-01-02T06:13:29Z

Janrinok: /* 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 (at) 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
|-
| hubie
| Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| CoolHand
| editor
| UTC-4 (EST/EDT)
|-
| NotSanguine
| editor
| UTC-4 (EST/EDT)
|-
| Cmn32480
| editor
| UTC-4 (EST/EDT)
|-
| takyon
| editor
| UTC-4 (EST/EDT)
|-
| Fnord666
| Assistant Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| mrpg
| editor
| UTC-4
|-
| chromas
| editor
| UTC-8 (PST; -7 PDT)
|-
| kolie
| editor
| UTC-8 (PST)
|-
| requerdanos
| editor
| UTC-4 (EST/EDT)
|}
<section end=whoweare />

==Retired Members==
Former editors that have relinquished 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)
|-
| charon
| editor
| UTC-4 (EST/EDT)
|-
| Xyem
| editor
| GMT
|-
|}

==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

2026-01-02T06:11:56Z

Janrinok: /* 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 (at) 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
|-
| hubie
| Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| CoolHand
| editor
| UTC-4 (EST/EDT)
|-
| NotSanguine
| editor
| UTC-4 (EST/EDT)
|-
| Cmn32480
| editor
| UTC-4 (EST/EDT)
|-
| takyon
| editor
| UTC-4 (EST/EDT)
|-
| Fnord666
| Assistant Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| mrpg
| editor
| UTC-4
|-
| chromas
| editor
| UTC-8 (PST; -7 PDT)
|-
! kolie
! editor
! UTC-8 (PST)
!-
| requerdanos
| editor
| UTC-4 (EST/EDT)
|}
<section end=whoweare />

==Retired Members==
Former editors that have relinquished 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)
|-
| charon
| editor
| UTC-4 (EST/EDT)
|-
| Xyem
| editor
| GMT
|-
|}

==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

2026-01-02T06:08:32Z

Janrinok: /* 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 (at) 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
|-
| hubie
| Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| CoolHand
| editor
| UTC-4 (EST/EDT)
|-
| NotSanguine
| editor
| UTC-4 (EST/EDT)
|-
| Cmn32480
| editor
| UTC-4 (EST/EDT)
|-
| takyon
| editor
| UTC-4 (EST/EDT)
|-
| Fnord666
| Assistant Editor-in-Chief
| UTC-4 (EST/EDT)
|-
| mrpg
| editor
| UTC-4
|-
| chromas
| editor
| UTC-8 (PST; -7 PDT)
|-
| requerdanos
| editor
| UTC-4 (EST/EDT)
|}
<section end=whoweare />

==Retired Members==
Former editors that have relinquished 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)
|-
| charon
| editor
| UTC-4 (EST/EDT)
|-
| Xyem
| editor
| GMT
|-
|}

==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]]

WhosWho

2025-05-27T07:29:00Z

Janrinok: Added comment to indicate that this page is Out-of-Date

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]].

= This Page is Out-of-Date and refers to the previous site structure and manning. =

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev (at) SoylentNews.org ([[#Development|Development]])
*editors (at) SoylentNews.org ([[#Editors|Editors]])
*suggestions (at) soylentNews.org ([[#Community Support|Community Support]])
*wiki (at) SoylentNews.org ([[#Wiki|Wiki]])
*ircqueries (at) SoylentNews.org ([[#IRC|IRC]])
*style (at) SoylentNews.org ([[#Style|Style/User Experience]])
*art (at) SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5*
Has a sleep disorder, hours are erratic
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| UTC-7 (MST)
|-
| [[User:mrcoolbp|mrcoolbp]]
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{#lst:Development|whoarewe}}

==Sysops==

{{#lst:SystemAdministration|whoarewe}}

==Style/User Experience==

{{#lst:UserExperience|whoarewe}}

==Editors==

{{#lst:Editors|whoweare}}

==Community Support==

{{#lst:CommunitySupport|whoarewe}}

==Wiki==

{{#lst:Wiki|whoarewe}}

==IRC==

{{#lst:IRC|whoarewe}}

==QA==

{{#lst:QA|whoarewe}}

==Notes==
<references />

Editing Process

2025-05-15T09:33:28Z

Janrinok: /* The Story */

Parent: [[Editors|Editors Team]]

= Introduction =
The editing process describes those actions taken to edit a submission received from a community member into a suitable format for release as a story. Some of these actions are typical of any editing process (e.g. spell checking, reformatting etc) but other actions are less obvious, especially to the new or inexperienced editor. This section aims to assist those new to the editing process to find their feet and help them gain experience. However, there are probably as many ways to edit a submission as there are editors; this section only describes one method which has been proven over time to work but do not feel that you must follow this guide slavishly if you have a better system that works for you.

The standard of submission can vary greatly from a title and a single URL link, to a fully researched story which requires the minimum of effort on the part of the editor to prepare it for publication. Despite the Submission Guidelines, peoples' abilities differ and some are reluctant or unable to allocate sufficient time to fully prepare a submission. Nevertheless, it is the editor's responsibility to try to make a story out of what is given. In some cases this will prove to be impossible but, in the majority of instances, there will be enough to get the editor started although significantly more work will be necessary before a finished story is finally realised. Conversely, there may not be enough time for the editor to complete all the research necessary and (s)he must decide whether to hold the submission until sufficient time is available or delete the submission and move on to something more reasonable to work with.

= The Role of the Editor =

== Introduction ==
The role of the editor is not as simple to define as one might initially imagine. (S)he must, of course, change what might be a simple submission into a reportable story that will appeal to at least a portion of the community, but there are several other task functions that are equally as important. The final aim is to provide a story that is both interesting and thought provoking thus encouraging as many of the community to read it and, hopefully, contribute further by adding to the discussion about it. However, the editor is also responsible for upholding the standards of the site in general, probably far more than any other member of the team that is working hard to keep the site active. (S)he is frequently the interface between the site and the community, and will also bear the brunt of much of the comment from the community when things are not going as well as they should. So, the task then is to identify how this can best be achieved.

===Dos and Don'ts===
These are generally accepted best practices for editors.

'''Do:'''
* Check spelling and grammar
* Check links
* Check related stories for dupes

'''Don't:'''
* Post stories that you submitted
* Add an "editor's note" with your ''opinion'' (put ''that'' in the comments)
* Edit quoted material. [Unless doing so to provide clarity, making sure to surround any changed text with square brackets.]

== Accurate, Balanced and Impartial Reporting ==
The first requirement is for an editor to provide accurate reporting which is also balanced and impartial. While it is unreasonable to expect an editor not to have strong opinions on at least some of the story topics, (s)he must ensure that such views do not express themselves in the stories that (s)he edits. Not everyone will share the same views and it is important that the editor does not abuse his or her position by slanting a story in such a way as to demonstrate a bias. Of course, the editor can always join in the subsequent discussion once a story is released and can express his or her views there as they deem fit. Some of the submissions that are received do themselves express a particular view or bias and, if possible, the editor should endeavour to find other links that provide contrasting or opposing viewpoints and include them in the story.

== Filter Unwanted Material ==
Secondly, it is essential that each link in a submission is clicked and checked. This is important not only to ensure that the link is functional, but also to remove links to unwanted material such as political electioneering, pornography, blatent advertising (also known as 'slashvertisements') and off-topic items. Sometimes such links can be the result of an error but, more often than not, they are an intentional attempt by someone to try to defeat the editorial system and to successfully 'troll' the site. Usually, such material is submitted by an Anonymous Coward but it can also be as a result of a misguided attempt at humour by a recognised community member. All such links should be deleted. Remember that we aim to be a global site and, while we should not and cannot comply with the laws of every nation, religion, or regional group, material which is likely to be offensive and is irrelevant to the story should be removed.

== Simple Understandable Summary ==
Finally, aim to write simple, understandable English at all times. The topics that we write about are often complex and technical but by writing in an easy and simple style the editor can make the subject matter more understandable. Leave terse technical writings for the articles that the story links to - and if you can provide several links examining the same subject at differing levels of complexity then you are more likely to have at least one that will appeal to each member of the community.

== Submission Feedback ==

(this may no-longer be necessary) [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 16:11, 10 July 2014 (UTC)

== When Things Go Wrong ==
From time to time the site will experience technical difficulties. If, because of a technical fault, the site is not publishing stories it is also likely that an editor will not be in a position to produce new stories. At such times the editorial team can divide itself into 2 specific roles. The first, and priority role, is to join the #soylent and #staff channels on IRC and act as the first point of contact with members of the community who wish to alert the team to the current problem and, more frequently, want to know when the site will return to normal operation. (This role is shared with other team members who are unable to continue with their own primary tasks). Rather than have each query from the community directed to the team that is trying to rectify the fault, the editorial team field these questions, provide answers when they are available, and act as a conduit between the community and the sys/dev teams such that they, in turn, are able to continue with their primary task of recovering the site. Any other spare editors can begin to collect new stories for eventual submission once the system is recovered.

= Preparing for Work =

The editing process revolves around 2 lists: the Submission List and the Story List. When you have received your editor permissions on the system, you will notice that whenever you log on to the site that you have an additional menu bar at the top of the page. I recommend that, if you have a browser that supports tabbed windows, you open 3 separate tabs. The first should be the Submission List, the second the Story List and the third the site front page.

Having the front page visible allows to you keep an eye on how the stories are being released. However, for the editing task it is not strictly necessary so you can omit it if you find it interferes with your work. You might also want to keep an eye on at least the #staff channel on IRC because any problems that arise will be flagged up on here in the first instance. Have the #editorial channel ready somewhere as well, if you can manage it. You will now realise that, for everything to work perfectly you need to keep an eye on mulitple windows. Often this is impractical - you simply have to do the best that you can. Ideally, there will be more than one editor active at any time so you can share the responsibilities between you. At other times you will be concentrating on one specific window and you will have to decide when to quickly shift to other displays to keep an eye on things. For the new or inexperienced editor - just concentrate on the editing task and leave others to take care of the rest. As you become more comfortable in your new role you will naturally develop the ability to switch around from time to time.

== Submission List ==

The Submission List is exactly what it says - it lists all the submissions that have been received but not yet processed into stories. The list is in chronological order with the oldest story at the top. Each submission has a number of fields associated with it. Currently (Mar 2014), they are:

* A comment field. This can be used by editors to keep notes on the story either for yourself or to inform other editors about something you might have discovered about the story (i.e. link not working, or a story that is best kept to be released at a specific time e.g. weekend or specific holiday)
* A drop-down list that allows a submission to be tagged as Back, Hold or Quik. [TODO Find out what they each mean/do]
* A drop-down list that allows selection of the Main Page or All Sections. [TODO Find out what they each mean/do]
* A selection box that enables each submission to be individually selected for a subsequent action to be applied.
* The date and time that the submission was received.
* The title provided by the submitter. Clicking this hyperlink selects the submission for editing.
* The nick of the submitter, his/her karma in brackets, and a contact email if it was provided.

Below the list of submissions are 5 buttons with the following labels and functions:

* Update - Updates the comment fields on each of the submissions whose selection box is ticked.
* Delete - Delete each submission whose selection box is ticked. Warning - this is permanent and immediate, care should be exercised when using the Delete function.
* Merge - Merge the selected submissions in to one story. This is useful when similar but not identical stories are submitted on a specific news item.
* Select All - Select all submissions.
* Select None - Deselect all submissions.

== Story List ==

[[File:StoriesList.jpg|thumb|right|400px|The Stories List]]
The Story List is in reverse chronological order and shows stories that have been published or are waiting to be published. The display is colour-coded. When a story is released by, say Editor A, it will appear in the list according to the date and time specified during the editing process. It will appear in a yellow colour to Editor A, but to all other editors it will appear in red. This indicates that the story has only been seen by the originating editor and that it has not been checked by a second editor. Wherever possible, stories are to be seen by at least 2 editors before they reach their release time. Once a second editor (Editor B) has viewed it and pressed the 'Update' button the story colour code will change to green for all editors. The action of editing or checking a story is known as a 'Sign Off'. A story opened from the Story List will show the 'Sign Off' information on the screen on the right hand side of the display. In our example, the first sign off will be Editor A and the second sign off will be Editor B. There is no limit to the number of editors who can view a story or make corrections to it and a history of who has made changes will be maintained (but not what has been changed) in the Sign Off information. Stories that have been placed in the list but have been stopped from release are coloured grey.

The format of each line in the Story List is as follows:

* List Index. As the stories progress down the list their index number will change according to their relative position.
* Title. The title is not necessarily the same as that suggested by the submitter. An editor can change the title at any time during the editing process. The title is also a hyperlink which allows the story to be opened for further editing either before or after story release. This is useful when an error is discovered in a released story and it is felt that editing is necessary. However, changes should be done only when necessary because they could affect the meaning and usefulness of comments that have been made to the story by the community.
* Originating Editor.
* Topic. Stories can be allocated to one or more Topic groups. Only the first Topic group is displayed in the Story List.
* Nexus. Currently, all stories are released on the Main Page nexus however, it is possible for different nexuses to be used.
* Page Hits. [TODO Confirm this!]
* Comment Count. The count is only useful after the story has been released. It indicates the number of total comments but does not differentiate between good and bad comments.
* Release Date/Time.

= Editing the Submission =
== Initial Actions ==

The initial actions when editing a submission are:
* Open the submission in the editor by clicking the submission's title hyperlink.
* Check all links work, and that they point to a site relevant to the story. Remove links to political or pornographic material, off-topic items, and advertisments. Check the date of all links, ensuring that they point to current news and not to historic events/stories.
* Check if the story is a duplicate of one that has already been released. (N.b. there is more on this topic in the [//wiki.soylentnews.org/wiki/Editing_Process#Using_the_Submission_Editor Using the Submission Editor] below.)
* After removing unwanted links, re-check that the story remains of interest to the community.
* Assess if the story is time critical - for example, does it describe critical software updates, or announce significant and relevant breaking news? It it does, prepare the story as quickly as possible and save it in the story queue. If possible, have a second editor sign it off and then release it as quickly as practicable.
* Assess if there is sufficient material to process the submission now or whether it should wait until more time is available. Decide whether to leave the editor and mark the submission with an appropriate comment in the submission queue, begin editing the submission as a standard story, or to start the research.

== Using the Submission Editor ==

Whilst there is only one Submission Editor, it has 2 possible page layouts. When the editor is first opened, usually by clicking the hyperlink title on either the submissions list (for a new story) or the story page (to re-edit an existing story), the first page layout is invoked. We will call this display the Basic Editing Page (BEP), and it displays a subset of all the fields than can be edited. If you are editing a story from a submission, then you cannot move to the Main Editing Page (MEP) until the nexus and topic fields are completed. Currently, the nexus field usually displays "Main Page" as default because this is the only nexus in use. The topic field next to it, however, has no default setting and it is essential to select a topic before you are able to move to the MEP by pressing the 'Preview' button.

=== Basic Editing Page (BEP) ===

The purpose of the BEP is to display enough information for the editor to assess whether the submission is worth processing into a full story. The links can be tested and their content checked, the summary can be reformatted and unprintable Unicode characters can be edited to something more suitable for the slashcode to manage. The submission can be discarded at this point. However, assuming that you are happy with everything so far, press the 'Preview' button and it will change the display to the MEP.

=== Main Editing Page (MEP) ===

[[File:EditorInterface.jpg|thumb|right|400px|Main Editing Panel 'ToolTips']]

The MEP allows the editing of <u>all</u> data. I recommend that you use the MEP as much as possible.

==== Story Display ====

The top portion of the MEP page displays the story as would currently appear if released at this point. Unless you are fortunate, there are likely to be layout, spelling or grammatical structure changes required - and in some cases all three! As a guide, use the layout described in the [[Story_Style|Story Style]] chapter in the Editors' Documentation wherever possible but, from time to time, you will have a submission that doesn't fall neatly into the usual style. Do your best to make it readable and clear while following the style guidelines as closely as you can. Having said all that, the Story Display is not directly editable - it will be necessary to use the 'Intro Copy' and possibly the 'Extended Copy' fields further down the page to modify the text. We will cover these fields in more detail in a moment.

==== Similar / Duplicate Story Detection ====

Below the story display is a small field designed to show similar stories to the one currently being edited. While this can be useful, take care not to rely upon it as a foolproof method of checking if your current submission is a duplicate. It will sometimes show stories that are superficially similar but might actually be very different in content, or it will fail to find a genuine duplicate because the structure and grammar chosen in the original story are significantly different from that which you are currently editing.

==== The Display Enable Line ====

Despite the title of this line, only one element on it is actually there to enable a story to be displayed - but it is so important that I have chosen to name this line as I have.
The first two buttons on this line are labelled 'Save' and 'Preview'. This pair of buttons is repeated in several locations on the page but they always fulfill the same function. The 'Preview' button reformats the display to show any changes that the editor has made so far, and the 'Save' button tells the editor that you have finished editing the submission and have accepted it as a story. The system will then transfer the story to the Story List, remove the submission that you have been editing from the Submission List, and finally display a modified copy of the Story List. It is important to recognise that this is a modified copy because it exhibits an unfortunate characteristic that is not shared by the usual Story List. If you refresh the page of a modified Story List, it will insert the same story, at the same release time into the main Story List i.e. you will have 2 identical stories both queued for release at the same time which cannot be deleted. However, all is not lost. At the right hand end of the Display Enable Line is a checkbox, labelled 'Display', which usually defaults to being ticked. This ticked box indicates that, once the story is placed into the main Story List, it will be released at the time that has been allocated to it. If you can recall the colour coding system described in paragraph describing the Story List earlier on this page, the story will initially be coloured yellow for the submitting editor and red for all others. If this box is unticked, it will prevent the story from being released and the colour coding scheme will turn it to grey. If you have accidentally placed 2 copies of the same story in to the Story List, select one of them and bring it into the editor, deselect the 'Display' checkbox, and save the story again. The second, duplicate story will not be released. This is an important function and one that you would do well to remember - any story can be stopped from being published by deselecting the 'Display' checkbox before its release time.

==== Topics ====

Each submission must be allocated to a nexus and one or more topics. Currently, there is only 1 nexus - 'The Main Page'. For technical reasons, each nexus should be hosted on its own server and, as Soylent News only has 1 primary server (with backups) then it is limited to one nexus. At a later date, it might be decided to add further nexuses (e.g. 'Nerd Cinema','Mobile Devices' or whatever). However, there are multiple topics (e.g. Business, Hardware, OS, Software etc) and a submission might fit into more than one topic area. It is strongly recommended that, in most instances, only the one most appropriate topic is allocated but, on occasion it might be sensible to select a second and, very rarely, a third.

The selected nexus and topics is shown in a single list with label embedded within it. Immediately to the right of the list are 4 symbols: an up pointer, a delete cross, an addition cross and a down pointer. The two pointers are for moving the order of topics in the list so that the most important one is displayed higher in the list than any others. Because only a single topic is used for the majority of stories the up and down pointer are not frequently used.

The delete cross will delete the currently highlighted nexus or topic. As only a single nexus in use ('The Main Page') there is little to be gained by deleting this nexus, particularly as the software will not let the submission complete the editing process with the nexus field left empty. However, an editor might choose to change the most appropriate topic and so might delete the topic currently displayed in the list.

The addition cross opens a second window called the Select Topics tree. Highlight the desired topic and then press the 'Add' button at the bottom os the Select Topics window. This can be repeated for several topics but, as discussed earlier, is usually limited to one and on occasion perhaps 2 or rarely 3 topics. There are several other buttons at the bottom of the Select Topics window but their usage is self-explanatory and will not be described here.

==== Title ====

Each story must have a title. The character length of the title is 100 chars but, at various point in the submission process, there appears to be an arbitrary limit enforced on the title length of 85 characters. [This appears to be a bug - it is being investigated] The title should clearly explain the essence of the story and is printed in Title Case. For full details of what is and is not acceptable, see the section on Editorial Style.

==== Department (Dept) ====

The Dept field is an opportunity for the editor to inject a witty or pithy comment appropriate to the Title and content of the submission. It is not always appropriate and there is no compulsion for it to be used at all. If nothing is entered into this field it simply does not display when the story is published. It should not be used to express the editor's personal point of view. The best way to gain a feel for how this field is used is to simply go through previous stories. The contents of the field should be all lower case. The system will insert 'from the' before the contents of the Dept field and 'dept' after. It will also automatically replace whitespace with a dash (-). E.g 'this is an example' would appear on publication as 'from the this-is-an-example dept'.

==== Author ====

If you are the first author to work on this submission then your nick should already appear in the left-hand selector box. If not, then select it manually. Most stories are published to elicit comments from the community but, for them to be able to do so, the Comments Enabled option has to be selected in the middle selector box. However, there are other options that have specialised uses and an alternative can be selected if it is more appropriate. This would be a fairly rare occurrence. The right-hand field is an editable text box which contains the date and time (UTC) that the story will be released. It will have a default time within the next 30 minutes or so and this is rarely appropriate. Check on the stories page that another editor has not released a different story since you started the editing process and decide the release time for the submission that you are processing. Remember to change the '''date''' portion if you are releasing a story after midnight on the current day.

It is possible to create Polls i.e. give the community a list of options for which they are able to vote, and these options are immediately below the fields discussed in the previous paragraph. As I have not currently used this facility I will not explain it any further here yet.

Below the Poll options are 2 selector buttons and a link. The link is invaluable. When you have made major changes to a submission it is possible to lose sight of what the original submission looked like. By using the 'submission' link you can open a BEP with the original unchanged submission within it. Be careful that you do not end up editing 2 different copies of the same submission which is easily done, and difficult to recover from without having to completely redo the submission again from scratch.

==== The Story ====

Having gone through all the controls, options and selections detailed above we finally arrive at the point of the entire process - the story itself. A submission might only be a few words or, if you are lucky, a few hundred words. But the story that the editor crafts from the submission might run into a thousand words or more. While this is uncommon, it does happen frequently enough that procedures have been created to help manage and display the story to maximum effect.

Currently, the editing of the story itself is carried out using a subset of Hyper-Text Markup Language (HTML). The editor is rudimentary and the process is error prone. Until an editor becomes proficient at the editing process, (s)he should work slowly and methodically through the story while previewing progress at regular intervals. Do NOT attempt to edit as quickly as more experienced editors, nor fall into the trap of thinking that you are not working hard enough. Most editors would prefer one or 2 well edited stories a day rather than 10 that required substantial reworking during the release checking process, or worse, risked incorrect information being published to the community. Errors will occur naturally and every editor will experience them, but inducing additional errors by undue haste is counter-productive to the entire editorial team. That said, you will make errors - accept this fact, try to learn from each error, and move on.

Every story is capable of being divided into 2 separate portions. The Intro Copy which is essential for every story, and the Extended Copy, which is only used for longer stories. There is no practical physical limit on the size of the Intro Copy but, for presentational purposes and to enable a reader to grasp the essential points that are being made, it is usually kept as concise as possible while maintaining readability and comprehensively covering the essential points. It should be possible to read the Intro Copy as a stand-alone document, understand the basic thrust and outcome of the story, and move on if no further detail is wanted.

Immediately below the Intro Copy editing window are 2 buttons marked initially 'save' and 'preview'. Pressing the 'preview' button will redraw the entire web page that you are working in and show you what your editing so far would look like if released as a story. Use the 'preview' button frequently, especially for checking layout, that the links point to the web pages that you expect them to, and that you are meeting the requirements of the Intro Copy with regards to content. When you have inspected your work so far, return down the page to the Intro Copy window again and place your cursor inside the window. Check that all the red underlined words are corrected for spelling or are correct abbreviations that the dictionary has simply not recognised. Do '''not''' correct source material. If the source web page or document says something - that is how it will be published. As an editor you can decide whether it is a simple spelling mistake (in which case put '[sic]' immediately after the error). Do not correct English dialect differences. As long as the summary is consistently written in US-English or UK-English, it is correct. Do not change the spelling of source material to suit your own particular dictionary. If, for example, the material is published in UK English, changing words to US English (or vice versa) can significantly change the meaning of what is being said. You edit the summary - not the source material. For other errors an Editor's Note is probably more appropriate.

If, by the end of the Intro Copy editing process there is nothing more to be said, then the document is complete and ready for publication. Quickly check the stories page to make sure that no one else has published a story while you have been editing (if so - change your timings, leave the published story untouched). If you are finished then press the 'save' button and it should present you with a modified story list. Remember that this is the 'modified' story list and has special properties which make it rather dangerous. If you renew this page, say, by pressing the F5 key in your browser, a second copy of your story at the exact same time of release will be inserted into the list. One of the copies will then have to be disabled. I recommend that you simply check that the timings for you story are as you expected and then close this window. You can then move to the Story Window that you have had open throughout the editing process, click 'stories' at the top of the page to update it, and your story will be displayed.

However, if you have more detail that you think some people will want to read but that might not be of interest to everybody, or simply information that you could not reasonably insert into the Intro Copy, then you use Extended Copy field just below. There are no additional headers or selections, it is simply a way of extending the story except that the contents of the Extended Copy window are not displayed immediately on the main website page but are accessed by the reader selecting 'Read More' from the bottom line of the story display. This conveniently solves the problem of keeping the main page full of short, concise stories but enables longer and more detailed stories to be seen by those who wish to read them. Editing the Extended Copy text is identical to editing the Intro Copy and the use of the 'preview' and 'save' buttons remain the same. If there is text in the Extended Copy field, the system will add '[Continues...]' to the end of the Intro Copy field to show that there is more to the summary when it displays on the main page. You should not add '[Continues...]' manually because there will be two instances.

It is possible to include text from a file into a summary or to attach media links - neither of these are used at present by the site and, for now, their usage can be ignored.

Soylent Phoenix - Bank Details

2025-04-04T13:35:42Z

Janrinok:

'''International wire transfers''' can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
U.S. Bank's Swift Code: USBKUS44IMT<br>

'''Within the USA''', wire transfers can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
Routing number: 123000220<br>

If you are asked for the address of Soylent Phoenix (usually only required in the US) it is:

1120 Niantic St<br>
Medford OR 97501

In all cases, please use your Nickname and User ID as a reference if you wish to have your SN account credited with the subscription. Without a reference the the transfer will be treated as an anonymous donation.

Soylent Phoenix - Bank Details

2025-04-04T13:34:58Z

Janrinok:

'''International wire transfers''' can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
U.S. Bank's Swift Code: USBKUS44IMT<br>

'''Within the USA''', wire transfers can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
Routing number: 123000220<br>

If you are asked for the address of Soylent Phoenix (usually only required in the US) it is:

1120 Niantic St
Medford OR 97501

In all cases, please use your Nickname and User ID as a reference if you wish to have your SN account credited with the subscription. Without a reference the the transfer will be treated as an anonymous donation.

Discussion Policy

2025-02-04T12:11:17Z

Janrinok: /* Journals */

== Discussion Policy ==

=== Main Page Stories ===

The aim of the site is to enable free and open discussions on the topics published so that community members can express their personal views on the subject while allowing threads to develop into related ideas. This was the intention of the original site created in 2014 and it has remained so since that time. One of the many reasons for choosing to base the site in the USA is that US laws permit and encourage freedom of speech with few restrictions compared with other countries.

In order to qualify for a Tax Exempt Status (IRC Section 501(c)(3)) it is necessary to show a specific purpose which justifies such a status, and SoylentNews has stated that its primary focus is science, technology, engineering and mathematics which together are widely known as STEM. Nevertheless, the site editorial policy accepts a very wide interpretation of this description and frequently posts stories that are only loosely related to the stated range of topics. Often, they can be allocated to a standard topic description but sometimes they can be published under the 'Random' topic. All of the topics are open to site discussion. Additionally, all stories are categorized into sub-divisions, each of which is known as a nexus. This permits community members to filter out stories in which they have no specific interest.

=== Journals ===

The range of main page topics does restrict the discussion of matters that are outside the stated purpose of the site. This is resolved by allowing community members who have an active account to create 'journals' which may be on any topic whatsoever provided that they comply with the relevant US and State laws. SoylentNews accepts no responsibility for the content or views expressed in journals and this warning is clearly shown on each journal. The owner of a journal can limit those whom they wish to allow to comment. This is entirely at the owner's discretion and is not a matter in which the staff are involved, and nor should they be. Furthermore, the journal owner can also delete any or all journals that they own. Again, this is not a staff matter.

'''The content of journals is, therefore, solely the responsibility of the journal owner and, providing that they comply with US and State law, they are free to express any opinion, political view or extreme statement in their own journal'''.

If commenting is permitted in that journal then others can argue for or against such expressions as in any other discussion. However, those views should only be discussed in that journal. It is not appropriate to counter a view that someone has made in a journal by responding to it in a different discussion elsewhere on the site. That is, at best, off-topic and can endanger our tax status. Nor should anyone expect the staff to take any form of action against the journal owner. The journal has been published in compliance with the rules of the site and it is not a staff matter. It is an expression of free speech. Journals must comply with all aspects of site policy. Repeated attempts to raise a personal objection against the owner of a journal, or against the ideas, views or content expressed in a journal elsewhere outside that journal discussion may constitute an abuse of the site.

The only acceptable ways to counter a journal that you strongly disagree with is argue against the views by commenting inside that journal, or to moderate the comments in that journal if you are able to do so, or to create your own journal and present your counter arguments and views. Alternatively, you can simply stop reading that person's journals.

Discussion Policy

2025-02-04T12:06:25Z

Janrinok: Created page with "== Discussion Policy == === Main Page Stories === The aim of the site is to enable free and open discussions on the topics published so that community members can express their personal views on the subject while allowing threads to develop into related ideas. This was the intention of the original site created in 2014 and it has remained so since that time. One of the many reasons for choosing to base the site in the USA is that US laws permit and encourage freedom..."

== Discussion Policy ==

=== Main Page Stories ===

The aim of the site is to enable free and open discussions on the topics published so that community members can express their personal views on the subject while allowing threads to develop into related ideas. This was the intention of the original site created in 2014 and it has remained so since that time. One of the many reasons for choosing to base the site in the USA is that US laws permit and encourage freedom of speech with few restrictions compared with other countries.

In order to qualify for a Tax Exempt Status (IRC Section 501(c)(3)) it is necessary to show a specific purpose which justifies such a status, and SoylentNews has stated that its primary focus is science, technology, engineering and mathematics which together are widely known as STEM. Nevertheless, the site editorial policy accepts a very wide interpretation of this description and frequently posts stories that are only loosely related to the stated range of topics. Often, they can be allocated to a standard topic description but sometimes they can be published under the 'Random' topic. All of the topics are open to site discussion. Additionally, all stories are categorized into sub-divisions, each of which is known as a nexus. This permits community members to filter out stories in which they have no specific interest.

=== Journals ===

The range of main page topics does restrict the discussion of matters that are outside the stated purpose of the site. This is resolved by allowing community members who have an active account to create 'journals' which may be on any topic whatsoever provided that they comply with the relevant US and State laws. SoylentNews accepts no responsibility for the content or views expressed in journals and this warning is clearly shown on each journal. The owner of a journal can limit those whom they wish to allow to comment. This is entirely at the owner's discretion and is not a matter in which the staff are involved, and nor should they be. Furthermore, the journal owner can also delete any or all journals that they own. Again, this is not a staff matter.

'''The content of journals is, therefore, solely the responsibility of the journal owner and, providing that they comply with US and State law, they are free to express any opinion, political view or extreme statement in their own journal'''.

If commenting is permitted in that journal then others can argue for or against such expressions as in any other discussion. However, those views should only be discussed in that journal. It is not appropriate to counter a view that someone has made in a journal by responding to it in a different discussion elsewhere on the site. That is, at best, off-topic and can endanger our tax status. Nor should anyone expect the staff to take any form of action against the journal owner. The journal has been published in compliance with the rules of the site and it is not a staff matter. It is an expression of free speech. Journals must comply with all aspects of site policy. Repeated attempts to raise a personal objection against the owner of a journal, or against the ideas, views or content expressed in a journal, outside that journal discussion may constitute an abuse of the site.

The only acceptable ways to counter a journal that you strongly disagree with is argue against the views by commenting inside that journal, or to moderate the comments in that journal if you are able to do so, or to create your own journal and present your counter arguments and views. Alternatively, you can simply stop reading that person's journals.

SoylentNews

2025-02-04T12:05:32Z

Janrinok: /* Useful Links */

This is a home for information about how '''[http://soylentnews.org SoylentNews.org]''' was started, and the vision for it.

==About SoylentNews.org==

Welcome to the '''[http://soylentnews.org SoylentNews.org]''' Wiki.

We deliver community-sourced news and discussion. This is an, grassroots effort powered by article submissions from our readers, volunteers, and our forked version of [https://github.com/SoylentNews/slashcode slashcode] called [https://github.com/SoylentNews/rehash 'Rehash']. We highlight stories on the web which are important to everyone - especially nerds. We also provide a soapbox for discussion moderated by the site's patrons, and allow anonymous discourse as there's no mandatory registration needed to comment.

We are mindful of community sentiment, and will not bend to overreaching corporate agenda. The goal is to be an excellent source for discussion and news about technology, art, science and politics.

We've incorporated as a Delaware Public Benefit Corporation (similar to a non-profit) as we feel our mission to provide a platform for news dissemination and relevant discussion is not only essential for mankind, but also a legal right (i.e. freedom of press, freedom of speech) in some places, and these are liberties which we aim to protect.

Though the site is young and there are [https://github.com/SoylentNews/rehash/issues bugs], we are improving and adapting to satisfy the community's needs. We look forward to pushing the boundaries of web experience and are committed to involving the community on all major decisions.

==Get Involved==

This project is run entirely by the community and there are many ways to contribute. Here are some of the many ways to participate:

*'''[http://soylentnews.org/submit.pl Submit a Story]'''
** Try joining the #rss-bot channel in [[SoylentNews:IRC|IRC]] for story ideas
*'''Volunteer'''
** Get in touch with the '''[[Development|Development Team]]''', especially if you know perl
** Reach out to one of the other '''[[TeamPages|Teams]]''' (we have openings for many skill sets)
** Contact the relevant person: '''[[WhosWho| Who's Who?]]'''
*Hop on to '''IRC:'''
** #Soylent on irc.soylentnews.org/6697
** [https://chat.soylentnews.org/ Webchat]
** [[SoylentNews:IRC|IRC Wiki Page]]
*'''Bugs''' and Features:
** [https://github.com/SoylentNews/rehash/issues/new Submit a bug or Feature Request]
** [[Suggestions|Add a Suggestion]] - larger projects to tackle for the future
*'''Tell Somebody''' A friend, a colleague, any major news source....
** Do what you can to [[Spreading the word|get the word out]]
** You could participate in [[The_Slashcott|The Slashcott]]

==Contacts==

A list of people working on this project:
===[[WhosWho| Who's Who?]]===

== Useful Links ==

*[[Submission guidelines]] - best practices for story submissions
*[[Story Style]] - a guide for editors on article formatting
*[[Development]] team page
**[https://github.com/SoylentNews/rehash Code Repo] - The Slashcode fork repository for this project on GitHub
** <strike>[[DevelopmentVMHowto]] - How to get our code setup in a VM</strike>
** [[SlashDocumentationIndex]]
*[[UserExperience]] team page
**[[Style]] - some of this info needs to be merged/moved/organized into/with [[UserExperience]]
**[[CssWork]]
* [[SystemAdministration|System Administration]]
*[[Finances]] - Breakdown of our proposed spending
*[[Licensing]] - ideas about which license to use for our slashcode fork
*[[Staff_Meetings|Staff Meeting Logs]]
*[[SoylentNews_PBC|SoylentNews PBC]]
*[[SoylentNews_Site_Policy|SoylentNews Policy]]
-------------------------------------------------
Administration - New Documents
*[[SoylentNews_Policy_New|Soylent Phoenix - Policy]]
*[[Definitions and Common Terms|Definitions and Common Terms]]
*[[Transfer Of Assets Agreement|Transfer Of Assets Agreement]]
*[[SoylentNews Phoenix - Bylaws (as submitted for Company Registration)|Soylent Phoenix - Bylaws (as submitted for Company Registration)]]
*[[SoylentNews Phoenix - Tax Exemption Status|Soylent Phoenix - Tax Exemption Status]]
*[[Soylent Phoenix - Bank Details|Soylent Phoenix - Wire Transfers (US and International)]]
*[[Discussion Policy|Discussion Policy]]
**

== Similar Projects ==
* [http://pipedot.org/ Pipedot] - A complete re-write that uses a modern codebase and sports a clean look
* Usenet newsgroup comp.misc - [https://groups.google.com/forum/#!forum/comp.misc on Google Groups], [http://squte.com/ on Squte], [news:comp.misc via newsreader application]
* [http://technocrat.net/ Technocrat] - (now defunct) News site presented by Bruce Perens

== Archive ==

[[Archive]] -- An archive of obsolete pages/discussions that occurred before launch

DRAFT - Discussion Policy

2025-02-04T12:00:12Z

Janrinok: /* Journals */

== Discussion Policy ==

=== Main Page Stories ===

The aim of the site is to enable free and open discussions on the topics published so that community members can express their personal views on the subject while allowing threads to develop into related ideas. This was the intention of the original site created in 2014 and it has remained so since that time. One of the many reasons for choosing to base the site in the USA is that US laws permit and encourage freedom of speech with few restrictions compared with other countries.

In order to qualify for a Tax Exempt Status (IRC Section 501(c)(3)) it is necessary to show a specific purpose which justifies such a status, and SoylentNews has stated that its primary focus is science, technology, engineering and mathematics which together are widely known as STEM. Nevertheless, the site editorial policy accepts a very wide interpretation of this description and frequently posts stories that are only loosely related to the stated range of topics. Often, they can be allocated to a standard topic description but sometimes they can be published under the 'Random' topic. All of the topics are open to site discussion. Additionally, all stories are categorized into sub-divisions, each of which is known as a nexus. This permits community members to filter out stories in which they have no specific interest.

=== Journals ===

The range of main page topics does restrict the discussion of matters that are outside the stated purpose of the site. This is resolved by allowing community members who have an active account to create 'journals' which may be on any topic whatsoever provided that they comply with the relevant US and State laws. SoylentNews accepts no responsibility for the content or views expressed in journals and this warning is clearly shown on each journal. The owner of a journal can limit those whom they wish to allow to comment. This is entirely at the owner's discretion and is not a matter in which the staff are involved, and nor should they be. Furthermore, the journal owner can also delete any or all journals that they own. Again, this is not a staff matter.

'''The content of journals is, therefore, solely the responsibility of the journal owner and, providing that they comply with US and State law, they are free to express any opinion, political view or extreme statement in their own journal'''.

If commenting is permitted in that journal then others can argue for or against such expressions as in any other discussion. However, those views should only be discussed in that journal. It is not appropriate to counter a view that someone has made in a journal by responding to it in a different discussion elsewhere on the site. That is, at best, off-topic and can endanger our tax status. Nor should anyone expect the staff to take any form of action against the journal owner. The journal has been published in compliance with the rules of the site and it is not a staff matter. It is an expression of free speech. Journals must comply with all aspects of site policy. Repeated attempts to raise a personal objection against the owner of a journal, or against the ideas, views or content expressed in a journal, outside that journal discussion may constitute an abuse of the site.

The only acceptable ways to counter a journal that you strongly disagree with is argue against the views by commenting inside that journal, or to moderate the comments in that journal if you are able to do so, or to create your own journal and present your counter arguments and views. Alternatively, you can simply stop reading that person's journals.

Soylent Phoenix - Bank Details

2024-12-16T09:03:08Z

Janrinok:

'''International wire transfers''' can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
U.S. Bank's Swift Code: USBKUS44IMT<br>

'''Within the USA''', wire transfers can be made using the following information:

Full Name: Soylent Phoenix<br>
Account number: 153699974314<br>
Routing number: 123000220<br>

In all cases, please use your Nickname and User ID as a reference if you wish to have your SN account credited with the subscription. Without a reference the the transfer will be treated as an anonymous donation.

Definitions and Common Terms

2024-12-15T19:33:46Z

Janrinok: /* SPAM */

= DEFINITIONS AND COMMON TERMS =

== DEFINITIONS ==

=== SPAM ===

The definition of Spam used on this site was adopted in 2021 and it is as published on Wikipedia (https://en.wikipedia.org/wiki/Spamming):
<blockquote>Spamming is the use of messaging systems to send multiple unsolicited messages (spam) to large numbers of recipients for the purpose of commercial advertising, non-commercial proselytizing, or any prohibited purpose (especially phishing), or simply repeatedly sending the same message to the same user. While the most widely recognized form of spam is email spam, the term is applied to similar abuses in other media: instant messaging spam, Usenet newsgroup spam, Web search engine spam, spam in blogs, wiki spam, online classified ads spam, mobile phone messaging spam, Internet forum spam, junk fax transmissions, social spam, spam mobile apps,television advertising and file sharing spam.</blockquote>

Spamming is forbidden on the site.

=== DOXXING (aka DOXING) ===

Doxxing is the intentional compromise or publication of personally identifiable information belonging to another individual, regardless of its source. As it can be difficult to verify the accuracy of PII if there is any doubt then it is assumed to be both accurate and an intentional attempt at doxxing.

Doxxing is forbidden on the site.

== COMMON TERMS ==

=== Board ===

The group of people who represent the formal and legal face of the site. They are formally recorded on the site documentation which is provided to the necessary State and Government departments. They are the highest authority on the site.

=== Management Group ===

The group of staff comprising of Team Leaders and Administrators who manage the day-to-day running of the site.

=== Team Leader ===

The senior or elected person of one or more of the functional teams which make up the Staff.

=== Personally Identifiable Information (PII) ===

PII is information that enables a person to be identified and is defined in the US as:

<blockquote>Information that can be used to distinguish or trace an individual's identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or recognizing linked or linkable information, such as date and place of birth, as well as the mother's maiden name, in official standards like the NIST Guide, demonstrates a proactive approach to ensuring robust privacy safeguards amid the dynamic landscape of data security. This integration into established standards is a foundational framework for organizations to adopt and implement effective measures in safeguarding individuals' personal information.</blockquote>

As some of our community are also covered by EU legislation, the EU definition is broader and is as follows:

<blockquote>Any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</blockquote>

SoylentNews Policy New

2024-12-15T19:25:24Z

Janrinok: /* Waiving of Subscription Fees */

== Privacy, Copyright, Disclaimers, Terms of Use, and DMCA (07 Dec 2024) ==

<b>The following pages may be revised and/or amended from time to time</b>

The SoylentNews site is currently based in the United States and is registered in the State of Oregon. As such, it is important to state the policy of SoylentNews with respect to certain laws in effect there as well as internationally.

=== Privacy Policy ===

It is the policy of SoylentNews, in as much as is reasonably possible, to retain the least amount of personally identifiable information about community members. Certain items are necessary in the conduct of the site's operation. These include, but are not necessarily restricted to: email address, IP data (either in plain or hashed form), and other personal information that users may optionally add to their own user page.

=== Copyright Notice ===

There are several places on the site where user-supplied content is published.

==== Submitted Stories ====
Anyone may submit a story for consideration by the editors for publication on the site. Editors attempt, within the site's guidelines ([[Submission_guidelines]]) to provide a consistent reading experience for the community. This may entail reformatting, rewriting, spelling corrections, and the like. The revised submission may then be published on the site for registered community members to read and comment on. Subsequent to publishing to the site additional edits may be made so as to correct mistakes (e.g. typos) and/or to add additional information, etc.

The original submitter retains copyright to their submission.

The original submitter grants a non-exclusive right to SoylentNews to publish the story.

==== Published Stories ====

SoylentNews retains copyright to the story as published on the site.

==== Journal Submissions ====

Each logged-in user has the ability to post "stories" to their journal in which they may discuss any topic they wish providing that it is permissible under US law. The submitter may edit (if they have the appropriate user permissions) or even delete any of their journal postings. Furthermore, they may restrict the ability of other users to comment in the journal as provided by the software.

The comments are owned by whoever posted them. SoylentNews is not responsible for them in any way. A statement to this effect will be displayed on each journal.

==== User Comments ====

The community is encouraged to provide comments in response to stories published on the site as well as to journal entries in which that option has been enabled. The site reserves the right to limit comments to some stories to logged-in users only, at its discretion. Comments may be submitted anonymously where such comments are enabled, as an Anonymous Coward, or attibuted the user's site Nickname.

In either case, the site's policy is stated on each story page:

<blockquote>The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.</blockquote>

Please note that comments are published under the Creative Commons Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]unless otherwise indicated.

==== Wiki Entries ====

Copyright on entries on the site's Wikipedia page are governed by this statement which appears at the bottom of each page:
<blockquote>Content is available under Creative Commons Attribution Share Alike license unless otherwise noted.</blockquote>

Further, when submitting to the Wiki, this notice appears above the "Save page", "Show Preview", and "Show changes" buttons:

<blockquote>Please note that all contributions to SoylentNews are considered to be released under the Creative Commons Attribution Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. <b>Do not submit copyrighted work without permission!</b></blockquote>

==== IRC (Internet Relay Chat) ====
The submitter of anything posted to any of the site's IRC channels specifically allows the site to retain anything posted there and make it available, for example, in the form of retained logs. In addition, any chats that take place in the form of staff meetings, board meetings, and the like will be retained and may be posted on the site Wiki.

==== SoylentCode (rehash) ====
The site is based on Slashcode (Version unknown) which is under a GPL v2 license. Wherever possible, commensurate with maintaining site security, any new or updated code originated by SoylentNews will retain this licensing and be made available for downloading by any individual in accord with this license. Links will be maintained on the site to enable the repository of the code to be easily located.

=== Disclaimers ===
* Content published on this website is for general information purposes only.
* SoylentNews offers no representations or warranties of any kind, expressed or implied, regarding completeness, accuracy, reliability, suitability or availability of this website, published information and related graphics or hyperlinks contained on this website for any purpose. Use of such information is therefore at your own risk.
* In no event shall SoylentNews or its affiliates be held liable for any losses or damages including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or revenue arising out of, or in connection with, the use of this website.
* SoylentNews has no control over the nature, content, and availability of hyperlinked websites. The inclusion of hyperlinks to other websites is for reference or informative purposes only and does not imply endorsement of them.
* Availability is not guaranteed. SoylentNews takes no responsibility for, and will not be liable for, this website being unavailable for any reason.

=== Terms of Use ===

Use of this website is subject to your agreement with the following terms, as well as your agreement with the Privacy Policy, Copyright Notice, and Disclaimer. You should review these terms and related documents regularly as they may be revised at any time without notice.

The date that these terms were last modified can be found at the top of the page.
* Use of this website and any disputes arising out of such use of this website are subject to the laws of the United States of America, and where applicable, the State of Oregon.
* All registered trademarks reproduced remain property of their respective owners.
* Unauthorized use of this website may give rise to a claim for damages and/or be a criminal offense.
* This website includes links to third party websites. These links are provided for your convenience to provide further information, and does not signify endorsement.
* Availability of this website is not guaranteed.
* Spamming, hacking and/or phishing this website is not permitted.
* Doxxing of community members is strictly forbidden regardless of the source of the information. Wherever personal information is published by anyone other than the person that it relates to it will be assumed to be accurate and may be assessed as being an attempt at doxxing.
* These terms, as well as terms in the related documents, shall remain continuously in force if there is a change to the domain of this website.

== Subscription Fees ==

=== Community Fees ===

The Board may choose to offer a subscription membership fee to some or all members of the SoylentNews community. Nevertheless, non-payment of the subscription fee will not prevent access to the site; the intention is to enable the site to be viewed by as many people as possible and to encourage them to submit stories for publication and to comment on the stories that have already been accepted and released.

=== Waiving of Subscription Fees ===

Once an individual has served as a staff member for 3 months he is no longer required to pay subscription fees to enjoy all the privileges of site membership. This privilege will remain for the period of their service on the staff, plus a discretionary extension of a maximum of 1 year from the individual leaving the staff. The actual duration will be decided by the Management Group (MG) (which comprises of Administrators and Team Leaders (TLs)).

Occasionally, the Management Group (MG) might recommend to the Board that an individual be granted lifetime site membership in recognition of a significant period of service, or being a prominent figure from any relevant field of technology or related interests, or some other act deserving of special recognition. The Board can accept or reject such recommendations as they deem fit.

== Site Control and Security ==

=== Access to Personal Data ===

No personal data held by the site will be shared, sold or otherwise distributed outside of the site with the exception of demands supported by the appropriate legal documentation served upon the Board.

Personal data shall be held by the site for the minimum time necessary, and efforts should be made to anonymize or encrypt such data wherever possible.

=== Abusive Behaviour ===

SoylentNews aims to be tolerant of any individual's personal views and will allow them to express their views in the comments of published stories. However, occasionally, individuals will not express their views relating to a story but will employ offensive and/or abusive behaviour towards an individual. This is not in the spirit of the site and a graduated response will be adopted to anyone who employs such behaviour in their comments.

*The moderation system employed usually results in offensive, abusive or off-topic information being reduced to the lowest viewable priority level such that, to most regular users of the site, it does not even display on their screen. Often, this is sufficient to defuse the situation and the offender departs after a short period of time. However, community members should also be encouraged not to 'feed the trolls' and to avoid responding to any posts by the offender. Staff should adopt a non-confrontational attitude while engaging with community members and the offender in an attempt to cool the situation down.

*A member of staff should issue a comment in which he politely but firmly requests that the offender stops his offensive/abusive behaviour while explaining that it does nothing to contribute to the site nor does it show the offender in a positive light. However, it is important to try to identify the true cause of the offenders attitude and for the staff member, alone or with the assistance of other members of staff, to try to resolve any genuine issues or grievances that the offender may have.

*A Team Leader or senior staff member should attempt to engage the offender in a private communication (either IRC/PM, email or whatever) and warn the offender that there could be serious consequences if the offender continues with his current course of action.

* The offender should be encouraged to submit a formal complaint by email to the Board using the "admin@soylentnews.org" email address. A formal complaint cannot be submitted anonymously but it may use a secure or temporary email provider. The Board shall then decide how the formal complaint should be resolved.

* The MG can agree to ban the offender for a specific period or permanently and take action to do so. There are, of course, technical difficulties associated with effectively banning an individual but a block of his personal IPs for each computer system as and when they are identified might be considered as a reasonable action. Other measures may be taken as necessary.

* Persistent site abuse, when all of the above measures have been exhausted, may result in the abuse being removed from display.

=== Control of SPAM ===

SPAM is most often found in story submissions (either as a link in an submission or as the entire contents of a submission) or in the comments to a published story. The definition of SPAM is that provided by Wikipedia and can be found in the [[Definitions and Common Terms]].

=== Control of Access and Password Policy ===

No-one should be given access privileges above those which are essential for them to complete their role. Additionally, no single individual should have a unique set of privileges because, in the event of some unforeseen circumstance, no other individual will be able to fulfill the same role. TLs should ensure that each task for which his team is responsible is documented and that privileges are assigned to team members as required.

In the event of a member of staff permanently leaving then a SuperAdmin is responsible for ensuring that access privileges are removed for that individual promptly. Shared passwords known by the individual, where they exist, should also be changed.

=== Response to Denial Of Service (DOS) Attack ===

The management and control of a Denial of Service (DOS) attack is the responsibility of the Systems Team, and may be more detailed by listing actions to be taken by one or more teams.

SoylentNews Policy New

2024-12-15T19:18:52Z

Janrinok: /* Disclaimers */

== Privacy, Copyright, Disclaimers, Terms of Use, and DMCA (07 Dec 2024) ==

<b>The following pages may be revised and/or amended from time to time</b>

The SoylentNews site is currently based in the United States and is registered in the State of Oregon. As such, it is important to state the policy of SoylentNews with respect to certain laws in effect there as well as internationally.

=== Privacy Policy ===

It is the policy of SoylentNews, in as much as is reasonably possible, to retain the least amount of personally identifiable information about community members. Certain items are necessary in the conduct of the site's operation. These include, but are not necessarily restricted to: email address, IP data (either in plain or hashed form), and other personal information that users may optionally add to their own user page.

=== Copyright Notice ===

There are several places on the site where user-supplied content is published.

==== Submitted Stories ====
Anyone may submit a story for consideration by the editors for publication on the site. Editors attempt, within the site's guidelines ([[Submission_guidelines]]) to provide a consistent reading experience for the community. This may entail reformatting, rewriting, spelling corrections, and the like. The revised submission may then be published on the site for registered community members to read and comment on. Subsequent to publishing to the site additional edits may be made so as to correct mistakes (e.g. typos) and/or to add additional information, etc.

The original submitter retains copyright to their submission.

The original submitter grants a non-exclusive right to SoylentNews to publish the story.

==== Published Stories ====

SoylentNews retains copyright to the story as published on the site.

==== Journal Submissions ====

Each logged-in user has the ability to post "stories" to their journal in which they may discuss any topic they wish providing that it is permissible under US law. The submitter may edit (if they have the appropriate user permissions) or even delete any of their journal postings. Furthermore, they may restrict the ability of other users to comment in the journal as provided by the software.

The comments are owned by whoever posted them. SoylentNews is not responsible for them in any way. A statement to this effect will be displayed on each journal.

==== User Comments ====

The community is encouraged to provide comments in response to stories published on the site as well as to journal entries in which that option has been enabled. The site reserves the right to limit comments to some stories to logged-in users only, at its discretion. Comments may be submitted anonymously where such comments are enabled, as an Anonymous Coward, or attibuted the user's site Nickname.

In either case, the site's policy is stated on each story page:

<blockquote>The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.</blockquote>

Please note that comments are published under the Creative Commons Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]unless otherwise indicated.

==== Wiki Entries ====

Copyright on entries on the site's Wikipedia page are governed by this statement which appears at the bottom of each page:
<blockquote>Content is available under Creative Commons Attribution Share Alike license unless otherwise noted.</blockquote>

Further, when submitting to the Wiki, this notice appears above the "Save page", "Show Preview", and "Show changes" buttons:

<blockquote>Please note that all contributions to SoylentNews are considered to be released under the Creative Commons Attribution Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. <b>Do not submit copyrighted work without permission!</b></blockquote>

==== IRC (Internet Relay Chat) ====
The submitter of anything posted to any of the site's IRC channels specifically allows the site to retain anything posted there and make it available, for example, in the form of retained logs. In addition, any chats that take place in the form of staff meetings, board meetings, and the like will be retained and may be posted on the site Wiki.

==== SoylentCode (rehash) ====
The site is based on Slashcode (Version unknown) which is under a GPL v2 license. Wherever possible, commensurate with maintaining site security, any new or updated code originated by SoylentNews will retain this licensing and be made available for downloading by any individual in accord with this license. Links will be maintained on the site to enable the repository of the code to be easily located.

=== Disclaimers ===
* Content published on this website is for general information purposes only.
* SoylentNews offers no representations or warranties of any kind, expressed or implied, regarding completeness, accuracy, reliability, suitability or availability of this website, published information and related graphics or hyperlinks contained on this website for any purpose. Use of such information is therefore at your own risk.
* In no event shall SoylentNews or its affiliates be held liable for any losses or damages including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or revenue arising out of, or in connection with, the use of this website.
* SoylentNews has no control over the nature, content, and availability of hyperlinked websites. The inclusion of hyperlinks to other websites is for reference or informative purposes only and does not imply endorsement of them.
* Availability is not guaranteed. SoylentNews takes no responsibility for, and will not be liable for, this website being unavailable for any reason.

=== Terms of Use ===

Use of this website is subject to your agreement with the following terms, as well as your agreement with the Privacy Policy, Copyright Notice, and Disclaimer. You should review these terms and related documents regularly as they may be revised at any time without notice.

The date that these terms were last modified can be found at the top of the page.
* Use of this website and any disputes arising out of such use of this website are subject to the laws of the United States of America, and where applicable, the State of Oregon.
* All registered trademarks reproduced remain property of their respective owners.
* Unauthorized use of this website may give rise to a claim for damages and/or be a criminal offense.
* This website includes links to third party websites. These links are provided for your convenience to provide further information, and does not signify endorsement.
* Availability of this website is not guaranteed.
* Spamming, hacking and/or phishing this website is not permitted.
* Doxxing of community members is strictly forbidden regardless of the source of the information. Wherever personal information is published by anyone other than the person that it relates to it will be assumed to be accurate and may be assessed as being an attempt at doxxing.
* These terms, as well as terms in the related documents, shall remain continuously in force if there is a change to the domain of this website.

== Subscription Fees ==

=== Community Fees ===

The Board may choose to offer a subscription membership fee to some or all members of the SoylentNews community. Nevertheless, non-payment of the subscription fee will not prevent access to the site; the intention is to enable the site to be viewed by as many people as possible and to encourage them to submit stories for publication and to comment on the stories that have already been accepted and released.

=== Waiving of Subscription Fees ===

Once an individual has served as a staff member for 3 months he is no longer required to pay subscription fees to enjoy all the privileges of site membership. This privilege will remain for the period of their service on the staff, plus a discretionary extension of a maximum of 1 year from the individual leaving the staff. The actual duration will be decided by the MG.

Occasionally, the Management Group (MG) (which comprises of Administrators and Team Leaders (TLs) might recommend to the Board that an individual be granted lifetime site membership in recognition of a significant period of service, or being a prominent figure from any relevant field of technology or related interests, or some other act deserving of special recognition. The Board can accept or reject such recommendations as they deem fit.

== Site Control and Security ==

=== Access to Personal Data ===

No personal data held by the site will be shared, sold or otherwise distributed outside of the site with the exception of demands supported by the appropriate legal documentation served upon the Board.

Personal data shall be held by the site for the minimum time necessary, and efforts should be made to anonymize or encrypt such data wherever possible.

=== Abusive Behaviour ===

SoylentNews aims to be tolerant of any individual's personal views and will allow them to express their views in the comments of published stories. However, occasionally, individuals will not express their views relating to a story but will employ offensive and/or abusive behaviour towards an individual. This is not in the spirit of the site and a graduated response will be adopted to anyone who employs such behaviour in their comments.

*The moderation system employed usually results in offensive, abusive or off-topic information being reduced to the lowest viewable priority level such that, to most regular users of the site, it does not even display on their screen. Often, this is sufficient to defuse the situation and the offender departs after a short period of time. However, community members should also be encouraged not to 'feed the trolls' and to avoid responding to any posts by the offender. Staff should adopt a non-confrontational attitude while engaging with community members and the offender in an attempt to cool the situation down.

*A member of staff should issue a comment in which he politely but firmly requests that the offender stops his offensive/abusive behaviour while explaining that it does nothing to contribute to the site nor does it show the offender in a positive light. However, it is important to try to identify the true cause of the offenders attitude and for the staff member, alone or with the assistance of other members of staff, to try to resolve any genuine issues or grievances that the offender may have.

*A Team Leader or senior staff member should attempt to engage the offender in a private communication (either IRC/PM, email or whatever) and warn the offender that there could be serious consequences if the offender continues with his current course of action.

* The offender should be encouraged to submit a formal complaint by email to the Board using the "admin@soylentnews.org" email address. A formal complaint cannot be submitted anonymously but it may use a secure or temporary email provider. The Board shall then decide how the formal complaint should be resolved.

* The MG can agree to ban the offender for a specific period or permanently and take action to do so. There are, of course, technical difficulties associated with effectively banning an individual but a block of his personal IPs for each computer system as and when they are identified might be considered as a reasonable action. Other measures may be taken as necessary.

* Persistent site abuse, when all of the above measures have been exhausted, may result in the abuse being removed from display.

=== Control of SPAM ===

SPAM is most often found in story submissions (either as a link in an submission or as the entire contents of a submission) or in the comments to a published story. The definition of SPAM is that provided by Wikipedia and can be found in the [[Definitions and Common Terms]].

=== Control of Access and Password Policy ===

No-one should be given access privileges above those which are essential for them to complete their role. Additionally, no single individual should have a unique set of privileges because, in the event of some unforeseen circumstance, no other individual will be able to fulfill the same role. TLs should ensure that each task for which his team is responsible is documented and that privileges are assigned to team members as required.

In the event of a member of staff permanently leaving then a SuperAdmin is responsible for ensuring that access privileges are removed for that individual promptly. Shared passwords known by the individual, where they exist, should also be changed.

=== Response to Denial Of Service (DOS) Attack ===

The management and control of a Denial of Service (DOS) attack is the responsibility of the Systems Team, and may be more detailed by listing actions to be taken by one or more teams.

SoylentNews Policy New

2024-12-15T19:17:26Z

Janrinok: /* Wiki Entries */

== Privacy, Copyright, Disclaimers, Terms of Use, and DMCA (07 Dec 2024) ==

<b>The following pages may be revised and/or amended from time to time</b>

The SoylentNews site is currently based in the United States and is registered in the State of Oregon. As such, it is important to state the policy of SoylentNews with respect to certain laws in effect there as well as internationally.

=== Privacy Policy ===

It is the policy of SoylentNews, in as much as is reasonably possible, to retain the least amount of personally identifiable information about community members. Certain items are necessary in the conduct of the site's operation. These include, but are not necessarily restricted to: email address, IP data (either in plain or hashed form), and other personal information that users may optionally add to their own user page.

=== Copyright Notice ===

There are several places on the site where user-supplied content is published.

==== Submitted Stories ====
Anyone may submit a story for consideration by the editors for publication on the site. Editors attempt, within the site's guidelines ([[Submission_guidelines]]) to provide a consistent reading experience for the community. This may entail reformatting, rewriting, spelling corrections, and the like. The revised submission may then be published on the site for registered community members to read and comment on. Subsequent to publishing to the site additional edits may be made so as to correct mistakes (e.g. typos) and/or to add additional information, etc.

The original submitter retains copyright to their submission.

The original submitter grants a non-exclusive right to SoylentNews to publish the story.

==== Published Stories ====

SoylentNews retains copyright to the story as published on the site.

==== Journal Submissions ====

Each logged-in user has the ability to post "stories" to their journal in which they may discuss any topic they wish providing that it is permissible under US law. The submitter may edit (if they have the appropriate user permissions) or even delete any of their journal postings. Furthermore, they may restrict the ability of other users to comment in the journal as provided by the software.

The comments are owned by whoever posted them. SoylentNews is not responsible for them in any way. A statement to this effect will be displayed on each journal.

==== User Comments ====

The community is encouraged to provide comments in response to stories published on the site as well as to journal entries in which that option has been enabled. The site reserves the right to limit comments to some stories to logged-in users only, at its discretion. Comments may be submitted anonymously where such comments are enabled, as an Anonymous Coward, or attibuted the user's site Nickname.

In either case, the site's policy is stated on each story page:

<blockquote>The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.</blockquote>

Please note that comments are published under the Creative Commons Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]unless otherwise indicated.

==== Wiki Entries ====

Copyright on entries on the site's Wikipedia page are governed by this statement which appears at the bottom of each page:
<blockquote>Content is available under Creative Commons Attribution Share Alike license unless otherwise noted.</blockquote>

Further, when submitting to the Wiki, this notice appears above the "Save page", "Show Preview", and "Show changes" buttons:

<blockquote>Please note that all contributions to SoylentNews are considered to be released under the Creative Commons Attribution Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. <b>Do not submit copyrighted work without permission!</b></blockquote>

==== IRC (Internet Relay Chat) ====
The submitter of anything posted to any of the site's IRC channels specifically allows the site to retain anything posted there and make it available, for example, in the form of retained logs. In addition, any chats that take place in the form of staff meetings, board meetings, and the like will be retained and may be posted on the site Wiki.

==== SoylentCode (rehash) ====
The site is based on Slashcode (Version unknown) which is under a GPL v2 license. Wherever possible, commensurate with maintaining site security, any new or updated code originated by SoylentNews will retain this licensing and be made available for downloading by any individual in accord with this license. Links will be maintained on the site to enable the repository of the code to be easily located.

=== Disclaimers ===
* Content published on this website is for general information purposes only.
* SoylentNews offers no representations or warranties of any kind, express or implied, regarding completeness, accuracy, reliability, suitability or availability of this website, published information and related graphics or hyperlinks contained on this website for any purpose. Use of such information is therefore at your own risk.
* In no event shall SoylentNews or its affiliates be held liable for any losses or damages including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or revenue arising out of, or in connection with, the use of this website.
* SoylentNews has no control over the nature, content, and availability of hyperlinked websites. The inclusion of hyperlinks to other websites is for reference or informative purposes only and does not imply endorsement of them.
* Availability is not guaranteed. SoylentNews takes no responsibility for, and will not be liable for, this website being unavailable for any reason.

=== Terms of Use ===

Use of this website is subject to your agreement with the following terms, as well as your agreement with the Privacy Policy, Copyright Notice, and Disclaimer. You should review these terms and related documents regularly as they may be revised at any time without notice.

The date that these terms were last modified can be found at the top of the page.
* Use of this website and any disputes arising out of such use of this website are subject to the laws of the United States of America, and where applicable, the State of Oregon.
* All registered trademarks reproduced remain property of their respective owners.
* Unauthorized use of this website may give rise to a claim for damages and/or be a criminal offense.
* This website includes links to third party websites. These links are provided for your convenience to provide further information, and does not signify endorsement.
* Availability of this website is not guaranteed.
* Spamming, hacking and/or phishing this website is not permitted.
* Doxxing of community members is strictly forbidden regardless of the source of the information. Wherever personal information is published by anyone other than the person that it relates to it will be assumed to be accurate and may be assessed as being an attempt at doxxing.
* These terms, as well as terms in the related documents, shall remain continuously in force if there is a change to the domain of this website.

== Subscription Fees ==

=== Community Fees ===

The Board may choose to offer a subscription membership fee to some or all members of the SoylentNews community. Nevertheless, non-payment of the subscription fee will not prevent access to the site; the intention is to enable the site to be viewed by as many people as possible and to encourage them to submit stories for publication and to comment on the stories that have already been accepted and released.

=== Waiving of Subscription Fees ===

Once an individual has served as a staff member for 3 months he is no longer required to pay subscription fees to enjoy all the privileges of site membership. This privilege will remain for the period of their service on the staff, plus a discretionary extension of a maximum of 1 year from the individual leaving the staff. The actual duration will be decided by the MG.

Occasionally, the Management Group (MG) (which comprises of Administrators and Team Leaders (TLs) might recommend to the Board that an individual be granted lifetime site membership in recognition of a significant period of service, or being a prominent figure from any relevant field of technology or related interests, or some other act deserving of special recognition. The Board can accept or reject such recommendations as they deem fit.

== Site Control and Security ==

=== Access to Personal Data ===

No personal data held by the site will be shared, sold or otherwise distributed outside of the site with the exception of demands supported by the appropriate legal documentation served upon the Board.

Personal data shall be held by the site for the minimum time necessary, and efforts should be made to anonymize or encrypt such data wherever possible.

=== Abusive Behaviour ===

SoylentNews aims to be tolerant of any individual's personal views and will allow them to express their views in the comments of published stories. However, occasionally, individuals will not express their views relating to a story but will employ offensive and/or abusive behaviour towards an individual. This is not in the spirit of the site and a graduated response will be adopted to anyone who employs such behaviour in their comments.

*The moderation system employed usually results in offensive, abusive or off-topic information being reduced to the lowest viewable priority level such that, to most regular users of the site, it does not even display on their screen. Often, this is sufficient to defuse the situation and the offender departs after a short period of time. However, community members should also be encouraged not to 'feed the trolls' and to avoid responding to any posts by the offender. Staff should adopt a non-confrontational attitude while engaging with community members and the offender in an attempt to cool the situation down.

*A member of staff should issue a comment in which he politely but firmly requests that the offender stops his offensive/abusive behaviour while explaining that it does nothing to contribute to the site nor does it show the offender in a positive light. However, it is important to try to identify the true cause of the offenders attitude and for the staff member, alone or with the assistance of other members of staff, to try to resolve any genuine issues or grievances that the offender may have.

*A Team Leader or senior staff member should attempt to engage the offender in a private communication (either IRC/PM, email or whatever) and warn the offender that there could be serious consequences if the offender continues with his current course of action.

* The offender should be encouraged to submit a formal complaint by email to the Board using the "admin@soylentnews.org" email address. A formal complaint cannot be submitted anonymously but it may use a secure or temporary email provider. The Board shall then decide how the formal complaint should be resolved.

* The MG can agree to ban the offender for a specific period or permanently and take action to do so. There are, of course, technical difficulties associated with effectively banning an individual but a block of his personal IPs for each computer system as and when they are identified might be considered as a reasonable action. Other measures may be taken as necessary.

* Persistent site abuse, when all of the above measures have been exhausted, may result in the abuse being removed from display.

=== Control of SPAM ===

SPAM is most often found in story submissions (either as a link in an submission or as the entire contents of a submission) or in the comments to a published story. The definition of SPAM is that provided by Wikipedia and can be found in the [[Definitions and Common Terms]].

=== Control of Access and Password Policy ===

No-one should be given access privileges above those which are essential for them to complete their role. Additionally, no single individual should have a unique set of privileges because, in the event of some unforeseen circumstance, no other individual will be able to fulfill the same role. TLs should ensure that each task for which his team is responsible is documented and that privileges are assigned to team members as required.

In the event of a member of staff permanently leaving then a SuperAdmin is responsible for ensuring that access privileges are removed for that individual promptly. Shared passwords known by the individual, where they exist, should also be changed.

=== Response to Denial Of Service (DOS) Attack ===

The management and control of a Denial of Service (DOS) attack is the responsibility of the Systems Team, and may be more detailed by listing actions to be taken by one or more teams.

SoylentNews Policy New

2024-12-15T19:16:40Z

Janrinok: /* User Comments */

== Privacy, Copyright, Disclaimers, Terms of Use, and DMCA (07 Dec 2024) ==

<b>The following pages may be revised and/or amended from time to time</b>

The SoylentNews site is currently based in the United States and is registered in the State of Oregon. As such, it is important to state the policy of SoylentNews with respect to certain laws in effect there as well as internationally.

=== Privacy Policy ===

It is the policy of SoylentNews, in as much as is reasonably possible, to retain the least amount of personally identifiable information about community members. Certain items are necessary in the conduct of the site's operation. These include, but are not necessarily restricted to: email address, IP data (either in plain or hashed form), and other personal information that users may optionally add to their own user page.

=== Copyright Notice ===

There are several places on the site where user-supplied content is published.

==== Submitted Stories ====
Anyone may submit a story for consideration by the editors for publication on the site. Editors attempt, within the site's guidelines ([[Submission_guidelines]]) to provide a consistent reading experience for the community. This may entail reformatting, rewriting, spelling corrections, and the like. The revised submission may then be published on the site for registered community members to read and comment on. Subsequent to publishing to the site additional edits may be made so as to correct mistakes (e.g. typos) and/or to add additional information, etc.

The original submitter retains copyright to their submission.

The original submitter grants a non-exclusive right to SoylentNews to publish the story.

==== Published Stories ====

SoylentNews retains copyright to the story as published on the site.

==== Journal Submissions ====

Each logged-in user has the ability to post "stories" to their journal in which they may discuss any topic they wish providing that it is permissible under US law. The submitter may edit (if they have the appropriate user permissions) or even delete any of their journal postings. Furthermore, they may restrict the ability of other users to comment in the journal as provided by the software.

The comments are owned by whoever posted them. SoylentNews is not responsible for them in any way. A statement to this effect will be displayed on each journal.

==== User Comments ====

The community is encouraged to provide comments in response to stories published on the site as well as to journal entries in which that option has been enabled. The site reserves the right to limit comments to some stories to logged-in users only, at its discretion. Comments may be submitted anonymously where such comments are enabled, as an Anonymous Coward, or attibuted the user's site Nickname.

In either case, the site's policy is stated on each story page:

<blockquote>The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.</blockquote>

Please note that comments are published under the Creative Commons Share Alike license [https://creativecommons.org/licenses/by-sa/4.0/deed.en]unless otherwise indicated.

==== Wiki Entries ====

Copyright on entries on the site's Wikipedia page are governed by this statement which appears at the bottom of each page:
<blockquote>Content is available under Creative Commons Attribution Share Alike unless otherwise noted.</blockquote>

Further, when submitting to the Wiki, this notice appears above the "Save page", "Show Preview", and "Show changes" buttons:

<blockquote>Please note that all contributions to SoylentNews are considered to be released under the Creative Commons Attribution Share Alike [https://creativecommons.org/licenses/by-sa/4.0/deed.en]. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. <b>Do not submit copyrighted work without permission!</b></blockquote>

==== IRC (Internet Relay Chat) ====
The submitter of anything posted to any of the site's IRC channels specifically allows the site to retain anything posted there and make it available, for example, in the form of retained logs. In addition, any chats that take place in the form of staff meetings, board meetings, and the like will be retained and may be posted on the site Wiki.

==== SoylentCode (rehash) ====
The site is based on Slashcode (Version unknown) which is under a GPL v2 license. Wherever possible, commensurate with maintaining site security, any new or updated code originated by SoylentNews will retain this licensing and be made available for downloading by any individual in accord with this license. Links will be maintained on the site to enable the repository of the code to be easily located.

=== Disclaimers ===
* Content published on this website is for general information purposes only.
* SoylentNews offers no representations or warranties of any kind, express or implied, regarding completeness, accuracy, reliability, suitability or availability of this website, published information and related graphics or hyperlinks contained on this website for any purpose. Use of such information is therefore at your own risk.
* In no event shall SoylentNews or its affiliates be held liable for any losses or damages including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or revenue arising out of, or in connection with, the use of this website.
* SoylentNews has no control over the nature, content, and availability of hyperlinked websites. The inclusion of hyperlinks to other websites is for reference or informative purposes only and does not imply endorsement of them.
* Availability is not guaranteed. SoylentNews takes no responsibility for, and will not be liable for, this website being unavailable for any reason.

=== Terms of Use ===

Use of this website is subject to your agreement with the following terms, as well as your agreement with the Privacy Policy, Copyright Notice, and Disclaimer. You should review these terms and related documents regularly as they may be revised at any time without notice.

The date that these terms were last modified can be found at the top of the page.
* Use of this website and any disputes arising out of such use of this website are subject to the laws of the United States of America, and where applicable, the State of Oregon.
* All registered trademarks reproduced remain property of their respective owners.
* Unauthorized use of this website may give rise to a claim for damages and/or be a criminal offense.
* This website includes links to third party websites. These links are provided for your convenience to provide further information, and does not signify endorsement.
* Availability of this website is not guaranteed.
* Spamming, hacking and/or phishing this website is not permitted.
* Doxxing of community members is strictly forbidden regardless of the source of the information. Wherever personal information is published by anyone other than the person that it relates to it will be assumed to be accurate and may be assessed as being an attempt at doxxing.
* These terms, as well as terms in the related documents, shall remain continuously in force if there is a change to the domain of this website.

== Subscription Fees ==

=== Community Fees ===

The Board may choose to offer a subscription membership fee to some or all members of the SoylentNews community. Nevertheless, non-payment of the subscription fee will not prevent access to the site; the intention is to enable the site to be viewed by as many people as possible and to encourage them to submit stories for publication and to comment on the stories that have already been accepted and released.

=== Waiving of Subscription Fees ===

Once an individual has served as a staff member for 3 months he is no longer required to pay subscription fees to enjoy all the privileges of site membership. This privilege will remain for the period of their service on the staff, plus a discretionary extension of a maximum of 1 year from the individual leaving the staff. The actual duration will be decided by the MG.

Occasionally, the Management Group (MG) (which comprises of Administrators and Team Leaders (TLs) might recommend to the Board that an individual be granted lifetime site membership in recognition of a significant period of service, or being a prominent figure from any relevant field of technology or related interests, or some other act deserving of special recognition. The Board can accept or reject such recommendations as they deem fit.

== Site Control and Security ==

=== Access to Personal Data ===

No personal data held by the site will be shared, sold or otherwise distributed outside of the site with the exception of demands supported by the appropriate legal documentation served upon the Board.

Personal data shall be held by the site for the minimum time necessary, and efforts should be made to anonymize or encrypt such data wherever possible.

=== Abusive Behaviour ===

SoylentNews aims to be tolerant of any individual's personal views and will allow them to express their views in the comments of published stories. However, occasionally, individuals will not express their views relating to a story but will employ offensive and/or abusive behaviour towards an individual. This is not in the spirit of the site and a graduated response will be adopted to anyone who employs such behaviour in their comments.

*The moderation system employed usually results in offensive, abusive or off-topic information being reduced to the lowest viewable priority level such that, to most regular users of the site, it does not even display on their screen. Often, this is sufficient to defuse the situation and the offender departs after a short period of time. However, community members should also be encouraged not to 'feed the trolls' and to avoid responding to any posts by the offender. Staff should adopt a non-confrontational attitude while engaging with community members and the offender in an attempt to cool the situation down.

*A member of staff should issue a comment in which he politely but firmly requests that the offender stops his offensive/abusive behaviour while explaining that it does nothing to contribute to the site nor does it show the offender in a positive light. However, it is important to try to identify the true cause of the offenders attitude and for the staff member, alone or with the assistance of other members of staff, to try to resolve any genuine issues or grievances that the offender may have.

*A Team Leader or senior staff member should attempt to engage the offender in a private communication (either IRC/PM, email or whatever) and warn the offender that there could be serious consequences if the offender continues with his current course of action.

* The offender should be encouraged to submit a formal complaint by email to the Board using the "admin@soylentnews.org" email address. A formal complaint cannot be submitted anonymously but it may use a secure or temporary email provider. The Board shall then decide how the formal complaint should be resolved.

* The MG can agree to ban the offender for a specific period or permanently and take action to do so. There are, of course, technical difficulties associated with effectively banning an individual but a block of his personal IPs for each computer system as and when they are identified might be considered as a reasonable action. Other measures may be taken as necessary.

* Persistent site abuse, when all of the above measures have been exhausted, may result in the abuse being removed from display.

=== Control of SPAM ===

SPAM is most often found in story submissions (either as a link in an submission or as the entire contents of a submission) or in the comments to a published story. The definition of SPAM is that provided by Wikipedia and can be found in the [[Definitions and Common Terms]].

=== Control of Access and Password Policy ===

No-one should be given access privileges above those which are essential for them to complete their role. Additionally, no single individual should have a unique set of privileges because, in the event of some unforeseen circumstance, no other individual will be able to fulfill the same role. TLs should ensure that each task for which his team is responsible is documented and that privileges are assigned to team members as required.

In the event of a member of staff permanently leaving then a SuperAdmin is responsible for ensuring that access privileges are removed for that individual promptly. Shared passwords known by the individual, where they exist, should also be changed.

=== Response to Denial Of Service (DOS) Attack ===

The management and control of a Denial of Service (DOS) attack is the responsibility of the Systems Team, and may be more detailed by listing actions to be taken by one or more teams.

SoylentNews Policy New

2024-12-15T19:15:15Z

Janrinok: /* Privacy Policy */

== Privacy, Copyright, Disclaimers, Terms of Use, and DMCA (07 Dec 2024) ==

<b>The following pages may be revised and/or amended from time to time</b>

The SoylentNews site is currently based in the United States and is registered in the State of Oregon. As such, it is important to state the policy of SoylentNews with respect to certain laws in effect there as well as internationally.

=== Privacy Policy ===

It is the policy of SoylentNews, in as much as is reasonably possible, to retain the least amount of personally identifiable information about community members. Certain items are necessary in the conduct of the site's operation. These include, but are not necessarily restricted to: email address, IP data (either in plain or hashed form), and other personal information that users may optionally add to their own user page.

=== Copyright Notice ===

There are several places on the site where user-supplied content is published.

==== Submitted Stories ====
Anyone may submit a story for consideration by the editors for publication on the site. Editors attempt, within the site's guidelines ([[Submission_guidelines]]) to provide a consistent reading experience for the community. This may entail reformatting, rewriting, spelling corrections, and the like. The revised submission may then be published on the site for registered community members to read and comment on. Subsequent to publishing to the site additional edits may be made so as to correct mistakes (e.g. typos) and/or to add additional information, etc.

The original submitter retains copyright to their submission.

The original submitter grants a non-exclusive right to SoylentNews to publish the story.

==== Published Stories ====

SoylentNews retains copyright to the story as published on the site.

==== Journal Submissions ====

Each logged-in user has the ability to post "stories" to their journal in which they may discuss any topic they wish providing that it is permissible under US law. The submitter may edit (if they have the appropriate user permissions) or even delete any of their journal postings. Furthermore, they may restrict the ability of other users to comment in the journal as provided by the software.

The comments are owned by whoever posted them. SoylentNews is not responsible for them in any way. A statement to this effect will be displayed on each journal.

==== User Comments ====

The community is encouraged to provide comments in response to stories published on the site as well as to journal entries in which that option has been enabled. The site reserves the right to limit comments to some stories to logged-in users only, at its discretion. Comments may be submitted anonymously where such comments are enabled, as an Anonymous Coward, or attibuted the user's site Nickname.

In either case, the site's policy is stated on each story page:

<blockquote>The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.</blockquote>

Please note that comments are published under the Creative Commons Share Alike [https://creativecommons.org/licenses/by-sa/4.0/deed.en]unless otherwise indicated.

==== Wiki Entries ====

Copyright on entries on the site's Wikipedia page are governed by this statement which appears at the bottom of each page:
<blockquote>Content is available under Creative Commons Attribution Share Alike unless otherwise noted.</blockquote>

Further, when submitting to the Wiki, this notice appears above the "Save page", "Show Preview", and "Show changes" buttons:

<blockquote>Please note that all contributions to SoylentNews are considered to be released under the Creative Commons Attribution Share Alike [https://creativecommons.org/licenses/by-sa/4.0/deed.en]. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. <b>Do not submit copyrighted work without permission!</b></blockquote>

==== IRC (Internet Relay Chat) ====
The submitter of anything posted to any of the site's IRC channels specifically allows the site to retain anything posted there and make it available, for example, in the form of retained logs. In addition, any chats that take place in the form of staff meetings, board meetings, and the like will be retained and may be posted on the site Wiki.

==== SoylentCode (rehash) ====
The site is based on Slashcode (Version unknown) which is under a GPL v2 license. Wherever possible, commensurate with maintaining site security, any new or updated code originated by SoylentNews will retain this licensing and be made available for downloading by any individual in accord with this license. Links will be maintained on the site to enable the repository of the code to be easily located.

=== Disclaimers ===
* Content published on this website is for general information purposes only.
* SoylentNews offers no representations or warranties of any kind, express or implied, regarding completeness, accuracy, reliability, suitability or availability of this website, published information and related graphics or hyperlinks contained on this website for any purpose. Use of such information is therefore at your own risk.
* In no event shall SoylentNews or its affiliates be held liable for any losses or damages including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or revenue arising out of, or in connection with, the use of this website.
* SoylentNews has no control over the nature, content, and availability of hyperlinked websites. The inclusion of hyperlinks to other websites is for reference or informative purposes only and does not imply endorsement of them.
* Availability is not guaranteed. SoylentNews takes no responsibility for, and will not be liable for, this website being unavailable for any reason.

=== Terms of Use ===

Use of this website is subject to your agreement with the following terms, as well as your agreement with the Privacy Policy, Copyright Notice, and Disclaimer. You should review these terms and related documents regularly as they may be revised at any time without notice.

The date that these terms were last modified can be found at the top of the page.
* Use of this website and any disputes arising out of such use of this website are subject to the laws of the United States of America, and where applicable, the State of Oregon.
* All registered trademarks reproduced remain property of their respective owners.
* Unauthorized use of this website may give rise to a claim for damages and/or be a criminal offense.
* This website includes links to third party websites. These links are provided for your convenience to provide further information, and does not signify endorsement.
* Availability of this website is not guaranteed.
* Spamming, hacking and/or phishing this website is not permitted.
* Doxxing of community members is strictly forbidden regardless of the source of the information. Wherever personal information is published by anyone other than the person that it relates to it will be assumed to be accurate and may be assessed as being an attempt at doxxing.
* These terms, as well as terms in the related documents, shall remain continuously in force if there is a change to the domain of this website.

== Subscription Fees ==

=== Community Fees ===

The Board may choose to offer a subscription membership fee to some or all members of the SoylentNews community. Nevertheless, non-payment of the subscription fee will not prevent access to the site; the intention is to enable the site to be viewed by as many people as possible and to encourage them to submit stories for publication and to comment on the stories that have already been accepted and released.

=== Waiving of Subscription Fees ===

Once an individual has served as a staff member for 3 months he is no longer required to pay subscription fees to enjoy all the privileges of site membership. This privilege will remain for the period of their service on the staff, plus a discretionary extension of a maximum of 1 year from the individual leaving the staff. The actual duration will be decided by the MG.

Occasionally, the Management Group (MG) (which comprises of Administrators and Team Leaders (TLs) might recommend to the Board that an individual be granted lifetime site membership in recognition of a significant period of service, or being a prominent figure from any relevant field of technology or related interests, or some other act deserving of special recognition. The Board can accept or reject such recommendations as they deem fit.

== Site Control and Security ==

=== Access to Personal Data ===

No personal data held by the site will be shared, sold or otherwise distributed outside of the site with the exception of demands supported by the appropriate legal documentation served upon the Board.

Personal data shall be held by the site for the minimum time necessary, and efforts should be made to anonymize or encrypt such data wherever possible.

=== Abusive Behaviour ===

SoylentNews aims to be tolerant of any individual's personal views and will allow them to express their views in the comments of published stories. However, occasionally, individuals will not express their views relating to a story but will employ offensive and/or abusive behaviour towards an individual. This is not in the spirit of the site and a graduated response will be adopted to anyone who employs such behaviour in their comments.

*The moderation system employed usually results in offensive, abusive or off-topic information being reduced to the lowest viewable priority level such that, to most regular users of the site, it does not even display on their screen. Often, this is sufficient to defuse the situation and the offender departs after a short period of time. However, community members should also be encouraged not to 'feed the trolls' and to avoid responding to any posts by the offender. Staff should adopt a non-confrontational attitude while engaging with community members and the offender in an attempt to cool the situation down.

*A member of staff should issue a comment in which he politely but firmly requests that the offender stops his offensive/abusive behaviour while explaining that it does nothing to contribute to the site nor does it show the offender in a positive light. However, it is important to try to identify the true cause of the offenders attitude and for the staff member, alone or with the assistance of other members of staff, to try to resolve any genuine issues or grievances that the offender may have.

*A Team Leader or senior staff member should attempt to engage the offender in a private communication (either IRC/PM, email or whatever) and warn the offender that there could be serious consequences if the offender continues with his current course of action.

* The offender should be encouraged to submit a formal complaint by email to the Board using the "admin@soylentnews.org" email address. A formal complaint cannot be submitted anonymously but it may use a secure or temporary email provider. The Board shall then decide how the formal complaint should be resolved.

* The MG can agree to ban the offender for a specific period or permanently and take action to do so. There are, of course, technical difficulties associated with effectively banning an individual but a block of his personal IPs for each computer system as and when they are identified might be considered as a reasonable action. Other measures may be taken as necessary.

* Persistent site abuse, when all of the above measures have been exhausted, may result in the abuse being removed from display.

=== Control of SPAM ===

SPAM is most often found in story submissions (either as a link in an submission or as the entire contents of a submission) or in the comments to a published story. The definition of SPAM is that provided by Wikipedia and can be found in the [[Definitions and Common Terms]].

=== Control of Access and Password Policy ===

No-one should be given access privileges above those which are essential for them to complete their role. Additionally, no single individual should have a unique set of privileges because, in the event of some unforeseen circumstance, no other individual will be able to fulfill the same role. TLs should ensure that each task for which his team is responsible is documented and that privileges are assigned to team members as required.

In the event of a member of staff permanently leaving then a SuperAdmin is responsible for ensuring that access privileges are removed for that individual promptly. Shared passwords known by the individual, where they exist, should also be changed.

=== Response to Denial Of Service (DOS) Attack ===

The management and control of a Denial of Service (DOS) attack is the responsibility of the Systems Team, and may be more detailed by listing actions to be taken by one or more teams.

Definitions and Common Terms

2024-12-14T16:37:45Z

Janrinok: /* DOXXING (aka DOXING) */

= DEFINITIONS AND COMMON TERMS =

== DEFINITIONS ==

=== SPAM ===

The definition of Spam used on this site was adopted in 2021. It is published on Wikipedia and is as follows (https://en.wikipedia.org/wiki/Spamming) :
<blockquote>Spamming is the use of messaging systems to send multiple unsolicited messages (spam) to large numbers of recipients for the purpose of commercial advertising, non-commercial proselytizing, or any prohibited purpose (especially phishing), or simply repeatedly sending the same message to the same user. While the most widely recognized form of spam is email spam, the term is applied to similar abuses in other media: instant messaging spam, Usenet newsgroup spam, Web search engine spam, spam in blogs, wiki spam, online classified ads spam, mobile phone messaging spam, Internet forum spam, junk fax transmissions, social spam, spam mobile apps,television advertising and file sharing spam.</blockquote>

Spamming is forbidden on the site.

=== DOXXING (aka DOXING) ===

Doxxing is the intentional compromise or publication of personally identifiable information belonging to another individual, regardless of its source. As it can be difficult to verify the accuracy of PII if there is any doubt then it is assumed to be both accurate and an intentional attempt at doxxing.

Doxxing is forbidden on the site.

== COMMON TERMS ==

=== Board ===

The group of people who represent the formal and legal face of the site. They are formally recorded on the site documentation which is provided to the necessary State and Government departments. They are the highest authority on the site.

=== Management Group ===

The group of staff comprising of Team Leaders and Administrators who manage the day-to-day running of the site.

=== Team Leader ===

The senior or elected person of one or more of the functional teams which make up the Staff.

=== Personally Identifiable Information (PII) ===

PII is information that enables a person to be identified and is defined in the US as:

<blockquote>Information that can be used to distinguish or trace an individual's identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or recognizing linked or linkable information, such as date and place of birth, as well as the mother's maiden name, in official standards like the NIST Guide, demonstrates a proactive approach to ensuring robust privacy safeguards amid the dynamic landscape of data security. This integration into established standards is a foundational framework for organizations to adopt and implement effective measures in safeguarding individuals' personal information.</blockquote>

As some of our community are also covered by EU legislation, the EU definition is broader and is as follows:

<blockquote>Any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</blockquote>

Definitions and Common Terms

2024-12-13T16:26:57Z

Janrinok: /* DEFINITIONS AND COMMON TERMS (7 Dec 2024) */

= DEFINITIONS AND COMMON TERMS =

== DEFINITIONS ==

=== SPAM ===

The definition of Spam used on this site was adopted in 2021. It is published on Wikipedia and is as follows (https://en.wikipedia.org/wiki/Spamming) :
<blockquote>Spamming is the use of messaging systems to send multiple unsolicited messages (spam) to large numbers of recipients for the purpose of commercial advertising, non-commercial proselytizing, or any prohibited purpose (especially phishing), or simply repeatedly sending the same message to the same user. While the most widely recognized form of spam is email spam, the term is applied to similar abuses in other media: instant messaging spam, Usenet newsgroup spam, Web search engine spam, spam in blogs, wiki spam, online classified ads spam, mobile phone messaging spam, Internet forum spam, junk fax transmissions, social spam, spam mobile apps,television advertising and file sharing spam.</blockquote>

Spamming is forbidden on the site.

=== DOXXING (aka DOXING) ===

Doxxing is the intentional compromise of personally identifiable information belonging to another individual, regardless of its source. As it can be difficult to verify the accuracy of PII if there is any doubt then it is assumed to be both accurate and an intentional attempt at doxxing.

Doxxing is forbidden on the site.

== COMMON TERMS ==

=== Board ===

The group of people who represent the formal and legal face of the site. They are formally recorded on the site documentation which is provided to the necessary State and Government departments. They are the highest authority on the site.

=== Management Group ===

The group of staff comprising of Team Leaders and Administrators who manage the day-to-day running of the site.

=== Team Leader ===

The senior or elected person of one or more of the functional teams which make up the Staff.

=== Personally Identifiable Information (PII) ===

PII is information that enables a person to be identified and is defined in the US as:

<blockquote>Information that can be used to distinguish or trace an individual's identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or recognizing linked or linkable information, such as date and place of birth, as well as the mother's maiden name, in official standards like the NIST Guide, demonstrates a proactive approach to ensuring robust privacy safeguards amid the dynamic landscape of data security. This integration into established standards is a foundational framework for organizations to adopt and implement effective measures in safeguarding individuals' personal information.</blockquote>

As some of our community are also covered by EU legislation, the EU definition is broader and is as follows:

<blockquote>Any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</blockquote>

SoylentNews - User contributions [en]

Hacktivist Википедия

Editorial Policy

2025年最佳SoundCloud播放量计算器与增长方案

2025年7月SMM金属产量数据发布 上海有色网

2025 Is The Year Of Arkadium Bubble Shooter

2025: Al Mejor Sonido

2024 年最好的 XXX 個免費同性戀色情網站，作者為 MrPornGeek

2019年十大男性增强药: Customer Review

10种最好的增强性功能的药物介绍 障碍 是一种 男性

10 Trendy Concepts For Your Arkadium Bubble Shooter

10 Most Wonderful Chaturbate Mature Changing Exactly How We See The World

10 Most Incredible Bisexual Porn Changing How Exactly We Start To See The World

10 Easy Ways To Figure Out The Tassimo Drinks Machine In Your Body.

User:SaraBlodgett2

A Guide To Gilf Porn

Best-handjob Videos

Japansex: In 5 Easy Steps

Cast Teenager Young Porn Videos 18

Hot Blondes In Free People Wind Up Tubing Videos In HD On PornDig

Dubbel Penetration Porno Video s Pornhub Com

Approaches To Use Top Porn Movies Site

An Unbiased View Of Japan Porn Video

Milf Smut Videos

Toys Disengage Porn Videos Porn For Women

Do We Need Best Premium Porn Sites Reddit Since We ve

The Fundamentals Of New Free Porn Video Sites Revealed

Unidentified Details About Porn Famous Websites Made Known

An Observational Study On The Popularity And Perception Of The "We The People" Graphic Cotton Tee

Roughly Sex Search

Blond Little Girl Porn Videos

Editors

Editors

Editors

WhosWho

Editing Process

Soylent Phoenix - Bank Details

Soylent Phoenix - Bank Details

Discussion Policy

Discussion Policy

SoylentNews

DRAFT - Discussion Policy

Soylent Phoenix - Bank Details

Definitions and Common Terms

SoylentNews Policy New

SoylentNews Policy New

SoylentNews Policy New

SoylentNews Policy New

SoylentNews Policy New

Definitions and Common Terms

Definitions and Common Terms

2025年7月SMM金属产量数据发布上海有色网

10种最好的增强性功能的药物介绍障碍是一种男性