User:Lcarsos

Explain xkcd: It's 'cause you're dumb.
Revision as of 20:59, 27 August 2012 by Lcarsos (Talk | contribs)

Jump to: navigation, search

The username is lcarsos. pronounced el-cars-oh-ess. The only other acceptable capitalizations are LCARSOS or LCARS OS. The second of those is frowned upon because that should be used for any project attempting to create an LCARS operating system, or overlay/window manager. And lastly, never Lcarsos, despicable.

I'm just a big xkcd and Star Trek fan (props if you got the reference).

Here, I'm just working backwards from the beginning to create missing pages, fix existing pages, updating them to the current header, adding categories, fixing double redirects, etc. I also try to find as much work for the admins as possible (just kidding).

Contents

Personal Achievements

Some of the things I've managed to do here, I'm very proud of. And by golly, I'm going to display them out in public so everyone else can see how vain I am.

Named Characters

  • Ponytail - Brought back the name from a dimly remembered past.
  • Danish - stumbled across 377 and suggested it to Blaisepascal to be used as her official name
  • Miss Lenhart - doesn't really count, I just created all the pages for her. But I'm very proud that I managed to do it all correctly on my own.

Things I Need to Remember

I'm currently at 993: Brand Identity

Categories I forget
Cool pages

Ruby Importer script

Bugs, Questions, Comments, Heaping Adulation, Scathing Remarks

User Talk:Lcarsos#Ruby Importer Please post there.

I'm trying to keep everything organized so nothing gets lost in the shuffle (lost cause, I know, but I can do my small part to battle entropy).

Introduction

Work on my import-assistant script is progressing. I'm using it to help create pages as I work my way backwards. Currently it is just using information from xkcd's json api and leaving explanation open for you to get.

I'm working on getting the explanation to pull in. But, managing to guess the right url alone was a difficult task, and it still doesn't get it right for some of the more odd ones, but it would be faster to just find the page manually than code for each exception to the rule. I'm going to do a bit more work on that, but I might just give it up and keep manually copying explanations in. Or at least write out a best-guess of what the url should be to get you close, if you aren't walking backward through the blog entries.

I want to be able to pull in the explanation so I can scan through it to get a rough idea of what characters appear to automatically generate Comics featuring ___ categories. But that's a bit of work, including lots of regular expressions (regex!) but it's good practice for basic data mining and pattern recognition.

I've found that already I'm much more productive simply by not having to type in the comic template info. And the page feels much more finished when it has the transcript.

Now, I'm going to give you a link, but I am requiring you to manually go through and look at what it generates and keep yourself engaged. As I explain in the README, there are things the human brain can do innately that computers need lots of work to get the logic hooked up.

You must go through and make links to appropriate wikipedia and external web pages. I can make links to the links that exist in the html, but you have to be a human and realize that if something has a wikipedia page it probably needs to be linked to.

Please tell me on my User Talk: Lcarsos#Ruby Importer page if you are using it, what features you want, and bugs you find.

Link

https://github.com/lcarsos/explainxkcd-importer/

Usage

Generic:

./importer.rb <number> ...

Specific examples:

./importer.rb 1000
./importer.rb 1000 1001 1002 1003 1004
./importer.rb `seq 1 600` Don't actually do that

It accepts any number of comic numbers as arguments (space delimited, duh) and will iterate through all of them and spit out a text file <number>.txt with Unix line-endings (if you open it up on Windows use Notepad++ or some other real text editor).

If I see you using this tool to blindly create pages without going through and cleaning things up I will kill you.

Known Issues

  • Active Development Work
    • Explanations are not being culled from the blog page.
    • Script will be made 859 compliant as soon as I get home.
  • Noted As Feature
    • Some transcripts come from the json api with extra newlines. Will not be fixed to encourage humans to look everything through. Good for fingerprinting brain-dead copy/paste usage.

Formatting

It is high time someone created one of these.

Paragraphs

Traditional paragraphs need to have an extra return between them

Typing this Produces this
If this is a paragraph, and there is typing.
 
Then the next one is down here.

If this is a paragraph, and there is typing.

Then the next one is down here.

If this is a paragraph, and there is typing.
Don't put the next paragraph on the next line.

If this is a paragraph, and there is typing. Don't put the next paragraph on the next line.

