Stealing from Google
taqib.dev
Stealing from Google
1–10 of 31 posts
Re: Stealing from Google
#2Nice, but doesn't automatically update when the Google avatar changes. Cache invalidation strikes again.
Re: Stealing from Google
#3This seems problematic to me. Beyond just caching issues, did you ever get permission from users to store their personal data? They gave google permission, but not you.
Re: Stealing from Google
#4If I wanted to achieve the same result, that is to serve assets of others from my own domain, I'd just create a custom endpoint like /api/user-avatar/:userId and an action proxies the actual image from google, maybe keep a cached copy for some time to not have to redownload the image on every request.
Re: Stealing from Google
#5No post body was provided.
Re: Stealing from Google
#6[flagged]
Re: Stealing from Google
#7I really didn't get what the post was about. I'm getting old or? And I thought I was clever because I work with distributed databases...
Re: Stealing from Google
#8I really didn't get what the post was about. I'm getting old or? And I thought I was clever because I work with distributed databases...
The post assumes the reader is familiar with where things are happening and who is involved. Guess I'm not part of the target audience.
Re: Stealing from Google
#9I really didn't get what the post was about. I'm getting old or? And I thought I was clever because I work with distributed databases...
The post assumes the reader is familiar with where things are happening and who is involved. Guess I'm not part of the target audience.
Loading an img tag doesn't involve trusting a domain. Especially using crossorigin and refererpolicy attributes.
Re: Stealing from Google
#10This seems problematic to me. Beyond just caching issues, did you ever get permission from users to store their personal data? They gave google permission, but not you.
The users are going through an OAuth flow and creating an account. Presumably they are agreeing to a ToS as part of that.