<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.soylentnews.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mattie+p</id>
	<title>SoylentNews - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.soylentnews.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mattie+p"/>
	<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/wiki/Special:Contributions/Mattie_p"/>
	<updated>2026-05-17T02:07:37Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.4</generator>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Board_of_Directors_Meeting_-_July_16,_2014&amp;diff=7857</id>
		<title>Board of Directors Meeting - July 16, 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Board_of_Directors_Meeting_-_July_16,_2014&amp;diff=7857"/>
		<updated>2014-07-17T02:23:04Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[23:07:33] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, audioguy bryan Bytram chromas cosurgi juggs|afk Landon matt_ mattie_p mechanicjay NCommander paulej72 prospectacle TheMightyBuzzard&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:07:34] &amp;amp;lt;mrcoolbp&amp;amp;gt; Guys, this is a &amp;quot;Board Meeting,&amp;quot; we are discussing business matters, not interstaff and procedural stuff.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:07:38] &amp;amp;lt;xlefay&amp;amp;gt; ^^ I think we're starting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:07:41] &amp;amp;lt;NCommander&amp;amp;gt; We should get that BlackHole guy on staff :-P&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:07:53] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ ready?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:02] &amp;amp;lt;matt_&amp;amp;gt; Ready to call to order today's meeting of the Board of Directors of SoylentNews PBC?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:09] &amp;amp;lt;matt_&amp;amp;gt; First, a reminder that until we adopt an amendment to the bylaws to allow board meetings on IRC, a conservative interpretation of our bylaws suggests that actions that we take here should be unanimous and followed up with an email confirmation to ensure that said actions are binding. Addressing this with an amendment to the bylaws is an item on the agenda for today's meeting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:17] &amp;amp;lt;matt_&amp;amp;gt; On that note, so far, I only have 5 items for today's agenda:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:22] &amp;amp;lt;matt_&amp;amp;gt; 1. Review the minutes of the last meeting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:26] &amp;amp;lt;matt_&amp;amp;gt; 2. Updates on progress towards financial stability (bank and payment-processor accounts, subscriptions, swag).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:30] &amp;amp;lt;matt_&amp;amp;gt; 3. Discuss remaining issues related to setting up the corporation (amending the bylaws to allow meetings on IRC, stock proposal, etc.).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:34] &amp;amp;lt;matt_&amp;amp;gt; 4. Any other business (community involvement in corporate governance, SN policies and procedures manual, including: staff appointment &amp;amp; authority, account and password management, individual team policy, policy on retaining records, etc.).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:37] &amp;amp;lt;matt_&amp;amp;gt; 5. Adjourn.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:41] &amp;amp;lt;matt_&amp;amp;gt; Any objections to this agenda or any items to add (remember that items can be added later at any point)?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:08:56] &amp;amp;lt;NCommander&amp;amp;gt; No objections here&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:04] &amp;amp;lt;Bytram&amp;amp;gt; none here&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:06] &amp;amp;lt;mrcoolbp&amp;amp;gt; no objections&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:13] &amp;amp;lt;matt_&amp;amp;gt; Great! First up, Item 1: Review the minutes of the last meeting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:17] &amp;amp;lt;matt_&amp;amp;gt; At the last meeting, the Board adopted 7 resolutions:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:22] &amp;amp;lt;matt_&amp;amp;gt; Resolved: The Certificate of Incorporation and Bylaws are hereby ratified in their current form.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:25] &amp;amp;lt;matt_&amp;amp;gt; Resolved: Michael Casadevall is the President of SoylentNews PBC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:29] &amp;amp;lt;matt_&amp;amp;gt; Resolved: Michael Casadevall is the Chief Executive Officer of SoylentNews PBC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:33] &amp;amp;lt;matt_&amp;amp;gt; Resolved: Ben Prentice is the Treasurer of SoylentNews PBC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:41] &amp;amp;lt;matt_&amp;amp;gt; Resolved: Matt Angel is the Secretary of SoylentNews PBC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:45] &amp;amp;lt;matt_&amp;amp;gt; Resolved: The Board authorizes opening a business checking account at Bank of America in the name of the Corporation.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:50] &amp;amp;lt;matt_&amp;amp;gt; Resolved: The Board authorizes opening a PayPal account in the name of the Corporation.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:09:54] &amp;amp;lt;matt_&amp;amp;gt; Several other items were discussed, but no other votes were taken.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:00] &amp;amp;lt;matt_&amp;amp;gt; The logs of the last meeting are available here: http://wiki.soylentnews.org&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:07] &amp;amp;lt;matt_&amp;amp;gt; Any comments or shall we move on to: Item 2: Updates on progress towards financial stability (bank and payment-processor accounts, subscriptions, swag)?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:33] &amp;amp;lt;xlefay&amp;amp;gt; Are the non-voted on issues outlined specifically? Or just in the log itself?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:43] &amp;amp;lt;matt_&amp;amp;gt; just in the log at the moment.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:55] &amp;amp;lt;NCommander&amp;amp;gt; We probably need to define a standardized format of minutes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:56] &amp;amp;lt;xlefay&amp;amp;gt; A suggestion: It may be wise, to make a table with a list of resolved items and unresolved/not-voted-on items after this meeting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:10:56] &amp;amp;lt;Bytram&amp;amp;gt; I have one thing&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:11] &amp;amp;lt;xlefay&amp;amp;gt; NCommander, said it better than I did. :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:12] &amp;amp;lt;matt_&amp;amp;gt; NCommander, i have a template for that :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:13] &amp;amp;lt;Bytram&amp;amp;gt; was there any consideration given to a bank *other* than Bank of America&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:27] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:30] &amp;amp;lt;matt_&amp;amp;gt; Bytram, a fair amount of consideration, yes.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:42] &amp;amp;lt;Bytram&amp;amp;gt; I personally have nothing against them, but wanted to ensure others were considered.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:49] &amp;amp;lt;NCommander&amp;amp;gt; there was quite a few reasons to go with BoA, and some against&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:53] &amp;amp;lt;Bytram&amp;amp;gt; I'm good then, thanks!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:11:59] &amp;amp;lt;xlefay&amp;amp;gt; Are those considerations also outlined somewhere? Or also in the logs?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:12:01] &amp;amp;lt;NCommander&amp;amp;gt; BUt the pros outweighed the cons&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:12:20] &amp;amp;lt;matt_&amp;amp;gt; xlefay, a number of the considerations are in the logs, several came up in irl meetings.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:12:20] &amp;amp;lt;NCommander&amp;amp;gt; xlefay, I think the pro/con didnt make it into the log fully, that was mostly RL meetings we had last month&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:12:39] &amp;amp;lt;Bytram&amp;amp;gt; I did not see any discussion in the logs&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:12:52] &amp;amp;lt;xlefay&amp;amp;gt; I realizes, there's a lot of &amp;quot;documentational&amp;quot; work here, perhaps, we should standardize such templates as well, even though it can be somewhat of a pain to document those things - they might be useful for future references?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:02] &amp;amp;lt;NCommander&amp;amp;gt; ^- that&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:05] &amp;amp;lt;matt_&amp;amp;gt; Bytram, i think the logged discussion related mainly to the availability of branches in different locations.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:07] &amp;amp;lt;xlefay&amp;amp;gt; (from this point forward)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:25] &amp;amp;lt;mattie_p&amp;amp;gt; hey folks, sorry I'm late&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:30] &amp;amp;lt;mrcoolbp&amp;amp;gt; that's okay&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:38] &amp;amp;lt;mrcoolbp&amp;amp;gt; wb&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:43] &amp;amp;lt;mattie_p&amp;amp;gt; thanks&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:13:59] &amp;amp;lt;Bytram&amp;amp;gt; in light of the foregoing, I propose an agenda item for discussing a standard &amp;quot;format&amp;quot; for board meetings&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:14:56] &amp;amp;lt;matt_&amp;amp;gt; added to Item 4.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:05] &amp;amp;lt;matt_&amp;amp;gt; Ok, getting back to the agenda:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:07] &amp;amp;lt;xlefay&amp;amp;gt; In addition a question, how much time has been allocated to this meeting? Has there been a predefined length or?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:13] &amp;amp;lt;Bytram&amp;amp;gt; matt_: thank-you.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:21] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: we did not alot a timeslot&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:31] &amp;amp;lt;matt_&amp;amp;gt; xlefay, we were very self-disciplined last time, and kept it to 2 hours, despite having a lot to go over.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:44] &amp;amp;lt;matt_&amp;amp;gt; xlefay, i think that sounds like a reasonable maximum.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:15:59] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, thanks. In the future, we should also keep that in mind. So everyone can schedule accordingly.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:10] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: noted, thank you.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:12] &amp;amp;lt;xlefay&amp;amp;gt; I agree, anyway, please do go on. Don't want to hold things up.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:21] &amp;amp;lt;matt_&amp;amp;gt; Ok, back to Item 2: Updates on progress towards financial stability (bank and payment-processor accounts, subscriptions, swag).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:26] &amp;amp;lt;Bytram&amp;amp;gt; IIRC, our very *first* staff meetiong also lasted approximately two hours.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:31] &amp;amp;lt;matt_&amp;amp;gt; Since the last meeting, we opened a business checking account at Bank of America and a paypal account, and set them up to receive payments.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:16:37] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp and I have debit cards, which we can use to pay for hosting, etc., as soon as funds are available.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:17:04] &amp;amp;lt;NCommander&amp;amp;gt; I've gone through ALL the old receipts and compiled an initial set of books when I fired off to mrcoolbp&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:17:19] &amp;amp;lt;mrcoolbp&amp;amp;gt; I can confirm all of that&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:17:22] &amp;amp;lt;NCommander&amp;amp;gt; so we know roughly how deep the hole is, and who owns which parts of it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:09] &amp;amp;lt;xlefay&amp;amp;gt; .voice matt_&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:25] &amp;amp;lt;mrcoolbp&amp;amp;gt; ?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:32] &amp;amp;lt;mrcoolbp&amp;amp;gt; .voice matt_&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:38] &amp;amp;lt;mrcoolbp&amp;amp;gt; .voice matt_&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:43] &amp;amp;lt;xlefay&amp;amp;gt; .voice matt__&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:45] &amp;amp;lt;matt__&amp;amp;gt; thanks&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:18:48] &amp;amp;lt;matt__&amp;amp;gt; Comments? Otherwise we can move on to: subscriptions: NCommander, were you and paulej72 able to make any headway on the backend?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:03] &amp;amp;lt;Bytram&amp;amp;gt; mrcoolbp: do you have a rough summary of where we stand financially?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:08] &amp;amp;lt;mrcoolbp&amp;amp;gt; yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:14] &amp;amp;lt;NCommander&amp;amp;gt; .op&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:21] &amp;amp;lt;NCommander&amp;amp;gt; to hell with that&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander: I'll let you take those two questions&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:19:30] &amp;amp;lt;paulej72&amp;amp;gt; I was busy with the irc migration and did not work on that&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:00] &amp;amp;lt;NCommander&amp;amp;gt; Real life kinda derailed for me, miniminal progress&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:17] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay so no progress on the Subscription Code&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:23] &amp;amp;lt;NCommander&amp;amp;gt; Sorry :-/&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:25] &amp;amp;lt;matt__&amp;amp;gt; ok, is that still a top priority?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:27] &amp;amp;lt;mrcoolbp&amp;amp;gt; Ncommander: summary of financials?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:20:36] &amp;amp;lt;NCommander&amp;amp;gt; Give me a sec, let me fire up gnucash&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:21:03] &amp;amp;lt;NCommander&amp;amp;gt; ... still firing up gnucash&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:21:18] &amp;amp;lt;NCommander&amp;amp;gt; So, as of today&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:21:38] &amp;amp;lt;NCommander&amp;amp;gt; We're $3,217.58 USD in the hole.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:21:46] &amp;amp;lt;mrcoolbp&amp;amp;gt; that's what I have as well&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:21:53] &amp;amp;lt;matt__&amp;amp;gt; that sounds about right.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:22:25] &amp;amp;lt;NCommander&amp;amp;gt; Dividing on money in v. money out, most of that is owed to Matt, at a toal value of $2,484, and $833 to me.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:22:31] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander: are subscriptions a top business priority right now?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:22:45] &amp;amp;lt;NCommander&amp;amp;gt; I believe so, they are, as they say, low hanging fruit&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:22:52] &amp;amp;lt;mrcoolbp&amp;amp;gt; great&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:05] &amp;amp;lt;matt_&amp;amp;gt; Ok, next is swag: mrcoolbp, how goes it?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:09] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:23] &amp;amp;lt;mrcoolbp&amp;amp;gt; So we have a mock-up of the store setup&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:34] &amp;amp;lt;mrcoolbp&amp;amp;gt; techincally things can be purchased right now&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:49] &amp;amp;lt;mrcoolbp&amp;amp;gt; But there was a small hangup on the Tagline &amp;quot;...is people&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:59] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, do you want to add additional designs/items before going live?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:23:59] &amp;amp;lt;mrcoolbp&amp;amp;gt; I wanted to resolve that here before we move forward&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:07] &amp;amp;lt;matt_&amp;amp;gt; ok, good point.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:14] &amp;amp;lt;xlefay&amp;amp;gt; Could we get a preview/screenshot of said mock-up? So we can visualize it?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:22] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: sec&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:27] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_: at the very least I'd like to spend a few hours on setting it up proper&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:37] &amp;amp;lt;mrcoolbp&amp;amp;gt; especially after we resolve the tagline issue&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:24:47] &amp;amp;lt;mrcoolbp&amp;amp;gt; (I think that's it for my update)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:04] &amp;amp;lt;xlefay&amp;amp;gt; And what kind of &amp;quot;swag&amp;quot; are we selling? Like, t-shirts, hats, usb sticks?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:11] &amp;amp;lt;Bytram&amp;amp;gt; Given the pent-up demand, I would prefer a couple extra day's time to get it solid before opening us up for potential troubles&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:12] &amp;amp;lt;xlefay&amp;amp;gt; planning on selling*&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:20] &amp;amp;lt;paulej72&amp;amp;gt; also I suggested we needed to add the url to the design as well&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:25] &amp;amp;lt;mrcoolbp&amp;amp;gt; ^^^&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:36] &amp;amp;lt;matt_&amp;amp;gt; so, my opinion of the tagline issue is: 1. it seems very unlikely that anyone will complain, 2. if we do get a letter or communication from someone who is unhappy with us using the tagline, we can probably work something out with them, and 3. since we aren't warehousing huge amounts of merchandise, it wouldn't be too difficult to change it later.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:25:39] &amp;amp;lt;xlefay&amp;amp;gt; Perhaps, a QR code or something similar would also be benefitial considering most people have a smart phone?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:26:27] &amp;amp;lt;mrcoolbp&amp;amp;gt; Screenshot of the 1st draft of the store: http://imgur.com&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:26:44] &amp;amp;lt;xlefay&amp;amp;gt; Where's the bacon++?! (hah)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:26:53] &amp;amp;lt;mrcoolbp&amp;amp;gt; !todo bacon++ items&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:26:53] &amp;amp;lt;Bender&amp;amp;gt; todo item 22 added&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:01] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, what are your thoughts on the tagline issue?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:06] &amp;amp;lt;NCommander&amp;amp;gt; so we proceed w/ the tagline?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:09] &amp;amp;lt;NCommander&amp;amp;gt; as is?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:21] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ I'm not well versed on the issue, I'll defer to your understanding of it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:25] &amp;amp;lt;xlefay&amp;amp;gt; I think that looks amazing. Are there also plans on selling USB-sticks with SoylentNews stamped logo's? As for the tagline, SoylentNews .. is people!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:26] &amp;amp;lt;Bytram&amp;amp;gt; Is this the proper time/place to discuss the *particulars* of the SWAG items? I'd suggest wse just recognize the need for the discussion, and if need be, have someone volunteer to lead the discussion and report back.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:40] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: I have it noted, I just haven't gotten there&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:27:59] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: the tagline issue yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:06] &amp;amp;lt;mrcoolbp&amp;amp;gt; which items we are offering no&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:24] &amp;amp;lt;xlefay&amp;amp;gt; Bytram, I concur. That would seem like the most logical course of action, to set up a task force for it, and have the taskforce deal with the selection of items in the store.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:29] &amp;amp;lt;matt_&amp;amp;gt; Bytram, the board just needs to make sure that we don't decide on something that places the corporation at unnecessary legal risk.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:29] &amp;amp;lt;Bytram&amp;amp;gt; I fully agree. thanks. What is the potential issue with the tag line?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:42] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_, NCommander: I will get to fleshing out the store ASAP, it will be on the top of my todo&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:47] &amp;amp;lt;mattie_p&amp;amp;gt; Bytram: probably copyright or trademark infringement from the movie&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:28:54] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, sounds good!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:05] &amp;amp;lt;matt_&amp;amp;gt; Next, Item 3: Discuss remaining issues related to setting up the corporation (amending the bylaws to allow meetings on IRC, stock proposal, etc.).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:06] &amp;amp;lt;NCommander&amp;amp;gt; mattie_p, that was my concern&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:17] &amp;amp;lt;matt_&amp;amp;gt; unless there are any remaining swag issues...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:22] &amp;amp;lt;Bytram&amp;amp;gt; yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:41] &amp;amp;lt;Bytram&amp;amp;gt; are we self-hosting the swag store; shipping, billing and all that?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:29:41] &amp;amp;lt;mrcoolbp&amp;amp;gt; = /&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:03] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: negative, we went with a 3rd party solution due to resource constraints&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:03] &amp;amp;lt;matt_&amp;amp;gt; Bytram, the swag store is on CafePress.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:21] &amp;amp;lt;Bytram&amp;amp;gt; do they get a cut of the sales, and if so, how much?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:27] &amp;amp;lt;xlefay&amp;amp;gt; Bytram, matt_, perhaps, a task force for dealing with those items would be the best? Then, that taskforce can make recommendations to the staff and/or board?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:29] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: self-hosting and shipping ourselves would take a huge amount of work&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:37] &amp;amp;lt;matt_&amp;amp;gt; Bytram, oh, that's a really good point. We need to decide on the markup.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:49] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: of course they do, they set a base price and we set markup&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:30:50] &amp;amp;lt;xlefay&amp;amp;gt; Regarding, whether we oursource things, what items are in the store, etc.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:03] &amp;amp;lt;Bytram&amp;amp;gt; mrcoolbp: I *fully* agree on self-hosting being work-intensive.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:06] &amp;amp;lt;matt_&amp;amp;gt; xlefay, that is a good idea too. my understanding is that mrcoolbp is currently leading that task force.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:17] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: I would love a taskforce on the specifics, I can make the rest happen&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; any volunteers?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:37] &amp;amp;lt;xlefay&amp;amp;gt; matt_, I see. Than I suggest, we wait till mrcoolbp and his team (which he'll assemble) make a recommendation.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:31:48] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, count me in. I would be delighted to help out!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:10] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: I'll send you an email, and send one out to staff soliciting other volunteers&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:14] &amp;amp;lt;matt_&amp;amp;gt; xlefay, that sounds good to me. shall we aim for about a week from today? does that sound reasonable?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:26] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay, any other swag issues? NCommander: are we okay with going WITH the tagline for now?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:45] &amp;amp;lt;xlefay&amp;amp;gt; matt_, I believe that question is supposed to be targeted to mrcoolbp, since it's his taskforce :-)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:50] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ we can have a store ready-to-go in 7 days, yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:32:51] &amp;amp;lt;Bytram&amp;amp;gt; I have a question on how the task force will report back... e-mail to staff@soylentnews.org? Post it on the wiki? How?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:02] &amp;amp;lt;NCommander&amp;amp;gt; Ulitmately, I'm worried about us getting sued out of existence for it since we'd be directly profitting&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:12] &amp;amp;lt;NCommander&amp;amp;gt; On the other hand, Soylent (food product) exists and hasn't been sued so ...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:12] &amp;amp;lt;mattie_p&amp;amp;gt; re Tagline: I'm searching the USPTO and there are two live trademarks on soylent, one for the food and one by WB&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:21] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: I'll make the final decisions availalble on the staff list&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:35] &amp;amp;lt;xlefay&amp;amp;gt; Bytram / mrcoolbp , I suggest, we make one or multiple wiki pages, in which we'll disclose our findings and our recommendations. And then send that link to the staff.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:39] &amp;amp;lt;Bytram&amp;amp;gt; mrcoolbp: that's great! thank you very much!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:52] &amp;amp;lt;NCommander&amp;amp;gt; so, assuming we accept this as acceptable risk&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:33:56] &amp;amp;lt;NCommander&amp;amp;gt; I don't have an issue with it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:10] &amp;amp;lt;matt_&amp;amp;gt; ok. ready to move on?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:17] &amp;amp;lt;mrcoolbp&amp;amp;gt; I am&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:17] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, that'll allow us to, also be open regarding our process and the particular details. Thoughts?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:21] &amp;amp;lt;Bytram&amp;amp;gt; was there a vote here?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: great, let's discuss that later&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:37] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, agreed. :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:39] &amp;amp;lt;NCommander&amp;amp;gt; Bytram, vote on what?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:39] &amp;amp;lt;mrcoolbp&amp;amp;gt; = )&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:46] &amp;amp;lt;xlefay&amp;amp;gt; moving on then ;-)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:34:57] &amp;amp;lt;matt_&amp;amp;gt; &amp;lt;+matt_&amp;gt; Next, Item 3: Discuss remaining issues related to setting up the corporation (amending the bylaws to allow meetings on IRC, stock proposal, etc.).&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:04] &amp;amp;lt;matt_&amp;amp;gt; First, amending our Bylaws to allow meetings on IRC. (For those not here for the last meeting, our Bylaws may or may not allow meetings on IRC, but the Board can still take &amp;quot;action without a meeting&amp;quot; as long as it is unanimous and in writing.)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:05] &amp;amp;lt;mrcoolbp&amp;amp;gt; (matt_ Bytram is wondering if that issue required a vote)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:16] &amp;amp;lt;Bytram&amp;amp;gt; we have agenda items, and it would be good to note whenever we finish an item, what the conclusion/result was&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:35] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, oh. Bytram, to be safe the board should authorize the opening of the store, when it is ready.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:45] &amp;amp;lt;Bytram&amp;amp;gt; EXACTLY!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:56] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ that works for me (Bytram we aren't &amp;quot;ready&amp;quot; yet)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:35:57] &amp;amp;lt;matt_&amp;amp;gt; Bytram, yes. so far, we have just been noting when we finish agenda items that require a vote.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:36:34] &amp;amp;lt;matt_&amp;amp;gt; Bytram, one of the benefits of a 3-person board is that we don't have to worry too much about sticking to the details of parlimentary procedure :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:36:38] &amp;amp;lt;Bytram&amp;amp;gt; matt_: I have been at too many meetings where there has been lots of disussion&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:36:43] &amp;amp;lt;xlefay&amp;amp;gt; matt_, regarding item #3, I think allowing meetings on IRC is fine, but I do believe we should have a format for doing so. It can get quite complicated, multiple conversations running at once, etc. So we'll need to prevent that.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:36:59] &amp;amp;lt;Bytram&amp;amp;gt; and when the meeting was over, it was unclear who was doing what by when&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:37:05] &amp;amp;lt;xlefay&amp;amp;gt; (e.g. focussing on one thing at a time)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:37:18] &amp;amp;lt;matt_&amp;amp;gt; xlefay, yes. however we decide to do it, i strongly suggest that we confirm any decisions made at a meeting immediately after the meeting via email.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:37:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; ^^&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:37:34] &amp;amp;lt;NCommander&amp;amp;gt; xlefay, we need to fix the bylaws to formally allow it, kinda an oversight &amp;gt;.&amp;lt;;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:37:54] &amp;amp;lt;matt_&amp;amp;gt; so i was hoping that we could vote on that amendment at this meeting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:38:00] &amp;amp;lt;matt_&amp;amp;gt; Shall we take a vote on amending the Bylaws to allow meetings on IRC?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:38:03] &amp;amp;lt;xlefay&amp;amp;gt; NCommander, I understand. I'm just suggesting we discuss what kind of format before we do so.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:38:26] &amp;amp;lt;xlefay&amp;amp;gt; Otherwise, we'll allow it, but there's no proper format to do so, and things can get messy down the road, which isn't what we want.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:38:55] &amp;amp;lt;NCommander&amp;amp;gt; point taken&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:39:22] &amp;amp;lt;matt_&amp;amp;gt; Any objections to voting on the issue of whether to allow board meetings on irc?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:39:24] &amp;amp;lt;Bytram&amp;amp;gt; these are the corporate bylaws that I reviewed a few weeks ago?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:39:30] &amp;amp;lt;matt_&amp;amp;gt; Bytram, correct.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:39:38] &amp;amp;lt;Bytram&amp;amp;gt; okay, thanks.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:39:47] &amp;amp;lt;xlefay&amp;amp;gt; Just out of curiosity. This is already a board meeting, and yet, it isn't formally allowed by, the bylaws? That seems rather odd, lol&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:00] &amp;amp;lt;matt_&amp;amp;gt; exactly why i suggest we vote to fix that =)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:07] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ no objections, can we add discussion of meeting format as another topic?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:17] &amp;amp;lt;xlefay&amp;amp;gt; matt_, the only objection I have is, that we first define a format to have such meetings, when we have that, I see no objection, not from me at least.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:31] &amp;amp;lt;matt_&amp;amp;gt; xlefay, our bylaws allow &amp;quot;action without a meeting&amp;quot;, by unanimous written consent of the board.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:36] &amp;amp;lt;mrcoolbp&amp;amp;gt; ^^^&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:36] &amp;amp;lt;xlefay&amp;amp;gt; Then again, I'm not even sure if I'm on the board as it stands so.... rather confused about that ;)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:45] &amp;amp;lt;xlefay&amp;amp;gt; I see, that's cool.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:49] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: you are not currently on the board&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:54] &amp;amp;lt;Bytram&amp;amp;gt; so there are two questions here... (1) whether or not to allow board meetings on IRC, (2) what changes are required in the bylaws to support said change&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:40:55] &amp;amp;lt;xlefay&amp;amp;gt; ah I see&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:41:03] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, added to Item 4.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:41:05] &amp;amp;lt;mrcoolbp&amp;amp;gt; thanhks&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:41:42] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: that would be the change&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:41:55] &amp;amp;lt;matt_&amp;amp;gt; ok, so i have prepared a question for the vote. if we are ready to vote, i can pose the question :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:42:01] &amp;amp;lt;mrcoolbp&amp;amp;gt; NComander: shall we vote on item #3?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:42:19] &amp;amp;lt;NCommander&amp;amp;gt; lets have the question specifically written up then vote&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:42:28] &amp;amp;lt;xlefay&amp;amp;gt; (just one question, as this is a board meeting, or at least, sort-of, does staff opinion/vote weigh in or?)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:42:41] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: that's why you are here&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:09] &amp;amp;lt;matt_&amp;amp;gt; NCommander, i have a question written up, which I can present if you are ready to vote on it. Of course, you can vote &amp;quot;No&amp;quot; if you don't like the wording...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:13] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, cool, just making sure. The &amp;quot;board meeting&amp;quot; subject in the e-mail implied it was for the board, but since I'm not on said board, I got a tiny bit confused.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:14] &amp;amp;lt;mattie_p&amp;amp;gt; Query: If the board isn't sure it can have meetings on IRC: will a vote taken in an IRC meeting be valid?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:16] &amp;amp;lt;mrcoolbp&amp;amp;gt; you don't get to vote (unless you are on the board) but we are hearing opinions for sure&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:19] &amp;amp;lt;Bytram&amp;amp;gt; from my reading of the bylaws, the community is invited to attend and to voice their views so that the board can make an informed decision.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:32] &amp;amp;lt;matt_&amp;amp;gt; xlefay, staff opinion certainly weighs in, but only the current Directors may vote by law.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:39] &amp;amp;lt;mrcoolbp&amp;amp;gt; mattie_p &amp;quot;action without a meeting&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:51] &amp;amp;lt;mrcoolbp&amp;amp;gt; mattie_p technically this &amp;quot;isn't a board meeting&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:43:56] &amp;amp;lt;mrcoolbp&amp;amp;gt; as I understand it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:10] &amp;amp;lt;matt_&amp;amp;gt; mattie_p, from the logs of our last meeting:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:11] &amp;amp;lt;matt_&amp;amp;gt; First: Our simple bylaws do not specifically allow board meetings over irc :( and we had less than the required 2 business days notice of this meeting :( but that's ok because we can take action without a meeting according to Article III, Section 11: &amp;quot;Action without a Meeting&amp;quot; :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:17] &amp;amp;lt;matt_&amp;amp;gt; This works as long as &amp;quot;all members of the Board of Directors [...] consent thereto in writing or by electronic transmission, and such writings or electronic transmissions are filed with the records of the meetings of the Board of Directors&amp;quot;, because &amp;quot;Such consent shall be treated as a valid and proper vote of the Board of Directors or committee thereof for all purposes&amp;quot;.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:21] &amp;amp;lt;matt_&amp;amp;gt; So, long-story short, any decisions that we make here need to be unanimous to be binding. We can change this by voting to amend the bylaws during this meeting, if you want, or we can leave that for later.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:39] &amp;amp;lt;mattie_p&amp;amp;gt; mrcoolbp, matt_ thanks for the clarification&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:46] &amp;amp;lt;mrcoolbp&amp;amp;gt; np&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:44:58] &amp;amp;lt;Bytram&amp;amp;gt; thanks for the clarification&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:10] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay: move to vote on #3&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:12] &amp;amp;lt;xlefay&amp;amp;gt; matt_, thanks for the full explanation &amp;amp; clarification. It's much appreciated. Anyway, I suggest we just move to the vote.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:26] &amp;amp;lt;matt_&amp;amp;gt; cool. NCommander, ready?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:44] &amp;amp;lt;NCommander&amp;amp;gt; Call the vote&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:49] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of amending the Bylaws of the Corporation to allow meetings of the Board of Directors to be held on IRC, such that any votes taken at such a meeting shall be confirmed after said meeting by email to the Secretary of the Corporation to be binding and effective, (or, in the event that such a meeting would be unlawful, to amend the Bylaws of the Corporation to allow the Board of Directors to take action without a meeting, such that&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:45:53] &amp;amp;lt;matt_&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:02] &amp;amp;lt;NCommander&amp;amp;gt; aye&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:05] &amp;amp;lt;NCommander&amp;amp;gt; wait&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:08] &amp;amp;lt;NCommander&amp;amp;gt; where the rest of it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:14] &amp;amp;lt;mrcoolbp&amp;amp;gt; such that...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:14] &amp;amp;lt;NCommander&amp;amp;gt; &amp;quot;such that ...&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:25] &amp;amp;lt;matt_&amp;amp;gt; please stand by :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:46:57] &amp;amp;lt;matt_&amp;amp;gt; it was too long :(&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:47:06] &amp;amp;lt;matt_&amp;amp;gt; ok, a 2-parter. please stand by :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:47:15] &amp;amp;lt;xlefay&amp;amp;gt; I cannot, as a staff member, agree with such an amendment unless, a format is first declared. So that, meetings on IRC will be properly structured and be sound. That's, my take on it anyway...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:47:26] &amp;amp;lt;xlefay&amp;amp;gt; but, feel free to ignore that hehe :P&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:47:43] &amp;amp;lt;NCommander&amp;amp;gt; xlefay, the format doesn't need to be locked in the bylaws&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:47:46] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: a discussion on the format is forthcoming already&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:48:00] &amp;amp;lt;xlefay&amp;amp;gt; NCommander, true, but it should be declared (say, on the wiki)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:48:05] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of amending the Bylaws of the Corporation to allow meetings of the Board of Directors to be held on IRC, such that any votes taken at such a meeting shall be confirmed after said meeting by email to the Secretary of the Corporation to be binding and effective, (or, in the event that such a meeting would be unlawful, to amend the Bylaws of the&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:48:09] &amp;amp;lt;matt_&amp;amp;gt; Corporation to allow the Board of Directors to take action without a meeting, such that any such action shall require the vote of a majority of the Directors then in office, confirmed by email to the Secretary of the Corporation, to be binding and effective):&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:48:29] &amp;amp;lt;NCommander&amp;amp;gt; xlefay, and it will be, but this is just fixig the bylaws so we can formally do it on IRC at all&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:48:52] &amp;amp;lt;Bytram&amp;amp;gt; matt_: question....&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:00] &amp;amp;lt;NCommander&amp;amp;gt; matt_, still seems bifuricated, stuff it on pastebin.com or something&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:10] &amp;amp;lt;NCommander&amp;amp;gt; or maybe xchat being stupid&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:11] &amp;amp;lt;Bytram&amp;amp;gt; are we over-specifying by mentioning &amp;quot;IRC&amp;quot;...&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:13] &amp;amp;lt;NCommander&amp;amp;gt; I see the whole thing now&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:21] &amp;amp;lt;matt_&amp;amp;gt; Bytram, it is complete.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:24] &amp;amp;lt;mrcoolbp&amp;amp;gt; bytram: no&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:37] &amp;amp;lt;matt_&amp;amp;gt; i meant NCommander :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:49:54] &amp;amp;lt;paulej72&amp;amp;gt; does this till have the x days stuff in effect&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:12] &amp;amp;lt;matt_&amp;amp;gt; Bytram, what other means would you envision wanting to use for a board meeting?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:22] &amp;amp;lt;xlefay&amp;amp;gt; NCommander, mrcoolbp, I have full faith in the board and the staff, but.. this is binding so I generally feel safer if something is first declared/written up/proposed before it is decided, just to avoid misunderstandings and the likes later on. This is just me &amp;quot;playing it safe&amp;quot;, feel free to disregard it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:34] &amp;amp;lt;matt_&amp;amp;gt; paulej72, the final text will have to be approved via email.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:42] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: it's been duly noted&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:52] &amp;amp;lt;mrcoolbp&amp;amp;gt; I'm gonna vote:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:50:54] &amp;amp;lt;mrcoolbp&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:03] &amp;amp;lt;Bytram&amp;amp;gt; so, IRC and *ONLY* IRC? No other real-time chat-type system would be permitted. i don't know of any specific alternative off-hand, but it is an *instance* of a *class* of communication tools.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:05] &amp;amp;lt;matt_&amp;amp;gt; xlefay, paulej72, the issue is that normally, this would be attached to an email or presented at a meatspace meeting, etc.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:16] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: we can always ammend later.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:43] &amp;amp;lt;NCommander&amp;amp;gt; Bytram, this is for regular BoD meetings, special meetings can be in any formal, meatspace or virtual space&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:54] &amp;amp;lt;matt_&amp;amp;gt; Bytram, if we wanted to use an alternative means, it would be easy to amend the bylaws again.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:51:56] &amp;amp;lt;xlefay&amp;amp;gt; Also, I suggest, that, those decisions are only binding if they are, indeed, properly documented.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:07] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: like a conference call? If so, I'm good then.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:10] &amp;amp;lt;NCommander&amp;amp;gt; and if we're going to move those somewhere else, we should have to vote on it&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:17] &amp;amp;lt;xlefay&amp;amp;gt; (with of course, those predefined templates)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:18] &amp;amp;lt;Bytram&amp;amp;gt; agreed.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:22] &amp;amp;lt;NCommander&amp;amp;gt; Bytram, that's already explicately allowed by the current bylaws&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:52:28] &amp;amp;lt;matt_&amp;amp;gt; xlefay, thus the &amp;quot;shall be confirmed after said meeting by email&amp;quot; line.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:53:09] &amp;amp;lt;xlefay&amp;amp;gt; matt_, I meant, on a public forum - since, we are for the public benefit? Say, the wiki? Of course, I understand if there are exceptions to certain decisions.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:53:18] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: yes, I'd forgotten about that temporarily. thanks for the reminder. I'm good.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:53:24] &amp;amp;lt;mrcoolbp&amp;amp;gt; xlefay: please bring that up at the format discussion&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:53:47] &amp;amp;lt;xlefay&amp;amp;gt; mrcoolbp, will do. Just figured I'd lay it out there, for possible amendment into the amendment itself.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:53:58] &amp;amp;lt;matt_&amp;amp;gt; xlefay, we are posting the minutes on the wiki. Once we have an actual official meeting (if we amend the bylaws to allow such a thing over IRC, for example), the minutes will be placed on the wiki in a standard format, i would think.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:54:28] &amp;amp;lt;NCommander&amp;amp;gt; anyway, Aye&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:54:34] &amp;amp;lt;mrcoolbp&amp;amp;gt; Aye&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:54:45] &amp;amp;lt;xlefay&amp;amp;gt; matt_, that's good - but shouldn't that be a requirement, for the sake of completeness? (forgive my questions, just ensuring I fully understand)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:54:50] &amp;amp;lt;matt_&amp;amp;gt; hah! to the question 50 lines up :D let me restate it:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:54:59] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of amending the Bylaws of the Corporation to allow meetings of the Board of Directors to be held on IRC, such that any votes taken at such a meeting shall be confirmed after said meeting by email to the Secretary of the Corporation to be binding and effective, (or, in the event that such a meeting would be unlawful, to amend the Bylaws of the&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:04] &amp;amp;lt;matt_&amp;amp;gt; Corporation to allow the Board of Directors to take action without a meeting, such that any such action shall require the vote of a majority of the Directors then in office, confirmed by email to the Secretary of the Corporation, to be binding and effective):&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:09] &amp;amp;lt;mrcoolbp&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:11] &amp;amp;lt;matt_&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:18] &amp;amp;lt;NCommander&amp;amp;gt; Aye&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:20] &amp;amp;lt;matt_&amp;amp;gt; Resolved.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:25] &amp;amp;lt;matt_&amp;amp;gt; Great! I will circulate the text of the amendment for final approval once I have it ready.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:41] &amp;amp;lt;NCommander&amp;amp;gt; yay&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:44] &amp;amp;lt;matt_&amp;amp;gt; Now, on to the proposal for issuing common stock to NCommander and myself to facilitate the transfer of assets from us to the Corporation without placing the Corporation in debt.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:55:53] &amp;amp;lt;matt_&amp;amp;gt; Did you guys have a chance to review the document that I sent? If so, what did you think of it? Would you like me to recap the purpose/benefits of this proposal?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:05] &amp;amp;lt;mrcoolbp&amp;amp;gt; yes please&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:14] &amp;amp;lt;matt_&amp;amp;gt; To recap, this agreement accomplishes the following:&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:18] &amp;amp;lt;NCommander&amp;amp;gt; briefly, not sure, yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:19] &amp;amp;lt;matt_&amp;amp;gt; 1. SoylentNews acquires all rights to its own accounts, data, domains, etc., which are currently owned by Michael and myself.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:24] &amp;amp;lt;matt_&amp;amp;gt; 2. SoylentNews gets long-term liabilities for start-up costs off of its books (i.e., SN is not in debt to anyone). If, once SN is financially stable, we wanted to reimburse start-up costs, the board could authorize the payment of a dividend, etc.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:27] &amp;amp;lt;matt_&amp;amp;gt; 3. The agreement provides a mechanism for us to contribute some cash directly to SN, which would allow SN to start directly paying for hosting, etc., thus minimizing accumulation of personal expenses for which we would later want to seek reimbursement. If this is of interest, we should discuss the amounts of cash that we would want to contribute. I included $700 for me as an example in the attachment.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:32] &amp;amp;lt;matt_&amp;amp;gt; 4. Tax implications are minimal because there are no restrictions that will lapse (e.g., vesting). If we wanted to include a vesting schedule, we would include that in a separate shareholder's agreement, which would be a bit more complicated (although I do have a template). This would then likely require the 83(b) election that I mentioned in our last meeting, unless we decided to impose vesting restrictions later.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:37] &amp;amp;lt;matt_&amp;amp;gt; 5. If the same number of shares are issued to Michael and to me, then there will be no change in authority relative to the current situation with a 3-member board that includes the two of us. For example, it would not be possible to accidentally sell the corporation to DICE, as both Michael and I would have to agree to such a sale :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:56:47] &amp;amp;lt;matt_&amp;amp;gt; i think that's pretty much it. =)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:57:30] &amp;amp;lt;xlefay&amp;amp;gt; I think that speaks for itself.. as a non-board member, let me just say &amp;quot;aye&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:57:35] &amp;amp;lt;mrcoolbp&amp;amp;gt; heh&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:57:50] &amp;amp;lt;Bytram&amp;amp;gt; matt_: is this *common* stock or *capital* stock?&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:57:55] &amp;amp;lt;mrcoolbp&amp;amp;gt; common&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:57:59] &amp;amp;lt;matt_&amp;amp;gt; Bytram, those two are the same thing for us :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:58:06] &amp;amp;lt;mrcoolbp&amp;amp;gt; oh&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:58:17] &amp;amp;lt;matt_&amp;amp;gt; Bytram, our Certificate of Incorporation doesn't allow us to issue Preferred Stock or any other kind of capital stock.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:58:31] &amp;amp;lt;Bytram&amp;amp;gt; ahhhhh, got it now. thanks!&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:58:37] &amp;amp;lt;NCommander&amp;amp;gt; I admit I'm still concerned about possible tax stuff on both a personal and corporate level&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:13] &amp;amp;lt;NCommander&amp;amp;gt; I'm willing to investigate further (I needo to talk w/ my accountant), and perhaps have things lined up for a formal yay/nay next meeting&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:20] &amp;amp;lt;matt_&amp;amp;gt; NCommander, the key with this is: if we want to do it, we should do it before the stock has any value, otherwise it gets more complicated.&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:31] &amp;amp;lt;mrcoolbp&amp;amp;gt; = /&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:33] &amp;amp;lt;NCommander&amp;amp;gt; Well, that's going to take awhile&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:41] &amp;amp;lt;NCommander&amp;amp;gt; with making sure we have proper provisions in allowing the PBC to buy itself back&amp;lt;br /&amp;gt;&lt;br /&gt;