The difference is that the wiki software will wrap the first example in paragraph tags, which means that it gets a margin between them. Where the behavior for the second seems a bit undefined. Sometimes you will end up with a line break, and sometimes it completely ignores it.

In only one instance can this be useful, and it is discussed in the Talk Pages section.

Editorial Voice

As you are going through, if you are using Jeff's explanations from the blog, please go through and edit the sentences to not include personal pronouns, e.g., "I". Since anyone can edit (nearly) every article here, there is no 'I'.

Next point, there is no 'we'. If you are referring to anyone who's edited the article, that could be anyone, there's hardly any consensus there. If you are referring to 'We' the editors of ExplainXKCD wiki, again, we don't agree on anything, don't believe it? Read the Community Portal pages.

For the purposes of this wiki, saying 'we' is referring to human beings in general, and it would have to be a very special case to mean any set/group of people smaller than that.

This is based off of the discussion that occurred in explain xkcd:Community portal/Proposals#Editorial Voice.

Talk Pages

Wikis have a well established tradition for how to use talk pages.

You begin your conversation, and someone else replies to you by commenting under the post and indenting by using the colon (":"). This mimics how threaded conversations work in blog comments.

All comments on talk pages should be signed by using ~~~~. It is easy to forget this, but it is equally easy to get into the habit.

There are 2 canonical ways to handle multi-paragraph comments.

  1. Single returns between paragraphs and signature on the last line.
  2. Double returns between paragraphs and signature on its own separate line.

This makes it easy to scan through to see who's comments are whom's.

Typing this Produces this
I think that there should be more lions.

Of course, then we need more wildebeests.

~~~~User1

:That is a good idea.

:And yes, then we would need more prey.

:~~~~User2

::I'm replying to User2.

::Because he's funny.

::~~~~User3

:I'm replying to User1, saying that we don't need lions.
Predators should be kept in cages ~~~~User4

:I'm replying to User1 also, telling him he's a genius.
~~~~User5

I think that there should be more lions.

Of course, then we need more wildebeests.

User1

That is a good idea.
And yes, then we would need more prey.
User2
I'm replying to User2.
Because he's funny.
User3
I'm replying to User1, saying that we don't need lions. Predators should be kept in cages User4
I'm replying to User1 also, telling him he's a genius. User5
I think that there should be more lions.
Of course, then we need more wildebeests. ~~~~User1

:That is a good idea.
:And yes, then we would need more prey. ~~~~User2

::I'm replying to User2.
::Because he's funny. ~~~~User3

:I'm replying to User1, saying that we don't need lions.
Predators should be kept in cages ~~~~User4

:I'm replying to User1 also, telling him he's a genius.
~~~~User5

I think that there should be more lions. Of course, then we need more wildebeests. User1

That is a good idea.
And yes, then we would need more prey. User2
I'm replying to User2.
Because he's funny. User3
I'm replying to User1, saying that we don't need lions. Predators should be kept in cages User4
I'm replying to User1 also, telling him he's a genius. User5

See how easy this is to read? And now we don't even have to start introducing bullet points into the discussion. Bullet lists can now be used for what they were intended: Making lists, even inside of a single post in a talk page.

But if you meet someone who doesn't know what they are doing everything breaks down quickly.

Typing this Produces this
I think that there should be more lions.
Of course, then we need more wildebeests. ~~~~User1

:That is a good idea.
:And yes, then we would need more prey. ~~~~User2

::I'm replying to User2.

::Because he's funny. ~~~~User3

:I'm replying to User1, saying that we don't need lions.
Predators should be kept in cages ~~~~User4

:I'm replying to User1 also, telling him he's a genius.
~~~~User5

I think that there should be more lions. Of course, then we need more wildebeests. User1

That is a good idea.
And yes, then we would need more prey. User2
I'm replying to User2.
Because he's funny. User3
I'm replying to User1, saying that we don't need lions. Predators should be kept in cages User4
I'm replying to User1 also, telling him he's a genius. User5

For those of you that are now confused, don't worry I had to look back to my perfect example to see where I was coming.

Do you see that User3 has now managed to make the conversation very hard to read? By ending the line with a username it looks like that user posted a reply to themselves, and then by using 2 returns, made it look his own comment was also a reply. In reality these two should be part of the same comment.

This is the only time in a wiki when paragraphs should not be double returned.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?