Post #1907593
2022-11-09 23:22 UTC
For half an hour full of stress I thought, I exposed the sessions database. I noticed a data folder in the git repository that should not have been there (wrong path). First I deleted the folder (to make it less visible), then I revoked the Twitter app tokens, filtered the data from the git history (to actually remove it) and put a notice on the #fedifinder homepage. Finally, I felt like I did, what I could. I relaxed and realized that user data was never at risk. The was the staging database.
Replies (2)
-
@Luca@vis.social 2022-11-10 18:52
I updated the ReadMe to help people run their own #Fedifinder (no coding skills needed) and how to contribute. https://github.com/lucahammer/fedifinder And fedifinder got a new API endpoint. api/check. You can use it with a domain and/or handle as query parameters and get back the cached information fedifinder has for that: https://fedifinder.glitch.me/api/check?handle=@luca@lucahammer.com
-
@roman@vis.social 2022-11-10 22:14
@Luca what a relief