<?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=Guanxi</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=Guanxi"/>
	<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/wiki/Special:Contributions/Guanxi"/>
	<updated>2026-04-18T01:16:22Z</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=1880</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=1880"/>
		<updated>2014-02-07T22:58:35Z</updated>

		<summary type="html">&lt;p&gt;Guanxi: /* Preserving UIDs */&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;
'''suggestion''': Maybe post it in their Journal instead of polluting the public forums? Just make sure it's a Journal post and not at reply when validating.&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;
== 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;/div&gt;</summary>
		<author><name>Guanxi</name></author>
	</entry>
</feed>