Migration of users from Slashdot: Difference between revisions
| Line 5: | Line 5: | ||
A simple system could be build, which would allow for safe and authorised migration of nicks of willing users. | A simple system could be build, which would allow for safe and authorised migration of nicks of willing users. | ||
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. | 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.. | ||
Then, we would know, that a user with a nick we know from Slashdot is really that user, and not a copycat. | Then, we would know, that a user with a nick we know from Slashdot is really that user, and not a copycat. | ||
| Line 14: | Line 12: | ||
* either for a certain period of time (one year, for example); | * either for a certain period of time (one year, for example); | ||
* or without any limit, for late-comers, to avoid trolling, and to encourage nick-innovation among new users. | * or without any limit, for late-comers, to avoid trolling, and to encourage nick-innovation among new users. | ||
To avoid polluting the public forums, the user might attach the key to a regular comment, or post it in Journal instead | |||
== Preserving UIDs == | == Preserving UIDs == | ||
Revision as of 06:39, 8 February 2014
The problem
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.
Preserving nicks
A simple system could be build, which would allow for safe and authorised migration of nicks of willing users.
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..
Then, we would know, that a user with a nick we know from Slashdot is really that user, and not a copycat.
All nicks used on Slashdot would be reserved to be taken by their respective user to the new site,
- either for a certain period of time (one year, for example);
- or without any limit, for late-comers, to avoid trolling, and to encourage nick-innovation among new users.
To avoid polluting the public forums, the user might attach the key to a regular comment, or post it in Journal instead
Preserving UIDs
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.
- Anyone who registers will get an initial AltSlashDot UID, which should start at 1.
- They also get a Slashdot UID, which is initially null and won't be displayed
- Once someone confirms their account, their Slashdot UID should also carry over
- When posting, both UIDs should be displayed with ??? UI-- like halcyon1234(834388 /.) [2 alt/.]-- obviously in a UI that doesn't suck. =)
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)?