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

Update 2024-01-23 #126

Open
ebrensi opened this issue Jan 24, 2024 · 0 comments
Open

Update 2024-01-23 #126

ebrensi opened this issue Jan 24, 2024 · 0 comments
Assignees

Comments

@ebrensi
Copy link
Owner

ebrensi commented Jan 24, 2024

I got contacted by Strava about some privacy issues with the app, and they threatened to disable my API access unless I fix it. The issue is that the app displays all activities that the user gave it permissions to access. So, if you as a user allowed heatflask access to your private activities and shared a link to your map, people could see all of your private activities. The way it should work is that if you are logged in as yourself, you can see all of your private activities on your map, but someone else with a link to your map will only see your public activities. Until I fix that, if a you as a user do not want anyone seeing your private activities, don't give heatflask access to them when you sign up. Or delete your heatflask account and start another one with stricter permissions.

So I'm doing some rewriting again. I haven't touched the master branch for years, and that is what is currently running in the cloud at www.heatflask.com. If you look at the branches here you'll see that there have been a few attempted re-writes that I had to abandon.

This time, instead of trying to re-write the whole thing (which really does need to be done), I am just going to try and update the backend first and leave the frontend as is, just fixing the privacy problem. Then, if I have time, I will update the frontend to use proper bundling and update a bunch of stuff, most notably the map API to MapBox.

The current working branch is new-old.

@ebrensi ebrensi self-assigned this Jan 24, 2024
@ebrensi ebrensi pinned this issue Jan 24, 2024
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

1 participant