http://skyrates.zosimple.net/lurker/
Jusque lurker Auto-scrolling, more features, not managed by me.

Lurkers science responses are disabled for the moment. He got too fixated on too few science ideas.

Info

• tracks messages, average characters per message, moo, science, and reply count
• lurker status Gives a status count of what lurker is currently keeping an account of.
  Should reset at midnight.
• lurker status me Gives a status count of what lurker is keeping track of for you

Commands

• Commands are prefaced by lurkers name, as in 'lurker help'
• Commands have some alternate words to respond to, I'll list the basic ones
• lurker announce Will list the last announcement lurker has seen, and the date and time
• lurker help Will send you here
• lurker links Will provide a list of link options (the short names)
• lurker seen NAME Help chat only! Will tell you when lurker last saw NAME talk -- depends on how long lurker has data for and a few names don't work yet
• lurker war Will give a mini primer on war resources

Links

• Commands are prefaced by the word 'link', as in 'link docs'
• lurker General web view page
• help Help web view page
• rp Roleplay web view page
• charts Rhaikh's skycharts
• crs Crew recovery services New
• dailies Dailies from skyrates.zo.com New
• docs compendium
• dp Dramatis Personae spreadsheet
• dyna Dynarank
• inf Kathryn's "Tuggers" inf tool New
• map zo.com map page [SR2.6! thanks @ Sohum]
• market Skybuy Disabled
• missions Google doc spreadsheet on missions
• mod Hotmod
• path Pathfinder
• skycust Skycust information page
• status zo.com skyrates status page
• war Mini primer on the forums Outdated

Information

• name "zolurker"
• Lurker does take a liking to some people and will occasionally respond to specific people.
• lurker likes 'moo'
• lurker is trying to learn about science and sometimes shares this. He needs more science however.
• Sits in General, Help, Roleplay chat (One page per channel)
• Records to html file tables
• Parses emotes, adds timestamps
• Will announce when it comes online in Help channel
• Will attempt to announce departure in Help channel if it can
  
• Will be cycling at 00:00 us/pacific -- One page per day
• Limited robustness -- should be able to log back in
• Archive directory structure (look for the archive link)

{{Special Thanks}}
Lurker II would not have existed without tSotW!

{{TODO}}
* Need to figure out a way to implement fiesta

Yay! Thank you!

Fantastic nehp. Good work!

Excellent. Thank you very much.
The only thing I would recommend (and this is purely cosmetic) is that you move the more recent posts to the top. At the moment, it just seems pointless to scroll down to the bottom to see the latest post. It's not massively irritating, just something that was in Lurker I and would be nice to have again.

That said, I'm just glad that we have a lurker at all.

The daily pages will stay chronological, although when I add sort, you can easy just reverse the order.
For those who want a 'just the recent bits' style of viewing, I'll be adding a special page for that which serves to keep from scrolling yet keep it chronological.

Huzzah! A triumph of triumphs!

Will be changing cycling to 03:00am us/pacific. it's what we use for dailies/etc, so I'll just keep it consistent. I can confirm it's the deadest time of the day cycle anyhow!

Due to an unfortunate incident involving science, lurker was knocked around earlier today and was not recording information. I have taken some time with lurker to help him understand the difficult concepts he was working, and to provide him some personal shielding against alleged blue death ray attacks, just in case. He is back online and should be happy.

Due to skyrates going offline during the reset while I was in the middle of some major lurker updates, I will not be able to have lurker waiting to log back in and so lurker will be offline until I get back on later today.

zolurker should be back online. Due to the simplicity of the changes but the large number of them, it's possible that lurker may be erratic, drop me a line here if he's misbehaving!

Can you add a "quote" button that adds BBCode to the chatlogs so they can be easily copied and pasted into forum posts? (We're still waiting for someone to pretty-up Remy's debriefing.)

This will not be happening anytime soon, I have not yet setup my lurker to use dynamic/db logs, so it's all static until I put time into rebuilding that area completely, and I'm currently under a very heavy contract load. You should be able to get bbcode from http://skyrates.jusque.net/lurker though.

For remy's chat, I went ahead and put it through prettychat to post.

Now "lurker carriers" will give a link to the carriers' status page.

Also,

Modified to capture the new OOC properly.

nehp, thanks for changing Lurker to accommodate the new OOC. I noticed it broke your Lurker and Kathryn's too. I'm kind of academically curious why it broke, since it was a server-side change.

Do you want to change your colors to match the new Orange and Brown? I can give you the hex triplets if you need them.

My guess is that they were routinely sanitizing the chat contents so that someone couldn't post a mess of javascript in chat and thereby inject malicious code into the lurker page. The new color was basically an unhandled exception to those sanitizing rules.

[short summary: nested tags are a New Thing (tm) from skyrates formatting]

When you provide system-formatting, you sanitize the content, and then add your own HTML tags. For OOC, you used <i></i>. However, the sanitization done by skyrates was not complete (the chat breaky "<..." bugs have shown this off as well from time to time), so I had to add extra sanitization in. Due to the skyrates formatting depending upon some of this, like OOC, I had to add an extra step to grab the outer tags -- if they existed -- in raw form. When the great titles-grant-color-text occurred, I added an extension to this that grabbed the font color tags and passed them through, so as to provide a duplicate of any colors y'all offered. However, they were either/or. <i> or <font...

My current modification will need more work to be more robust, as it stands, I look for the i/b/etc, then I check for the <font>. This would be broken if, say, you put the <i> inside the <font>. After this (highly profitable) year of {static} work hours combined with (now complete) massive household clearing are over, zolurker gets a cleanup (separating logger from responder as processes) and I've noted for myself to make the tag parsing recursive and robust. This should hopefully survive further improvements naturally, hehe.

-- For sanitization, it's been quite a while since I built that part, in response to various users doing the 'test ways to break things.' Due to this, I dont' remember what was not being sanitized off the top of my head. If you'd like, I can drop y'all a message if I uncover what I was responding to when I get back into lurker (likely early 2011 at this point.) I think you may have finally fixed it after the last chat breakage, but that came after I'd put sanitization into place (which is complicated enough as it has to avoid sanitizing pre-sanitized bits! hehe.)

And yeah, drop me the updated hex or names and I can update the css =)

New faction colors:

FS: #ffcc00
RED: #ff0000
GREEN: #00cc00
BLUE: #2079ff
DEVS: #999999
ORANGE: #ff8c00
BROWN: #a0522d
PURPLE: #a45bfd

Well, I guess I just thought I'd put this here, since I thought about it.

Often times, people use the 'seen X' command to figure if somebody is online. Generally speaking, anything longer than half an hour is assumed to mean X is offline. In some cases, X may be a player that the speaker is waiting for, and the speaker might decide to simply log off, if X is not around (assuming there is nothing else to do).
However, if X is simply AFK for a short time, it is possible that they missed the speaker by moments, even. Since not every person would read the lurker to look for posts from X (even though I would), I thought of this suggestion:

PLAYER: 'lurker report X' -- When 'seen PLAYER' is called, reply with 'SPEAKER: TIME_LAST_SPOKEN (X)'.
So that if someone's looking another person, they will know what they are doing if they are not currently around.
And to turn it off, 'lurker report' would be used. X would be nil (or "", depending on how lurker handles this), and would simply have handling to reply with 'SPEAKER: TIME_LAST_SPOKEN' as usual.



This sound helpful/applicable/otherwise?