Browsing info to accountability partners

cloudveiltech / Filter-Windows

HTTP/S Content Filter for Windows 7 and newer

Mozilla Public License 2.0

9 stars 13 forks source link

Browsing info to accountability partners #70

Open dkwiebe opened 6 years ago

dkwiebe commented 6 years ago

We have users who would like to have information on their browsing habits sent to accountability partners. If this information could be opted in to by the user it could be pushed back to the server. This would be controlled server side.

dkwiebe commented 6 years ago

@TechnikEmpire We've been putting some thoughts into this. I have a few thoughts. @montesound Does this match what you're thinking?

Currently the browsing data is just stored in the the app itself but we'll need a 1/2 ways decent place to store it to prevent removing evidence until it can be submitted to the server.

Reporting will be controlled by group or (in the future) installation settings.
There will be the following choices. 0 - Default - no reporting 1 - Blocked Only
Reporting will happen on the same schedule as the app checks for updates.
We'll need to add support to CitadelManager for this but I'd like to get some of the details worked out before documenting that. The manager would parse the banned data and trigger an event as necessary.

TechnikEmpire commented 6 years ago

What if we developed this as a p2p system so only the accountability partner can see it. I just wonder how much of a deterrent and attraction for hacks holding people's browser history will be.

My 2 cents. I think it's a great idea I just personally would be super cautious about implementation.

dkwiebe commented 6 years ago

@TechnikEmpire I appreciate the caution. Are you comfortable delivering this via email? Is your primary concern it touching the management system or the end delivery method?

dkwiebe commented 6 years ago

Other accountability stuff we're planning to deliver via email or Telegram.

dkwiebe commented 6 years ago

Here's what we're currently looking at:

Two tier accountability system, first tier notifies a summary of block actions per category and the second notifies that plus specific urls presently in history at the time of the event.

We don't intend to store the urls in the management system but will be parsing them and passing it on to an accountability partner.

kfreezen commented 6 years ago

@dkwiebe Do you have a server-side system in place for this yet?

dkwiebe commented 6 years ago

@kfreezen I don't have the server side in place on this yet. Are you ready for it? This is related to #83

kfreezen commented 6 years ago

@dkwiebe I told you this through other channels, but recording this here to attach it to this issue. Commits 00dafa2 and 102631f implement basic fix.

dkwiebe commented 6 years ago

@kfreezen I have implemented a very, very basic start to this. Do we need to do anything to turn this on? My start just logs the results so I can work on parsing them.

kfreezen commented 6 years ago

@dkwiebe I believe this is going to be in branch-1.7. I can build you a test version.

dkwiebe commented 6 years ago

@kfreezen, that would be great. No rush on it.