sha2nk

4 ms·

1. 1.▲
   by sha2nk 8y ago

   Thanks for the feedback! Yes, the intent is to automatically prevent capture of personally identifiable information. The problem with asterisk though is that it still leaks the lengtg of the email address. We are exploring other options wit
2. 2.▲
   by sha2nk 8y ago

   The pixelation is just a visual effect. When redaction is on, the text content/images etc are not captured at all. During replay/playback the place where the original content was is filled with randomly generated data whixh is the
3. 3.▲
   by sha2nk 8y ago

   The actual amount in bytes will vary with the complexity of the app, the amount of activity in the session and the length of history the recorder is configured to store. Typically this will be a few MBs for the default 10 minutes of history
4. 4.▲
   by sha2nk 8y ago

   In the case of offline recording the data is stored in indexedDB. Localstorage limits are typically too small to store a reasonably sized session recording.
5. 5.▲
   by sha2nk 8y ago

   Thanks for pointing it out. We are indeed using wevcrypto to encrypt the data generated during the recording. This usecase, however, we’d argue is quite well suite for webcrypto. The typical critique (including the one you linked to) referr
6. 6.▲
   by sha2nk 8y ago

   Thanks for sharing this. We had posted this as a “Show HN” a couple of weeks ago but it didn’t get a lot of traction there. Happy to answer any questions!
7. 7.▲
   by sha2nk 8y ago

   Thanks for your thoughtful comments! Regarding blurring: It’s just a visual layer on top. The actual content that is underneath the blurring layer is just some randomly generated data. If you are familiar with chrome debugger you can check
8. 8.▲
   Show HN: RecapJS – Record and Replay Browser Sessions Without Leaking User Data(recapjs.com)

   9 points by sha2nk 8y ago|3 comments