[23:59:51] &amp;amp;lt;mrcoolbp&amp;amp;gt; yes, agreed&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:00:27] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander, matt_: it's true that we don't currently have a revenue stream, but we do have plans in place to start that going&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:00:31] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: I'm not so sure about how long it would take; between subscriptions and swag, we could be in the black in a few weeks.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:00:52] &amp;amp;lt;matt_&amp;amp;gt; normally this type of agreement is done within 2-3 days of incorporation :/&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:01:05] &amp;amp;lt;Bytram&amp;amp;gt; NOTE: *could* not necessarily *will*.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:01:12] &amp;amp;lt;matt_&amp;amp;gt; to eliminate any possibility that the stock has increased in value between incorporation and issuance.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:01:27] &amp;amp;lt;matt_&amp;amp;gt; NCommander, when can you talk with your accountant?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:01:53] &amp;amp;lt;NCommander&amp;amp;gt; probably this week&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:02:27] &amp;amp;lt;matt_&amp;amp;gt; ok. i know that you're planning a trip soon, do you think it would be realistic to try to sqeeze in a meeting before then, at least on this issue?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:02:45] &amp;amp;lt;NCommander&amp;amp;gt; My concern with issuing stock of any kind is it means that part of the corporation isn't owned by itself. Lets say a year from now, we're in the black you have got stock though for the site&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:07] &amp;amp;lt;NCommander&amp;amp;gt; And then hit a personal issue like bankruptecy and sell assets to a third part :-P&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:08] &amp;amp;lt;Bytram&amp;amp;gt; can the board agree now to have the corporation issue stock, contingent on NCommander's discussion with his accountant and acceptance of it?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:27] &amp;amp;lt;matt_&amp;amp;gt; NCommander, oh, this is a key point. The Board of Directors has to approve all transfers of stock.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander: I don't beleive they can be sold to a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:34] &amp;amp;lt;mrcoolbp&amp;amp;gt; ah that&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:37] &amp;amp;lt;matt_&amp;amp;gt; NCommander, so you're not allowed to sell it without board approval.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:43] &amp;amp;lt;matt_&amp;amp;gt; that's in our bylaws.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:03:58] &amp;amp;lt;NCommander&amp;amp;gt; ALright&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:04:15] &amp;amp;lt;NCommander&amp;amp;gt; I'm willing to approve a tentative approval to make sure I'm not upsetting a legal mess&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:04:31] &amp;amp;lt;matt_&amp;amp;gt; approve a tentative approval :?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:04:32] &amp;amp;lt;paulej72&amp;amp;gt; so what happens if someone does sell it. is the stock void?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:04:43] &amp;amp;lt;matt_&amp;amp;gt; paulej72, the sale is null and void.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:04:50] &amp;amp;lt;paulej72&amp;amp;gt; ok&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:08] &amp;amp;lt;NCommander&amp;amp;gt; matt_, basically, make it hinge on me talking taxes w/ my personal accountent, and if he doesn't see any issues for my person issue, ACK&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:25] &amp;amp;lt;juggs&amp;amp;gt; could a majority of board members cause the bylaw that forbids the sale of stock to be removed?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:33] &amp;amp;lt;matt_&amp;amp;gt; ok. i can adjust my pre-prepared voting language to that effect.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:43] &amp;amp;lt;matt_&amp;amp;gt; juggs, yes.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:45] &amp;amp;lt;NCommander&amp;amp;gt; juggs, yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:46] &amp;amp;lt;mrcoolbp&amp;amp;gt; juggs: yes&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:05:55] &amp;amp;lt;NCommander&amp;amp;gt; wow, echo&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:03] &amp;amp;lt;juggs&amp;amp;gt; ha&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:07] &amp;amp;lt;juggs&amp;amp;gt; I hear ya!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:27] &amp;amp;lt;matt_&amp;amp;gt; ok, please stand by for a vote. of course, let me know if you have any questions/issues with the following language.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:34] &amp;amp;lt;matt_&amp;amp;gt; this is a long one :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:45] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of authorizing the officers of the Corporation to sell and issue 50,000 shares of the Corporation's Common Stock to Michael Casadevall at a purchase price of $0.10 per share, payable in cash, or by any other form of consideration permitted by applicable law, including the contribution of tangible property, and authorizing the officers of the Corporation to sell and issue 50,000 shares of the Corporation's Common Stock to Matt Ang&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:49] &amp;amp;lt;matt_&amp;amp;gt; payable in cash, or by any other form of consideration permitted by applicable law, including the contribution of tangible property, and resolving that the form of the Founder's Common Stock Subscription Agreement be, and hereby is, adopted, ratified and approved, and that the sale and issuance of Common Stock to each of the above named persons shall be conditioned upon the receipt by the Corporation of (a) the purchase price for said stock and (b)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:06:53] &amp;amp;lt;matt_&amp;amp;gt; Agreement, including executed copies of any and all documents attached thereto as exhibits, and that the officers of the Corporation be, and each of them hereby is, authorized and directed, for and on behalf of the Corporation, to take such further action and execute such additional documents as each may deem necessary or appropriate to carry out the purposes of this resolution:&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:07:44] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ are we getting message truncation again?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:07:49] &amp;amp;lt;mattie_p&amp;amp;gt; looks like you missed a few words in there&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:07:55] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, i think that came through.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:04] &amp;amp;lt;matt_&amp;amp;gt; mattie_p, let me triple-check.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:05] &amp;amp;lt;mattie_p&amp;amp;gt; matt_: your name didn't&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:09] &amp;amp;lt;Bytram&amp;amp;gt; first paragraph, your name is incomplete&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:25] &amp;amp;lt;Bytram&amp;amp;gt; matt_: ^^&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:28] &amp;amp;lt;paulej72&amp;amp;gt; flood control&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:39] &amp;amp;lt;matt_&amp;amp;gt; *sigh&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:46] &amp;amp;lt;juggs&amp;amp;gt; :D&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:08:49] &amp;amp;lt;matt_&amp;amp;gt; ok, trying again :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:10] &amp;amp;lt;paulej72&amp;amp;gt; paste in smaller chunks&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:16] &amp;amp;lt;NCommander&amp;amp;gt; matt_, pastebin.com or something similar is your friend&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:19] &amp;amp;lt;paulej72&amp;amp;gt; submit between each&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:37] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of authorizing the officers of the Corporation to sell and issue 50,000 shares of the Corporation's Common Stock to Michael Casadevall at a purchase price of $0.10 per share, payable in cash, or by any other form of consideration permitted by applicable law, including the&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:44] &amp;amp;lt;matt_&amp;amp;gt; contribution of tangible property, and authorizing the officers of the Corporation to sell and issue 50,000 shares of the Corporation's Common Stock to Matt Angel at a purchase price of $0.10 per share,&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:09:50] &amp;amp;lt;matt_&amp;amp;gt; payable in cash, or by any other form of consideration permitted by applicable law, including the contribution of tangible property, and resolving that the form of the Founder's Common Stock Subscription Agreement be, and hereby is, adopted, ratified and approved, and that the sale and&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:11:35] &amp;amp;lt;matt__&amp;amp;gt; Agreement, including executed copies of any and all documents attached thereto as exhibits, and that the officers of the Corporation be, and each of them hereby is, authorized and directed, for and on behalf of the Corporation, to take such further action and execute such additional&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:11:40] &amp;amp;lt;matt__&amp;amp;gt; documents as each may deem necessary or appropriate to carry out the purposes of this resolution:&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:15] &amp;amp;lt;paulej72&amp;amp;gt; .op&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:34] &amp;amp;lt;matt__&amp;amp;gt; paulej72, i was flood-controlled :(&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:43] &amp;amp;lt;NCommander&amp;amp;gt; matt_, pastebin is your friend, seriously&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:46] &amp;amp;lt;xlefay&amp;amp;gt; matt__, hence why pastebin is suggested :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:47] &amp;amp;lt;NCommander&amp;amp;gt; Its easier to read&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:48] &amp;amp;lt;juggs&amp;amp;gt; missed a bit again around here &amp;quot;issuance of Common Stock to each of the above named persons shall be conditioned upon the receipt by the Corporation of (a) the purchase price for said stock and (b)&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:12:49] &amp;amp;lt;mrcoolbp&amp;amp;gt; .voice matt__&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:00] &amp;amp;lt;matt__&amp;amp;gt; NCommander, ack. ok, pastebin next time, definitely!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:29] &amp;amp;lt;matt__&amp;amp;gt; anyway, i think everyone has the jist of it :)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:32] &amp;amp;lt;NCommander&amp;amp;gt; matt__, 50k shared is &amp;gt; what either of us owe though&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:36] &amp;amp;lt;NCommander&amp;amp;gt; *shares&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:38] &amp;amp;lt;matt__&amp;amp;gt; so, we can just do the final text over email.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:13:49] &amp;amp;lt;matt__&amp;amp;gt; NCommander, it's at $0.10 per share.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:01] &amp;amp;lt;NCommander&amp;amp;gt; 50000*.10 == 5000&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:05] &amp;amp;lt;juggs&amp;amp;gt; $5K each?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:07] &amp;amp;lt;matt__&amp;amp;gt; NCommander, we have to value our &amp;quot;Tangible and Intangible Property&amp;quot; in a way that the IRS, etc. will accept.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:11] &amp;amp;lt;mattie_p&amp;amp;gt; up to 50,000 shares are authorized to be sold, don't have to sell them all&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:19] &amp;amp;lt;NCommander&amp;amp;gt; oh&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:14:19] &amp;amp;lt;matt__&amp;amp;gt; so, for example, your contributions to date add up to a total value of $5000.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:15:26] &amp;amp;lt;mrcoolbp&amp;amp;gt; .voice matt_&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:15:48] &amp;amp;lt;matt_&amp;amp;gt; Ok, so the last remaining step to get the Corporation officially set up is: I will collect all of the resolutions adopted by the board so far, including language for amending the Bylaws to allow meetings on IRC, and put together a &amp;quot;Unanimous Written Consent of the Board of Directors&amp;quot; document, which the three of us should sign.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:16:18] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:16:24] &amp;amp;lt;NCommander&amp;amp;gt; k&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:16:26] &amp;amp;lt;matt_&amp;amp;gt; Finally, Item 4: Any other business (community involvement in corporate governance, SN policies and procedures manual, including: staff appointment &amp;amp; authority, account and password management, individual team policy, policy on retaining records, etc.).&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:16:37] &amp;amp;lt;matt_&amp;amp;gt; NCommander, how's your incorporation post going?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:17:20] &amp;amp;lt;matt_&amp;amp;gt; i ask, because i think that it would be nice to post the bylaws, etc. on the wiki, so that everyone can see them...&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:17:50] &amp;amp;lt;Bytram&amp;amp;gt; matt_: point of order? was there a vote taken on the issuance of common stock?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:17:58] &amp;amp;lt;mrcoolbp&amp;amp;gt; negative&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:18:10] &amp;amp;lt;matt_&amp;amp;gt; Bytram, due to technical issues, we will go with an email vote for that one, i think.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:18:22] &amp;amp;lt;NCommander&amp;amp;gt; matt_, its going very slowly&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:18:30] &amp;amp;lt;NCommander&amp;amp;gt; I got about a 1/3rd through it&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:18:30] &amp;amp;lt;matt_&amp;amp;gt; Bytram, since it didn't seem that there were any questions (unless i missed any).&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:18:55] &amp;amp;lt;Bytram&amp;amp;gt; matt_: okay, thanks.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:19:42] &amp;amp;lt;matt_&amp;amp;gt; NCommander, also at the last meeting we had mentioned that your post would be a geat place to ask the community specifically how they would like to be involved in the governance of SoylentNews PBC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:12] &amp;amp;lt;mrcoolbp&amp;amp;gt; yes, please throw that in there somewhere&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:17] &amp;amp;lt;matt_&amp;amp;gt; let us know if you need any help with that, ok?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:32] &amp;amp;lt;NCommander&amp;amp;gt; mrcoolbp, its in there&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:35] &amp;amp;lt;NCommander&amp;amp;gt; alright&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:36] &amp;amp;lt;mrcoolbp&amp;amp;gt; great&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:37] &amp;amp;lt;matt_&amp;amp;gt; Next is the SN policies and procedures manual.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:38] &amp;amp;lt;NCommander&amp;amp;gt; *already&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:20:43] &amp;amp;lt;mrcoolbp&amp;amp;gt; On the Policy manual I have an update&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:21:14] &amp;amp;lt;mrcoolbp&amp;amp;gt; Janrinok and I started drafting an SN Policy manual based on conversations with LaminatorX and matt_&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:21:35] &amp;amp;lt;mrcoolbp&amp;amp;gt; once we have something readable, the plan is to circulate on the staff list for suggestions and criticisms&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:22:08] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ can you elaborate on &amp;quot;staff appointment &amp;amp; authority&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:22:10] &amp;amp;lt;mrcoolbp&amp;amp;gt; ?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:22:43] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, actually, i think that you probably already have that in there. basically, how does someone become &amp;quot;staff&amp;quot;, and what authority do staff have.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:22:59] &amp;amp;lt;mrcoolbp&amp;amp;gt; oh, part of the policy manual got it&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:23:00] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:23:03] &amp;amp;lt;mrcoolbp&amp;amp;gt; account and password management: We have done a decent job of duplicating privledges and passwords on various accounts&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:23:15] &amp;amp;lt;mrcoolbp&amp;amp;gt; but I think we need to do a once over on each account&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:23:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; I can work with paulej72 on making sure that is done&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:23:43] &amp;amp;lt;mrcoolbp&amp;amp;gt; I think 3 people should be able to access each system&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:09] &amp;amp;lt;mrcoolbp&amp;amp;gt; but we had discussed locking the keys in a container and needing mulitple people to unlock (food for thought)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:30] &amp;amp;lt;matt_&amp;amp;gt; nice. it sounds like you have a good grip on the issue. the question of SN's policy on retaining records came up recently, as well.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:35] &amp;amp;lt;paulej72&amp;amp;gt; would like it to be 3 qualified people, but we will tak what we can get&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:39] &amp;amp;lt;Bytram&amp;amp;gt; mrcoolbp: do we have *one* place which itemizes *all* the (computer) accounts we have? Each system (e.g. Boron), service, DNS entries, *everything*?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:42] &amp;amp;lt;mrcoolbp&amp;amp;gt; paulej72: well said&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:24:53] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram, not compiled, I'll note that&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:25:12] &amp;amp;lt;Bytram&amp;amp;gt; great! thank you.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:25:27] &amp;amp;lt;xlefay&amp;amp;gt; We can certainly get records from LDAP, as for local accounts - that'll require some inventorisation.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:25:28] &amp;amp;lt;Bytram&amp;amp;gt; might check with xlefay who has a pretty good list from setting up icinga, too.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:25:33] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ that's all I have for now on that item, is now a good time to bring up a point from a staff memeber who couldn't make it?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:25:48] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: noted, thank you!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:26:10] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, yes! we have reached the end of the agenda, so let's open the floor.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:26:22] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:26:31] &amp;amp;lt;mrcoolbp&amp;amp;gt; &amp;lt;+mechanicjay&amp;gt; I'm wondering about regular meetings, their frequency and I'd like to see 1 weeks notice before future meetings. While that wont' be an idea time, it does give folks a chance to arrange their schedules accordingly.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:26:31] &amp;amp;lt;mrcoolbp&amp;amp;gt; &amp;lt;+mechanicjay&amp;gt; Also, now that incorporation has started, what are the responsibilities of regular old staff folks. Does the relationship between a volunteer staff person and the corporation get formalized at some point?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:26:51] &amp;amp;lt;mrcoolbp&amp;amp;gt; idea = ideal I think&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:27:18] &amp;amp;lt;mrcoolbp&amp;amp;gt; the second one I'll add to my SN policy manual draft&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:27:38] &amp;amp;lt;mrcoolbp&amp;amp;gt; I have &amp;quot;a template for that&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:27:43] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, yes, the second one sounds like it would be perfect for the policy draft.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:27:45] &amp;amp;lt;matt_&amp;amp;gt; =)&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:28:14] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ is one week notice a good goal to shoot for?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:28:29] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, as for the first one, it's also related to the policy draft, as it should be made clear that the board meetings are different than the staff meetings, i think.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:28:52] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ if you want I can add a distiction to the manual&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:03] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, this also gets to the issue of electing additional directors, which we can do at any time.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:11] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, yes please.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:13] &amp;amp;lt;mrcoolbp&amp;amp;gt; ah yes, nice segway&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:17] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ noted&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:37] &amp;amp;lt;matt_&amp;amp;gt; also, i forgot one last item that was added to the agenda: discuss a standard format for board meetings&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:29:50] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay, so let's take those one at a time&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:30:13] &amp;amp;lt;mrcoolbp&amp;amp;gt; first, are there any board positions that we feel should be fulfilled?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:30:24] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ could you recap the common unfilled positions?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:30:33] &amp;amp;lt;xlefay&amp;amp;gt; oops, a bit too late, but... Additionally, when meetings are made in advance, people can easily - suggest topics/items ahead of time.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:30:47] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, well there are really two questions there: do we want to elect additional Directors, and do we want to appoint additional officers.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:06] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ can you elaborate on the difference?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:27] &amp;amp;lt;Bytram&amp;amp;gt; I'd appreciate a refresher, too.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:32] &amp;amp;lt;matt_&amp;amp;gt; xlefay, actually, wouldn't it be good if there were a wiki where people could raise issues, so that we would be sure to bring them up at the next meeting, whenever that meeting is?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:53] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ that's a great idea&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:55] &amp;amp;lt;mattie_p&amp;amp;gt; officers are &amp;quot;official&amp;quot; staff of the corporation, board members vote in these meetings. They do not necessarily overlap, although right now they do&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:31:58] &amp;amp;lt;xlefay&amp;amp;gt; matt_, that's a great idea!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:32:31] &amp;amp;lt;Bytram&amp;amp;gt; how would/could they be different?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:32:41] &amp;amp;lt;matt_&amp;amp;gt; mrcoolbp, ok. so directors are directors (they take votes at board meetings, and the board has general responsibility for the corporation), while the officers are President, CEO, Treasurer, Secretary, and any number of Vice Presidents, Assistant Treasurers, Assistant Secretaries, etc., each of whom has specific duties.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:32:57] &amp;amp;lt;paulej72&amp;amp;gt; do we want team leaders to be board members?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:33:05] &amp;amp;lt;matt_&amp;amp;gt; mattie_p, exactly!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:33:08] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander ^^&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:06] &amp;amp;lt;NCommander&amp;amp;gt; paulej72, dev, Ieditoral, community, IRC?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:07] &amp;amp;lt;mattie_p&amp;amp;gt; officers run the day to day business of the corporation. board members control the overall direction and appoint officers, but do not make day-to-day operational business decisions&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:08] &amp;amp;lt;matt_&amp;amp;gt; i would suggest that the officers should be given maximum leeway to discharge their duties, and that the board only step in on specific issues if there is a credible legal or financial issue.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:22] &amp;amp;lt;NCommander&amp;amp;gt; ack on what matt_ says&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:32] &amp;amp;lt;mattie_p&amp;amp;gt; so each of the three board members currently has two hats, if you will&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:34:43] &amp;amp;lt;mrcoolbp&amp;amp;gt; matt_ I ACK that as well&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:17] &amp;amp;lt;paulej72&amp;amp;gt; yes NCommander&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:35] &amp;amp;lt;juggs&amp;amp;gt; ack as in dislike?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:44] &amp;amp;lt;xlefay&amp;amp;gt; ack as in acknowledge I assume&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:45] &amp;amp;lt;mattie_p&amp;amp;gt; ack = acknowledge&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:50] &amp;amp;lt;juggs&amp;amp;gt; ty&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:53] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: and qa, too?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:35:53] &amp;amp;lt;matt_&amp;amp;gt; i would also suggest that the board be kept to a reasonable size to facilitate scheduling, discussion, and voting.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:09] &amp;amp;lt;NCommander&amp;amp;gt; Bytram, yes, but I also don't want to overcrowd the board&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:19] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: noted.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:39] &amp;amp;lt;NCommander&amp;amp;gt; I recommend we toss this on chillax or the mailing list, and bring it back up next meeting&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:54] &amp;amp;lt;mrcoolbp&amp;amp;gt; NCommander: agreed&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:54] &amp;amp;lt;Bytram&amp;amp;gt; matt_: in your experience, how large is &amp;quot;too big&amp;quot;?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:36:55] &amp;amp;lt;paulej72&amp;amp;gt; and should the board confirm the current team structure or do a restructure if we do make team leaders booard members&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:37:20] &amp;amp;lt;mrcoolbp&amp;amp;gt; paulej72: we don't have an outline for the structure in any formal means&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:37:32] &amp;amp;lt;mrcoolbp&amp;amp;gt; so I wouldn't feel right confirming that&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:37:56] &amp;amp;lt;matt_&amp;amp;gt; Bytram, in the very early stages (e.g., now), it is helpful to keep it to 3, just to keep things moving forward. Pretty soon, i would imagine it could/should be increased, probably to a maximum of 5-ish.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:38:46] &amp;amp;lt;juggs&amp;amp;gt; I d/conned not sure if I missed anything :(&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:38:57] &amp;amp;lt;Bytram&amp;amp;gt; matt_: thanks. My experience has been that many more than 6 or so and things take much longer to decide. thanks for the confirmation.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:39:01] &amp;amp;lt;mrcoolbp&amp;amp;gt; juggs: check the log after&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:40:04] &amp;amp;lt;matt_&amp;amp;gt; Bytram, agreed. Also, there is a lot on the agenda in these early days, but pretty soon i would expect board meetings to need to happen less frequently, and have fewer major issues to discuss.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:40:28] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay, so should we move on to the Format for Board Meetings on IRC?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:41:17] &amp;amp;lt;matt_&amp;amp;gt; ok. any thoughts?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:41:28] &amp;amp;lt;Bytram&amp;amp;gt; should we discuss that here, and now, or just agree we need one and work itout later?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:41:52] &amp;amp;lt;Bytram&amp;amp;gt; the details of the IRC board meeting, that is&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:41:56] &amp;amp;lt;mrcoolbp&amp;amp;gt; maybe get someone on a task force that could propose something for another meeting?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:42:31] &amp;amp;lt;Bytram&amp;amp;gt; I'll take that.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:42:45] &amp;amp;lt;mrcoolbp&amp;amp;gt; Bytram: thanks, I'd suggest working with xlefay&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:42:51] &amp;amp;lt;mrcoolbp&amp;amp;gt; okay, anything else?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:42:54] &amp;amp;lt;mrcoolbp&amp;amp;gt; did we miss anything?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:43:52] &amp;amp;lt;Bytram&amp;amp;gt; I can't think of anything off-hand.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:44:11] &amp;amp;lt;matt_&amp;amp;gt; i think that's it. so my tasks (aside from investigating pastebin) are: draft and send a &amp;quot;Unanimous Written Consent of the Board of Directors&amp;quot; that includes the proposed amendment to the bylaws, and everything else that has been decided so far.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:44:29] &amp;amp;lt;NCommander&amp;amp;gt; Mine are bang on the subscription code, and call accountent&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:45:24] &amp;amp;lt;mrcoolbp&amp;amp;gt; mine are the policy manual and the store&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:45:27] &amp;amp;lt;Bytram&amp;amp;gt; I'll work on a draft format for holding Board Meeting discussions on IRC.&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:45:51] &amp;amp;lt;matt_&amp;amp;gt; NCommander, also to finish up your incorporation post?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:45:52] &amp;amp;lt;mrcoolbp&amp;amp;gt; I think that's it&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:00] &amp;amp;lt;NCommander&amp;amp;gt; oh that too&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:07] &amp;amp;lt;NCommander&amp;amp;gt; Beyond that, anything else, or can we close this ot?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:15] &amp;amp;lt;matt_&amp;amp;gt; All those in favor of adjourning?&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:26] &amp;amp;lt;Bytram&amp;amp;gt; NCommander: I can help with the incorporation post&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:28] &amp;amp;lt;NCommander&amp;amp;gt; aye&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:29] &amp;amp;lt;mrcoolbp&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:30] &amp;amp;lt;matt_&amp;amp;gt; Aye!&amp;lt;br /&amp;gt;&lt;br /&gt;
[00:46:32] &amp;amp;lt;matt_&amp;amp;gt; This Meeting of the Board of Directors of SoylentNews PBC stands adjourned!&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Incorporation/Bylaws&amp;diff=7649</id>
		<title>Incorporation/Bylaws</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Incorporation/Bylaws&amp;diff=7649"/>
		<updated>2014-05-29T21:10:43Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Article VI ~ Board of Directors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''LIBRENEWS FOUNDATION BYLAWS'''&lt;br /&gt;
&lt;br /&gt;
== Article I ~ Name ==&lt;br /&gt;
&lt;br /&gt;
The name of this corporation (hereinafter referred to as the Foundation) shall be LibreNews Foundation.&lt;br /&gt;
&lt;br /&gt;
== Article II ~ Purpose ==&lt;br /&gt;
&lt;br /&gt;
The purposes of the Foundation shall be:&lt;br /&gt;
* to create the best sources for independent, not-for-profit journalism&lt;br /&gt;
* to create forums where people can discuss, and review any topic&lt;br /&gt;
* to be an advocate for freedom of press, freedom of speech, and digital rights&lt;br /&gt;
* to improve the dissemination of news to the general public&lt;br /&gt;
* to help promote awareness of issues and challenges facing the aforementioned items.&lt;br /&gt;
* to provide a legal basis for member sites which promote the purposes of the Foundation&lt;br /&gt;
&lt;br /&gt;
== Article III ~ Definitions ==&lt;br /&gt;
&lt;br /&gt;
Terms in this document have the following meaning.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Account - [NOTE: cannot be &amp;quot;Under uncle Ed's mattress; how to define?] A savings or checking account at a Licensed Institution (Federal or State Bank or Credit Union.)&lt;br /&gt;
&amp;lt;li&amp;gt;Board Member - Someone who holds an office in the Foundation.&lt;br /&gt;
&amp;lt;li&amp;gt;Board of Directors - Is comprised of all of the Board Members.&lt;br /&gt;
&amp;lt;li&amp;gt;Business Day - Any calendar weekday (Monday, Tuesday, Wednesday, Thursday, or Friday) that is also not one of the ten (10) official Federal holiday as defined in &amp;quot;Title 5 U.S. Code § 6103 - Holidays&amp;quot;: &lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;New Year’s Day, January 1.&lt;br /&gt;
&amp;lt;li&amp;gt;Birthday of Martin Luther King, Jr., the third Monday in January.&lt;br /&gt;
&amp;lt;li&amp;gt;Washington’s Birthday, the third Monday in February.&lt;br /&gt;
&amp;lt;li&amp;gt;Memorial Day, the last Monday in May.&lt;br /&gt;
&amp;lt;li&amp;gt;Independence Day, July 4.&lt;br /&gt;
&amp;lt;li&amp;gt;Labor Day, the first Monday in September.&lt;br /&gt;
&amp;lt;li&amp;gt;Columbus Day, the second Monday in October.&lt;br /&gt;
&amp;lt;li&amp;gt;Veterans Day, November 11.&lt;br /&gt;
&amp;lt;li&amp;gt;Thanksgiving Day, the fourth Thursday in November.&lt;br /&gt;
&amp;lt;li&amp;gt;Christmas Day, December 25. &lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Majority Vote - Strictly greater than exactly fifty (50) percent of those voting.&lt;br /&gt;
&amp;lt;li&amp;gt;Member Site - A semi-autonomous organization that exists to promote the goals and objectives of the Foundation. Member sites operate under a charter ratified by the Board of Directors. Such objectives shall be in line with the purposes of the Foundation. &lt;br /&gt;
&amp;lt;li&amp;gt;Quorum - At least two-thirds (2/3) of the designated members.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Article IV ~ Membership ==&lt;br /&gt;
&lt;br /&gt;
At the time of incorporation, the Foundation shall have no members. '''ISSUE: what is a member'''&lt;br /&gt;
&lt;br /&gt;
== Article V ~ Member Sites ==&lt;br /&gt;
&lt;br /&gt;
=== Section 1 - Creation of a Member Site ===&lt;br /&gt;
Voting for a new Member Site requires a majority vote of voting members present at a Board Meeting.  New Member Sites may be proposed either by a Board Member or by an independent organization.  Such proposals must be submitted to the Secretary, in writing, at least ten (10) business days prior to the Foundation Board meeting in which it is to be discussed/voted.&lt;br /&gt;
&lt;br /&gt;
=== Section 2 - Member Site Charter ===&lt;br /&gt;
Each Member Site shall draft and present the Board of Directors with a charter that defines their operational procedures, and specific objectives. This charter shall include the following:&lt;br /&gt;
'''ISSUE: what do we do about the site amending their charter after becoming a member and how do we deal with disputes over the site charter between the board and the site's owners.'''&lt;br /&gt;
* Name of the member site&lt;br /&gt;
* Specific objectives of the member site&lt;br /&gt;
* Operating staff positions of the member site&lt;br /&gt;
* Projected operating budget&lt;br /&gt;
* Method of Dissolution&lt;br /&gt;
&lt;br /&gt;
Each Member Site shall appoint a member of its staff to represent it at Foundation meetings, and to raise issues regarding that Member Site.&lt;br /&gt;
&lt;br /&gt;
=== Section 3 - Division of Income ===&lt;br /&gt;
A member site may raise funds via any means legal within the State of New Hampshire, and in accordance with both its charter and these bylaws. Money raised by a member site shall be deposited in an account designated by the Treasurer, and be divided in the following matter&lt;br /&gt;
&lt;br /&gt;
* 10% of incoming funds shall be placed in account designated as &amp;quot;Available Funds&amp;quot; for a member site to use freely towards the benefit of their objectives.&lt;br /&gt;
* 10% of incoming funds shall be placed in the main account for the Foundation, to provide funding for Foundation activities.&lt;br /&gt;
* The remaining 80% shall be placed in trust between a member-site and the Foundation&lt;br /&gt;
&lt;br /&gt;
The division of funds may be changed via agreement between the Board of Directors, and the operating staff of a Member Site.&lt;br /&gt;
&lt;br /&gt;
=== Section 4 - Trust Funds ===&lt;br /&gt;
Each site's trust fund is money that set aside for the use of the Member Site that raised it. Funds in trust are reserved for the member site that raised it, but the Board of Directors may, at their discretion, leverage funds against trust accounts for the benefit of the Foundation as a whole. Staff from a member site may request access to funds in their trust for any purpose by submitting a request to the Secretary.&lt;br /&gt;
&lt;br /&gt;
Requests may be one-time (i.e. purchase order), or in perpetuity (i.e., hosting expenses, employee salaries), and shall be submitted to the Treasurer any time up to ten (10) business days  prior to the meeting at which they are to be raised. Assuming available funding, requests shall be approved unless there is any legal, pressing, or overwhelming reason(s) for such a request to be denied. '''question: who decides what is denied and by what method'''&lt;br /&gt;
&lt;br /&gt;
Upon approval, funds shall be transferred to the Member Site's available funds, for use in the matter the request approved for.&lt;br /&gt;
&lt;br /&gt;
=== Section 5 - Expenditure of Funds ===&lt;br /&gt;
Member Sites must maintain a record of use of all expenditures, and submit such records to the Treasurer, to be documented as part of the general expenditures of the Foundation. All expenditures of funds shall only be used to further the objectives of a member site, or the Fondation as a whole, and must meet the requirements set by these bylaws.&lt;br /&gt;
&lt;br /&gt;
=== Section 6 - Employment by Member Sites ===&lt;br /&gt;
Member sites may, if they choose, hire full or part time employees to conduct duties including, but not limited to, site operation and maintainance, promotional activities and administrative support. The Operating Staff of a Member Site must submit a request for a paid position to the Secretary and Treasurer with the position name, description, and maximum expected expense that the respective site is willing to incur for said position. A Member Site must have funds available to cover the position through a combination of their trust fund and petty cash. '''question: what about future income? should this be counted'''&lt;br /&gt;
&lt;br /&gt;
For periods of employment for less than one (1) year, the member site must have funds available for the full duration of the position. For paid positions lasting more than one (1) year, funds must be available for at least one year. This condition may be waved by the Board of Directors if a Member Site's incoming revenue is stable, and can be expected to be maintained for the duration of employment. &lt;br /&gt;
&lt;br /&gt;
Upon receiving a request, funds shall be transferred to the Foundation's account, and the Foundation shall open a hiring requestion for the position, prudent to all rules and regulations in the State of New Hampshire, and the United States Department of Labor. The Foundation, in accordance with the Member Site shall select a candidate, and make an offer of employment on behalf of a member site. A Member Site may withdraw their request for a paid position at any time; the Foundation shall return funds withdrawn from a member site within one (1) week of the position being withdrawn. '''question: should this be 10 business days'''&lt;br /&gt;
&lt;br /&gt;
Member sites may include paid employees within their organizational charts as they see fit. Employees of a member site are employees of the Foundation for all intents and purposes, and subject to same standards of behaviour of any volunteer of the organization. All Employees are subject to these bylaws, as well as the charter of the member site which sponsored their employment. In the case of termination of an employee, remaining funds set aside for that position shall be returned to the Member Site within ten (10) business days.&lt;br /&gt;
&lt;br /&gt;
=== Section 7 - Dissolution ===&lt;br /&gt;
A Member Site may be dissolved by either its own operating staff, or by the Board of Directors by majority vote if just cause exists. Upon dissolution, all assets operated by a member site shall immediately be controlled by the Board of Directors. '''ISSUE: why should foundation dissolve a member site. This can be abused to steal their funds.  This should only be done when a site is essentially dead (i.e. no contact by the site's admins, or when there is an issue like the member site is knowingly hosting illegal stuff like CP).'''&lt;br /&gt;
&lt;br /&gt;
'''ISSUE: how does a site unjoin the foundation and what happens to their funds.  Should they be returned with a small maintenance fee removed?'''&lt;br /&gt;
&lt;br /&gt;
== Article VI ~ Board of Directors ==&lt;br /&gt;
&lt;br /&gt;
'''ISSUE: no mention on how to become a board member, term lengths, and such.  Also weather the member site's representative is a board member or just a non-voting attendee.  Are Officers members of the board upon being voted on if they are not already board members.  do we have members-at-large and do they have voting rights (i.e. community members that are part of the board for a period of time)'''&lt;br /&gt;
&lt;br /&gt;
=== Section 1 - List of Offices ===&lt;br /&gt;
The officers of this association shall be:&lt;br /&gt;
&lt;br /&gt;
* President&lt;br /&gt;
* Vice-President&lt;br /&gt;
* Secretary&lt;br /&gt;
* Treasurer&lt;br /&gt;
&lt;br /&gt;
=== Section 2 - Term Lengths ===&lt;br /&gt;
Officers shall be elected by majority vote of the board present at the annual meeting for the term of two years.&lt;br /&gt;
&lt;br /&gt;
=== Section 3 - Term Start ===&lt;br /&gt;
The term of officers so elected shall begin with the next meeting following the annual meeting, and shall continue until their successors are elected. '''ISSUE: there is period where no officers between election meeting and next'''&lt;br /&gt;
&lt;br /&gt;
=== Section 4 - Vacancies ===&lt;br /&gt;
A vacancy in any office shall be filled for the remainder of the term through appointment by the remaining officers, pending ratification by the membership at the next meeting.&lt;br /&gt;
&lt;br /&gt;
=== Section 5 - General ===&lt;br /&gt;
The Board will determine the rules of its proceedings.&lt;br /&gt;
&lt;br /&gt;
== Section VII ~ Duties of Officers ==&lt;br /&gt;
&lt;br /&gt;
=== President ===&lt;br /&gt;
&lt;br /&gt;
The President shall be responsible for the following:&lt;br /&gt;
* serve as the primary channel of communication with the Foundation and Member Sites.&lt;br /&gt;
* facilitate the appointment of committees and ensure that the goals and purposes of the Foundation are realized.&lt;br /&gt;
* have the power to pursue resources, pending ratification by the board of directors.&lt;br /&gt;
&lt;br /&gt;
=== Vice-President ===&lt;br /&gt;
The Vice-President shall act in the capacity of the President in the President’s absence.&lt;br /&gt;
&lt;br /&gt;
=== Secretary ===&lt;br /&gt;
The Secretary shall be responsible for the following:&lt;br /&gt;
* record attendance, take the minutes of all meetings, and maintain a file of meeting minutes for reference at future meetings.&lt;br /&gt;
* conduct necessary correspondence for the Foundation&lt;br /&gt;
* receive all petitions and notices from the general public and member sites to be discussed during the next meeting&lt;br /&gt;
&lt;br /&gt;
=== Treasurer ===&lt;br /&gt;
&lt;br /&gt;
The Treasurer shall be responsible for the following:&lt;br /&gt;
* collection, safekeeping, and disbursement of all funds and assets&lt;br /&gt;
* keep and maintain financial records of all financial transactions of the Foundation.&lt;br /&gt;
* keep records of all Member Site accounts.&lt;br /&gt;
* submit a financial accounting of the association’s transactions and financial status at the montly meeting and at other times when requested.&lt;br /&gt;
* assist any necessary documents for the IRS and the New Hampshire Attorney General related to the finances of the association.&lt;br /&gt;
&lt;br /&gt;
== Article VIII ~ Meetings ==&lt;br /&gt;
&lt;br /&gt;
=== Section 1 - Frequency ===&lt;br /&gt;
Meetings of the Foundation shall be held monthly unless otherwise voted by the board of directors.&lt;br /&gt;
&lt;br /&gt;
=== Section 2 - Quorum ===&lt;br /&gt;
Business can be conducted if a quorum is present. A quorum shall be defined as 2/3rds of officers with voting powers.&lt;br /&gt;
&lt;br /&gt;
=== Section 3 - Special Meetings ===&lt;br /&gt;
Special meetings of the Foundation may be called at any time by the President or by two officers of the Foundation. Special meetings are meant for dealing with matters that can not wait until the general general meeting, and shall be limited to the specific topic that necessitated the meeting. Special meetings may be closed or open, as per Section 4 of this article.&lt;br /&gt;
&lt;br /&gt;
=== Section 4 - Open/Closed Meetings ===&lt;br /&gt;
Meetings shall be open to the public unless voted otherwise by the Board of Directors. Closed meetings shall only be used to discuss confidential or sensitive information related to Foundation business, or when public disclosure is against the Foundations best interest. Meetings may be closed at any time by majority vote. Alternatively, a closed meeting may be scheduled in advance by the President, or two officers of the Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Section 5 - Location Of Meetings ===&lt;br /&gt;
Regular business meetings of the Foundation shall be conducted on IRC and be open to the general public. Such information shall be posted on the Foundation's web site, with the time, location, and access means for which the general public join. Closed meetings may be held in any venue considered secure for the contents of said meeting. Special meetings may be conducted in any matter that is practical given the subject matter.&lt;br /&gt;
&lt;br /&gt;
=== Section 6 - Minutes ===&lt;br /&gt;
It shall be the duty of the Secretary to keep the minutes of all meetings. Should the Secretary be unavailable for a meeting, this duty shall pass to an officer selected by the President. Minutes for open (general or special) meetings shall published within ten (10) business days of the conclusion of that meeting. Closed meetings shall have minutes kept in the same matter, but dissemination shall be limited to the board of directors, and revelent parties.&lt;br /&gt;
&lt;br /&gt;
=== Section 7 - Notification ===&lt;br /&gt;
Meeting dates shall be posted publicly, on the Foundation's web site, with at least ten (10) business days advance notice before the meeting date.&lt;br /&gt;
&lt;br /&gt;
== Article IX ~ Funds and Liability ==&lt;br /&gt;
&lt;br /&gt;
=== Section 1 - Receivership of Funds ===&lt;br /&gt;
Funds received to the Foundation via a Member Site shall be divided as per the Member Site section of these bylaws. The Treasurer is responsible that funds are properly divided between the Foundation's account, and those of each Member Site.&lt;br /&gt;
&lt;br /&gt;
=== Section 2 - Depositories ===&lt;br /&gt;
The Board of Directors shall determine what depositories shall be used by the Corporation as long as such depositories are located within the State of New Hampshire and are authorized to transact business by the State of New Hampshire and are federally insured.  All checks and orders for the payment of money from said depository shall be signed such signatories as have been authorized and required in advance by the Board of Directors.&lt;br /&gt;
&lt;br /&gt;
=== Section 3 - Records ===&lt;br /&gt;
Adequate records of accounts shall be maintained by the Treasurer. Records shall include (but not be limited to):&lt;br /&gt;
* Total Funds Received&lt;br /&gt;
* Balance of Member Site Accounts, and trusts&lt;br /&gt;
* Balance of Foundation Accounts&lt;br /&gt;
* Expected expenses (including recurring and one-time)&lt;br /&gt;
&lt;br /&gt;
Such records shall be posted at the next meeting of the Foundation, and shall be available for public viewing.&lt;br /&gt;
&lt;br /&gt;
=== Section 4 - Trust Funds ===&lt;br /&gt;
Should the Foundation's primary account be unable to cover costs and expenses, the Board of Directors may use money within Member Site's Trust Funds for the Foundation's operating expenses. The President shall notify all member sites in advance before Trust Funds are leveraged, with accounting how much shall be used, and for what reasons. The Treasurer shall transfer money within ten (10) business days from the notification.&lt;br /&gt;
&lt;br /&gt;
=== Section 5 - Fiscal Year ===&lt;br /&gt;
The fiscal year shall be January 1 through December 31. The fiscal year may be changed by the Board of Directors without amending these bylaws.&lt;br /&gt;
&lt;br /&gt;
== Article X ~ Amendments ==&lt;br /&gt;
&lt;br /&gt;
These bylaws may be amended, with ten (10) business days’ prior notice, at any meeting of the Foundation, by a majority vote of the board of directors.  '''question: should this be 2/3rds?'''&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=ForProfit&amp;diff=7544</id>
		<title>ForProfit</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=ForProfit&amp;diff=7544"/>
		<updated>2014-05-11T20:03:32Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: Protected &amp;quot;ForProfit&amp;quot; ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Update:'''This project will be non-profit and community-driven.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''This page is archival&lt;br /&gt;
&lt;br /&gt;
'''Note:'''This page is a candidate for deletion.&lt;br /&gt;
&lt;br /&gt;
Here's a copy of my vision for the project, was sent around in one of the mailing list posts. Note that it puts &amp;quot;attract and keep readers&amp;quot; first, before &amp;quot;make money&amp;quot;. The intent is to avoid trading off user satisfaction for money - the users come first.&lt;br /&gt;
&lt;br /&gt;
* The purpose of the site will be to attract and keep readers.&lt;br /&gt;
* The site is intended to make money&lt;br /&gt;
* The site will hire people, and be a good employer&lt;br /&gt;
* I intend to listen to community feedback and do whatever makes the site better&lt;br /&gt;
* There will be monetization; however, this is secondary to the primary goal, which is to attract and keep readers.&lt;br /&gt;
* Users ('''I think won't''') will be monetized (ie we won't sell our user's contact info)&lt;br /&gt;
* We won't poach from Slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(Monetization meaning largely what Slashdot does now: advertizing, merchandise, and job postings.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Note:''' this is only a proposal! This has never been done before, and I have no idea at this time whether it's feasible, or even legal.&lt;br /&gt;
&lt;br /&gt;
==Synopsis:==&lt;br /&gt;
&lt;br /&gt;
The financial intent of the business will be to make people independent. To that end, the company will fund $52,000 annuities to be given to people who help build and maintain the system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overall description:==&lt;br /&gt;
&lt;br /&gt;
The purpose of the fund is to take people out of the workforce without leaving them in poverty. A fund participant receives a weekly income large enough to live on, by which they may (if they choose) leave the workforce.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Income is paid in perpetuity: payout continues after death of original recipient, can be willed, inherited, sold or given away. Income is strictly one per person.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The proposed fund account returns $52,000/year ($1000/week). Fund amount needed to attain that level is hypothetically $1 million per participant:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* 10% Overall return (Indexed fund returns over 40 years == 12%. [http://www.forbes.com/sites/rickferri/2013/04/04/index-fund-returns-get-better-with-age/ source])&lt;br /&gt;
&lt;br /&gt;
* -3.5% Inflation adjustment&lt;br /&gt;
&lt;br /&gt;
* -0.5% Management fees (Similar to Fidelity Portfolio Advisory Service. [https://www.fidelity.com/managed-accounts/portfolio-advisory-service/overview source])&lt;br /&gt;
&lt;br /&gt;
* -5.2% Annual payout&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
With these numbers, fund will gain 0.8% annual value over time, which can be used as hedge against poor market performance.&lt;br /&gt;
&lt;br /&gt;
* I'd be careful with assuming a 10% return. While long term history shows that to be the case, in the previous 10 years the S&amp;amp;P 500 has yielded under 8%. Additionally, if you are planning to deduct money out of the fund every year, one bad year can have catastrophic effects on the overall viability of the fund since you would be forced to liquidate assets at non-optimal prices. I would urge a more conservative measure. I would be happy look into these options with you as well since this is one of my areas of expertise. -Nightbrood&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Participation==&lt;br /&gt;
&lt;br /&gt;
AltSlashdot will employ N people for site management. Site will accrue profits until N times $1 million is attained, and then award each employee with one annuity.&lt;br /&gt;
&lt;br /&gt;
This is the weak point 'site will accrue profits' but how? Advertising? advertorials? Donations? In general, I'd suggest that we use a standard template that deals with cash flow, income etc.&lt;br /&gt;
&lt;br /&gt;
*It has been awhile since I have been in the website business. What is the non-intrusive advertising market like as far as compensation rates? I'd be against advertorials. It is bad enough that supposedly reputable places like CNN and CNBC are littered with them. Donations and Premium subscriptions are another cash flow stream that could make the site viable. Especially if we are transparent what donations are used for etc. -Nightbrood&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
&lt;br /&gt;
This is very good for 'employees' but it does nothing to prevent the same thing as happened to Slashdot 1.0. How is this new endeavor going to protect its users and be accountable to them? What prevents this from being a pump and dump? ~ElectricTurtle&lt;br /&gt;
&lt;br /&gt;
* I have to agree with the others, I do not mind us starting something with paid staff. However, I do not feel this effort would be met with success if we essentially tell our community that this business won't mistreat them like the prior one did. Even though the prior one said they would not change anything. At this point, I think many in the community would be reticent to trade one corporate master for another. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
* Agree with Electric...  Primary purpose of any fund should be to cover operating costs, then worry about paying the people who run the place.  To get a true quourum of /. here, I think it needs to be more open source than that, with assurances that the community won't lose out again...   -- CoolHnd30&lt;br /&gt;
&lt;br /&gt;
* I suppose it means that those involved in running this venture will bust their asses to make sure the fund hits that magic number. It would mean keeping visitors happy for how ever long that takes, spreading the word, and making that $$ come in. If the community isn't happy, people wont see ads / buy merch, and retirement never comes. I'm just assuming that's the thought process. - Cactus&lt;br /&gt;
&lt;br /&gt;
** And once the goal is reached, the oligarchs can just turn on the community again, cash out, and say &amp;quot;Deuces!&amp;quot; while they get paid in perpetuity. ~ElectricTurtle&lt;br /&gt;
&lt;br /&gt;
*** True enough. Any suggestions on what would allay community fears while letting Okian Warrior do something at least similar to what he wants to try? I really think this idea could be a very strong motivator to those involved... but I don't know what would keep it from possibly going down in flames once the goal is reached. - Cactus&lt;br /&gt;
**** I had made a suggestion [http://www.altslashdot.org/wiki/index.php?title=Talk:AltSlashdot#Group_or_Business] about establishing some guarantees in a charter that can only be changed with buy-in from the userbase. (Unlike the sundry TOS where terms can be changed at any time without notice bullshit.)--[[User:ElectricTurtle|ElectricTurtle]] ([[User talk:ElectricTurtle|talk]]) 13:23, 6 February 2014 (MST)&lt;br /&gt;
*****I'm all for a &amp;quot;Bill of Rights&amp;quot; thing. If people are to switch over wholesale from Slashdot, the general community will need to come up with a list of demands, or a charter or something. We can't completely ruin any desire to run this site, but I think there are things a userbase can reasonably expect from a community driven site.&lt;br /&gt;
&lt;br /&gt;
* Well, if you want to do this and not succumb to the &amp;quot;sold out&amp;quot; aspect, then the 'annuities' need to be in the form of shares - then the people who contributed to make the site get a say in how and what happens to it, and if the majority think selling out is a bad thing, then it will not get sold off. Sure, you need income to pay hosting and other things, but I think that can come with a subtle bit of advertising stuck off the bottom. Or you can sell the userbase's details to the marketeers .. like &amp;quot;not evil&amp;quot; Google does. Anyway, I think it should be more concerned with being more open source and idealistic from the start.&lt;br /&gt;
**I second this motion of shares; the meme du jour is that The Users are Slashdot - let's make it literally true.  If you buy a sub, you buy a share in the profits of any advertising after expenses, plus a vote on the future direction of the website. --Kell&lt;br /&gt;
&lt;br /&gt;
*micropayments for highly rated posts?  --CoolHnd30&lt;br /&gt;
**That is an interesting idea. I have always wanted to reward people who take the time to contribute high quality content to a site. May be an idea worth considering but determining how such a system will work would require some thought. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
*What about using a &amp;quot;premium&amp;quot; model, as arstechnica does? People paying like 1$ or 5$ a month don't get ads. Plus a pdf of the most insulting comments that month :)&lt;br /&gt;
&lt;br /&gt;
*Have you thought of created a cooperative? You would be CEO but managed by a board of directors. Board of directors would be elected by members. Members would be anyone who wants to pay for *premium* membership (no ads) with a $5 annual membership share. Members have a right to vote for the board of directors who make decisions about how the organization is run. One member one vote. You're still profitable but DICE-type heavy handed decisions are impossible because in most cooperatives, major decisions require a referendum by the membership. Something to consider, NCBA in the USA or ICA internationally have tons of resources on setting them up.&lt;br /&gt;
** I like this idea. There are piles of resources online that will direct you in setting up a co-op. - Cactus&lt;br /&gt;
** I like the idea of a cooperative. This should ultimately be for the community and would remove the negative stigma attached to a conventional corporation. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
* I am curious why you are proposing this model rather than just hiring people, or profit-sharing. I see practical problems with its implementation: how can you be sure the site will ever make N times $1 million? What about people who work hard for six or twelve months and burn out before you hit the magic number -- they get nothing? What about someone who joins the team late? And so on. I respect the novelty of your idea but if I were one of three developers and you only(!) made $2 million the first year, I would feel kind of shafted working all year for nothing when there are $2 million sitting in the bank. Doubly so, if something bad happened and the site shut down without ever having paid anyone. [[User:Sir Garlon|Sir Garlon]]&lt;br /&gt;
*If it's for-profit, that'll always be the primary goal, regardless of any other suggestion. Has to be community driven and supported by donations. Also, the goal shouldn't be to attract people, but to aggregate the best content and discussions.&lt;br /&gt;
** Can I support idea to drive the site from community contributions and public donations? Take a page from kickstarter and offer an involved donation menu - be transparent about your ongoing costs etc and how much is recommended to keep things afloat. Some sort of small visual indicator of the overall status can be shown at the top of the main page. Donations can even be broken down into different goals if necessary.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=ForProfit&amp;diff=7543</id>
		<title>ForProfit</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=ForProfit&amp;diff=7543"/>
		<updated>2014-05-11T20:00:03Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Update:'''This project will be non-profit and community-driven.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''This page is archival&lt;br /&gt;
&lt;br /&gt;
'''Note:'''This page is a candidate for deletion.&lt;br /&gt;
&lt;br /&gt;
Here's a copy of my vision for the project, was sent around in one of the mailing list posts. Note that it puts &amp;quot;attract and keep readers&amp;quot; first, before &amp;quot;make money&amp;quot;. The intent is to avoid trading off user satisfaction for money - the users come first.&lt;br /&gt;
&lt;br /&gt;
* The purpose of the site will be to attract and keep readers.&lt;br /&gt;
* The site is intended to make money&lt;br /&gt;
* The site will hire people, and be a good employer&lt;br /&gt;
* I intend to listen to community feedback and do whatever makes the site better&lt;br /&gt;
* There will be monetization; however, this is secondary to the primary goal, which is to attract and keep readers.&lt;br /&gt;
* Users ('''I think won't''') will be monetized (ie we won't sell our user's contact info)&lt;br /&gt;
* We won't poach from Slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(Monetization meaning largely what Slashdot does now: advertizing, merchandise, and job postings.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Note:''' this is only a proposal! This has never been done before, and I have no idea at this time whether it's feasible, or even legal.&lt;br /&gt;
&lt;br /&gt;
==Synopsis:==&lt;br /&gt;
&lt;br /&gt;
The financial intent of the business will be to make people independent. To that end, the company will fund $52,000 annuities to be given to people who help build and maintain the system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overall description:==&lt;br /&gt;
&lt;br /&gt;
The purpose of the fund is to take people out of the workforce without leaving them in poverty. A fund participant receives a weekly income large enough to live on, by which they may (if they choose) leave the workforce.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Income is paid in perpetuity: payout continues after death of original recipient, can be willed, inherited, sold or given away. Income is strictly one per person.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The proposed fund account returns $52,000/year ($1000/week). Fund amount needed to attain that level is hypothetically $1 million per participant:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* 10% Overall return (Indexed fund returns over 40 years == 12%. [http://www.forbes.com/sites/rickferri/2013/04/04/index-fund-returns-get-better-with-age/ source])&lt;br /&gt;
&lt;br /&gt;
* -3.5% Inflation adjustment&lt;br /&gt;
&lt;br /&gt;
* -0.5% Management fees (Similar to Fidelity Portfolio Advisory Service. [https://www.fidelity.com/managed-accounts/portfolio-advisory-service/overview source])&lt;br /&gt;
&lt;br /&gt;
* -5.2% Annual payout&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
With these numbers, fund will gain 0.8% annual value over time, which can be used as hedge against poor market performance.&lt;br /&gt;
&lt;br /&gt;
* I'd be careful with assuming a 10% return. While long term history shows that to be the case, in the previous 10 years the S&amp;amp;P 500 has yielded under 8%. Additionally, if you are planning to deduct money out of the fund every year, one bad year can have catastrophic effects on the overall viability of the fund since you would be forced to liquidate assets at non-optimal prices. I would urge a more conservative measure. I would be happy look into these options with you as well since this is one of my areas of expertise. -Nightbrood&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Participation==&lt;br /&gt;
&lt;br /&gt;
AltSlashdot will employ N people for site management. Site will accrue profits until N times $1 million is attained, and then award each employee with one annuity.&lt;br /&gt;
&lt;br /&gt;
This is the weak point 'site will accrue profits' but how? Advertising? advertorials? Donations? In general, I'd suggest that we use a standard template that deals with cash flow, income etc.&lt;br /&gt;
&lt;br /&gt;
*It has been awhile since I have been in the website business. What is the non-intrusive advertising market like as far as compensation rates? I'd be against advertorials. It is bad enough that supposedly reputable places like CNN and CNBC are littered with them. Donations and Premium subscriptions are another cash flow stream that could make the site viable. Especially if we are transparent what donations are used for etc. -Nightbrood&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
&lt;br /&gt;
This is very good for 'employees' but it does nothing to prevent the same thing as happened to Slashdot 1.0. How is this new endeavor going to protect its users and be accountable to them? What prevents this from being a pump and dump? ~ElectricTurtle&lt;br /&gt;
&lt;br /&gt;
* I have to agree with the others, I do not mind us starting something with paid staff. However, I do not feel this effort would be met with success if we essentially tell our community that this business won't mistreat them like the prior one did. Even though the prior one said they would not change anything. At this point, I think many in the community would be reticent to trade one corporate master for another. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
* Agree with Electric...  Primary purpose of any fund should be to cover operating costs, then worry about paying the people who run the place.  To get a true quourum of /. here, I think it needs to be more open source than that, with assurances that the community won't lose out again...   -- CoolHnd30&lt;br /&gt;
&lt;br /&gt;
* I suppose it means that those involved in running this venture will bust their asses to make sure the fund hits that magic number. It would mean keeping visitors happy for how ever long that takes, spreading the word, and making that $$ come in. If the community isn't happy, people wont see ads / buy merch, and retirement never comes. I'm just assuming that's the thought process. - Cactus&lt;br /&gt;
&lt;br /&gt;
** And once the goal is reached, the oligarchs can just turn on the community again, cash out, and say &amp;quot;Deuces!&amp;quot; while they get paid in perpetuity. ~ElectricTurtle&lt;br /&gt;
&lt;br /&gt;
*** True enough. Any suggestions on what would allay community fears while letting Okian Warrior do something at least similar to what he wants to try? I really think this idea could be a very strong motivator to those involved... but I don't know what would keep it from possibly going down in flames once the goal is reached. - Cactus&lt;br /&gt;
**** I had made a suggestion [http://www.altslashdot.org/wiki/index.php?title=Talk:AltSlashdot#Group_or_Business] about establishing some guarantees in a charter that can only be changed with buy-in from the userbase. (Unlike the sundry TOS where terms can be changed at any time without notice bullshit.)--[[User:ElectricTurtle|ElectricTurtle]] ([[User talk:ElectricTurtle|talk]]) 13:23, 6 February 2014 (MST)&lt;br /&gt;
*****I'm all for a &amp;quot;Bill of Rights&amp;quot; thing. If people are to switch over wholesale from Slashdot, the general community will need to come up with a list of demands, or a charter or something. We can't completely ruin any desire to run this site, but I think there are things a userbase can reasonably expect from a community driven site.&lt;br /&gt;
&lt;br /&gt;
* Well, if you want to do this and not succumb to the &amp;quot;sold out&amp;quot; aspect, then the 'annuities' need to be in the form of shares - then the people who contributed to make the site get a say in how and what happens to it, and if the majority think selling out is a bad thing, then it will not get sold off. Sure, you need income to pay hosting and other things, but I think that can come with a subtle bit of advertising stuck off the bottom. Or you can sell the userbase's details to the marketeers .. like &amp;quot;not evil&amp;quot; Google does. Anyway, I think it should be more concerned with being more open source and idealistic from the start.&lt;br /&gt;
**I second this motion of shares; the meme du jour is that The Users are Slashdot - let's make it literally true.  If you buy a sub, you buy a share in the profits of any advertising after expenses, plus a vote on the future direction of the website. --Kell&lt;br /&gt;
&lt;br /&gt;
*micropayments for highly rated posts?  --CoolHnd30&lt;br /&gt;
**That is an interesting idea. I have always wanted to reward people who take the time to contribute high quality content to a site. May be an idea worth considering but determining how such a system will work would require some thought. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
*What about using a &amp;quot;premium&amp;quot; model, as arstechnica does? People paying like 1$ or 5$ a month don't get ads. Plus a pdf of the most insulting comments that month :)&lt;br /&gt;
&lt;br /&gt;
*Have you thought of created a cooperative? You would be CEO but managed by a board of directors. Board of directors would be elected by members. Members would be anyone who wants to pay for *premium* membership (no ads) with a $5 annual membership share. Members have a right to vote for the board of directors who make decisions about how the organization is run. One member one vote. You're still profitable but DICE-type heavy handed decisions are impossible because in most cooperatives, major decisions require a referendum by the membership. Something to consider, NCBA in the USA or ICA internationally have tons of resources on setting them up.&lt;br /&gt;
** I like this idea. There are piles of resources online that will direct you in setting up a co-op. - Cactus&lt;br /&gt;
** I like the idea of a cooperative. This should ultimately be for the community and would remove the negative stigma attached to a conventional corporation. - Nightbrood&lt;br /&gt;
&lt;br /&gt;
* I am curious why you are proposing this model rather than just hiring people, or profit-sharing. I see practical problems with its implementation: how can you be sure the site will ever make N times $1 million? What about people who work hard for six or twelve months and burn out before you hit the magic number -- they get nothing? What about someone who joins the team late? And so on. I respect the novelty of your idea but if I were one of three developers and you only(!) made $2 million the first year, I would feel kind of shafted working all year for nothing when there are $2 million sitting in the bank. Doubly so, if something bad happened and the site shut down without ever having paid anyone. [[User:Sir Garlon|Sir Garlon]]&lt;br /&gt;
*If it's for-profit, that'll always be the primary goal, regardless of any other suggestion. Has to be community driven and supported by donations. Also, the goal shouldn't be to attract people, but to aggregate the best content and discussions.&lt;br /&gt;
** Can I support idea to drive the site from community contributions and public donations? Take a page from kickstarter and offer an involved donation menu - be transparent about your ongoing costs etc and how much is recommended to keep things afloat. Some sort of small visual indicator of the overall status can be shown at the top of the main page. Donations can even be broken down into different goals if necessary.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Story_Style&amp;diff=7533</id>
		<title>Story Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Story_Style&amp;diff=7533"/>
		<updated>2014-05-10T22:36:13Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Editor's Notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Note: Whereas some languages, like French and German, have standardized forms governed by regulatory bodies, English is in many ways a free-for-all. Let this be a collection of information on which we english-speakers (typers?) agree.&lt;br /&gt;
&lt;br /&gt;
Parent: [[Editors|Editors Team]]&lt;br /&gt;
&lt;br /&gt;
=What is a Manual of Style=&lt;br /&gt;
&lt;br /&gt;
This document is intended to form a manual of style that dictates the way stories are written, mainly in matters of format, punctuation, and grammar. The Manual of soylent Style will hopefully create a uniform presentation that is in line with journalistic practices, while leaving many matters open to the personal preferences of editors and submitters.&lt;br /&gt;
&lt;br /&gt;
=Why a Manual of Style?=&lt;br /&gt;
&lt;br /&gt;
As we develop our own unique process, this will inform on common editor practices, and help guide new editors to the conventions that have been established thus far.&lt;br /&gt;
&lt;br /&gt;
=Story Structure=&lt;br /&gt;
&lt;br /&gt;
Stories begin with:&amp;lt;br&amp;gt;&lt;br /&gt;
*&amp;quot;[$submitter] writes:&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
*or &amp;quot;[$submitter] informs us of [a link]&amp;quot; (when the submission contains little or no summary)&amp;lt;br&amp;gt;&lt;br /&gt;
The colon and structure signifies the following text is the summary, and quotes are '''not''' necessary surrounding the entire text. [$submitter] should be a link to their site profile if available. The next component should be a summary of the article with in-line links, and any direct quotes from the article(s) using quotation marks normally. HTML formatting should use &amp;lt;nowiki&amp;gt;&amp;lt;p&amp;gt; and &amp;lt;/p&amp;gt; tags. Block-quoting is done with the &amp;lt;blockquote&amp;gt; and &amp;lt;/blockquote&amp;gt;&amp;lt;/nowiki&amp;gt; tags.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap; &lt;br /&gt;
white-space: -moz-pre-wrap; &lt;br /&gt;
white-space: -pre-wrap; &lt;br /&gt;
white-space: -o-pre-wrap; &lt;br /&gt;
word-wrap: break-word;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;http://soylentnews.org/~soylent+bob/&amp;quot;&amp;gt;Soylent Bob&amp;lt;/a&amp;gt; writes:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur massa elit, pharetra sed lacus vitae, vehicula porta elit. Nulla ac porta nibh. &amp;quot;Quisque adipiscing sem 'nisi', sit amet pulvinar velit vestibulum in&amp;quot;, says Soylent Mel. Morbi luctus aliquet erat quis tempor. Nulla facilisi:&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Morbi leo purus, fermentum non felis vitae, mattis tempus mauris. Nunc bibendum neque non dolor pharetra, quis dignissim tortor semper. Phasellus sed nisl sit amet elit rutrum interdum. Ut rutrum pellentesque tempus.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Integer id nisl vel ante sodales consectetur nec nec tortor. Suspendisse a congue est. Donec ut consectetur mauris. Duis hendrerit nibh nec quam consequat dapibus. Aenean luctus iaculis magna, aliquet aliquam nisi consectetur eget.&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;[ED's note: the quick brown fox jumps over the lazy dog.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=US/UK Spelling=&lt;br /&gt;
&lt;br /&gt;
The site is endeavouring not to be a US-centric site, and by doing so wishes to encourage members, casual-readers and interest from english-speakers around the world.  As the dialects of English differ between the US and many other English speaking regions, it is essential that the site remains inclusive to all but provides clearly written stories that are easily understandable.  Each submission contains 2 essentially different elements at the most basic level: the linked source material  and the summary (TFS).  &lt;br /&gt;
&lt;br /&gt;
== Linked Material ==&lt;br /&gt;
&lt;br /&gt;
The linked material (the information source) must be in English but can be in '''any''' English dialect.  It is reported exactly as printed to remove the possibility of an editor changing the meaning accidentally. Having two or more linked sources in different English dialects is acceptable.&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
The summary can be written in any commonly-used English dialect but must be consistent throughout.  Other than quoted material (which is always quoted exactly as written) only one dialect can be used throughout the summary. Mixing US and UK spelling, for example, in a single summary is unacceptable.  It does not have to be written in the same dialect as the source material - indeed, if there are 2 different sources it might be impossible to do so.&lt;br /&gt;
&lt;br /&gt;
=Headline Capitalization=&lt;br /&gt;
&lt;br /&gt;
# Except for function words, all words are regularly capitalized in headlines, e.g. &amp;quot;'Moon Made of Soylent Green Cheese', Says NASA.&amp;quot;&lt;br /&gt;
# Function words are:&lt;br /&gt;
## Prepositions, e.g. in, at, and on.&lt;br /&gt;
## Conjunctions, e.g. and, if, and but.&lt;br /&gt;
## Articles, i.e. the, an, and a.&lt;br /&gt;
## Pronouns, e.g. who, you, they, who, and which. The single exception is of course the pronoun I, which is always capitalized.&lt;br /&gt;
## The copula (&amp;quot;the verb &amp;lt;i&amp;gt;to be&amp;lt;/i&amp;gt;&amp;quot;), e.g. is, am, and are.&lt;br /&gt;
# But when headline-initial, even function words are capitalized, 'Is Soylent Green Made of People?&amp;quot; (cf. [[Story_Style#Betteridge.27s_Law_of_Headlines]]).&lt;br /&gt;
&lt;br /&gt;
=Serial Comma= &lt;br /&gt;
In a series of three or more items, place a comma between the second-to-last item and the conjunction that follows, e.g. &amp;quot;Soylent Green, Soylent Purple, and Soylent Yellow&amp;quot; instead of &amp;quot;Soylent Green, Soylent Purple and Soylent Yellow&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This is commonly referred to as the Harvard or Oxford Comma, and it reduces ambiguitiy. It usefulness is often illustrated with the (non-Oxford-Comma-conforming) phrase &amp;quot;To my parents, Ayn Rand and God,&amp;quot;  as this sentence reads that the parents in question are actually &amp;quot;Ayn Rand and God&amp;quot;. [http://en.wikipedia.org/wiki/Serial_comma#Ambiguity (wikipedia reference)].&lt;br /&gt;
&lt;br /&gt;
=Dashes=&lt;br /&gt;
&lt;br /&gt;
=Betteridge's Law of Headlines=&lt;br /&gt;
Betteridge's Law explains: Any headline that ends in a question mark can be answered with one word -- &amp;lt;i&amp;gt;no&amp;lt;/i&amp;gt;. The use of such questions in headlines is a journalistic device that is used when the story has little proof, no basis at all, or describes events that did not actually occur at the time of writing, i.e. not news. This should be avoided whenever possible. Note: this axiom naturally applies only to yes/no questions rather than wh-prefixed questions.&lt;br /&gt;
&lt;br /&gt;
=Possessive S=&lt;br /&gt;
# The possessive form of singular nouns is marked with 's, except for some archaic proper nouns that end in -es or -is, e.g. Moses' law (http://www.bartleby.com/141/strunk.html#1).&lt;br /&gt;
# The possessive form of plural nouns ending in &amp;quot;s&amp;quot; does &amp;lt;i&amp;gt;not&amp;lt;/i&amp;gt; require an additional &amp;quot;s&amp;quot;, e.g. pirates'.&lt;br /&gt;
&lt;br /&gt;
=Apostrophes=&lt;br /&gt;
# Apostrophes are used in the possessive form of nouns, e.g. soylent's (singular) and news' (plural).&lt;br /&gt;
# Apostrophes are not used to form the plural ending of nouns, e.g. the plural form of apple is apples, and its possessive form is apples'. Apple's is the possessive form of the singular apple, while apples' is the possessive form of the plural apples.&lt;br /&gt;
# Apostrophes are likewise not used with decades, when written in numbers, e.g. 1980s rather than 1980's.&lt;br /&gt;
# The form &amp;lt;i&amp;gt;it's&amp;lt;/i&amp;gt; is a contraction of &amp;lt;i&amp;gt;it is&amp;lt;/i&amp;gt;. The word &amp;lt;i&amp;gt;its&amp;lt;/i&amp;gt;, on the other hand, is the possessive form of the pronoun &amp;lt;i&amp;gt;it&amp;lt;/i&amp;gt;. This can be easily remembered by comparing the other third person pronouns: &amp;lt;i&amp;gt;he's&amp;lt;/i&amp;gt; has an apostrophe because it is a contraction of &amp;lt;i&amp;gt;he&amp;lt;/i&amp;gt; and &amp;lt;i&amp;gt;is&amp;lt;/i&amp;gt;, whereas &amp;lt;i&amp;gt;his&amp;lt;/i&amp;gt; never has one. The same also applies to &amp;lt;i&amp;gt;hers&amp;lt;/i&amp;gt; and &amp;lt;i&amp;gt;she's&amp;lt;/i&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Hyper-Prescriptivism: Split Infinitives and Stranded Prepositions=&lt;br /&gt;
# The use of adverbs between the word &amp;lt;i&amp;gt;to&amp;lt;/i&amp;gt; and its following infinitive is allowed, e.g. &amp;lt;i&amp;gt;to boldly go&amp;lt;/i&amp;gt; is just as acceptable as &amp;lt;i&amp;gt;boldly, to go&amp;lt;/i&amp;gt; and &amp;lt;i&amp;gt;to go boldly&amp;lt;/i&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Weasel Words=&lt;br /&gt;
Weasel words include a variety of terms that can mislead and and deceive readers. Examples include use of: non sequitur statements, [http://en.wikipedia.org/wiki/Passive_voice passive voice], vague expressions (e.g. &amp;quot;some people think,&amp;quot; and &amp;quot;experts agree&amp;quot;), and adverbs that weaken a statement through ambiguity (e.g. &amp;quot;probably&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
=Source Needed=&lt;br /&gt;
&lt;br /&gt;
=Titles of Works=&lt;br /&gt;
# The titles of books, films, albums, etc. are rendered in italics rather than quotation marks, e.g. &amp;lt;i&amp;gt;Planet of the Apes&amp;lt;/i&amp;gt; instead of &amp;quot;Planet of the Apes&amp;quot;.&lt;br /&gt;
# The names of websites and products receive no such marking, e.g. &amp;quot;CNN reports that Charlton Heston has discovered the secret ingredient in Soylent Green.&amp;quot; Contrast this to the following sentence, in which Soylent Green is the film rather than the product: &amp;quot;CNN reports that Charlton Heston has discovered the secret ingredient in &amp;lt;i&amp;gt;Soylent Green&amp;lt;/i&amp;gt;.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=Quotations=&lt;br /&gt;
Punctuation marks appear before closing quotation marks. Example:&lt;br /&gt;
: &amp;quot;Moon is Made of Soylent Green Cheese,&amp;quot; says NASA.&lt;br /&gt;
Instead of:&lt;br /&gt;
: &amp;quot;Moon is Made of Soylent Green Cheese&amp;quot;, says NASA.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Punctuation should follow the format of presented material, even if it differs from source material. Example:&lt;br /&gt;
: &amp;quot;Moon is Made of Soylent Green Cheese,&amp;quot; says NASA.&lt;br /&gt;
Source material:&lt;br /&gt;
: &amp;quot;Moon is Made of Soylent Green Cheese.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=Editor's Notes=&lt;br /&gt;
Editor's notes should be used sparingly. They should never be used to add the editor's opinion, that can be done as a comment on the story. One accepted case would be in notifying readers that a story was updated or changed, or informing the readers of important information ex: [Editor's Note: The live-stream appears to be inaccessible at this time.]&lt;br /&gt;
&lt;br /&gt;
Editor's notes can also be used to link to previous stories on the subject or related subjects, where adding the links to the story would be obtrusive or change the submission drastically.&lt;br /&gt;
&lt;br /&gt;
[[Category:Editorial team]]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=MediaWiki:Sidebar&amp;diff=6042</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=MediaWiki:Sidebar&amp;diff=6042"/>
		<updated>2014-03-12T15:32:15Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** Help:Contents|Help&lt;br /&gt;
** SoylentNews:Sandbox|Sandbox&lt;br /&gt;
* SoylentNews&lt;br /&gt;
** http://www.SoylentNews.org/|Main site&lt;br /&gt;
** FAQ|FAQ&lt;br /&gt;
** TeamPages|Team pages&lt;br /&gt;
** WhosWho|Who's who&lt;br /&gt;
** http://forums.SoylentNews.org/|Forum&lt;br /&gt;
** SoylentNews:IRC|IRC&lt;br /&gt;
** http://irc.sylnt.us/?channels=#soylent|Webchat&lt;br /&gt;
** https://github.com/SoylentNews/slashcode|Code&lt;br /&gt;
** https://github.com/SoylentNews/slashcode/issues|Bugs&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=TeamPages&amp;diff=5985</id>
		<title>TeamPages</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=TeamPages&amp;diff=5985"/>
		<updated>2014-03-11T20:16:51Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are links to individual team pages with their respective goals&lt;br /&gt;
&lt;br /&gt;
Team Pages&lt;br /&gt;
*[[Development]]&lt;br /&gt;
*[[UserExperience|User Experience]]&lt;br /&gt;
*[[Editors]]&lt;br /&gt;
*[[Wiki]]&lt;br /&gt;
*[[IRC]]&lt;br /&gt;
*[[CommunitySupport|Community Support]]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Historic:TodoList&amp;diff=5603</id>
		<title>Historic:TodoList</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Historic:TodoList&amp;diff=5603"/>
		<updated>2014-03-07T18:30:27Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Business */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Undefined Group==&lt;br /&gt;
*Develop process for volunteer-&amp;gt; staff (get email/ on mailiing list etc)&lt;br /&gt;
*Develop task-list of ongoing duties from each &amp;quot;group&amp;quot;&lt;br /&gt;
*Solicit volunteers on specific tasks as indicated below&lt;br /&gt;
*Create volunteer@soylentnews.org and link in various places&lt;br /&gt;
*Develop system for recruiting/organizing volunteers (currently just mrcoolbp *attempting* to collect and send in the right direction)&lt;br /&gt;
*SN Story Submission: Volunteers Needed (after determining which skills we need most)&lt;br /&gt;
*Coordinate tasks with new volunteers &lt;br /&gt;
*IRC log links need updating in various places&lt;br /&gt;
*revisit the legal (copyright?) implications of cross-posting (reposting stories posted elsewhere)&lt;br /&gt;
*Summarize staff meeting (or not ???)&lt;br /&gt;
*Formulate Plan/vision/bylaws&lt;br /&gt;
*Get ALL staff @SN.org emails and migrate mailing list to new addresses (this should be optional, not automatic) (mechanicjay can help add people)&lt;br /&gt;
*New Name contest (final one, we hope)&lt;br /&gt;
*Regular status updates with key leaders&lt;br /&gt;
*Organize staff, don't do everything yourself, delegate to appropriate people&lt;br /&gt;
*Fire people when it isn't working out sooner rather than later (this should go in ongoing duties task-list)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Sys/Dev==&lt;br /&gt;
*Ensure staff have privileges in all platforms we use&lt;br /&gt;
*Implement Fire-hose of some kind&lt;br /&gt;
*Single sign on to all services (register once, central administration)&lt;br /&gt;
*Add markdown support?&lt;br /&gt;
*Make it easy for people to submit bugs (need to re-link from various places) (bugs@ email?)&lt;br /&gt;
*“you should update your organization template” ← I think there is a pull request that fixes this (and fixes “about” page)&lt;br /&gt;
*Implement system for keeping old UIDs?&lt;br /&gt;
*Make sure the SSL login page POSTs to an SSL page! The cookie needs HTTPS headers set (this should be a bug?)(collected via [[Suggestions]])&lt;br /&gt;
&lt;br /&gt;
==Communications==&lt;br /&gt;
*Determine better communication Forum (or keep mailing list) (suggestions: redmine, slash), get concensus, cut the dead weight&lt;br /&gt;
*Change wording on wiki to specifically solicit volunteers&lt;br /&gt;
*Consolidated ways to post suggestions (single repository, easy to add to, possibly via multiple means that all end up in one spot)(will be wiki, mrcoolbp collecting currently via email and !suggestions irc)&lt;br /&gt;
*Refine Suggestions system (develop process to select good items, pose for vote, then implement)&lt;br /&gt;
*incorporate !suggestions for any user (post directly to wiki)&lt;br /&gt;
*Contact CmdrTaco via twitter?&lt;br /&gt;
&lt;br /&gt;
==Editors==&lt;br /&gt;
*Press release (at some point)&lt;br /&gt;
*Develop editorial process, informed by Poll results&lt;br /&gt;
*Documentation pages (FAQ, &amp;quot;Authors&amp;quot; page)&lt;br /&gt;
&lt;br /&gt;
==Business==&lt;br /&gt;
*pick incorporation model, then do it&lt;br /&gt;
*Swag? (sync with art)&lt;br /&gt;
*Marketing - Do we do it? how do we do it?&lt;br /&gt;
*Ads?&lt;br /&gt;
*Donations? (these all Depend on incorporation model)&lt;br /&gt;
*social media, do we want to pursue it?  who? How?&lt;br /&gt;
*Solicit legal advice on keeping logs of user activity. What is required?&lt;br /&gt;
*How to respond to DMCA takedown requests&lt;br /&gt;
&lt;br /&gt;
==Paulej72==&lt;br /&gt;
*change &amp;quot;Read More&amp;quot; to button.&lt;br /&gt;
*Kill D2&lt;br /&gt;
*fix all buttons to have proper case&lt;br /&gt;
*bug 48 fix log in screen ul list&lt;br /&gt;
*fix bug #68 some links are worn color in comment details  trace JS loads to fix JS re-size of certain elements on mobile devices.&lt;br /&gt;
*style blockquote and see what is up with quote&lt;br /&gt;
*add hyperlink to article story title to story page per bug 106&lt;br /&gt;
*style input boxes to have better border contrast per bug 107&lt;br /&gt;
*add night mode skin per 112&lt;br /&gt;
*make sure site displays “Log In” and “Log Out” per bug 116&lt;br /&gt;
*fix journal template to fix broken link title tex per bug 118&lt;br /&gt;
*fix preference pages per many bugs&lt;br /&gt;
*fix relationships ui as per bug 37&lt;br /&gt;
*migrate bugs to GitHub (curretnly in progress)&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Staff_Meeting_2_March_2014&amp;diff=5424</id>
		<title>Staff Meeting 2 March 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Staff_Meeting_2_March_2014&amp;diff=5424"/>
		<updated>2014-03-03T16:06:56Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: Created page with &amp;quot;This is a page regarding the SoylentNews Staff Meeting, held on 2 March at 1800 UTC.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a page regarding the SoylentNews Staff Meeting, held on 2 March at 1800 UTC.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4736</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4736"/>
		<updated>2014-02-16T20:22:28Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
[http://imgur.com/otMmmcM.png Latest Front Page]&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
'''2014-02-16 13:32 UTC:''' Reposted from the site:&lt;br /&gt;
&lt;br /&gt;
So, since this site went up three days ago, we've made tremendous progress in getting this site up and functional, and many of you gone above and beyond to try and give us content and provide meaningful comments. I'm completely blown away to say the least. I've got some big news to share, and a list of site improvements made over the last few days. Read on for more details ...&lt;br /&gt;
&lt;br /&gt;
Moderation: IT WORKS! I finished implementing the algorithm last night, and purging slash of the old one so they won't conflict. The new algorithm is somewhat of a radical departure from the old one. I won't go into full details in this post, but there's a good write-up in my comments here.&lt;br /&gt;
&lt;br /&gt;
Comment Counts: Got these working (again). ACs will only see a static HTML page which is updated every once in awhile. Logged-in users get the dynamic index which should have up-to-date counts. The fix is a bit wonky, so it might snap again. Let me know ASAP as the moderation scripts depend on this number being present (and correct!)&lt;br /&gt;
&lt;br /&gt;
Theme: As you may have noticed, the site looks less ass. Due to the heroic efforts of audioguy, Paul, and others, we've gotten a steady stream of CSS fixes to make the site look and feel more consistent. Its not perfect (Firefox still has width issues), but its a fair improvement. This is one of the last major launch blockers&lt;br /&gt;
&lt;br /&gt;
Topics: Finally got them implemented after we snapped the site in two last night. For the moment, they're all sharing the same icon, so it seems kinda unimpressive, but hopefully we'll have the art assets sometime soon to get them in place. Editors will notice I updated the labels to make them a bit clearer; two important notes on this: For an article to show up you MUST have &amp;quot;The Main Page&amp;quot; in the topic list (slash will complain if you don't have it).&lt;br /&gt;
&lt;br /&gt;
Signoff Requirements: A new feature of SoylentNews requires that editors must have a peer sign-off an article before it can be displayed to the world. Slash has some limited support for this, and I got it working last night. For editors, stories are now marked in red and state &amp;quot;unsigned&amp;quot; on the index if only one person has edited it. Right now, this check is not enforced, but I plan to hopefully address that soon. For the moment, editors can future date and use the buddy system to get things checked off properly so we can have consistent formatting and quality.&lt;br /&gt;
&lt;br /&gt;
Other Changes: I stripped out some of the dead features that I probably won't have time to fix before launch like OpenID login, and fixed the admin spellchecker. I also have a couple of ideas to get varnish going I need to bounce off Robin. &lt;br /&gt;
&lt;br /&gt;
-- NCommander&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 04:40 UTC:''' Expanded Alpha (Feb 15, 11:40PM EST)&lt;br /&gt;
We are expanding our alpha test to 100 users (from 70) over the next 24 hours.  Stay alert for ways to get in on the action! Check the IRC Channel for details!  ##altshashdot on freenode.net  I am passing out about 2-3 approximately every hour.&lt;br /&gt;
&lt;br /&gt;
-- Mattie_p.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 4:26AM UTC:''' The plan is coming (Feb 15, 2014  11:25PM EST)&lt;br /&gt;
&lt;br /&gt;
I'm putting together a manifesto to answer everyone's questions regarding the future of the project. Briefly, the community will choose all aspects of the project including the business model.&lt;br /&gt;
&lt;br /&gt;
I'm planning on first giving the community the opportunity to choose a permanent name, then the business model, then I'll start implementing the model (incorporating or whatever) while we sort out the rest of the issues.&lt;br /&gt;
&lt;br /&gt;
I have warmed to the notion of non-profit, and would like to set before the community a list of notes and observations to provoke discussion. I'm hoping to write this coming week and publish by Friday next or the Monday after.&lt;br /&gt;
&lt;br /&gt;
I'm not able to follow all the threads or forums, so if anyone asks, please pass this along.&lt;br /&gt;
&lt;br /&gt;
--John Barrabas&lt;br /&gt;
&lt;br /&gt;
John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-15 17:30 UTC:''' Alpha Test (Feb 15, 2014  12:30PM EST)&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 09:50 UTC:''' Status (Feb 14, 2014  4:50AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 02:50 UTC:''' Status (Feb 13, 2014  9:00PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 16:08 UTC:''' Status (Feb 13, 2014  1:08PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 05:33 UTC:''' Status (Feb 13, 2014  12:33AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 02:40 UTC:''' Status (Feb 12, 2014  9:40PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-12 13:24 UTC:''' Status (Feb, 12 2014 8:24 EST)&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 20:01 UTC:''' Status (Feb 11, 2014  3:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 17:01 UTC:''' Need some sphinx help (Feb 11, 2014 12:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4735</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4735"/>
		<updated>2014-02-16T20:18:10Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
[http://imgur.com/otMmmcM.png Latest Front Page]&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
'''2014-02-16 13:32 UTC:''' Reposted from the site:&lt;br /&gt;
&lt;br /&gt;
So, since this site went up three days ago, we've made tremendous progress in getting this site up and functional, and many of you gone above and beyond to try and give us content and provide meaningful comments. I'm completely blown away to say the least. I've got some big news to share, and a list of site improvements made over the last few days. Read on for more details ...&lt;br /&gt;
&lt;br /&gt;
Moderation: IT WORKS! I finished implementing the algorithm last night, and purging slash of the old one so they won't conflict. The new algorithm is somewhat of a radical departure from the old one. I won't go into full details in this post, but there's a good write-up in my comments here.&lt;br /&gt;
&lt;br /&gt;
Comment Counts: Got these working (again). ACs will only see a static HTML page which is updated every once in awhile. Logged-in users get the dynamic index which should have up-to-date counts. The fix is a bit wonky, so it might snap again. Let me know ASAP as the moderation scripts depend on this number being present (and correct!)&lt;br /&gt;
&lt;br /&gt;
Theme: As you may have noticed, the site looks less ass. Due to the heroic efforts of audioguy, Paul, and others, we've gotten a steady stream of CSS fixes to make the site look and feel more consistent. Its not perfect (Firefox still has width issues), but its a fair improvement. This is one of the last major launch blockers&lt;br /&gt;
&lt;br /&gt;
Topics: Finally got them implemented after we snapped the site in two last night. For the moment, they're all sharing the same icon, so it seems kinda unimpressive, but hopefully we'll have the art assets sometime soon to get them in place. Editors will notice I updated the labels to make them a bit clearer; two important notes on this: For an article to show up you MUST have &amp;quot;The Main Page&amp;quot; in the topic list (slash will complain if you don't have it).&lt;br /&gt;
&lt;br /&gt;
Signoff Requirements: A new feature of SoylentNews requires that editors must have a peer sign-off an article before it can be displayed to the world. Slash has some limited support for this, and I got it working last night. For editors, stories are now marked in red and state &amp;quot;unsigned&amp;quot; on the index if only one person has edited it. Right now, this check is not enforced, but I plan to hopefully address that soon. For the moment, editors can future date and use the buddy system to get things checked off properly so we can have consistent formatting and quality.&lt;br /&gt;
&lt;br /&gt;
Other Changes: I stripped out some of the dead features that I probably won't have time to fix before launch like OpenID login, and fixed the admin spellchecker. I also have a couple of ideas to get varnish going I need to bounce off Robin. &lt;br /&gt;
&lt;br /&gt;
-- NCommander&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 04:40 UTC:''' Expanded Alpha (Feb 15, 11:40PM EST)&lt;br /&gt;
We are expanding our alpha test to 100 users (from 70) over the next 24 hours.  Stay alert for ways to get in on the action! Check the IRC Channel for details!  ##altshashdot on freenode.net&lt;br /&gt;
&lt;br /&gt;
-- Mattie_p.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 4:26AM UTC:''' The plan is coming (Feb 15, 2014  11:25PM EST)&lt;br /&gt;
&lt;br /&gt;
I'm putting together a manifesto to answer everyone's questions regarding the future of the project. Briefly, the community will choose all aspects of the project including the business model.&lt;br /&gt;
&lt;br /&gt;
I'm planning on first giving the community the opportunity to choose a permanent name, then the business model, then I'll start implementing the model (incorporating or whatever) while we sort out the rest of the issues.&lt;br /&gt;
&lt;br /&gt;
I have warmed to the notion of non-profit, and would like to set before the community a list of notes and observations to provoke discussion. I'm hoping to write this coming week and publish by Friday next or the Monday after.&lt;br /&gt;
&lt;br /&gt;
I'm not able to follow all the threads or forums, so if anyone asks, please pass this along.&lt;br /&gt;
&lt;br /&gt;
--John Barrabas&lt;br /&gt;
&lt;br /&gt;
John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-15 17:30 UTC:''' Alpha Test (Feb 15, 2014  12:30PM EST)&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 09:50 UTC:''' Status (Feb 14, 2014  4:50AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 02:50 UTC:''' Status (Feb 13, 2014  9:00PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 16:08 UTC:''' Status (Feb 13, 2014  1:08PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 05:33 UTC:''' Status (Feb 13, 2014  12:33AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 02:40 UTC:''' Status (Feb 12, 2014  9:40PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-12 13:24 UTC:''' Status (Feb, 12 2014 8:24 EST)&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 20:01 UTC:''' Status (Feb 11, 2014  3:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 17:01 UTC:''' Need some sphinx help (Feb 11, 2014 12:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4727</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4727"/>
		<updated>2014-02-16T14:44:55Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
[http://imgur.com/otMmmcM.png Latest Front Page]&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
'''2014-02-16 13:32 UTC:''' Reposted from the site&lt;br /&gt;
 So, since this site went up three days ago, we've made tremendous progress in getting this site up and functional, and many of you gone above and beyond to try and give us content and provide meaningful comments. I'm completely blown away to say the least. I've got some big news to share, and a list of site improvements made over the last few days. Read on for more details ...&lt;br /&gt;
&lt;br /&gt;
Moderation: IT WORKS! I finished implementing the algorithm last night, and purging slash of the old one so they won't conflict. The new algorithm is somewhat of a radical departure from the old one. I won't go into full details in this post, but there's a good write-up in my comments here.&lt;br /&gt;
&lt;br /&gt;
Comment Counts: Got these working (again). ACs will only see a static HTML page which is updated every once in awhile. Logged-in users get the dynamic index which should have up-to-date counts. The fix is a bit wonky, so it might snap again. Let me know ASAP as the moderation scripts depend on this number being present (and correct!)&lt;br /&gt;
&lt;br /&gt;
Theme: As you may have noticed, the site looks less ass. Due to the heroic efforts of audioguy, Paul, and others, we've gotten a steady stream of CSS fixes to make the site look and feel more consistent. Its not perfect (Firefox still has width issues), but its a fair improvement. This is one of the last major launch blockers&lt;br /&gt;
&lt;br /&gt;
Topics: Finally got them implemented after we snapped the site in two last night. For the moment, they're all sharing the same icon, so it seems kinda unimpressive, but hopefully we'll have the art assets sometime soon to get them in place. Editors will notice I updated the labels to make them a bit clearer; two important notes on this: For an article to show up you MUST have &amp;quot;The Main Page&amp;quot; in the topic list (slash will complain if you don't have it).&lt;br /&gt;
&lt;br /&gt;
Signoff Requirements: A new feature of SoylentNews requires that editors must have a peer sign-off an article before it can be displayed to the world. Slash has some limited support for this, and I got it working last night. For editors, stories are now marked in red and state &amp;quot;unsigned&amp;quot; on the index if only one person has edited it. Right now, this check is not enforced, but I plan to hopefully address that soon. For the moment, editors can future date and use the buddy system to get things checked off properly so we can have consistent formatting and quality.&lt;br /&gt;
&lt;br /&gt;
Other Changes: I stripped out some of the dead features that I probably won't have time to fix before launch like OpenID login, and fixed the admin spellchecker. I also have a couple of ideas to get varnish going I need to bounce off Robin. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 04:40 UTC:''' Expanded Alpha (Feb 15, 11:40PM EST)&lt;br /&gt;
We are expanding our alpha test to 100 users (from 70) over the next 24 hours.  Stay alert for ways to get in on the action!&lt;br /&gt;
&lt;br /&gt;
-- Mattie_p.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 4:26AM UTC:''' The plan is coming (Feb 15, 2014  11:25PM EST)&lt;br /&gt;
&lt;br /&gt;
I'm putting together a manifesto to answer everyone's questions regarding the future of the project. Briefly, the community will choose all aspects of the project including the business model.&lt;br /&gt;
&lt;br /&gt;
I'm planning on first giving the community the opportunity to choose a permanent name, then the business model, then I'll start implementing the model (incorporating or whatever) while we sort out the rest of the issues.&lt;br /&gt;
&lt;br /&gt;
I have warmed to the notion of non-profit, and would like to set before the community a list of notes and observations to provoke discussion. I'm hoping to write this coming week and publish by Friday next or the Monday after.&lt;br /&gt;
&lt;br /&gt;
I'm not able to follow all the threads or forums, so if anyone asks, please pass this along.&lt;br /&gt;
&lt;br /&gt;
--John Barrabas&lt;br /&gt;
&lt;br /&gt;
John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-15 17:30 UTC:''' Alpha Test (Feb 15, 2014  12:30PM EST)&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 09:50 UTC:''' Status (Feb 14, 2014  4:50AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 02:50 UTC:''' Status (Feb 13, 2014  9:00PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 16:08 UTC:''' Status (Feb 13, 2014  1:08PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 05:33 UTC:''' Status (Feb 13, 2014  12:33AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 02:40 UTC:''' Status (Feb 12, 2014  9:40PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-12 13:24 UTC:''' Status (Feb, 12 2014 8:24 EST)&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 20:01 UTC:''' Status (Feb 11, 2014  3:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 17:01 UTC:''' Need some sphinx help (Feb 11, 2014 12:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4725</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4725"/>
		<updated>2014-02-16T14:41:35Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
[http://imgur.com/otMmmcM Latest Front Page]&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
'''2014-02-16 13:32 UTC:''' Reposted from the site&lt;br /&gt;
 So, since this site went up three days ago, we've made tremendous progress in getting this site up and functional, and many of you gone above and beyond to try and give us content and provide meaningful comments. I'm completely blown away to say the least. I've got some big news to share, and a list of site improvements made over the last few days. Read on for more details ...&lt;br /&gt;
&lt;br /&gt;
Moderation: IT WORKS! I finished implementing the algorithm last night, and purging slash of the old one so they won't conflict. The new algorithm is somewhat of a radical departure from the old one. I won't go into full details in this post, but there's a good write-up in my comments here.&lt;br /&gt;
&lt;br /&gt;
Comment Counts: Got these working (again). ACs will only see a static HTML page which is updated every once in awhile. Logged-in users get the dynamic index which should have up-to-date counts. The fix is a bit wonky, so it might snap again. Let me know ASAP as the moderation scripts depend on this number being present (and correct!)&lt;br /&gt;
&lt;br /&gt;
Theme: As you may have noticed, the site looks less ass. Due to the heroic efforts of audioguy, Paul, and others, we've gotten a steady stream of CSS fixes to make the site look and feel more consistent. Its not perfect (Firefox still has width issues), but its a fair improvement. This is one of the last major launch blockers&lt;br /&gt;
&lt;br /&gt;
Topics: Finally got them implemented after we snapped the site in two last night. For the moment, they're all sharing the same icon, so it seems kinda unimpressive, but hopefully we'll have the art assets sometime soon to get them in place. Editors will notice I updated the labels to make them a bit clearer; two important notes on this: For an article to show up you MUST have &amp;quot;The Main Page&amp;quot; in the topic list (slash will complain if you don't have it).&lt;br /&gt;
&lt;br /&gt;
Signoff Requirements: A new feature of SoylentNews requires that editors must have a peer sign-off an article before it can be displayed to the world. Slash has some limited support for this, and I got it working last night. For editors, stories are now marked in red and state &amp;quot;unsigned&amp;quot; on the index if only one person has edited it. Right now, this check is not enforced, but I plan to hopefully address that soon. For the moment, editors can future date and use the buddy system to get things checked off properly so we can have consistent formatting and quality.&lt;br /&gt;
&lt;br /&gt;
Other Changes: I stripped out some of the dead features that I probably won't have time to fix before launch like OpenID login, and fixed the admin spellchecker. I also have a couple of ideas to get varnish going I need to bounce off Robin. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 04:40 UTC:''' Expanded Alpha (Feb 15, 11:40PM EST)&lt;br /&gt;
We are expanding our alpha test to 100 users (from 70) over the next 24 hours.  Stay alert for ways to get in on the action!&lt;br /&gt;
&lt;br /&gt;
-- Mattie_p.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 4:26AM UTC:''' The plan is coming (Feb 15, 2014  11:25PM EST)&lt;br /&gt;
&lt;br /&gt;
I'm putting together a manifesto to answer everyone's questions regarding the future of the project. Briefly, the community will choose all aspects of the project including the business model.&lt;br /&gt;
&lt;br /&gt;
I'm planning on first giving the community the opportunity to choose a permanent name, then the business model, then I'll start implementing the model (incorporating or whatever) while we sort out the rest of the issues.&lt;br /&gt;
&lt;br /&gt;
I have warmed to the notion of non-profit, and would like to set before the community a list of notes and observations to provoke discussion. I'm hoping to write this coming week and publish by Friday next or the Monday after.&lt;br /&gt;
&lt;br /&gt;
I'm not able to follow all the threads or forums, so if anyone asks, please pass this along.&lt;br /&gt;
&lt;br /&gt;
--John Barrabas&lt;br /&gt;
&lt;br /&gt;
John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-15 17:30 UTC:''' Alpha Test (Feb 15, 2014  12:30PM EST)&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 09:50 UTC:''' Status (Feb 14, 2014  4:50AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 02:50 UTC:''' Status (Feb 13, 2014  9:00PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 16:08 UTC:''' Status (Feb 13, 2014  1:08PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 05:33 UTC:''' Status (Feb 13, 2014  12:33AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 02:40 UTC:''' Status (Feb 12, 2014  9:40PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-12 13:24 UTC:''' Status (Feb, 12 2014 8:24 EST)&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 20:01 UTC:''' Status (Feb 11, 2014  3:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 17:01 UTC:''' Need some sphinx help (Feb 11, 2014 12:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4716</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4716"/>
		<updated>2014-02-16T04:43:42Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
'''2014-02-16 04:40 UTC:''' Expanded Alpha (Feb 15, 11:40PM EST)&lt;br /&gt;
We are expanding our alpha test to 100 users (from 70) over the next 24 hours.  Stay alert for ways to get in on the action! -- Mattie_p).&lt;br /&gt;
&lt;br /&gt;
'''2014-02-16 4:26AM UTC:''' The plan is coming (Feb 15, 2014  11:25PM EST)&lt;br /&gt;
&lt;br /&gt;
I'm putting together a manifesto to answer everyone's questions regarding the future of the project. Briefly, the community will choose all aspects of the project including the business model.&lt;br /&gt;
&lt;br /&gt;
I'm planning on first giving the community the opportunity to choose a permanent name, then the business model, then I'll start implementing the model (incorporating or whatever) while we sort out the rest of the issues.&lt;br /&gt;
&lt;br /&gt;
I have warmed to the notion of non-profit, and would like to set before the community a list of notes and observations to provoke discussion. I'm hoping to write this coming week and publish by Friday next or the Monday after.&lt;br /&gt;
&lt;br /&gt;
I'm not able to follow all the threads or forums, so if anyone asks, please pass this along.&lt;br /&gt;
&lt;br /&gt;
--John Barrabas&lt;br /&gt;
&lt;br /&gt;
John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-15 17:30 UTC:''' Alpha Test (Feb 15, 2014  12:30PM EST)&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 09:50 UTC:''' Status (Feb 14, 2014  4:50AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-14 02:50 UTC:''' Status (Feb 13, 2014  9:00PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 16:08 UTC:''' Status (Feb 13, 2014  1:08PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 05:33 UTC:''' Status (Feb 13, 2014  12:33AM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-13 02:40 UTC:''' Status (Feb 12, 2014  9:40PM EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-12 13:24 UTC:''' Status (Feb, 12 2014 8:24 EST)&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 20:01 UTC:''' Status (Feb 11, 2014  3:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''2014-02-11 17:01 UTC:''' Need some sphinx help (Feb 11, 2014 12:01PM EST)&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4713</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4713"/>
		<updated>2014-02-16T04:17:51Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: Undo revision 4712 by Mattie p (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs (registration required, and email approval may be intermittent, be patient), check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Try not to post duplicate bugs, but if you do it isn't the end of the world.&lt;br /&gt;
&lt;br /&gt;
Keep editing this page for any suggestions you have about the site that aren't bugs.&lt;br /&gt;
&lt;br /&gt;
Note: When you register on the actual alpha site, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
Note: We have had at least three people join the alpha site without a specific invitation anyone on staff. They have uids right now on the alpha server. Based on the method they used, they deserved to get in.  We have not removed them nor do we intend to. We just asked that they tell us what they did, we all had a good laugh and left that door open.  Feel free to use it.  PM one of the leaders on the IRC with URL of the top article and we'll give you the IRC channel to discuss the alpha project specifically.&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
&lt;br /&gt;
===Please &amp;lt;font style=&amp;quot;color: red&amp;quot;&amp;gt;stop posting bugs here&amp;lt;/font&amp;gt;===&lt;br /&gt;
&lt;br /&gt;
...instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
===DISCLAIMER:===&lt;br /&gt;
&lt;br /&gt;
'''This is not a full list of bugs, that list will be on the tracker here: https://dev.soylentnews.org/tracker/?group_id=6'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
** Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
* The front page shows the wrong number of comments (most often 0) on the articles.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
* ''For lack of a better place for these things'':&lt;br /&gt;
** The two lines at top of page &amp;quot;You have 0 new messages waiting for you, and 1 old message. This page was generated by a Cadre of Attack Midgets for Appalbarry (66)&amp;quot; could be smaller and not boldface. They kind of hammer you.&lt;br /&gt;
** Throughout the back end is a lot of language that really isn't clear - much left from Slashdot.  This could be cleaned up and simplified to eliminate a lot of &amp;quot;huh?&amp;quot; moments.&lt;br /&gt;
** In the &amp;quot;posted by Dopefish on Saturday February 15, @12:00PM&amp;quot; section, the linked poster names don't go anywhere.&lt;br /&gt;
** I give up - what is the &amp;quot;li694-22.members.linode.com&amp;quot; link at the bottom of each story?&lt;br /&gt;
** I'm not that young, don't have great eyesight, and don't sit too close or far from my monitors, but find that the type in the articles is a bit large for my taste.&lt;br /&gt;
** Are Amigos and Friends the same thing?&lt;br /&gt;
** I'm in favour of being conventional and defaulting to Italics OFF in almost every area.&lt;br /&gt;
** I'm on the &amp;quot;Configuring User Preferences For Appalbarry (66) barry.rueger@gmail.com&amp;quot; page, and find that in the menu strip above that header I'm seeing a link to another user. Can't think why. &amp;quot;Logout Preferences Password ~Appalbarry (66)~ragequit (44)&amp;quot;&lt;br /&gt;
* At least initially, until the major bugs have been fixed, and the first wave of new users are in place, the site needs a contact page, likely with the Overlord contact addresses. Better to have people e-mailing the site admins than cluttering up the comments sections with complaints.&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4712</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4712"/>
		<updated>2014-02-16T04:17:25Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Suggestions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs (registration required, and email approval may be intermittent, be patient), check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Try not to post duplicate bugs, but if you do it isn't the end of the world.&lt;br /&gt;
&lt;br /&gt;
Keep editing this page for any suggestions you have about the site that aren't bugs.&lt;br /&gt;
&lt;br /&gt;
Note: When you register on the actual alpha site, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
Note: We have had at least three people join the alpha site without a specific invitation anyone on staff. They have uids right now on the alpha server. Based on the method they used, they deserved to get in.  We have not removed them nor do we intend to. We just asked that they tell us what they did, we all had a good laugh and left that door open.  Feel free to use it.  PM one of the leaders on the IRC with URL of the top article and we'll give you the IRC channel to discuss the alpha project specifically.&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
&lt;br /&gt;
===Please &amp;lt;font style=&amp;quot;color: red&amp;quot;&amp;gt;stop posting bugs here&amp;lt;/font&amp;gt;===&lt;br /&gt;
&lt;br /&gt;
...instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
===DISCLAIMER:===&lt;br /&gt;
&lt;br /&gt;
'''This is not a full list of bugs, that list will be on the tracker here: https://dev.soylentnews.org/tracker/?group_id=6'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
** Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
* The front page shows the wrong number of comments (most often 0) on the articles.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
* ''For lack of a better place for these things'':&lt;br /&gt;
** The two lines at top of page &amp;quot;You have 0 new messages waiting for you, and 1 old message. This page was generated by a Cadre of Attack Midgets for Appalbarry (66)&amp;quot; could be smaller and not boldface. They kind of hammer you.&lt;br /&gt;
** Throughout the back end is a lot of language that really isn't clear - much left from Slashdot.  This could be cleaned up and simplified to eliminate a lot of &amp;quot;huh?&amp;quot; moments.&lt;br /&gt;
** In the &amp;quot;posted by Dopefish on Saturday February 15, @12:00PM&amp;quot; section, the linked poster names don't go anywhere.&lt;br /&gt;
** I'm not that young, don't have great eyesight, and don't sit too close or far from my monitors, but find that the type in the articles is a bit large for my taste.&lt;br /&gt;
** Are Amigos and Friends the same thing?&lt;br /&gt;
** I'm in favour of being conventional and defaulting to Italics OFF in almost every area.&lt;br /&gt;
** I'm on the &amp;quot;Configuring User Preferences For Appalbarry (66) barry.rueger@gmail.com&amp;quot; page, and find that in the menu strip above that header I'm seeing a link to another user. Can't think why. &amp;quot;Logout Preferences Password ~Appalbarry (66)~ragequit (44)&amp;quot;&lt;br /&gt;
* At least initially, until the major bugs have been fixed, and the first wave of new users are in place, the site needs a contact page, likely with the Overlord contact addresses. Better to have people e-mailing the site admins than cluttering up the comments sections with complaints.&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4704</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4704"/>
		<updated>2014-02-16T00:30:13Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 15, 2014  12:30PM EST (-5 UTC):''' Alpha Test&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 14, 2014  4:50AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  9:00PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  1:08PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  12:33AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 12, 2014  9:40PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb, 12 2014 8:24 EST:''' Status&lt;br /&gt;
&lt;br /&gt;
'''WE HAVE A FIRST POST'''&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  3:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' Need some sphinx help&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==The Slashcott==&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott (boycott) is getting attention'''&lt;br /&gt;
&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Project Goal==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlord Contacts==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4703</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4703"/>
		<updated>2014-02-15T23:59:40Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Introduction to Alpha */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs (registration required, and email approval may be intermittent, be patient), check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Try not to post duplicate bugs, but if you do it isn't the end of the world.&lt;br /&gt;
&lt;br /&gt;
Keep editing this page for any suggestions you have about the site that aren't bugs.&lt;br /&gt;
&lt;br /&gt;
Note: When you register on the actual alpha site, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
Note: We have had at least three people join the alpha site without a specific invitation anyone on staff. They have uids right now on the alpha server. Based on the method they used, they deserved to get in.  We have not removed them nor do we intend to. We just asked that they tell us what they did, we all had a good laugh and left that door open.  Feel free to use it.  PM one of the leaders on the IRC with URL of the top article and we'll give you the IRC channel to discuss the alpha project specifically.&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
* The front page shows the wrong number of comments (most often 0) on the articles.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
* ''For lack of a better place for these things'':&lt;br /&gt;
** The two lines at top of page &amp;quot;You have 0 new messages waiting for you, and 1 old message. This page was generated by a Cadre of Attack Midgets for Appalbarry (66)&amp;quot; could be smaller and not boldface. They kind of hammer you.&lt;br /&gt;
** Throughout the back end is a lot of language that really isn't clear - much left from Slashdot.  This could be cleaned up and simplified to eliminate a lot of &amp;quot;huh?&amp;quot; moments.&lt;br /&gt;
** In the &amp;quot;posted by Dopefish on Saturday February 15, @12:00PM&amp;quot; section, the linked poster names don't go anywhere.&lt;br /&gt;
** I give up - what is the &amp;quot;li694-22.members.linode.com&amp;quot; link at the bottom of each story?&lt;br /&gt;
** I'm not that young, don't have great eyesight, and don't sit too close or far from my monitors, but find that the type in the articles is a bit large for my taste.&lt;br /&gt;
** Are Amigos and Friends the same thing?&lt;br /&gt;
** I'm in favour of being conventional and defaulting to Italics OFF in almost every area.&lt;br /&gt;
** I'm on the &amp;quot;Configuring User Preferences For Appalbarry (66) barry.rueger@gmail.com&amp;quot; page, and find that in the menu strip above that header I'm seeing a link to another user. Can't think why. &amp;quot;Logout Preferences Password ~Appalbarry (66)~ragequit (44)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4695</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4695"/>
		<updated>2014-02-15T20:55:45Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Introduction to Alpha */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs (registration required, and email approval may be intermittent, be patient), check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Try not to post duplicate bugs, but if you do it isn't the end of the world.&lt;br /&gt;
&lt;br /&gt;
Keep editing this page for any suggestions you have about the site that aren't bugs.&lt;br /&gt;
&lt;br /&gt;
Note: When you register on the actual alpha site, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
Note: We have had at least three people join the alpha site without a specific invitation anyone on staff. They have uids right now on the alpha server. Based on the method they used, they deserved to get in.  We have not removed them nor do we intend to. We just asked that they tell us what they did, we all had a good laugh and left that door open.  Feel free to use it.  PM one of the leaders on the IRC with the top article and we'll give you the IRC channel to discuss the alpha project specifically.&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4693</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4693"/>
		<updated>2014-02-15T18:19:01Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
&lt;br /&gt;
'''Feb 15, 2014  12:30PM EST:''' Alpha Test&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 20 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
'''Feb 14, 2014  4:50AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  9:00PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  1:08PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  12:33AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 12, 2014  9:40PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===WE HAVE A FIRST POST===&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Site Announcements'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  8:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Yeah, yeah... we're working on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So if you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
editors@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
forums@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
wiki@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  3:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' Need some sphinx help&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
EDIT:  Sent a discussion to John (at) SoylentNews (dot) org&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott is getting attention'''&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Get Involved '''&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
'''Contact:'''&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==Status==&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4692</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4692"/>
		<updated>2014-02-15T18:02:34Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Introduction to Alpha */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs (registration required, and email approval may be intermittent, be patient), check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Try not to post duplicate bugs, but if you do it isn't the end of the world.&lt;br /&gt;
&lt;br /&gt;
Keep editing this page for any suggestions you have about the site that aren't bugs.&lt;br /&gt;
&lt;br /&gt;
Note: When you register on the actual alpha site, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4691</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4691"/>
		<updated>2014-02-15T17:55:12Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
&lt;br /&gt;
'''Feb 15, 2014  12:30PM EST:''' Alpha Test&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 15 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC (##altslashdot on freenode.net), or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
'''Feb 14, 2014  4:50AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  9:00PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  1:08PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  12:33AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 12, 2014  9:40PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===WE HAVE A FIRST POST===&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Site Announcements'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  8:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Yeah, yeah... we're working on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So if you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
editors@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
forums@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
wiki@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  3:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' Need some sphinx help&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
EDIT:  Sent a discussion to John (at) SoylentNews (dot) org&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott is getting attention'''&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Get Involved '''&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
'''Contact:'''&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==Status==&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4690</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4690"/>
		<updated>2014-02-15T17:45:13Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Introduction to Alpha */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs, check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Keep editing this page for suggestions.&lt;br /&gt;
&lt;br /&gt;
Note: When you register, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine. -- Mattie_p&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
* There is no CAPTCHA on the post page for ACs&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;br /&gt;
&lt;br /&gt;
== Broken Links for Stories ==&lt;br /&gt;
* When not logged in there are some stories that return 404 errors. Logging in the stories show up.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4689</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4689"/>
		<updated>2014-02-15T17:40:12Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]] ... Was your question not answered? Get on IRC and pester the relevant person: [[WhosWho| Who's Who?]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
&lt;br /&gt;
'''Feb 15, 2014  12:30PM EST:''' Alpha Test&lt;br /&gt;
&lt;br /&gt;
Greetings, fellow Soylentils.  As of right now, we have 15 articles posted on the alpha test site and about 60 registered users, who have produced over 150 comments so far.  We're slowly increasing the number of Alphans on a daily basis.  The best way to get invited is to participate somewhere, either in the forums, the IRC, or on the wiki page. Contribute articles via the forum.  Make suggestions.  Etc.  Anyway, I'd ask everyone to carefully read the [[Alpha_Bugs|Alpha Bugs]] page, particularly the Introduction to Alpha, it will give you information that will help you become an Alphan. Thanks for reading.  --Mattie_p&lt;br /&gt;
&lt;br /&gt;
'''Feb 14, 2014  4:50AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Started mod system rework. Here's my writeup on thoughts from the test site:&lt;br /&gt;
&lt;br /&gt;
As the to-do list of tasks continues to be whittled bit by bit towards launch, one large item remains: distribution of moderation points. While I wish I could reuse the existing Slash code, the fact is that this code is completely inappropriate for a site smaller than Slashdot. So, I've been working with a couple of users in chat to rework the underlying math so that mod point distribution actually works in a reasonable way. If you're interested in the potential algorithm behind this, read on. Be warned, it is a bit dry and technical.&lt;br /&gt;
&lt;br /&gt;
The current thoughts are that slash should enforce that a specific number of mod points must ALWAYS be in circulation, and in the hands of our potential moderators. Without going into too much detail, we're running off the assumption that the total number of moderations applied in an article should approximately equal the number of comments. To account for inactive users and for the constant flow of new articles/comments, twice as many mod points will be distributed.&lt;br /&gt;
Have I lost you yet? To reiterate, two mod points must exist for every comment in active articles. As far as problems go, having too many mod points in circulation is far preferable to too few. If you don't understand why, I recommend trying to find +5 posts on other slash sites like Slashdot Japan or BarraPunto.&lt;br /&gt;
&lt;br /&gt;
Here's an example:&lt;br /&gt;
Assuming that we have two articles with approximately 200 comments each, that means we need to have 800 points in circulation. However, if we stuck with the old Slashdot method of 5 points to a user, we'd end up needing to have 80 people read an article and not comment on it. Obviously, that's not going to work, and as we have more articles/comments, that number will only increase.&lt;br /&gt;
&lt;br /&gt;
Instead, we'll limit the number of moderators to approximately 30% of active accounts who haven't moderated relatively recently. In this context, active means that you have logged in within the last 5 days. The process_moderators script will calculate how many mod points are currently in circulation, how many need to be in circulation, and how many, if any, it needs to add to the pool. It then looks at the list of eligible moderators, selects 30% of them, and hands them out. To prevent moderation fatigue, we'll cap the maximum number of points a user can receive, and by the same logic, also set a minimum. I don't know about you, but I'd be a little annoyed if I found I had gotten a whopping 1 whole mod point.&lt;br /&gt;
&lt;br /&gt;
This should allow a relatively fluid system, and I hope, allow us to have something very similar to the moderation system we've all grown to love. I'm open to suggestions or even radically different ideas on how to improve this below.&lt;br /&gt;
[[User:NCommander|NCommander]] ([[User talk:NCommander|talk]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  9:00PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We just modified the DNS a little. It'll take awhile for the changes to propagate through the net. I bumped the TTL down to 30 minutes (from 3 hours), so future changes should go pretty fast. There may be some intermittent problems for a short while.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're not going live ''just'' yet, but we're comfortable letting more people in. Slowly I turned, step by step...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander installed FusionForge on the dev site. It comes with MediaWiki (the same package as this), forum software, project management, and integrated bug tracking. It's pretty nice. It's the same package that runs SourceForge, so it'll be familiar to many people.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's not a lot of discussion on the forums about which bug tracker to use, so absent any wailing and gnashing-of-teeth, I'd like to go with his choice. If people don't like this, start a protest and we'll talk.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  1:08PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCommander, our chief architect and hero, who has been putting in marathon days since Friday, is taking a much-needed &amp;quot;mental health day&amp;quot;. We are idling in test mode (a few editors, the systems team, the alpha-test group) for at least a day while people catch their breath.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Varnish, our web accelerator, is not passing site cookies back to the user so we've disabled it for now. This means that the site is working, just not able to handle any sort of high-traffic load.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It's been pointed out that the wiki is a bad place to manage bugs. I agree completely, but for the first day it tends to avoid duplicates and it was only for a day or so anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There's been some discussion among the ''system'' group (about a dozen people) about bug trackers, but that decision should really come from the ''dev'' team (30 or more, on the forum). The dev team should start discussing what they'd like to see for bug tracking on the forums. I'll monitor the thread and take consensus opinion (if there is one), or make an executive decision.&lt;br /&gt;
&lt;br /&gt;
Please keep in mind the full scope of project bug tracking. System has suggested bug tracking be split into two sections - a mantis install, easy and user-friendly, used for overall site issues, and GitHub for technical issues which might be more appropriate for engineering bugs. Also, we intend to release the code open-source, so GitHub could field technical issues from other sites using our interface.&lt;br /&gt;
&lt;br /&gt;
Food for thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 13, 2014  12:33AM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A select few editors, dev, and system types are working through the system finding bugs. User registration works, there are stories on the front page, comments and replies. A screenshot of testing from last night is here: https://dl.dropboxusercontent.com/u/52836172/2014-02-13-SN-aplha.png&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We could use a temporary bug tracking system that's easily accessible by the users (ie - not requiring onerous registration). Can anyone hook us up?&lt;br /&gt;
: How about &amp;quot;Bug:&amp;quot; namespace here on wiki? [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 00:45, 13 February 2014 (MST) &amp;lt;=== Done&lt;br /&gt;
:: If you expect more reports, I suggest using something structured like [[Template:Bug]] (example use in [[Bug:Testbug]]). Expand the template however you see fit. :) [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 02:07, 13 February 2014 (MST)&lt;br /&gt;
::: Technically, this solution still requires registration (since anonymous editing is disabled on the wiki), and I don't think it would be able to handle some usual features of bug trackers like being able to list issues and filter them by stuff like their status.  [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 04:22, 13 February 2014 (MST)&lt;br /&gt;
:::: I created a [[Bug tracker]] page for figuring out what we want to do. [[User:FunPika|&amp;lt;span style=&amp;quot;color:blue&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Fun&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]][[User_Talk:FunPika|&amp;lt;span style=&amp;quot;color:green&amp;quot;&amp;gt;&amp;lt;b&amp;gt;Pika&amp;lt;/b&amp;gt;&amp;lt;/span&amp;gt;]] 05:23, 13 February 2014 (MST)&lt;br /&gt;
: Why temporary? We should just get a proper bug tracker in place then even in the future when someone notices a quirk they can report it. One of the big issues with /. was people were constantly complaining about bugs with no way to tell if they were being addressed. How long were people complaining about unicode support? [[User:Vanderhoth|Vanderhoth]] &lt;br /&gt;
&lt;br /&gt;
: ''Later we want to have recommendations and properly choose a system that's well suited. At present, we don't want to spend time on things not directly related to bringing the system up. -John''&lt;br /&gt;
&lt;br /&gt;
E-mail me: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 12, 2014  9:40PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Freenode is complaining &amp;quot;Server is full&amp;quot; and not letting me into chat, so this is a '''guess status''' :-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thanks to everyone who volunteered to help test the system this evening. At the last minute, the team found a nest of bugs that effectively broke the moderation system, so testing was put off until 10:PM EST, and then later was put off until Thu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Nothing is impossible for the person who doesn’t have to do it himself.&lt;br /&gt;
* Any project can be estimated accurately once it’s completed.&lt;br /&gt;
* The sooner you get behind schedule, the more time you have to make it up.&lt;br /&gt;
* A badly planned project will take three times longer than expected&lt;br /&gt;
* A well planned project only twice as long as expected.&lt;br /&gt;
* Schedules are made to be broken&lt;br /&gt;
* Work expands to fill the Time. Cost expands to meet the Budget.&lt;br /&gt;
* The first 90% of a project takes 90% of the time. The last 10% takes the other 90%.&lt;br /&gt;
* The only certainty in a project is uncertainty&lt;br /&gt;
* On time, on budget, on spec – pick 2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===WE HAVE A FIRST POST===&lt;br /&gt;
&lt;br /&gt;
From the site:&lt;br /&gt;
I know its been a long wait, but we've been steadily moving towards launch. With luck, you're reading this on the main index of the site, which means we've gone, and haven't gone mad in the process. Now that we're here, we hope to have made the wait worth it, but we depend on everyone in the community. To make this site a success, we depend on each and every single user even if its just from passing word of mouth. Remember, every single user can submit stories, moderate, and contribute to discussions all at the same time, and that's what makes us unique. May I be the first to welcome you to your new home. &lt;br /&gt;
&lt;br /&gt;
[[http://imgbin.org/index.php?page=image&amp;amp;id=16708]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Site Announcements'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  8:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
Yeah, yeah... we're working on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We're starting to get overlords that manage various features. An overlord is responsible for granting access - it's intended to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So if you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords have agreed to hold the position until Mar 1, at which time we will choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
editors@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
forums@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
wiki@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014  3:01PM EST:''' Status&lt;br /&gt;
&lt;br /&gt;
We have a working system, and two people fixing the CSS (sadly, none for sphinx). As far as I can tell, we're trying to get the high-bandwidth aspects of the site running: Varnish, MySQL configuration options, and such. We want the system to be able to withstand a tsunami of visitors 10 meters high.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The system team has been working around the clock to get things running, and I mean that literally. I have to as-much-as order people to break off at night and go to bed. They *really* want to see this thing work. Send them some love in chat if you can.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that these are not &amp;quot;deadlines&amp;quot;, nor do I particularly care if we miss them: We're  reporting when we &amp;quot;predict&amp;quot; things will be ready. The first 90% of the project is done, now we're working on the remaining 90%.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stand by for launch...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
P.S. - Check out the logo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' Need some sphinx help&lt;br /&gt;
&lt;br /&gt;
We still need [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]&lt;br /&gt;
expertise, so if you are familiar with this package, please E-mail me:&lt;br /&gt;
&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
EDIT:  Sent a discussion to John (at) SoylentNews (dot) org&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott is getting attention'''&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* http://arstechnica.com/information-technology/2014/02/slashdots-new-interface-could-kill-what-keeps-slashdot-relevant/   &amp;lt;=== Nice article by Ars &lt;br /&gt;
::* http://spallshurgenson.blogspot.com/2014/02/tragedy-of-commons-redesigning-social.html   &amp;lt;=== A good summary of the situation&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.tidbitsfortechs.com/2014/02/biting-hand-feeds-less-boycotting-slashdot-org-1-week&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Get Involved '''&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
* &amp;lt;EM&amp;gt;&amp;lt;B&amp;gt;Slashcott, Week 2, officially begins Monday, February 17th, 2014 and runs through the 23rd.&amp;lt;/B&amp;gt;&amp;lt;/EM&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
'''Contact:'''&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
==Status==&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
::The forums have four user groups: Code, Content, Style, and System.&lt;br /&gt;
* We upgraded the hosting by two tiers&lt;br /&gt;
* The System team is working on installing SlashCode. They are busting their collective tails to get this site up for us.  Hopefylly, soon!&lt;br /&gt;
* This *might* be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately.&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* Possible Trademark issues&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
*[[NewName]]&lt;br /&gt;
*[[MailingListUpdates]]&lt;br /&gt;
*[[Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business]]&lt;br /&gt;
*[[Moderation]] -- how/if to enhance; was it so bad it was the primary reason for the diaspora?&lt;br /&gt;
*[[FeatureList]] -- discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- how to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- points of contact in different project areas&lt;br /&gt;
*[[Spreading the word]]&lt;br /&gt;
*[[Comments]]&lt;br /&gt;
*[[To do]]&lt;br /&gt;
*[[Bugs]]&lt;br /&gt;
*[[Stories from former Slashdot users]]&lt;br /&gt;
*[[IRCVision|What should the IRC network be like?]]&lt;br /&gt;
*[[URLShortener|How do we want a URL shortener to be used?]]&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
SoylentNews Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org &lt;br /&gt;
&lt;br /&gt;
== Similar Projects ==&lt;br /&gt;
* [http://pipedot.org/ Pipedot] - Rewrite project - Aiming to create a cleaner news site with modern technology.&lt;br /&gt;
* 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]&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4683</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4683"/>
		<updated>2014-02-15T15:46:48Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, submit articles, test stuff, try to figure out all the things that aren't working yet.  In other words, be an aggressive participant.  Log out and check the site as an AC, try different browsers.  See if you can inject bad links or sql, but don't do [http://xkcd.com/327/ this], please.  Actually, TABLE students might be the safest way to go.  Coordinate with someone else on the IRC and double-team issues.  Click every link you can find so you can tell us what works.&lt;br /&gt;
&lt;br /&gt;
Post bugs, and issues at http://sylnt.us/bugs, check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  Keep editing this page for suggestions.&lt;br /&gt;
&lt;br /&gt;
Note: When you register, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good commentor and you'll be fine.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4676</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4676"/>
		<updated>2014-02-15T06:38:12Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction to Alpha===&lt;br /&gt;
Hello.  If you are reading this you may have been selected to participate in the alpha.  Don't be alarmed.  Everything is under control. I've been giving this little speech to everyone as they join the alpha site.  First, please don't share the alpha site's IRC channel information or the alpha site URL with anyone outside of that channel.&lt;br /&gt;
&lt;br /&gt;
When you get on, feel free to register, play around, post comments, test stuff, try to figure out all the things that aren't working yet.  In other words, be a participant. Post bugs, issues, and suggestions at http://sylnt.us/bugs, check this page for known issues until we transfer everything into the bug tracker, and even after.  Read all the known issues below before you start complaining about bugs in the IRC, we haven't lost patience yet but there are only so many times we want to hear about how you can't check for availability of your nickname before you register.  &lt;br /&gt;
&lt;br /&gt;
When you register, the registration email might get caught in your spam folder, so make sure to check that if you don't see it. &lt;br /&gt;
&lt;br /&gt;
The only people with mod points right now are the site admins, and they have better things to do for the most part, so don't worry too much about your karma unless you post really dumb things.  Be a good participant and you'll be fine.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
&lt;br /&gt;
Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
*: The 'Misc' pref page (/my/misc) has no content (no error messages, just nothing to see or interact with)&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
*When making comments, or going to preferences, or anything else, a link at the bottom in a familiar place saying &amp;quot;Continue to .. (whatever area you were in before)&amp;quot; to navigate to the parent page would be very helpful. (I must not have noticed but a link to parent does appear after submitting comment). Clicking 'save' button should also redirect to the parent page.  &lt;br /&gt;
** For comments the code would go here: slashcode/themes/slashcode/templates/comment_submit;comments;default .. snippit can be taken from: slashcode/themes/slashcode/templates/linkStory;misc;default&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
**This page could include a timed auto-redirect in addition to the link to parent page. &lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
** Also, the default threshold is either too high, or index mode is kicking in too early.&lt;br /&gt;
* Possible usability improvements:&lt;br /&gt;
** Add an explicit 'Main page' option in the Navigation menu on the left: slashcode/themes/slashcode/templates/mainmenu;misc;default&lt;br /&gt;
** blockquote in comments should be more than just a tab, but instead be shaded, for example. Also should be achievable with the word 'quote' or 'q' and not just 'blockquote' &lt;br /&gt;
** Quote Parent feature in comments&lt;br /&gt;
** Article summary could appear as the parent comment when commenting to the root of a thread&lt;br /&gt;
** Consider smaller font size for low mod comments&lt;br /&gt;
** In left hand menu bar: Create Account / Login .. wraps around improperly and is ambiguous. Possibly rename to Sign Up / Login&lt;br /&gt;
*** Also, Change Password could be truncated to just Password&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4650</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4650"/>
		<updated>2014-02-14T21:52:05Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.  Please stop posting bugs here, instead, sign up at https://dev.soylentnews.org, and direct link to bug submission is at http://sylnt.us/bugs &lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* ''Posted by'' user link under the story heading always points to the current page (whether from the front page or story page)&lt;br /&gt;
* Remove ALPHA_SERVER/help page (See Section Titled &amp;quot;Broken Links not Found in FAQ&amp;quot; for more information)&lt;br /&gt;
* Under Topics --&amp;gt; Navigation, the word “Topics” refers to Search, but the search functionality seems fundamentally broken.  Additionally: “Topics” is not an intuitive word for “Search”.  Under “Topics”, there are several links for searching different sections of the.  All of this is confusing.  Edit: Just found Navigation --&amp;gt; Older Stuff leads to another search as well.  Navigation --&amp;gt; Past Polls ==&amp;gt; More Polls is also another search.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
*: Preferences page /users.pl?op=edituser not saving most changes, Real Name, Homepage, Mobile Text Address, Sig and possibly others I didn't test&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Create account - check for availability gives no response&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
* Altering comments settings (You --&amp;gt; Comments ==&amp;gt; Make a change ==&amp;gt; Save) will re-display your old, unwanted settings, but if you leave and come back, then your new settings will show.  (Apparently, settings really are saved.)&lt;br /&gt;
  - Trying this in Chrome.  Settings activate immediately, but will not save for a return to the page.&lt;br /&gt;
* On the password page, the 'login session' link 404's.&lt;br /&gt;
* Achievements - I got the &amp;quot;You've posted a comment&amp;quot; achievement which is very nice, and then the same for journal, but the links take me to a page ( /~ancientt/achievements ) where there are no listed achievements&lt;br /&gt;
*On my 800X600 screen there is a horizontal scrollbar. Small issue, but it is there&lt;br /&gt;
* Instances of the word 'Slashdot'&lt;br /&gt;
** The comment creation / reply page (comments.pl op=reply) shows &amp;quot;Slashdot Comments&amp;quot; in the page title (the [html][head][title] element)&lt;br /&gt;
* The Lameness filter is not working. With a comment that triggers it, (a) pressing Preview just reloads the comment-creation page, and (b) pressing Submit just reloads the comment-creation page. No error message is printed.&lt;br /&gt;
* Navigation --&amp;gt; Past Polls ==&amp;gt; Submit Poll : Goes to same page as Navigation --&amp;gt; Submit Story; In other words, submitted a poll makes it looks like you are submitting a story.&lt;br /&gt;
&lt;br /&gt;
==Security Problems==&lt;br /&gt;
* There is no sanitation of URLs containing potentially malicious code. A comment can be a vehicle for a XSS/CSRF attack. (of course it could be wrapped up in a shortened url and then posted anyway)&lt;br /&gt;
&lt;br /&gt;
==Serious Usability Problems==&lt;br /&gt;
This is reserved for things that might completely baffle a new user, due to such problems as required fields not indicated as such, error messages that point the wrong way,wrong labels, etc.&lt;br /&gt;
* There is no clear indication on the journal edit page that comments must be enabled for these to even show up for the user himself, if it is unselected. The comments selector is labeled 'Comments cannot be disabled once enabled' which suggests a cautious approach may be wise to a new user. If a journal entry is made and submitted, the only message that indicates something may be wrong is the text 'You must enable comments for all users if you've marked your submission as &amp;quot;publicize&amp;quot; or &amp;quot;publish.' This text appears in no way like an error message, it is in normal, not even bold text, and refers to a function which does not appear to exist ('publish').&lt;br /&gt;
** Thanks to mattie_p and CommonJoe for helping me track this down.&lt;br /&gt;
* Friend / Foe seems to be best changed by clicking on faces next to names.  This is not intuitive.  (Found a couple of others places to click on but I don't find them intuitive either.)&lt;br /&gt;
* Generally users expect changes to take place immediately. Where this is not the case (cron jobs,etc.) there needs to be a clear indication in the text. Specific cases listed below:&lt;br /&gt;
** Friend / Foe can (sometimes) take at least 20 minutes to propogate.  There is no warning about this and it can be confusing since you save one setting and it immediately shows the old setting again.  Note: A job seems to run every 20 minutes starting at the top of the hour.&lt;br /&gt;
*Passwords sent to email address upon registration: warn it could be in spam folder.&lt;br /&gt;
&lt;br /&gt;
==Pure layout, appearance, and css problems==&lt;br /&gt;
This is mostly for future use, as the work on layout, theme, etc has not yet been integrated into the site yet. Completely missing elements should not go here, this is just about formatting issues.&lt;br /&gt;
&lt;br /&gt;
* Needs new template&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
* When a reply to a reply is submitted, instead of there being a &amp;quot; &amp;lt;b&amp;gt;Comment Submitted. There will be a delay before the comment becomes part of the static page. What you submitted appears below. If there is a mistake...well, you should have used the 'Preview' button! &amp;lt;/b&amp;gt;&amp;quot; notice, maybe the reply should be submitted to the static page, but 'lightened' or 'greyed out' to show it is not yet a part of the regular page.&lt;br /&gt;
* Also, maybe the default should be 'nested' for viewing replies (what slashdot users are used to seeing, i believe)&lt;br /&gt;
** On the other hand I always hated that default and thought it should be flat. Maybe vote on this one.&lt;br /&gt;
&lt;br /&gt;
== Broken Links not Found in FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; About&lt;br /&gt;
** OSTG (www.ostg.com) does not exist&lt;br /&gt;
** CmdrTaco (http://cmdrtaco.net) leads to a database error&lt;br /&gt;
** Krow (http://tangent.org/~brian) leads to 404&lt;br /&gt;
** Note: Suspect most of this page is outdated.&lt;br /&gt;
&lt;br /&gt;
* Remove ALPHA_SERVER/help page (Is used by a number of &amp;quot;Return to Help and Preferences links&amp;quot;; Common Joe is still trying to hunt these links down)&lt;br /&gt;
&lt;br /&gt;
* Is this the exact same or different page?&lt;br /&gt;
** Navigation --&amp;gt; Journals ==&amp;gt; Messages : ALPHA_SERVER/my/inbox/&lt;br /&gt;
** Navigation --&amp;gt; Messages : ALPHA_SERVER/messages.pl&lt;br /&gt;
** Note: This matters because of the “Return to Help and Preferences” link that needs to be removed.&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Messages&lt;br /&gt;
** ==&amp;gt; Message Preferences ==&amp;gt; Return to Help and Preferences: Link needs to be removed&lt;br /&gt;
&lt;br /&gt;
* Navigation --&amp;gt; Authors : ALPHA_SERVER/authors.pl&lt;br /&gt;
** The link NCommander and the link mattie_p simply refers back to ALPHA_SERVER/authors.pl&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4591</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4591"/>
		<updated>2014-02-14T06:58:45Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Bugs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* You can create, edit, and preview journal entries, but they are not saved.&lt;br /&gt;
** really? I could make one - mattie_p&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4586</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4586"/>
		<updated>2014-02-14T01:15:31Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Suggestions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* You can create, edit, and preview journal entries, but they are not saved.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;br /&gt;
&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
** but if your article happens to begin with a quote it winds up like&lt;br /&gt;
*** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
** which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
*** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
*** So quoted text would look like this&lt;br /&gt;
*** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
**Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4585</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4585"/>
		<updated>2014-02-14T01:14:17Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Suggestions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
* You can create, edit, and preview journal entries, but they are not saved.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
* but if your article happens to begin with a quote it winds up like&lt;br /&gt;
** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
* which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
** So quoted text would look like this&lt;br /&gt;
** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;br /&gt;
&lt;br /&gt;
* Can we get the ability for logged in users to edit their own posts (as themselves, not AC)?&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4580</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4580"/>
		<updated>2014-02-13T23:31:37Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Suggestions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
* but if your article happens to begin with a quote it winds up like&lt;br /&gt;
** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
* which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
** So quoted text would look like this&lt;br /&gt;
** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;br /&gt;
*Editors will have to check for quotes and make sure they make sense.  I'll keep my eyes open for them - mattie_p&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4579</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4579"/>
		<updated>2014-02-13T23:29:51Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Bugs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
* Karma score of -1 means you cannot post as yourself, meaning you essentially remain at -1 forever.&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;br /&gt;
* Just submitted an article to make sure that function worked ok with no javascript - it does. However, I noticed that the articles are always surrounded automatically with quotes &lt;br /&gt;
** AudioGuy writes &amp;quot;blah blah blah&amp;quot; &lt;br /&gt;
* but if your article happens to begin with a quote it winds up like&lt;br /&gt;
** AudioGuy Writes &amp;quot;&amp;quot;blah blah blah&amp;quot;&amp;quot;&lt;br /&gt;
* which looks kind of odd. Maybe the outer quotes could be left off and something like italicizing the initial text used instead:&lt;br /&gt;
** ''AudioGuy writes:'' blah blah blah&lt;br /&gt;
** So quoted text would look like this&lt;br /&gt;
** ''AudioGuy writes:'' &amp;quot;blah blah blah&amp;quot;&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4573</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4573"/>
		<updated>2014-02-13T21:30:14Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
* FAQ links don't work when directed to slashcode. Internal links work fine.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4571</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4571"/>
		<updated>2014-02-13T21:06:50Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Suggestions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;br /&gt;
* Would like to be able to click on the title, as well as 'Read more...', to go from the main list to an individual story page.&lt;br /&gt;
* &amp;quot;Dupe detector&amp;quot; at submission time. Use submitted title to search previous stories for dupes and get user to confirm that what they're submitting really is novel. (partial solution here, in that if you base the submission off a URL, that must be unique - mattie_p)&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4555</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4555"/>
		<updated>2014-02-13T16:18:58Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4554</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4554"/>
		<updated>2014-02-13T16:18:50Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs for now.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.soy&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4553</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4553"/>
		<updated>2014-02-13T16:17:22Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here.  Do not hyperlink to the pages, please provide that information separately to the devs at this time.&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.soy&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4543</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4543"/>
		<updated>2014-02-13T15:40:57Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
* Categories (section and topics) for new submissions need expanding. - (current suggested list is here: http://www.soylentnews.org/Forum/viewtopic.php?f=10&amp;amp;t=33&amp;amp;start=20#p486 - mattie_p)&lt;br /&gt;
* Is there a way for users to make posts on submitted stories, or is that an editor-only thing.soy&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4539</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4539"/>
		<updated>2014-02-13T15:18:26Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions==&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4538</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4538"/>
		<updated>2014-02-13T15:18:13Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
Bugs affect the operability of the site.&lt;br /&gt;
&lt;br /&gt;
* Some (most?) saved changes to settings on the &amp;quot;You&amp;quot; pages are not reflected following pressing &amp;quot;save&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Issues==&lt;br /&gt;
Issues don't affect the operability, but are inconvenient or undesirable&lt;br /&gt;
* Firehose &lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Suggestions&lt;br /&gt;
* Having the comments section work in a slightly less retro way would be awesome. Specifically: a) clicking on a comment URL shouldn't make the rest of the thread vanish. b) have the site automatically return you to the view you came from following posting of a comment.&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4525</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4525"/>
		<updated>2014-02-13T14:34:23Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;br /&gt;
&lt;br /&gt;
* Firehose&lt;br /&gt;
* Many 404 errors on Help and Preferences page&lt;br /&gt;
* Email links and registration email are all NCommander's personal address&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4500</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4500"/>
		<updated>2014-02-13T07:51:02Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;br /&gt;
&lt;br /&gt;
* Firehose&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4498</id>
		<title>Alpha Bugs</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Alpha_Bugs&amp;diff=4498"/>
		<updated>2014-02-13T07:40:45Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: Created page with &amp;quot;Post bugs and issues here:&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Post bugs and issues here:&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4463</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4463"/>
		<updated>2014-02-12T17:34:16Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC, this is a summary of who is involved in SoylentNews. Please add yourself or others if you can field questions about the topic.&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
* Barrabas&lt;br /&gt;
==Code==&lt;br /&gt;
* NCommander&lt;br /&gt;
* robinld&lt;br /&gt;
&lt;br /&gt;
==Style==&lt;br /&gt;
Water&lt;br /&gt;
&lt;br /&gt;
==Content==&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* Dopefish&lt;br /&gt;
* Cactus&lt;br /&gt;
* mattie_p&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* applesmasher&lt;br /&gt;
* Dopefish&lt;br /&gt;
&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* mattie_p - I'm just an active user and in the Editor Group.  I'm nobody official on the forums, though.&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* Cactus&lt;br /&gt;
* FunPika&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4361</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4361"/>
		<updated>2014-02-12T07:16:28Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Forums */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC, this is a summary of who is involved in SoylentNews. Please add yourself or others if you can field questions about the topic.&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
* Barrabas&lt;br /&gt;
==Code==&lt;br /&gt;
* robinld&lt;br /&gt;
==Style==&lt;br /&gt;
==Content==&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* Dopefish&lt;br /&gt;
* Cactus&lt;br /&gt;
* mattie_p&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* applesmasher&lt;br /&gt;
* Dopefish&lt;br /&gt;
&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* mattie_p - I'm just an active user and in the Editor Group.  I'm nobody official on the forums, though.&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* Cactus&lt;br /&gt;
* FunPika&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4353</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4353"/>
		<updated>2014-02-12T04:17:56Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Forums */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC, this is a summary of who is involved in SoylentNews. Please add yourself or others if you can field questions about the topic.&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
* Barrabas&lt;br /&gt;
==Code==&lt;br /&gt;
* robinld&lt;br /&gt;
==Style==&lt;br /&gt;
==Content==&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* Dopefish&lt;br /&gt;
* Cactus&lt;br /&gt;
* mattie_p&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* applesmasher&lt;br /&gt;
* Dopefish&lt;br /&gt;
&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* mattie_p - wait, I'm in charge now? I'm just in the editorial group. I didn't put this here, but I am on the IRC if you want to bug me, usually.&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* Cactus&lt;br /&gt;
* FunPika&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4350</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4350"/>
		<updated>2014-02-12T02:23:42Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Forums */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC, this is a summary of who is involved in SoylentNews. Please add yourself or others if you can field questions about the topic.&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
* Barrabas&lt;br /&gt;
==Code==&lt;br /&gt;
* robinld&lt;br /&gt;
==Style==&lt;br /&gt;
==Content==&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* Dopefish&lt;br /&gt;
* Cactus&lt;br /&gt;
* mattie_p&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* apple_smasher&lt;br /&gt;
* Dopefish&lt;br /&gt;
&lt;br /&gt;
* mattie_p - wait, I'm in charge now? I'm just in the editorial group. I didn't put this here - mattie_p&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* Cactus&lt;br /&gt;
* FunPika&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4347</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=4347"/>
		<updated>2014-02-12T01:49:21Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* Forums */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC, this is a summary of who is involved in SoylentNews. Please add yourself or others if you can field questions about the topic.&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
* Barrabas&lt;br /&gt;
==Code==&lt;br /&gt;
* robinld&lt;br /&gt;
==Style==&lt;br /&gt;
==Content==&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* Dopefish&lt;br /&gt;
* Cactus&lt;br /&gt;
* mattie_p&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* mattie_p - wait, I'm in charge now? I'm just in the editorial group. I didn't put this here - mattie_p&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* Cactus&lt;br /&gt;
* FunPika&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4332</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4332"/>
		<updated>2014-02-11T20:01:56Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* List of Discussion Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]]&lt;br /&gt;
&lt;br /&gt;
'''Site Announcements'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' We need some CSS and sphinx help&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As part of the SlashCode rollout we need to fix a lot of broken CSS and to install [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]. We need 2+1 volunteers to help with the conversion this afternoon via IRC. Two to fix CSS issues, and one familiar with install and config of the sphinx software package.&lt;br /&gt;
&lt;br /&gt;
We need people who are fast, so I'll choose based on experience.&lt;br /&gt;
&lt;br /&gt;
If you're interested, please send ONLY a one liner of the number of years you've been doing CSS or sphinx. Something like this:&lt;br /&gt;
&lt;br /&gt;
''3 years doing CSS professionally''&lt;br /&gt;
&lt;br /&gt;
This will be on IRC, coordinating with robin and our tech lead.&lt;br /&gt;
&lt;br /&gt;
Thanks go to everyone - it looks like we're on the final stretch!&lt;br /&gt;
&lt;br /&gt;
If interested, send E-mail to: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott is getting attention'''&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.kuro5hin.org/story/2014/2/7/183544/0702&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
::* http://www.gamefaqs.com/boards/916373-pc/68540288&lt;br /&gt;
::* http://www.tuicool.com/articles/bmUvMj&lt;br /&gt;
::* http://www.reddit.com/r/socialmedia/comments/1x77zt/user_backlash_to_slashdotorg_beta/&lt;br /&gt;
::* http://www.fark.com/comments/8133044/Since-when-was-Slashdot-a-Fark-Beta-site-Since-Dice-started-redirecting-25-of-its-users-to-a-failed-site-redesign&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''Feb 10, 2014:''' We are still working on getting the &amp;amp;^#$*$%^ code to run.  If everything comes together, we hope to open the doors on Wednesday. Cross your fingers everyone!  When we are ready for &amp;quot;soft launch&amp;quot;, we'll invite a bunch of people to use the site and see how things hold up.&lt;br /&gt;
&lt;br /&gt;
There may be some teething problems in the first couple of days. We will bump the server to whatever level is needed, but it may take some hours of slow access before we decide to do that.  &lt;br /&gt;
&lt;br /&gt;
The Slashcode group has been working very hard to get things up and running. Consider that SlashCode is 5 years old - it's got sharp edges and rough spots. Please have patience.&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Get Involved '''&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Contact:'''&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org   &amp;lt;--- Does not appear to be working ??&lt;br /&gt;
&lt;br /&gt;
==Status==&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
* We upgraded the hosting by two tiers - this should fix the problems people were having yesterday accessing the system.&lt;br /&gt;
* The System team is working on installing SlashCode. If all goes well, we expect to have a working system by Monday. Everyone believes this goal is achievable.&lt;br /&gt;
* The site now has forums with four user groups: Code, Content, Style, and System.&lt;br /&gt;
* Probably won't be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately (like I did, but with more people).&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
* Trademark issues&lt;br /&gt;
&lt;br /&gt;
* We are getting some community flak on the name&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
==ToDo==&lt;br /&gt;
[[SlashcodeTodo|Slashcode Todo list]]&lt;br /&gt;
&lt;br /&gt;
* Install SlashCode on the production site&lt;br /&gt;
* Get some people to help with the site&lt;br /&gt;
* Run a contest for a better name [[NewName|New name discussion]]&lt;br /&gt;
* Incorporate&lt;br /&gt;
* Consult a lawyer&lt;br /&gt;
* How to handle Advertising (necessary evil) - Opt Out, Limited, Typical(box with ads in the top-right corner)?  &lt;br /&gt;
::Why can't we have an advertising cookie with things we are in the market for?  I.e. if I'm in the market for a computer, I see computer-related ads.  If I opt out, then I don't see any ads.  An interest-centric (not user centric) cookie.  &amp;lt;=='''+1 Insightful'''&lt;br /&gt;
* Improved Mod/Meta-Mod/Story-Selection system to minimize required editor input&lt;br /&gt;
* Provide a voting system to decide which articles hit the main page (Mod point related?) &lt;br /&gt;
* Find and submit some stories&lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
*[[NewName|NewName]]&lt;br /&gt;
*[[MailingListUpdates|MailingListUpdates]]&lt;br /&gt;
*[[Finances|Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business|Business]]&lt;br /&gt;
*[[Monetization]] -- Discussion on how to cover costs to make this thing happen (and grow)&lt;br /&gt;
*[[FeatureList]] -- Discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines|Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- How to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]] -- Points of contact in different project areas&lt;br /&gt;
&lt;br /&gt;
== Noteworthy Comments==&lt;br /&gt;
*Grabbed the Domain Names: AltSlashdot.org, Soylentnews.org&lt;br /&gt;
*Other potential website solutions &lt;br /&gt;
::Bruce Perens (created &amp;quot;technocrat.net&amp;quot;) is aware of Soylentnews.org and is considering contributing  (Relaunch ?? stay tuned)&lt;br /&gt;
::/. user 'dotancohen' registered the domain &amp;quot;slashdotan&amp;quot; and is looking to build a new Slashdot (He is willing to coordinate and has cloud experience)&lt;br /&gt;
::Add info on Pipedot...[http://pipedot.org/ pipedot.org] by 'Bryan'&lt;br /&gt;
::User somenickname (1270442) has registered bangslashdot.(org|net|com)&lt;br /&gt;
::Usenet was also suggested as an alternative  'comp.misc is the new Slashdot'&lt;br /&gt;
*Scrapping content from old Slashdot suggestion made. benefits/drawbacks ?   Overall I think this is a thumbs down&lt;br /&gt;
::Content is easier to &amp;quot;find&amp;quot; &lt;br /&gt;
::Moral/Legal objections were brought up  (Even if it was initially &amp;quot;our&amp;quot; content)&lt;br /&gt;
::We should build our own brand&lt;br /&gt;
::Pointless to scrap, since it is the comments that draw people in&lt;br /&gt;
::Editors should be in multiple timezones to cleanup/improve/multi-source submissions for presentation to the main page&lt;br /&gt;
*Initial code build will be from Slashcode... Available (Git?),  Old:(5 years)  Workable:(maybe)&lt;br /&gt;
*Alternate choices for code base: Wiki, Discourse, Usenet&lt;br /&gt;
*Non-profit vs For-profit discussion should go here ( [[Business]] )&lt;br /&gt;
:: Debian style project organization ?&lt;br /&gt;
:: Community driven projects need strong leadership or they tend to flounder&lt;br /&gt;
*Codebase&lt;br /&gt;
:: Code should be in the public domain&lt;br /&gt;
:: Allow the entire website (Stories+Comments+Code)? to be created as a Creative commons work - codebase also available ?&lt;br /&gt;
:: AGPL&lt;br /&gt;
*Keep the former Slashdot community together&lt;br /&gt;
&lt;br /&gt;
[[Comment History]]&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
&lt;br /&gt;
* Do this as a non-profit, user-run organization '''please'''. From what you write it looks like you want replace the regime, not giving the users the control over the website. Why should we trust you not to sell the website to a DICE-like company after it becomes successful? I applaud your efforts to change things, but I really believe that a [https://en.wikipedia.org/wiki/Debian#Organization Debian Project] like institution that is both non-commercial and controlled/run by the community has a much higher chance of securing the goals we fight for right now in the long-term. --[[Special:Contributions/141.84.69.20|141.84.69.20]] 03:20, 6 February 2014 (MST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Relevant Slashdot stats from 2011 [[http://www.dbasoul.com/2011/992.html]]&lt;br /&gt;
:::5.5 million user visits per month.&lt;br /&gt;
:::7,000 comments are added every day.&lt;br /&gt;
:::Over 9 million pages views daily.&lt;br /&gt;
:::Over 21 million comments.&lt;br /&gt;
:::Average monthly bandwidth usage is around 40-50 mbit/sec (450GB/day)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* From Hacker News on Slashdot: 'When you have the same group of minds selecting the content that gets seen, over the course of years, the users eventually get burnt out seeing the same type of stuff, chosen by the same people over and over again. The content becomes stale even if its fresh &amp;lt;--- A really good point&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
AltSlashdot Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Stories from former Slashdot users ==&lt;br /&gt;
&lt;br /&gt;
[[Confessions of an Ex-Slashdot Beta User]]&lt;br /&gt;
&lt;br /&gt;
[[Banned from Slashdot]]&lt;br /&gt;
&lt;br /&gt;
[[Dice is killing Slashdot]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== An interesting Idea ==&lt;br /&gt;
Check this out while it's still available.  feedback appreciated&lt;br /&gt;
* http://slashdot.org/submission/3324011/a-modest-proposal-re-beta-vs-classic?utm_source=rss1.0&amp;amp;utm_medium=feed&amp;amp;sbsrc=firehose&lt;br /&gt;
&lt;br /&gt;
== Telling the world about SoylentNews.org == &lt;br /&gt;
*Please mention SoylentNews.org as much as possible. &lt;br /&gt;
*It seems like the word is spreading (over 45,000 views in &amp;lt;1 week) Good job everyone! &lt;br /&gt;
**Any idea on how and where to make sure people know about this project, please post them here?&lt;br /&gt;
:::I'd send a note along to Ars Technica &amp;amp; BoingBoing. (That would get some attention)&amp;lt;br&amp;gt;&lt;br /&gt;
:::Anyone have a Reddit account with a reasonable activity level?&amp;lt;br&amp;gt;&lt;br /&gt;
:::The Register, Digg, Hacker News and anything else you feel would help get the word out there&lt;br /&gt;
* Contacted:&lt;br /&gt;
** The Register:: No word back&lt;br /&gt;
** Ars Technica:: Was passed along to one of the writers&lt;br /&gt;
** Hacker News&lt;br /&gt;
::: [https://news.ycombinator.com/item?id=7193251 Submission from when AltSlashdot just started]&lt;br /&gt;
::: Due for an update once we get an actual site up and running&lt;br /&gt;
:::: [https://news.ycombinator.com/item?id=7209927 Similar thread from today] [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 10:05, 10 February 2014 (MST)&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4331</id>
		<title>SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=SoylentNews&amp;diff=4331"/>
		<updated>2014-02-11T20:01:20Z</updated>

		<summary type="html">&lt;p&gt;Mattie p: /* List of Discussion Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[FAQ|Frequently Asked Questions]]&lt;br /&gt;
&lt;br /&gt;
'''Site Announcements'''&lt;br /&gt;
&lt;br /&gt;
'''Feb 11, 2014 12:01PM EST:''' We need some CSS and sphinx help&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As part of the SlashCode rollout we need to fix a lot of broken CSS and to install [http://en.wikipedia.org/wiki/Sphinx_(search_engine)  sphinx (search engine)]. We need 2+1 volunteers to help with the conversion this afternoon via IRC. Two to fix CSS issues, and one familiar with install and config of the sphinx software package.&lt;br /&gt;
&lt;br /&gt;
We need people who are fast, so I'll choose based on experience.&lt;br /&gt;
&lt;br /&gt;
If you're interested, please send ONLY a one liner of the number of years you've been doing CSS or sphinx. Something like this:&lt;br /&gt;
&lt;br /&gt;
''3 years doing CSS professionally''&lt;br /&gt;
&lt;br /&gt;
This will be on IRC, coordinating with robin and our tech lead.&lt;br /&gt;
&lt;br /&gt;
Thanks go to everyone - it looks like we're on the final stretch!&lt;br /&gt;
&lt;br /&gt;
If interested, send E-mail to: John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''The Slashcott is getting attention'''&lt;br /&gt;
:A selection of Slashcott/Beta comments from around the web.......&lt;br /&gt;
&lt;br /&gt;
::* https://community.republicwireless.com/thread/23151          &amp;lt;== &amp;quot;How not to treat your community&amp;quot;&lt;br /&gt;
::* http://www.kuro5hin.org/story/2014/2/7/183544/0702&lt;br /&gt;
::* http://community.spiceworks.com/topic/442346-trouble-at-slashdot&lt;br /&gt;
::* http://www.gamefaqs.com/boards/916373-pc/68540288&lt;br /&gt;
::* http://www.tuicool.com/articles/bmUvMj&lt;br /&gt;
::* http://www.reddit.com/r/socialmedia/comments/1x77zt/user_backlash_to_slashdotorg_beta/&lt;br /&gt;
::* http://www.fark.com/comments/8133044/Since-when-was-Slashdot-a-Fark-Beta-site-Since-Dice-started-redirecting-25-of-its-users-to-a-failed-site-redesign&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
'''Feb 10, 2014:''' We are still working on getting the &amp;amp;^#$*$%^ code to run.  If everything comes together, we hope to open the doors on Wednesday. Cross your fingers everyone!  When we are ready for &amp;quot;soft launch&amp;quot;, we'll invite a bunch of people to use the site and see how things hold up.&lt;br /&gt;
&lt;br /&gt;
There may be some teething problems in the first couple of days. We will bump the server to whatever level is needed, but it may take some hours of slow access before we decide to do that.  &lt;br /&gt;
&lt;br /&gt;
The Slashcode group has been working very hard to get things up and running. Consider that SlashCode is 5 years old - it's got sharp edges and rough spots. Please have patience.&lt;br /&gt;
&lt;br /&gt;
Check out the [http://imgbin.org/index.php?page=image&amp;amp;id=16688| look and feel] of the new site!&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''To everyone involved... THANK YOU!'''&lt;br /&gt;
&lt;br /&gt;
We are building a news site alternative to Slashdot. We have started only a few days ago, and this wiki is a temporary measure so that volunteers can coordinate and others can see what's happening.&lt;br /&gt;
&lt;br /&gt;
The idea is to build a news aggregation site that delivers what's important - better articles, less fluff, and all the functionality you expect from the moderation system. We are still looking for volunteers so stop by the boards and the IRC and let us know you want to help!&lt;br /&gt;
&lt;br /&gt;
* The proposed business model is [[Finances|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* Some business planning is [[Business|here]] &amp;lt;br&amp;gt;&lt;br /&gt;
* A statement of functionality (turn into a requirements document?)--- [[FeatureList]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Get Involved '''&lt;br /&gt;
&lt;br /&gt;
'''Hop in to IRC!''' - [[SoylentNews:IRC|IRC]]: ##altslashdot on chat.freenode.net ([https://webchat.freenode.net/?channels=##altslashdot Webchat], we are growing in [http://irc.netsplit.de/channels/details.php?net=freenode&amp;amp;room=%23%23altslashdot strength!])&lt;br /&gt;
&lt;br /&gt;
'''Register on the forums''' - http://forums.SoylentNews.org&lt;br /&gt;
* Go to forums.SoylentNews.org and register a user&lt;br /&gt;
* Read [http://forums.soylentnews.org/viewtopic.php?f=10&amp;amp;t=38&amp;amp;sid=e55255cb6dfe68b28c8cf5f2b9697a64| this] post if you are having problems. (Thanks MrGuy)&lt;br /&gt;
* Add yourself to whichever groups you are interested in&lt;br /&gt;
* For tech issues with the forum software, please Email Joel: soylent (at) finite (dot) ms&lt;br /&gt;
&lt;br /&gt;
'''Slashcott''' Organized boycott of the Dice-owned Slashdot pages&lt;br /&gt;
* Show your support for the &amp;quot;Get rid of Beta&amp;quot; crowd by avoiding Slashdot during the week of February 10-17&lt;br /&gt;
&lt;br /&gt;
'''Tell Somebody''' A friend, a colleague, any major news source....&lt;br /&gt;
*Do what you can to get the word out&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Contact:'''&lt;br /&gt;
If you want to send the project lead a message:  John (at) SoylentNews (dot) org&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Mumble (Voice / Text Server)''' : voice.whackperiod.org   &amp;lt;--- Does not appear to be working ??&lt;br /&gt;
&lt;br /&gt;
==Status==&lt;br /&gt;
&lt;br /&gt;
Check out the [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
* Forums are available at forums.SoylentNews.org&lt;br /&gt;
* We upgraded the hosting by two tiers - this should fix the problems people were having yesterday accessing the system.&lt;br /&gt;
* The System team is working on installing SlashCode. If all goes well, we expect to have a working system by Monday. Everyone believes this goal is achievable.&lt;br /&gt;
* The site now has forums with four user groups: Code, Content, Style, and System.&lt;br /&gt;
* Probably won't be non-profit, see [[Finances|business model]].&lt;br /&gt;
* We won't poach from Slashdot. This includes articles and logos, also &amp;quot;style&amp;quot; to a reasonable extent.&lt;br /&gt;
&lt;br /&gt;
Mailing list update Messages are [[MailingListUpdates|here]]&lt;br /&gt;
&lt;br /&gt;
== Site Name ==&lt;br /&gt;
We have a '''temporary''' name!&lt;br /&gt;
&lt;br /&gt;
Thanks go out to everyone who made suggestions - some of them were&lt;br /&gt;
absolutely brilliant! For example, it hadn't occurred to me to choose a name based on a&lt;br /&gt;
non-English word, or a palindrome, or a puzzle. Many of the entries were quite clever.&lt;br /&gt;
(Adies, it took me more than a day to figure yours out. Bravo!)&lt;br /&gt;
&lt;br /&gt;
I won't post the runners up because squatters might take the names before we hold the real&lt;br /&gt;
contest. We'll figure out a way to prevent this somehow - at worst case we can choose judges&lt;br /&gt;
and do it privately (like I did, but with more people).&lt;br /&gt;
&lt;br /&gt;
Jerry had the winning entry.&lt;br /&gt;
&lt;br /&gt;
The temp name is: '''SoylentNews''' with the tagline: '''SoylentNews is people!'''&lt;br /&gt;
&lt;br /&gt;
Does this rock? It hits the trifecta of website goodness:&lt;br /&gt;
&lt;br /&gt;
* Descriptive in a way that mundanes will understand (compare &amp;quot;Photoshop&amp;quot; with &amp;quot;GIMP&amp;quot;, &amp;quot;Internet Explorer&amp;quot; with &amp;quot;Firefox&amp;quot;, and &amp;quot;MediaPlayer&amp;quot; with &amp;quot;VLC&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* It's part of Nerd culture, a pun, and slightly twisted&lt;br /&gt;
&lt;br /&gt;
* It's suggestive of being community driven&lt;br /&gt;
&lt;br /&gt;
* It is attached to some movie about eating corpses and implies &amp;quot;News fresh as processed corpses&amp;quot; (??)&lt;br /&gt;
&lt;br /&gt;
* Trademark issues&lt;br /&gt;
&lt;br /&gt;
* We are getting some community flak on the name&lt;br /&gt;
&lt;br /&gt;
This will be a hard act to beat. Start thinking up names for the contest, or throw your weight&lt;br /&gt;
behind this one. The contest will be held soon after we open the doors.&lt;br /&gt;
&lt;br /&gt;
(And it was poutine (from IRC) who suggested we use a temporary name. Others may also have suggested it, but it was his post that I noticed. Be sure to thank him if you see him on IRC.)&lt;br /&gt;
&lt;br /&gt;
==ToDo==&lt;br /&gt;
[[SlashcodeTodo|Slashcode Todo list]]&lt;br /&gt;
&lt;br /&gt;
* Install SlashCode on the production site&lt;br /&gt;
* Get some people to help with the site&lt;br /&gt;
* Run a contest for a better name [[NewName|New name discussion]]&lt;br /&gt;
* Incorporate&lt;br /&gt;
* Consult a lawyer&lt;br /&gt;
* How to handle Advertising (necessary evil) - Opt Out, Limited, Typical(box with ads in the top-right corner)?  &lt;br /&gt;
::Why can't we have an advertising cookie with things we are in the market for?  I.e. if I'm in the market for a computer, I see computer-related ads.  If I opt out, then I don't see any ads.  An interest-centric (not user centric) cookie.  &amp;lt;=='''+1 Insightful'''&lt;br /&gt;
* Improved Mod/Meta-Mod/Story-Selection system to minimize required editor input&lt;br /&gt;
* Provide a voting system to decide which articles hit the main page (Mod point related?) &lt;br /&gt;
* Find and submit some stories&lt;br /&gt;
&lt;br /&gt;
== List of Discussion Pages ==&lt;br /&gt;
*[[NewName|NewName]]&lt;br /&gt;
*[[MailingListUpdates|MailingListUpdates]]&lt;br /&gt;
*[[Finances|Finances]] -- which model would allow to minimise and/or distribute hosting costs&lt;br /&gt;
*[[Business|Business]]&lt;br /&gt;
*[[Monetization]] -- Discussion on how to cover costs to make this thing happen (and grow)&lt;br /&gt;
*[[FeatureList]] -- Discussion of required/desired characteristics&lt;br /&gt;
*[[Submission guidelines|Submission guidelines]]&lt;br /&gt;
*[[Content]]&lt;br /&gt;
*[[Style]]&lt;br /&gt;
*[[Migration of users from Slashdot]] -- How to handle Nicks and UIDs&lt;br /&gt;
*[[Licensing]]&lt;br /&gt;
*[[WhosWho]]&lt;br /&gt;
&lt;br /&gt;
== Noteworthy Comments==&lt;br /&gt;
*Grabbed the Domain Names: AltSlashdot.org, Soylentnews.org&lt;br /&gt;
*Other potential website solutions &lt;br /&gt;
::Bruce Perens (created &amp;quot;technocrat.net&amp;quot;) is aware of Soylentnews.org and is considering contributing  (Relaunch ?? stay tuned)&lt;br /&gt;
::/. user 'dotancohen' registered the domain &amp;quot;slashdotan&amp;quot; and is looking to build a new Slashdot (He is willing to coordinate and has cloud experience)&lt;br /&gt;
::Add info on Pipedot...[http://pipedot.org/ pipedot.org] by 'Bryan'&lt;br /&gt;
::User somenickname (1270442) has registered bangslashdot.(org|net|com)&lt;br /&gt;
::Usenet was also suggested as an alternative  'comp.misc is the new Slashdot'&lt;br /&gt;
*Scrapping content from old Slashdot suggestion made. benefits/drawbacks ?   Overall I think this is a thumbs down&lt;br /&gt;
::Content is easier to &amp;quot;find&amp;quot; &lt;br /&gt;
::Moral/Legal objections were brought up  (Even if it was initially &amp;quot;our&amp;quot; content)&lt;br /&gt;
::We should build our own brand&lt;br /&gt;
::Pointless to scrap, since it is the comments that draw people in&lt;br /&gt;
::Editors should be in multiple timezones to cleanup/improve/multi-source submissions for presentation to the main page&lt;br /&gt;
*Initial code build will be from Slashcode... Available (Git?),  Old:(5 years)  Workable:(maybe)&lt;br /&gt;
*Alternate choices for code base: Wiki, Discourse, Usenet&lt;br /&gt;
*Non-profit vs For-profit discussion should go here ( [[Business]] )&lt;br /&gt;
:: Debian style project organization ?&lt;br /&gt;
:: Community driven projects need strong leadership or they tend to flounder&lt;br /&gt;
*Codebase&lt;br /&gt;
:: Code should be in the public domain&lt;br /&gt;
:: Allow the entire website (Stories+Comments+Code)? to be created as a Creative commons work - codebase also available ?&lt;br /&gt;
:: AGPL&lt;br /&gt;
*Keep the former Slashdot community together&lt;br /&gt;
&lt;br /&gt;
[[Comment History]]&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
&lt;br /&gt;
* Do this as a non-profit, user-run organization '''please'''. From what you write it looks like you want replace the regime, not giving the users the control over the website. Why should we trust you not to sell the website to a DICE-like company after it becomes successful? I applaud your efforts to change things, but I really believe that a [https://en.wikipedia.org/wiki/Debian#Organization Debian Project] like institution that is both non-commercial and controlled/run by the community has a much higher chance of securing the goals we fight for right now in the long-term. --[[Special:Contributions/141.84.69.20|141.84.69.20]] 03:20, 6 February 2014 (MST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Relevant Slashdot stats from 2011 [[http://www.dbasoul.com/2011/992.html]]&lt;br /&gt;
:::5.5 million user visits per month.&lt;br /&gt;
:::7,000 comments are added every day.&lt;br /&gt;
:::Over 9 million pages views daily.&lt;br /&gt;
:::Over 21 million comments.&lt;br /&gt;
:::Average monthly bandwidth usage is around 40-50 mbit/sec (450GB/day)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* From Hacker News on Slashdot: 'When you have the same group of minds selecting the content that gets seen, over the course of years, the users eventually get burnt out seeing the same type of stuff, chosen by the same people over and over again. The content becomes stale even if its fresh &amp;lt;--- A really good point&lt;br /&gt;
&lt;br /&gt;
== IRC ==&lt;br /&gt;
General Slashdot Discussion: Come on IRC channel #slashdot at irc.slashnet.org. Or use the web client: http://www.slashnet.org/webclient&lt;br /&gt;
&lt;br /&gt;
AltSlashdot Discussion: Head to IRC channel ##AltSlashdot on irc.freenode.net, Web client is here: https://webchat.freenode.net/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Stories from former Slashdot users ==&lt;br /&gt;
&lt;br /&gt;
[[Confessions of an Ex-Slashdot Beta User]]&lt;br /&gt;
&lt;br /&gt;
[[Banned from Slashdot]]&lt;br /&gt;
&lt;br /&gt;
[[Dice is killing Slashdot]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== An interesting Idea ==&lt;br /&gt;
Check this out while it's still available.  feedback appreciated&lt;br /&gt;
* http://slashdot.org/submission/3324011/a-modest-proposal-re-beta-vs-classic?utm_source=rss1.0&amp;amp;utm_medium=feed&amp;amp;sbsrc=firehose&lt;br /&gt;
&lt;br /&gt;
== Telling the world about SoylentNews.org == &lt;br /&gt;
*Please mention SoylentNews.org as much as possible. &lt;br /&gt;
*It seems like the word is spreading (over 45,000 views in &amp;lt;1 week) Good job everyone! &lt;br /&gt;
**Any idea on how and where to make sure people know about this project, please post them here?&lt;br /&gt;
:::I'd send a note along to Ars Technica &amp;amp; BoingBoing. (That would get some attention)&amp;lt;br&amp;gt;&lt;br /&gt;
:::Anyone have a Reddit account with a reasonable activity level?&amp;lt;br&amp;gt;&lt;br /&gt;
:::The Register, Digg, Hacker News and anything else you feel would help get the word out there&lt;br /&gt;
* Contacted:&lt;br /&gt;
** The Register:: No word back&lt;br /&gt;
** Ars Technica:: Was passed along to one of the writers&lt;br /&gt;
** Hacker News&lt;br /&gt;
::: [https://news.ycombinator.com/item?id=7193251 Submission from when AltSlashdot just started]&lt;br /&gt;
::: Due for an update once we get an actual site up and running&lt;br /&gt;
:::: [https://news.ycombinator.com/item?id=7209927 Similar thread from today] [[User:Yahwotqa|Yahwotqa]] ([[User talk:Yahwotqa|talk]]) 10:05, 10 February 2014 (MST)&lt;/div&gt;</summary>
		<author><name>Mattie p</name></author>
	</entry>
</feed>