If it helps focus the discussion: the things I’m most unsure about are (1) how privacy leaks happen even when you store very little, and (2) whether Telegram introduces risks I’m underestimating.
If you’ve built alerting systems or privacy-minimal services, I’d love to hear what you’d try to break first.
My two cents, if you use storage.googleapis.com privacy is zero. You are just telling Google what you are doing. No need for that, right?
Out of curiosity what is jwnozfjzczoufsdzwfvd.supabase.co for?
Those storage.googleapis.com URLs are just Supabase Storage (it sits on Google Cloud Storage). I’m not using it for anything user related or anything like that, it’s mostly static stuff + app data. Not sure how to get around that, unless I host everything myself, which I dont have the capacity to do.
jwnozfjzczoufsdzwfvd.supabase.co is just the Supabase project endpoint (db/auth/storage).
If it helps focus the discussion: the things I’m most unsure about are (1) how privacy leaks happen even when you store very little, and (2) whether Telegram introduces risks I’m underestimating.
If you’ve built alerting systems or privacy-minimal services, I’d love to hear what you’d try to break first.
My two cents, if you use storage.googleapis.com privacy is zero. You are just telling Google what you are doing. No need for that, right? Out of curiosity what is jwnozfjzczoufsdzwfvd.supabase.co for?
I appreciate that :) Thanks for replying.
Those storage.googleapis.com URLs are just Supabase Storage (it sits on Google Cloud Storage). I’m not using it for anything user related or anything like that, it’s mostly static stuff + app data. Not sure how to get around that, unless I host everything myself, which I dont have the capacity to do.
jwnozfjzczoufsdzwfvd.supabase.co is just the Supabase project endpoint (db/auth/storage).
Fair. But most of the times scripts can be downloaded and integrated on the webpage. Don't know if that is the case but many can.