<?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=Mcgrew</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=Mcgrew"/>
	<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/wiki/Special:Contributions/Mcgrew"/>
	<updated>2026-04-17T23:17:04Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.4</generator>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Historic:Migration_of_users_from_Slashdot&amp;diff=3378</id>
		<title>Historic:Migration of users from Slashdot</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Historic:Migration_of_users_from_Slashdot&amp;diff=3378"/>
		<updated>2014-02-08T15:41:11Z</updated>

		<summary type="html">&lt;p&gt;Mcgrew: /* Preserving nicks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The problem ==&lt;br /&gt;
Slashdot users are a community, where users are known by nicks. Starting with a new set of nicks would disrupt the years--long network of acquaintances, etc.&lt;br /&gt;
&lt;br /&gt;
== Preserving nicks ==&lt;br /&gt;
A simple system could be build, which would allow for safe and authorised migration of nicks of willing users.&lt;br /&gt;
&lt;br /&gt;
If anyone would want to register on Altslashdot with a nick that already exists on Slashdot, the user would be presented with a generated key. The user would then need to post any comment on Slashdot, that would contain that key. The migrating user would then present a link to that comment in the registration form..&lt;br /&gt;
&lt;br /&gt;
Then, we would know, that a user with a nick we know from Slashdot is really that user, and not a copycat.&lt;br /&gt;
&lt;br /&gt;
All nicks used on Slashdot would be reserved to be taken by their respective user to the new site,&lt;br /&gt;
* either for a certain period of time (one year, for example);&lt;br /&gt;
* or without any limit, for late-comers, to avoid trolling, and to encourage nick-innovation among new users.&lt;br /&gt;
&lt;br /&gt;
To avoid polluting the public forums, the user might attach the key to a regular comment, or post it in Journal instead&lt;br /&gt;
&lt;br /&gt;
'''Note:''' this must be new, as I registered here using my slashdot name with no code. My slash UID is 5 characters, alt UID 3.&lt;br /&gt;
&lt;br /&gt;
== Preserving UIDs ==&lt;br /&gt;
As above with Preserving Nicks, UIDs are a valued commodity.  When AltSlashDot goes online, it should determine what the last registered UID on Slashdot is at that moment.  That is the Cutoff UID.&lt;br /&gt;
* Anyone who registers will get an initial AltSlashDot UID, which should start at 1.&lt;br /&gt;
* They also get a Slashdot UID, which is initially null and won't be displayed&lt;br /&gt;
* Once someone confirms their account, their Slashdot UID should also carry over&lt;br /&gt;
* When posting, both UIDs should be displayed with ??? UI-- like halcyon1234(834388 /.) [2 alt/.]-- obviously in a UI that doesn't suck. =)&lt;br /&gt;
&lt;br /&gt;
'''Suggestion''': 2 UIDs seems overly complex. Why not use the original Slashdot UID for those who verify them, and otherwise hand out new UIDs starting with (Cutoff UID +1)?&lt;br /&gt;
&lt;br /&gt;
== UID Requirements ==&lt;br /&gt;
It seems a lot of people tend to lean towards 3 characters instead of 5 as from my understanding new slashdot requires 5 characters? Don't know if this is true but I think it would make people happy to have 3 character minimum.&lt;br /&gt;
&lt;br /&gt;
== Password Requirements ==&lt;br /&gt;
Uppercase / alpha-numerical combinations as a requirement should die in a fire. What do you guys think?&lt;br /&gt;
&lt;br /&gt;
== Copyright of content ==&lt;br /&gt;
Let's remember that the content on /. is likely protected by copyright, which also means its database of users and their posts. However, it doesn't seem like any search engine is getting into hot water for indexing users so I think we will be okay if a spider is built for reserving names.&lt;/div&gt;</summary>
		<author><name>Mcgrew</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Talk:Submission_guidelines&amp;diff=3290</id>
		<title>Talk:Submission guidelines</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Talk:Submission_guidelines&amp;diff=3290"/>
		<updated>2014-02-08T15:08:22Z</updated>

		<summary type="html">&lt;p&gt;Mcgrew: Linux&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rather than &amp;quot;Linux&amp;quot; wouldn't &amp;quot;Operating syetems&amp;quot; be better? Leaving room for BSD, Windows, Apple OSes, smartphone OSes, hell even old mainframe OSes.&lt;br /&gt;
&lt;br /&gt;
Perhaps have subtopics?&lt;/div&gt;</summary>
		<author><name>Mcgrew</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Talk:SoylentNews&amp;diff=1216</id>
		<title>Talk:SoylentNews</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Talk:SoylentNews&amp;diff=1216"/>
		<updated>2014-02-07T15:47:56Z</updated>

		<summary type="html">&lt;p&gt;Mcgrew: Journals&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;quot;You have followed a link to a page that does not exist yet. To create the page, start typing in the box below&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Okay, let's see if that works.&lt;br /&gt;
&lt;br /&gt;
And help kill beta by joining the Slashcott&lt;br /&gt;
&lt;br /&gt;
February 10th -17th&lt;br /&gt;
&lt;br /&gt;
unitron&lt;br /&gt;
&lt;br /&gt;
Slashdot UID 5733&lt;br /&gt;
&lt;br /&gt;
== Teething pains? ==&lt;br /&gt;
&lt;br /&gt;
This message was created automatically by mail delivery software.&lt;br /&gt;
&lt;br /&gt;
A message that you sent could not be delivered to one or more of its&lt;br /&gt;
recipients. This is a permanent error. The following address(es) failed:&lt;br /&gt;
&lt;br /&gt;
John@AltSlashdot.org&lt;br /&gt;
SMTP error from remote mail server after RCPT TO:&amp;lt;John@AltSlashdot.org&amp;gt;:&lt;br /&gt;
host mail.altslashdot.org [66.147.244.192]: 550 No Such User Here&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
Is this an &amp;quot;only if Slashdot doesn't back down on beta&amp;quot; contingency, or =&lt;br /&gt;
&amp;quot;going to happen no matter what Slashdot does&amp;quot;?&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
== Hot Grits ==&lt;br /&gt;
&lt;br /&gt;
I have poured them down my pants. Thank you. [[Special:Contributions/86.50.93.164|86.50.93.164]] 10:16, 6 February 2014 (MST) Iskender (1040286)&lt;br /&gt;
&lt;br /&gt;
*Why are they down your pants?  They should be on Natalie Portman - naked and petrified..&lt;br /&gt;
&lt;br /&gt;
== Group or Business ==&lt;br /&gt;
&lt;br /&gt;
Okian Warrior seems to want to be CmdrTaco all over again. While I am a very, very pro-business sort of person, I don't think we want to just push reset and do Slashdot over again as another build it up and cash out endeavor. It seems like that's exactly what would happen, and on the backs of volunteers no less. The only way I could see supporting this endeavor as a business would be with some sort of codified protection like a charter, whereby certain attributes of the way the site functions would be guaranteed, and those guarantees could only be changed if (the charter could only be modified if) the users were polled and agreed to it. In this way the business could operate but be ultimately accountable to and restrained by the userbase. This seems like a good hybrid solution. ~ElectricTurtle&lt;br /&gt;
&lt;br /&gt;
You could solve this by managing it similar to the debian project.&lt;br /&gt;
&lt;br /&gt;
==Stories==&lt;br /&gt;
*Could there be [[Open Hardware FPGAs]]? http://www.electronicsweekly.com/mannerisms/fpga/will-expiring-patents-boost-fp-2007-03/&lt;br /&gt;
&lt;br /&gt;
== Barrapunto ==&lt;br /&gt;
&lt;br /&gt;
People here should be familiar with the Spanish language version of Slashdot,&lt;br /&gt;
Barrapunto.com.  It looks like it was forked from older Slashcode, and it does&lt;br /&gt;
not appear to be a dice holding.  This is the most durable SlashClone with which&lt;br /&gt;
I'm familiar.  I seem to recall reading about it more than 5 years ago.  If nothing&lt;br /&gt;
else, we could learn a lot from them about running a successful SlashClone.&lt;br /&gt;
&lt;br /&gt;
We should make a list of any currently running clones.&lt;br /&gt;
*http://slashcode.com/www.slashcode.com/&lt;br /&gt;
&lt;br /&gt;
Thanks for posting the link.  That looks a lot more like /. Classic.  Now we certainly&lt;br /&gt;
don't want to knock over the server that discusses SlashCode, so we shouldn't be&lt;br /&gt;
posting there... but they seem like an ideal candidate for a bunch to form a non-profit&lt;br /&gt;
org.  IMHO, that's the answer.  We need to form a non-profit dedicated to serving the&lt;br /&gt;
users.  Worst case scenario we replace ads with something like the annual Wikipedia&lt;br /&gt;
begging; but it might be worth it.&lt;br /&gt;
&lt;br /&gt;
The Wikipedia begging beats having advertizes dictating the content of your site or selling the users info for $$$ Wikipedia I believe does it right. [[User:Script Cat|Script Cat]] ([[User talk:Script Cat|talk]]) 14:28, 6 February 2014 (MST)&lt;br /&gt;
&lt;br /&gt;
== Alternate domain ideas? ==&lt;br /&gt;
&lt;br /&gt;
It's come up elsewhere online that a name including slashdot might get this project into hot water with DICE&lt;br /&gt;
&lt;br /&gt;
== Hosting and collaboration ==&lt;br /&gt;
make it foss with gpl2&amp;lt;br&amp;gt;&lt;br /&gt;
is there any reason why the site can't be directly hosted by https://github.com/&amp;lt;br&amp;gt;&lt;br /&gt;
ultra-nerdy, with plenty of linuxy flavor&amp;lt;br&amp;gt;&lt;br /&gt;
no need to worry about dedicated infrastructure, and domain doesn't matter that much if it's something like &amp;quot;github.com/altslash&amp;quot; nerds are gunna find and remember it&lt;br /&gt;
&lt;br /&gt;
== Journals ==&lt;br /&gt;
I hope journals are included and hope people use them.&lt;/div&gt;</summary>
		<author><name>Mcgrew</name></author>
	</entry>
</feed>