Historic:Migration of users from Slashdot - Revision history

Admin: Admin moved page Migration of users from Slashdot to Historic:Migration of users from Slashdot

2024-12-04T05:19:56Z

Admin moved page Migration of users from Slashdot to Historic:Migration of users from Slashdot

← Older revision	Revision as of 05:19, 4 December 2024
(No difference)

Sir Finkus: Protected "Migration of users from Slashdot" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2016-09-22T01:43:21Z

Protected "Migration of users from Slashdot" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 01:43, 22 September 2016
(No difference)

Sir Finkus at 01:43, 22 September 2016

2016-09-22T01:43:14Z

← Older revision		Revision as of 01:43, 22 September 2016
Line 1:		Line 1:
			{{archival}}
	'''Note: this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing these ideas at the start. These would be extremely difficult to tackle at this point, and would require re-assigning nicks, UIDs etc.'''		'''Note: this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing these ideas at the start. These would be extremely difficult to tackle at this point, and would require re-assigning nicks, UIDs etc.'''

ModernGeek at 00:01, 23 September 2014

2014-09-23T00:01:51Z

← Older revision		Revision as of 00:01, 23 September 2014
Line 48:		Line 48:
	* All posts are owned by the person who posted it. (Check the footer of Slashdot after the Slashcott). Wholesale spidering MAY violate some mysterious TOS or be interpreted as a DOS. '''However''', is there anything wrong with spidering the Wayback Machine?		* All posts are owned by the person who posted it. (Check the footer of Slashdot after the Slashcott). Wholesale spidering MAY violate some mysterious TOS or be interpreted as a DOS. '''However''', is there anything wrong with spidering the Wayback Machine?
	** Using the Wayback Machine may be a better option altogether. There's a chance that Dice gets all lawyery about all of this and scraping anything from their site gives them a case. At the very least, they could block access attempts and jam up the migration attempt.		** Using the Wayback Machine may be a better option altogether. There's a chance that Dice gets all lawyery about all of this and scraping anything from their site gives them a case. At the very least, they could block access attempts and jam up the migration attempt.

			I have to wonder, maybe slashdot wouldn't be against giving us a dump of the database with uids, usernames, and hashed so that we could facilitate the migration, and maybe it could be a two way street so that they could "link" the accounts in some way? Perhaps someone could make it their diplomatic mission to see if that would be possible.
			[[User:ModernGeek\|ModernGeek]] ([[User talk:ModernGeek\|talk]]) 00:01, 23 September 2014 (UTC)

Mrcoolbp at 15:48, 26 April 2014

2014-04-26T15:48:12Z

← Older revision		Revision as of 15:48, 26 April 2014
Line 1:		Line 1:
	'''Note:~~'''~~ this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing these ideas at the start. These would be difficult to tackle at this point, and would require re-assigning nicks, UIDs etc.		'''Note: this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing these ideas at the start. These would be extremely difficult to tackle at this point, and would require re-assigning nicks, UIDs etc.'''

	== The problem ==		== The problem ==

Mrcoolbp at 23:49, 7 March 2014

2014-03-07T23:49:46Z

← Older revision		Revision as of 23:49, 7 March 2014
Line 1:		Line 1:
	'''Note:''' this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing ~~this~~ at the start. ~~This~~ would ~~probably~~ be ~~very~~ difficult to tackle at this point.		'''Note:''' this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing these ideas at the start. These would be difficult to tackle at this point, and would require re-assigning nicks, UIDs etc.

	== The problem ==		== The problem ==

Mrcoolbp at 23:46, 7 March 2014

2014-03-07T23:46:41Z

← Older revision		Revision as of 23:46, 7 March 2014
Line 1:		Line 1:
	'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.~~'''~~		'''Note:''' this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.

	== The problem ==		== The problem ==

Mrcoolbp at 23:46, 7 March 2014

2014-03-07T23:46:20Z

← Older revision		Revision as of 23:46, 7 March 2014
Line 1:		Line 1:
	'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.'''		'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly ended up prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.'''

	== The problem ==		== The problem ==

Mrcoolbp at 19:35, 7 March 2014

2014-03-07T19:35:47Z

← Older revision		Revision as of 19:35, 7 March 2014
Line 1:		Line 1:
			'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.'''

	== The problem ==		== 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.		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.

	'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.'''

	== Preserving nicks ==		== Preserving nicks ==

Mrcoolbp: /* Preserving nicks */ Removed "Note: This must be new" and added a section at the top stating this was an original intention and not currently being worked on

2014-03-07T19:35:19Z

Preserving nicks: Removed "Note: This must be new" and added a section at the top stating this was an original intention and not currently being worked on

← Older revision		Revision as of 19:35, 7 March 2014
Line 1:		Line 1:
	== The problem ==		== 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.		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.

			'''Note this was on the "Wish List" before the site launched. Plans to launch the site quickly prevented us from implementing this at the start. This would probably be very difficult to tackle at this point.'''

	== Preserving nicks ==		== Preserving nicks ==
	A simple system could be ~~build~~, which would allow for safe and authorised migration of nicks of willing users.		A simple system could be built, 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 SoylentNews 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 16:

	To avoid polluting the public forums, the user might attach the key to a regular comment, or post it in Journal instead		To avoid polluting the public forums, the user might attach the key to a regular comment, or post it in Journal instead

	~~'''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.~~

	== Preserving UIDs ==		== Preserving UIDs ==