After several early attempts, we have settled on a process for deciding on the final name for this site currently known as SoylentNews.org. You'll need to log in and go to: userprefs/homepage and check the box marked "Willing to Vote" if you'd like to participate (do this now, the submission round will go out soon). The vote will occur using an email-based solution loosely based on the Debian/Condercet method that we cooked up. Note: checking this box will indicate that we are scraping your email address from the database for participation (this is completely opt-in). If you wish not to participate, just make sure this box is unchecked (this is the default).
We are opening the floor to name suggestions. If you have suggested a name earlier, you'll need to re-submit it through this email voting system. Though we prefer available domains, if you have pre-purchased a domain (eg: to prevent squatters), by submitting the name you are stating that you are the owner of the domain(s) and will give it without strings attached to this project if it were to be chosen.
The criteria for an acceptable name:
This is how it will work:
If you're interested:
NCommander adds: So its finally here, and I wanted to apologize for the long delay before this actually happened. To the editoral team, please bump this to the top of the index for the next 24 hours so everyone gets a chance to see it (click 'fastforward' then save to autoupdate the timestamp). I promise a Featured Story option is coming in the next major update so we don't have to deal with this!
Of course the first issue is that if your email bounces, you will never see the voting stuff at all - so make sure that address is actually valid.
Use plain text email only. And make sure any line wrapping is set to 70 characters or above - or off.
There are several thousands email programs and variants out there, -your refrigerator can probably send email-.
There is no practical way to write a program to decode all variants of html and other email in a week or two. Even large companies have trouble will all the variations and bugs.
So we have fallen back to the basic mode that is simple to parse and was the original format of email.
What is a plain text email?
Here is, in raw form, what a real plain text email looks like:
-X-X-X-X-X-X-X-X-X-X-X-X-X-X-Return-Path: X-Original-To: firstname.lastname@example.orgDelivered-To: email@example.comReceived: by boron.soylentnews.org (Postfix, from userid 1001)
id 2CEBD27A69; Mon, 31 Mar 2014 06:50:23 +0000 (UTC)To: firstname.lastname@example.orgFrom: "Soylent Staff Vote" Subject: [Soylent Staff Vote](FirstStaffP) Submissions for vote requestedMessage-Id: Date: Mon, 31 Mar 2014 06:50:23 +0000 (UTC)
The actual poll question is:
What KIND of name should we use for the new Soylentnews name? (notlooking at names, but simply types of names)
What this is really about, however, is testing this new system. ...-X-X-X-X-X-X-X-X-X-X-X-X-X-X-
Just 7 bit ascii characters, line wrapped at about 70 characters.
What is NOT a plain text email?
Any kind of html, mime, special encoding, etc.
Here is an example of an email that is NOT plain text (despite it claimimg to be):
-X-X-X-X-X-X-X-X-X-X-X-X-X-X-Message-ID: Content-Type: multipart/alternative;
boundary="_025bb878-695c-4212-bf15-ef78a3f8630e_"From: Sixpack To: Soylent Staff Vote Subject: RE: [Soylent Staff Vote](FirstStaffP) Submissions for vote requestedDate: Mon, 31 Mar 2014 19:31:33 +1100Importance: NormalIn-Reply-To: References: MIME-Version: 1.0X-OriginalArrivalTime: 31 Mar 2014 08:31:33.0719 (UTC) FILETIME=[9F985670:01CF4CBB]
--_025bb878-695c-4212-bf15-ef78a3f8630e_Content-Type: text/plain; charset="iso-8859-1"Content-Transfer-Encoding: quoted-printable
> To: email@example.com> From: firstname.lastname@example.org> Subject: [Soylent Staff Vote](FirstStaffP) Submissions for vote requested> Date: Mon=2C 31 Mar 2014 06:50:23 +0000>=20> The actual poll question is:>=20> What KIND of name should we use for the new Soylentnews=20> name? (not looking at names=2C but simply types of names)>=20> What this is really about=2C however=2C is testing this new=20> system. Specifically I want to make sure that:>=20 ...
--_025bb878-695c-4212-bf15-ef78a3f8630e_Content-Type: text/html; charset="iso-8859-1"Content-Transfer-Encoding: quoted-printable
>=3B To: email@example.com>=3B From: firstname.lastname@example.org=>=3B Subject: [Soylent Staff Vote](FirstStaffP) Submissions for vote requ=ested>=3B Date: Mon=2C 31 Mar 2014 06:50:23 +0000>=3B >==3B The actual poll question is:>=3B >=3B What KIND of name sho= ...-X-X-X-X-X-X-X-X-X-X-X-X-X-X-
That is mime encoded, further 'quoted-printable' encoded, and the second part contains html. That is NOT what we need to see.
You can email yourself and look at your own mail as a check, most email readers have some sort of 'raw' mode so you can see what is really there.
What if you have no way to send plain text?
We anticipated a few people might be in this situation. So we have made a good faith effort to TRY to decode this stuff, if possible.
If your mail is in -standard- mime format with a plain text and an html section, we may be able to decode it. No guarantees, but we have done some tests, at least.
On the other hand if you are using an old version of Outlook that ONLY sends non-standard 'x-html' mail with no plain text section and too long lines, it will most likely NOT be decoded. The same is true for all the really ghastly progams such as 'IncrediMail'
Sorry, but that is the best we can do for the moment.
Will there at least be a warning if your reply was impossible to decode?
Anything not decoded properly will be kicked out and hand checked.
If a -human- can't decode it, no promises. :-)