So just thinking out loud in case it helps anyone else. Looking at the 5th message’s html because it is the least “corrupted”
The spacer codes appear in blocks. In the first line, there are 8 spacers together, then a group of 16, then 8.
Out of the first group of 8, one of them is a unique spacer, the sixth of the 8. 6/8
First Line
6/ 8group
6,14,15,16/ 16group
6,8/ 8group
There are two unique spacers used throughout the code.  is shown as 6 and ‬ is 8
/////6//
/////6///////688
/////6/6
Looks like it is always ‌‌‌‌‌ followed by changes after before text shows, this repeats throughout.
1 Like
DevilinPixy:
‬ ;‬ ;
Yeah, noticed that above. Can’t really make out a pattern, though. Here’s the first paragraph without the groups of 5 zvenschies, assuming they’re a delimiter:
paragraph 1
line 1
‌&zwnj
‬‌
‬‬
‌‍
‍‌
‬‬
‍‌
line 2
‌‌
‌‬‬
line 3
‌‬
‌‍
‬‬
‌‍
line 4
‌‌
‬‬
‌‌
‌‌
‌‬‬
Edit: Now with proper formatting. Much more interesting than a blank page
1 Like
I was also looking into Prosigns, although not sure if something similar happens here, you get the idea.
Procedural signs or prosigns are shorthand signals used in Morse code radio telegraphy procedure, for the purpose of simplifying and standardizing radio communication protocol. They are separate from Morse code abbreviations, which consist mainly of brevity codes that convey messages to other parties with greater speed and accuracy.
In general prosigns are just standardised parts of short form radio protocol, and can include any abbreviation. An example would be K for "okay, heard you, continue"...
1 Like
Agreed. 8204 also appears in blocks. This is an Ascii-Decimal conversion of the first Emily post:
065 110 100 8204 8204 8204 8204 8204 65279 8204 8204 121 111 117 039 114 101 8204 8204 8204 8204 8204 65279 8204 8205 116 111 111 115 104 097 114 112 116 111 098 101 117 115 101 100
8204 8204 8204 8204 8204 8236 65279 8236 079 114 8204 8204 8204 8204 8204 65279 8204 8204 121 111 117 039 8204 8204 8204 8204 8204 65279 8205 65279 114 101 116 111 111 115 104 111 099 107 101 100 102 114 111 109 098 101 105 110 103 8204 8204 8204 8204 8204 8236 65279 8205 117 115 101 100
066 121 8204 8204 8204 8204 8204 65279 8204 8204 116 104 101 115 101 098 117 108 108 121 105 110 103 8204 8204 8204 8204 8204 65279 8205 8236 099 104 105 108 100 114 101 110 8204 8204 8204 8204 8204 8236 65279 8236 111 102 116 104 101 102 097 098 117 108 111 117 115
082 097 102 102 108 105 110 103 111 102 102 8204 8204 8204 8204 8204 65279 8204 8204 8204 8204 8204 8204 8204 65279 8205 65279 108 105 109 105 116 101 100 101 100 105 116 105 111 110 115 104 111 101 115
As you can easily see, there are whole blocks of code way outside the normal Ascii range.
2 Likes
Ahuh, loads of characters. Here is a Unicode list … it appears to go on forever, although has a handy search feature.
Unicode web service for character search. Find, copy and paste your favorite characters: 😎 Emoji, ❤ Hearts, 💲 Currencies, → Arrows, ★ Stars and many others 🚩
1 Like
Morse code could have three “symbols” if you think of three things that can happen,
silence, dot, and dash
Edit: anyone know why they would give us the doctor’s name along with the city?
1 Like
Emily has made six posts with hidden data.
Emily is suffering from the effects of one out of six possible Ware Labs.
We have the task of finding the rogue lab.
It seems reasonable to assume that both sixes are linked. The six posts, and their hidden data, contain clues to finding the rogue laboratory.
5 Likes
Emily, ETARC, Song
I wonder if any of this has to do with Radio waves?
2 Likes
Looks like there are sequences of 8 NPCs (funny how that abbreviates):
‌‌‌‌‌‌‌
‌‌‌‌‌‬‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‍‌
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‍
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‍‍
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌
‌‌‌‌‌‌‬
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‬‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‍‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‍
‌‌‌‌‌‍
‌‌‌‌‌‬‬
‌‌‌‌‌‍‌
‌‌‌‌‌‌‌
‌‌‌‌‌‬‌‌
‌‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌
‌‌‌‌‌‌
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‌
‌‌‌‌‌‌‍
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‍
‌‌‌‌‌‬‍
‌‌‌‌‌‌‌
‌‌‌‌‌‍‬
‌‌‌‌‌‬‬
‌‌‌‌‌‌‌
‌‌‌‌‌‍
3 Likes
So I was catching up and discord and they have timestamps. It looks like they turned each unique spacer into numbers 0-3. then base64 to ascii. Haven’t tried to replicate if that works but that’s how I read it. Dwarf on Discord provides,
01.07-06.0700:33:0000:48:00
07:15:20
15:17:40
15:32:00
20:25:00
23:40:00
07:45:40
20:40:00
23:55:00
08:14:40
21:10:00
Yea he used base4 not base64 but it’s just a detail… and the list is
01.07-06.07
00:33:00
00:48:00
07:15:20
15:17:40
15:32:00
20:25:00
23:40:00
07:45:40
20:40:00
23:55:00
08:14:40
21:10:00
Speculating that we need to predict the satellites position between July 1-July 6 on those times, UTC?
Most likely they will correspond to a position of one of the W/ARE labs. Do you remember in the new email,
We need to analyze her recent interactions to figure out if she was able to make predictions that could help to identify and isolate the source of the broadcast.
“The broadcast” being from one of the W/ARE labs…
4 Likes
I wonder whether there’s a pattern that corresponds to “message received and understood - all OK”, and a message that says “AAARGH - What are you doing to me???”
Even if we don’t know what the messages mean, we know that five of the labs are OK. It’s the lab that prompts a different message that’s the problem.
Can we track down one location that’s consistently getting different messages from the others?
1 Like
What is the name of the satellite we are tracking?
The satelites name is sj 16-02
2 Likes
SJ 16-02
NORAD Cat ID: 41634
1 Like
I’t probably just unicode characters placed by the word processor.
8204 == 0x200c == Zero width non-joiner. A zero width space where word or line breaks are permitted.
8205 == 0x200d == Zero width joiner.
65279 == 0xFEFF == Zero width non-breaking space. This use is deprecated, the FEFF code point is used as the BOM (byte order mark) .
Though, one thing I didn’t find is any spaces with width.
(edit) 8236 == 0x202c which might be the ‘pop directional formatting’ character but is more likely a bug in a conversion somewhere that grouped 8 bit characters into 16 bits. Separate them and you get 0x20 0x2c (space comma). 200c becomes space followed by form feed, 200d becomes space followed by carriage return. (FEFF shouldn’t be where it is though).
I think we have a lot of cut and paste between different systems causing a lot of searches in the unicode character tables.
Problem is no website seem to be able to predict satellite positions for more than 30 days ahead… and we’d need until July 6…
1 Like
I think we need to track backwards. I don’t think we need to know where it’s going - we need to know where it’s been, and when.
Emily sent out six posts. Presumably, they corresponded with six satellite positions. One of those positions is over the bad laboratory.