User talk:ArsenicLupin

From otp22 db
Revision as of 21:26, March 27, 2013 by ArsenicLupin (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

If you want a Wiki page fixed, drop me a note.

Kauai drop markup

It was there all along. The Dead_drop page wasn't updated though. Sometimes when you change transclusions or Semantic MediaWiki information you have to Purge/Refresh the page (link on top bar; eg: ) -- Crash demons (talk) 02:28, February 1, 2013 (UTC)

Note: this is completely distinct from a browser refresh. -- Crash demons (talk) 02:30, February 1, 2013 (UTC)
Gotcha. BTW, the Help link in the left navbar is content-free. Would it usually contain info about the Wiki itself, about Wiki formatting, or what? -- ArsenicLupin (talk) 02:36, February 1, 2013 (UTC)

Notes from Investigation cleanup

To-do list

  • Pri 1: Reoganize message desk
  • Clean up Theories/Hunches/&c
  • Create order page (mine News)
  • Todo



  • Should Investigation_Journal be replaced by the Investigations category? YES.
  • Query: Should open tag go on investigation pages, on the superpages for investigations, or both? OPEN TAG GOES ON INVESTIGATION ONLY.


  • How can I embed a search for =situation_code=Lambda= into Agent_Systems/Investigation/Situation_Lambda ?
{{#ask: [[Category:OTP22_message]] [[MSG situation code::Lambda]] 
| ?MSG agent code
| ?MSG phone number
-- Crash demons (talk) 02:31, February 2, 2013 (UTC)
you should note that the Situation Lambda page appears to be yet another page about the 3233 code, but considering how short it is, it doesn't have to remain that way -- Crash demons (talk)



why don't we do Investigation pages, the main pages are bound to be out of date at some point or not contain the specifics of the problem... unless like... the entire page is dedicated to the problem. -- Crash demons (talk) 21:15, February 3, 2013 (UTC) Works for me. Stepping away from the keyboard now. Really. -- ArsenicLupin (talk) 21:16, February 3, 2013 (UTC)


[18:48] <AluisioASG> Well, have to go. Tell WORM that SSUN-214 is ready for deploy.
[18:48] == AluisioASG [~Thunderbi@] has quit [Quit: black otp1 file start 194 121 138 177 offset 39715]
[18:50] <mwally> the dialer will be offline during the migration to a VPS
[18:50] <ArsenicLupin> Did anybody make anything of Aluisio's last message?
[18:50] <ArsenicLupin> Like, did a puppet-master just wash through?
[18:51] <XkeeperLaptop> beats me, maybe a joke.
[18:53] <crash_demons> I've heard a lot of different theories:  22 (Decoder's age)   22 (some other fine detail about the messages we got... forgot what it was)
[18:53] <crash_demons> re: "OTP22"
[18:54] <ArsenicLupin> I have been wondering for some time if his standard signature (the otp1 file) bears decoding.
[18:54] <nadando> what?
[18:55] <crash_demons> do you want me to decode it for you?
[18:55] <XkeeperLaptop> go ahead :p
[18:55] <ArsenicLupin> Please.
[18:55] <crash_demons> elpaso("194 121 138 177 offset 39715")
[18:55] <AutoBit> PUBLIC_elpaso("194 121 138 177 offset 39715") == (String) "RDLK."
[18:57] <XkeeperLaptop> RDLK?
[18:57] <crash_demons> don't ask me
[18:58] <ArsenicLupin> Hmmm.
[18:58] <ArsenicLupin> I think I'll save that and his WORM note in my sandbox, just in case.
[18:58] <filer> Red Lake?

OTP22 tools

Document how to disentangle abism

(and recognize!)

[19:03] <ArsenicLupin> Run it through a spectogram?
[19:04] <nadando> just look at the bits
[19:04] <crash_demons> ArsenicLupin, audio editing software with visual output?  Audacity eg
[19:04] <Xkeeper4400_> to decode just open specogram from favorite program
[19:04] <Xkeeper4400_> there are 7 "bits"
[19:04] <ArsenicLupin> I do not do these sounds of which you speak.  I am strictly a typing-type person.
[19:04] <Xkeeper4400_> if there is a tone at a frequency, 1, otherwise 0
[19:05] <ArsenicLupin> aha!
[19:05] <ArsenicLupin> and then translate to DEC 6-bit?
[19:05] <Xkeeper4400_> next section starts when it starts reaches the bottom. sort of
[19:05] <Xkeeper4400_> run it through
[19:05] <nadando> no
[19:05] <crash_demons> it used to, but not this set afaik
[19:05] <nadando> they invented their own encoding or something
[19:05] <Xkeeper4400_> I forget the settings but just reverse should work
[19:05] <crash_demons> I guess dec-sixbit was the primer course
[19:05] <crash_demons> lol
ow again :p
[19:22] <ArsenicLupin> I am staring at a spectrogram.  Do I count bits left-to-right or top-to-bottom?
[19:22] <ArsenicLupin> (row-major or column-major?)
[19:22] <Xkeeper4400_> the bits go ike this
[19:22] <Xkeeper4400_> 1234567 1234567 1234567 1234567
[19:22] <Xkeeper4400_> or as you will usually seee
[19:22] <Xkeeper4400_> 367 567 13567  12567 etc
[19:23] <ArsenicLupin> Can you unpack that a bit?
[19:24] == juj [1b641309@gateway/web/freenode/ip.] has joined #ARG
[19:24] <Xkeeper4400_>
[19:25] <Xkeeper4400_> basically (if present, in this order) 900, 800, 700, 660, 600, 500, 400, <next byte>.
[19:25] <ArsenicLupin> okay, so I think reading that from left to right, the first six bits are 000100
[19:26] <ArsenicLupin> OHHHH
[19:26] <ArsenicLupin> right
[19:26] <ArsenicLupin> sorry, I was doing it entirely wrong.
[19:27] <ArsenicLupin> so in fact the first one was 000100 (but for the wrong reason)
[19:28] <Xkeeper4400_> there should be 7 bits
[19:28] <Xkeeper4400_>
[19:28] <Xkeeper4400_> e.g., in this image
[19:28] <Xkeeper4400_> the first two sequences are 0000111 0101011
[19:29] <ArsenicLupin> OH!  One bit per vertical line, not two.  It's not like reading a hollerith card.
[19:30] <nadando> the hard part is distinguishing the 3rd and 4th bits

Using censor tag

 *Emergency Agent: {{Censor|Hidden Text}}

Collapsible text

This text is collapsible. blah blah blah blah oher blah blah blah blah blah blah blah blah

Flatlist query links

Thought you might be interested in this PoC:

{{flatlist|{{#ask: [[Category:Dead_drops]] [[Drop Status::+]] | format=ul }}}}

- I suspect it only works because style values are inherited. Before we implement this in infoboxes though, we need better categorization/tagging for Drop pages; I'm open to suggestions (I had good ideas about a month ago but I forgot :( ... )-- Crash demons (talk) 03:18, March 13, 2013 (UTC)

Note: it may be more portable also to output flatlist entries from a query using a template output-formatter per each entry, but I'm not sure it will even work -- Crash demons (talk) 03:20, March 13, 2013 (UTC)
"Good ideas that I forget" are the story of my life. HOORAY for the PoC. I agree that drops are getting cumbersome. My best effort is "Disc drops", "Component drops", "Book drops", "Open drops", and "Other drops" just in case. Your thoughts? That way if you're looking for information we already got, you can go along natural lines -- "Where did we get the green book?" and if you just want to see what's open, there's a link to that. ArsenicLupin (talk) 19:26, March 14, 2013 (UTC)

Mystery and News subobject ID's

Mystery and News entries are grouped by their subobject name, which is generated from the Date/Time parameters. Tonight we had an issue where Mystery entries overlapped and Solved ones showed as both Solved/Unsolved. The issue was that multiple entries were set to the same Day but no time was given (0:00 default), so they had the same ID. I solved the issue by manually setting each entry a minute apart if in the same day (Day 1: 0:00, 0:01; Day 2: 0:00; Day 3: 0:00, 0:01, 0:02) which gave them unique IDs. Thought you should know -- Crash demons (talk) 22:16, March 26, 2013 (EDT)

Thanks for the note. I'll make sure to use unique timestamps going forward. ArsenicLupin (talk) 17:26, March 27, 2013 (EDT)