3 ms·

"To use Pernosco, you must consent to collection, transfer, storage and use of your data" I understand the need to monetize but honestly seems like a huge com

"To use Pernosco, you must consent to collection, transfer, storage and use of your data" I understand the need to monetize but honestly seems like a huge commitment in terms of both trust and money to use a tool like this. Perhaps a nagging screen model would work better? (better => more users using the tool, a percentage of which would def. pay to remove the nag and support the creator/s). A list of successful paid software I can think of from the top of my head: * https://www.reaper.fm/ https://www.reaper.fm/ (nagging screen) * https://www.linqpad.net/ https://www.linqpad.net/ (PRO versions with additional features) * https://www.jetbrains.com/idea https://www.jetbrains.com/idea ("Community" and "Professional" versions) * https://cursive-ide.com/ https://cursive-ide.com/ (30 day trial? I think? Personal, Commercial and Non Commercial licenses avail.) * https://www.sublimetext.com/ https://www.sublimetext.com/ (no limitations but purchase is expected, not enforced) * https://github.com/cognitect-labs/REBL-distro https://github.com/cognitect-labs/REBL-distro (used to _require_ joining a Patreon to use the software, but did not enforce it... Also I think it used to have commercial licenses available).

db48x 6y ago
It's definitely a factor worth considering before purchasing the service. It's going to record an entire program running on your local machine, including all the data that it reads and writes. That includes local files, network connections, events from your window manager, pixels put on the screen, any environment variables that happened to be defined, etc. If any of that is private then you shouldn't upload the recording to Pernosco. If you're working on a public GitHub repository then your concern is pretty much limited only to your local environment. Make sure you don't have security tokens in your environment variables when you record. If your program opens files, make sure it opens something harmless. If your program visits webpages, don't record it visiting a page you want kept private. It's only natural then that the EULA would want you to give Pernosco permission to receive that data, store it for you, and then present it back to you during your debugging sessions. There's also the on-premises option.
- roca 6y ago
  Note that the pernosco-submit script supports detecting "sensitive" environment variables leaking into the recording: https://github.com/Pernosco/pernosco-submit/blob/a6119a1b291487dd056c38cfeb4280604358ca12/pernosco-submit#L142 https://github.com/Pernosco/pernosco-submit/blob/a6119a1b291... And we accept PRs :-)
  - db48x 6y ago
    That's true! I ran afoul of that several times. It was easiest to clean up my environment, but I thought about writing a patch to rr that would bail out before recording anything if it detected those variables. Having that would have saved me from having to rerecord a few things.
    - roca 6y ago
      I suppose an option to run the same checks in rr at recording time would be a fine feature to have ... though you could implement it pretty easily as a wrapper script too.
roca 6y ago
The service model is not just about monetization. It enables collaboration features that are really useful, e.g. https://pernos.co/about/browser https://pernos.co/about/browser Resource utilization is also an issue. To accelerate the debugging experience we build huge databases of all program states. You can't run Pernosco on your laptop. Having said that, we understand the trust issue, we are very open to offering an on-premises version of Pernosco and we are keen to talk to people interested in that.

db48x 6y ago

It's definitely a factor worth considering before purchasing the service. It's going to record an entire program running on your local machine, including all the data that it reads and writes. That includes local files, network connections, events from your window manager, pixels put on the screen, any environment variables that happened to be defined, etc. If any of that is private then you shouldn't upload the recording to Pernosco. If you're working on a public GitHub repository then your concern is pretty much limited only to your local environment. Make sure you don't have security tokens in your environment variables when you record. If your program opens files, make sure it opens something harmless. If your program visits webpages, don't record it visiting a page you want kept private. It's only natural then that the EULA would want you to give Pernosco permission to receive that data, store it for you, and then present it back to you during your debugging sessions. There's also the on-premises option.

roca 6y ago
Note that the pernosco-submit script supports detecting "sensitive" environment variables leaking into the recording: https://github.com/Pernosco/pernosco-submit/blob/a6119a1b291487dd056c38cfeb4280604358ca12/pernosco-submit#L142 https://github.com/Pernosco/pernosco-submit/blob/a6119a1b291... And we accept PRs :-)
- db48x 6y ago
  That's true! I ran afoul of that several times. It was easiest to clean up my environment, but I thought about writing a patch to rr that would bail out before recording anything if it detected those variables. Having that would have saved me from having to rerecord a few things.
  - roca 6y ago
    I suppose an option to run the same checks in rr at recording time would be a fine feature to have ... though you could implement it pretty easily as a wrapper script too.

roca 6y ago

The service model is not just about monetization. It enables collaboration features that are really useful, e.g. https://pernos.co/about/browser https://pernos.co/about/browser Resource utilization is also an issue. To accelerate the debugging experience we build huge databases of all program states. You can't run Pernosco on your laptop. Having said that, we understand the trust issue, we are very open to offering an on-premises version of Pernosco and we are keen to talk to people interested in that.