Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional persistence of activities #106

Open
lennartblom opened this issue Jan 12, 2021 · 4 comments
Open

Optional persistence of activities #106

lennartblom opened this issue Jan 12, 2021 · 4 comments

Comments

@lennartblom
Copy link

Is there any way to setup the sync process, that your application does not store any data inside the mongo db?

One of my running club mates is complaining about data privacy aspect, that he did not approve my attempt to sync the club activities and would like to be excluded from the channel where the activities are synchronized.

Is there any way your application can skip specific users or is just acting as a "relay" of the activity data? So the stuff is not stored anywhere except the slack channel?

@dblock dblock changed the title Optional persistence of activities or exclude users Optional persistence of activities Jan 12, 2021
@dblock
Copy link
Owner

dblock commented Jan 12, 2021

This is a very valid feature request, there's really no reason for the bot to store all the identifiable information other than for stats, so something that I support. Open to suggestions of what that looks like. A retention policy where older activities are deleted could definitely be a start (#107).

For clubs, the issue is that the club activity does not say what user it belongs to (for privacy reasons), so I don't see a way to give someone a way to exclude themselves from the sync.

@dblock
Copy link
Owner

dblock commented Jan 12, 2021

Implementing complete passthrough would be doable, but there are a few places where this is tricky/requires work. First we don't notify in the synchronous path of a Strava event. Second some information needs to be stored to update recent posts following edits.

@lennartblom
Copy link
Author

Thanks Daniel for reaching out so nicely! Unfortunately I stopped syncing our club activities because I feel uncomfortable if one member is concerned regarding the data stuff. Otherwise I would have picked up my credit card 💳 to subscribe for one year.

But I guess there's always one in the group how has concerns. Too bad! I like your implementation and see your technical reasons to not be able to provide my desired software routine. What a pity. 😞

@dblock
Copy link
Owner

dblock commented Apr 1, 2021

In ebfb98b I've capped data storage to 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants