<?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=Pino+p</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=Pino+p"/>
	<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/wiki/Special:Contributions/Pino_p"/>
	<updated>2026-10-25T05:15:53Z</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=4341</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=4341"/>
		<updated>2014-02-11T23:08:56Z</updated>

		<summary type="html">&lt;p&gt;Pino p: /* Password Requirements */ ObXKCD&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;
&#039;&#039;&#039;Note:&#039;&#039;&#039; 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&#039;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&#039;t suck. =)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Suggestion&#039;&#039;&#039;: 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;
OP of UID-- I think Cutoff UID +1 would work perfectly, I agree 2 UIDs would be complex.&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&#039;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;
* Necessary evil?  &lt;br /&gt;
* Min password length, sure. [http://explainxkcd.com/936/ Correct horse battery staple], of course.&lt;br /&gt;
* Password expiry, no.&lt;br /&gt;
* Also, there should be no limitation on what goes into a password field. It&#039;s all going to be salted and hashed anyways.&lt;br /&gt;
&lt;br /&gt;
== Copyright of content ==&lt;br /&gt;
Let&#039;s remember that the content on /. is likely protected by copyright, which also means its database of users and their posts. However, it doesn&#039;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;br /&gt;
&lt;br /&gt;
* 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. &#039;&#039;&#039;However&#039;&#039;&#039;, is there anything wrong with spidering the Wayback Machine?&lt;br /&gt;
** Using the Wayback Machine may be a better option altogether. There&#039;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.&lt;/div&gt;</summary>
		<author><name>Pino p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=User:Pino_p&amp;diff=223</id>
		<title>User:Pino p</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=User:Pino_p&amp;diff=223"/>
		<updated>2014-02-07T04:36:00Z</updated>

		<summary type="html">&lt;p&gt;Pino p: solidarity; statement of purpose&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;My name is Pino.&lt;br /&gt;
I came because [[wikipedia:USD|buck]] [[wikipedia:feta|feta]], but first, spuck fam.&lt;br /&gt;
I have run other wikis and have installed [[mediawikiwiki:Extension:QuestyCaptcha|effective]] [[mediawikiwiki:Extension:AbuseFilter|measures]] to keep their RC clean of offtopic vandalism.&lt;br /&gt;
If you want to learn how to keep wiki spammers out, ask me on my user talk page.&lt;/div&gt;</summary>
		<author><name>Pino p</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=User:Pino_p&amp;diff=213</id>
		<title>User:Pino p</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=User:Pino_p&amp;diff=213"/>
		<updated>2014-02-07T04:20:37Z</updated>

		<summary type="html">&lt;p&gt;Pino p: I want to help with your spam problem&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;My name is Pino.&lt;br /&gt;
I have run other wikis and have installed [[mediawikiwiki:Extension:QuestyCaptcha|effective]] [[mediawikiwiki:Extension:AbuseFilter|measures]] to keep their RC clean of spam.&lt;/div&gt;</summary>
		<author><name>Pino p</name></author>
	</entry>
</feed>