|
7 | 7 | <p> |
8 | 8 | Lobsters is a technology-focused community centered around link aggregation |
9 | 9 | and discussion, launched on July 1st, 2012. |
10 | | - The current administrator is <a href="/u/pushcx">Peter (pushcx) Bhat Harkins</a>, contact him with any support issues. |
| 10 | + The current administrator is <a href="/u/pushcx">Peter Bhat Harkins</a> ("pushcx"), contact him with any support issues. |
11 | 11 | Lobsters was created by <a href="/u/jcs">joshua stein</a> |
12 | 12 | with some specific design goals in mind to avoid problems faced by |
13 | 13 | other link aggregation sites: |
14 | 14 | </p> |
15 | 15 |
|
16 | 16 | <ul> |
17 | | - <li>a <a href="#tagging">tagging</a> system to categorize and filter |
18 | | - submissions, |
19 | | - <li>a user <a href="#invitations">invitation tree</a> to combat spam, |
20 | | - <li><a href="#downvotes">downvote explanations</a> to curb reflexive |
21 | | - downvoting, |
22 | | - <li>a strong commitment to <a href="#transparency">transparency</a>, |
23 | | - <li>and <a href="#features">many other features</a> that have been added over |
24 | | - the years. |
| 17 | + <li>a <a href="#tagging">tagging</a> system to categorize and filter submissions,</li> |
| 18 | + <li>a user <a href="#invitations">invitation tree</a> to combat spam,</li> |
| 19 | + <li><a href="#downvotes">downvote explanations</a> to curb reflexive downvoting,</li> |
| 20 | + <li>a strong commitment to <a href="#transparency">transparency</a>,</li> |
| 21 | + <li>and <a href="#features">many other features</a> that have been added over the years.</li> |
25 | 22 | </ul> |
26 | 23 |
|
27 | 24 | <p id="tagging"> |
28 | 25 | <strong>Tagging</strong> |
29 | 26 | <br> |
30 | | - When links/stories are submitted, they must be tagged by the submitter from a |
31 | | - list of predefined <a href="/tags">tags</a>. Users can choose to <a |
32 | | - href="/filters">filter</a> out all submissions with particular tags, but |
33 | | - rather than use rigidly segmented sub-forums that users must each subscribe |
34 | | - to, all users see all stories by default. The reason for this is threefold: |
| 27 | + When links/stories are submitted, they must be tagged by the submitter from a list of predefined <a href="/tags">tags</a>. |
| 28 | + Users can choose to <a href="/filters">filter</a> out or |
| 29 | + subscribe to all submissions with particular tags (<a href="https://lobste.rs/t/programming.rss">example</a>). |
| 30 | + All users see all stories by default. |
| 31 | + The tagging system works this way for three reasons: |
35 | 32 | </p> |
36 | 33 |
|
37 | 34 | <ul> |
|
66 | 63 | </ul> |
67 | 64 |
|
68 | 65 | <p> |
69 | | - Creating new tags and retiring old tags is done by the community by |
70 | | - submitting, discussing, and voting on |
71 | | - <a href="/t/meta" class="tag">meta</a>-tagged requests about them. |
| 66 | + Creating new tags and retiring old tags is done by the community by submitting, discussing, and voting on <a href="/t/meta" class="tag">meta</a>-tagged requests about them, |
| 67 | + and these events are <a href="https://lobste.rs/moderations?utf8=✓&moderator=(All)&what[tags]=tags">logged</a> (since 2018-04). |
72 | 68 | </p> |
73 | 69 |
|
74 | 70 | <p id="invitations"> |
75 | 71 | <strong>Invitation Tree</strong><br /> |
76 | | - Invitations are used as a mechanism for spam-control and to encourage users |
77 | | - to "be nice". New users must be invited by a current user, though there is |
78 | | - no vetting process and invitations are not intended to promote exclusivity. |
| 72 | + New users must be invited by a current user, though there is no formal vetting process. |
| 73 | + Invitations are used as a mechanism for spam-control and to encourage users to be nice, not to make the Lobsters userbase an elite club. |
79 | 74 | The most efficient way to receive an invitation is to talk to someone you |
80 | 75 | recognize from the site or |
81 | 76 | <% if Rails.application.allow_invitation_requests? %> |
82 | 77 | <a href="/invitations/request">request one publicly</a>. |
83 | 78 | <% else %> |
84 | 79 | request one in <a href="/chat">chat</a>. |
85 | 80 | <% end %> |
86 | | - Invitations are unlimited unless scaling problems temporarily prevent new |
87 | | - accounts. If spammers are invited to the site and banned, the user that |
88 | | - invited them may also be banned, going up the chain of invitations as needed. |
89 | 81 | </p> |
90 | 82 |
|
91 | 83 | <p> |
92 | 84 | The full <a href="/u">user tree</a> is made public and each user's profile |
93 | | - shows who invited them. This provides some degree of accountability and can |
94 | | - act as a tool to help identify voting rings. |
| 85 | + shows who invited them. This provides some degree of accountability and |
| 86 | + helps identify voting rings. |
| 87 | + </p> |
| 88 | + |
| 89 | + <p> |
| 90 | + There's no limit on how many invitations a user can send (though that might be prompted by scaling problems in the future). |
| 91 | + When accounts are banned for spam, <a href="https://en.wikipedia.org/wiki/Sockpuppet_(Internet)">sockpuppeting</a>, or other abuse, |
| 92 | + moderators will look up the invitation tree to consider disabling their inviter's ability to send invitations or, rarely, also banning. |
95 | 93 | </p> |
96 | 94 |
|
97 | 95 | <p id="downvotes"> |
|
111 | 109 | All <a href="/moderations">moderator actions</a> on this site are visible to |
112 | 110 | everyone and the identities of those moderators are <a |
113 | 111 | href="/u?moderators=1">made public</a>. While the individual actions of a |
114 | | - moderator may cause debate, there should be no question about which moderator |
115 | | - it was or whether they had an ulterior motive for those actions. |
| 112 | + moderator may cause debate, there should be no question about if an action happened or who is responsible. |
116 | 113 | </p> |
117 | 114 |
|
118 | 115 | <p> |
119 | 116 | All user voting and story ranking on this site uses a universal algorithm and |
120 | 117 | does not <a |
121 | 118 | href="http://www.righto.com/2013/11/how-hacker-news-ranking-really-works.html" |
122 | | - rel="nofollow">artificially penalize</a> or prioritize users or domains. |
| 119 | + rel="nofollow">penalize</a> or prioritize specific users or domains. |
123 | 120 | Per-tag <a href="/filters">hotness modifiers</a> do affect all stories with |
124 | | - those tags, but these modifiers are made public and usually used to shorten |
125 | | - the life of meta-discussions. If certain domains have to be banned from |
126 | | - being submitted due to spam, the list will be made publicly available. |
| 121 | + those tags, but these modifiers (and <a href="https://lobste.rs/moderations?utf8=%E2%9C%93&moderator=(All)&what[tags]=tags">changes</a> to them) are made public. |
| 122 | + Domains used for tracking are banned and tracking parameters are removed from links |
| 123 | + (look for <tt>TRACKING_DOMAINS</tt> and <tt>utm_</tt> in |
| 124 | + <a href="https://github.com/lobsters/lobsters/blob/master/app/models/story.rb">story.rb</a>). |
127 | 125 | </p> |
128 | 126 |
|
129 | 127 | <p> |
130 | 128 | If users are disruptive enough to warrant banning, they will be banned |
131 | 129 | absolutely, given notice of their banning, and their disabled user profile |
132 | | - will indicate which moderator banned them and why. There will be no hidden, |
133 | | - antisocial "shadow banning" or "hellbanning" of users. |
| 130 | + will indicate which moderator banned them and why. |
| 131 | + There will be no <a href="https://en.wikipedia.org/wiki/Shadow_banning">shadow banning</a> or other secret moderation actions. |
| 132 | + </p> |
| 133 | + |
| 134 | + <p> |
| 135 | + The <a href="https://github.com/lobsters/lobsters">source code to this site</a> and |
| 136 | + its <a href="https://github.com/lobsters/lobsters-ansible">provisioning and deployment</a> are |
| 137 | + made available under a 3-clause BSD license for viewing, auditing, forking, or contributing to. |
134 | 138 | </p> |
135 | 139 |
|
136 | 140 | <p> |
137 | | - The <a href="https://github.com/lobsters/lobsters">source code to this site</a> is |
138 | | - made available under a 3-clause BSD license for viewing, auditing, forking, |
139 | | - or contributing to. |
| 141 | + If you dislike the content or moderation policies here, you may prefer |
| 142 | + <a href="https://news.ycombinator.com">Y Combinator News</a>, |
| 143 | + <a href="https://reddit.com/r/programming">r/programming</a>, |
| 144 | + <a href="https://en.wikipedia.org/wiki/Comp.*_hierarchy">comp.*</a>, or |
| 145 | + <a href="http://boards.4chan.org/g/">/g/</a>. |
140 | 146 | </p> |
141 | 147 |
|
142 | 148 | <p id="features"> |
|
199 | 205 | be automatically applied to a story when a quorum of users agrees on a new |
200 | 206 | title (such as removing a site's name, or appending the story's year of |
201 | 207 | publication) or set of tags, without any moderator action required. |
| 208 | + (<a href="https://lobste.rs/moderations?utf8=%E2%9C%93&moderator=(Users)">Log</a>) |
202 | 209 | </p></li> |
203 | 210 |
|
204 | 211 | <li><p> |
|
228 | 235 | </p></li> |
229 | 236 | <% end %> |
230 | 237 |
|
| 238 | + <li name="emoji"><p> |
| 239 | + <strong><a href="https://unicode.org/consortium/adopted-characters.html#s1f99E">Sponsor of the 🦞 emoji</a></strong>: |
| 240 | + In February 2018, Lobsters <a href="https://lobste.rs/s/pnysdr/lobsters_emoji_adoption">held a fundraiser</a> |
| 241 | + to officially adopt the new lobster emoji in support of the Unicode Foundation. |
| 242 | + </p></li> |
| 243 | + |
231 | 244 | <li><p> |
232 | 245 | <strong>Stickers</strong> are |
233 | 246 | no longer available until an alternative to the Stickermule marketplace is found. |
|
0 commit comments