How to decompress payload of the Fullstory traffic for debugging?

Hi @lindsay, do you have time to follow up this thread? I basically want to know if it is possible that we can integrate fullstory to our data capture test/dev workflow. The current payload is compressed binary that begins with `FSF`

@lindsay, thank you so much for your comment! We current have the debugging workflow build upon the packet capture of the phone traffic with the server. We are inspecting the traffic data with Charles to automate the test with various environments and external services. We choose such way of testing because we use a lot of SaaS and we are Internet sensitive. The traffic would provide us a more standardized way of understanding the performance than any other build-in framework. 

However, when we try to integrate the Fullstory to our test workflow, we are not able to decode the package content of the Fullstory traffic. For query messages to `/rec/bundles`, we are getting messages like the following (decoded in HEX). We learnt from the introductory materials in the knowledge base that the traffic is compressed for better performance, but the actual algorithm for compression is not mention. We would like to know how can we understand/decode the traffic message. 

```

00000000  46 53 46 00 01 ed 7d 0f 5c 15 c5 da f0 1e 40 44   FSF   } \     @D
00000010  44 e5 1c d1 14 51 4f 5c 35 24 35 40 fe 89 24 bb   D    QO\5$5@  $ 
00000020  07 50 40 44 44 50 23 53 40 40 40 04 3a e2 3f 54    P@DDP#S@@@ : ?T
00000030  24 b3 32 35 35 32 35 ae 15 99 b7 8c cc cc eb eb   $ 25525         
00000040  35 b3 2e 9a 99 51 99 99 9a 71 b5 c8 ac bc 66 5e   5 .  Q   q    f^
00000050  33 2b 23 93 ef 79 66 66 d9 d9 b3 bb c7 d3 7d df   3+#  yff      } 
00000060  f7 f7 fb 7e f7 fb ac e1 cc ee 33 f3 cc 33 cf bf      ~      3  3  
00000070  79 66 76 76 76 88 20 08 41 42 92 e0 25 f8 08 be   yfvvv   AB  %   
00000080  82 9f d0 41 e8 25 04 08 56 61 00 b9 3f 44 f0 84      A %  Va  ?D  
00000090  df 10 21 5c 88 15 3a c2 35 fc 33 b9 99 56 c0 4f     !\  : 5 3  V O
000000a0  29 a4 74 48 e1 78 0b 52 23 a4 75 16 41 a8 10 a1   ) tH x R# u A   
000000b0  bc 29 2e bf 92 95 59 e8 f3 c2 3b 8f 40 81 96 ce    ).   Y   ; @  

```

Hey @LearnToFly  - stepping in for Lindsay who is out today.

As our algorithm you inquired about is proprietary, we are unable to share it.

Let us know if there is something else we can help you troubleshoot in terms of using FullStory with your app.

Thanks,