This may not be a huge issue depending on mitigating controls but are they saying that anyone can submit a PR (containing anything) to Immich, tag the pr with `preview` and have the contents of that PR hosted on https://pr- .preview.internal.immich.cloud? Doesn't that effectively let anyone host anything there?
Google flags Immich sites as dangerous
351–360 of 713 posts
Re: Google flags Immich sites as dangerous
#352Earlier quoted context omitted.
They're auto-deploying PRs to a subdomain of a domain that they also use for production traffic. This allows any member of the public with a GitHub account to deploy any arbitrary code to that subdomain without any review or approval from the Immich team. That's bad for two reasons: 1. PR deploys on public repos are inherently tricky as code gains access to the server environment, so you need to be diligent about seg…
> This allows any member of the public with a GitHub account to deploy any arbitrary code to that subdomain without any review or approval from the Immich team. This part is not correct: the "preview" label can be set only by collaborators. > a subdomain of a domain that they also use for production traffic To clarify this part: the only production traffic that immich.cloud serves are static map tiles (tiles.immich.c…
That's good & is a decent starting point. A decent second step might be to have the Github Actions workflow also check the approval status of the PR before deploying (requiring all collaborators to be constantly aware that the risk of applying a label is similar to that of an approval seems less viable)
Re: Google flags Immich sites as dangerous
#353From their perspective, a few false positives over the total number of actual malicious websites blocked is fractional.
Re: Google flags Immich sites as dangerous
#354Can I use this space to comment on how amazing Immich is? I self host lots of stuff, and there’s this one tier above everything else that’s currently, and exclusively, held by Home Assistant and Immich. It is actually _better_ than Google photos (if you keep your db and thumbs on ssd, and run the top model for image search). You give up nothing, and own all your data.
What model do you recommend for image search?
Essentially CLIP lets to encode both text and images in same vector space.
It is really easy and pretty fast too generate embeddings. Took less than hour on Google Colab.
I made a quick and dirty Flask app that lets me query my own collection of pictures and provide most relevant ones via cosine similarity.
You can query pretty much anything on CLIP (metaphors, lightning, object, time, location etc).
From what I understand many photo apps offer CLIP embedding search these days including Immich - https://meichthys.github.io/foss_photo_libraries/
Alternatives could be something like BLIP.
Re: Google flags Immich sites as dangerous
#355Be sure to see the team's whole list of Cursed Knowledge. https://immich.app/cursed-knowledge
Some of these seem less cursed, and more just security design? > Some phones will silently strip GPS data from images when apps without location permission try to access them. That strikes me as the right thing to do?
Try to get an iPhone user to send you an original copy of a photo with all metadata. Even if they want to do it most of them don't know how.
Re: Google flags Immich sites as dangerous
#356If you're going to host user content on subdomains, then you should probably have your site on the Public Suffix List https://publicsuffix.org/list/ . That should eventually make its way into various services so they know that a tainted subdomain doesn't taint the entire site....
In the past, browsers used an algorithm which only denied setting wide-ranging cookies for top-level domains with no dots (e.g. com or org). However, this did not work for top-level domains where only third-level registrations are allowed (e.g. co.uk). In these cases, websites could set a cookie for .co.uk which would be passed onto every website registered under co.uk. Since there was and remains no algorithmic meth…
Re: Google flags Immich sites as dangerous
#357Re: Google flags Immich sites as dangerous
#358Never host your test environments as Subdomains of your actual production domain. You'll also run into email reputation as well as cookie hell. You can get a lot of cookies from the production env if not managed well.
This. I cannot believe the rest of the comments on this are seemingly completely missing the problem here & kneejerk-blaming Google for being an evil corp. This is a real issue & I don't feel like the article from the Immich team acknowledges it. Far too much passing the buck, not enough taking ownership.
1. You should host dev stuff and separate domains.
2. Google shouldn't be blocking your preview environments.
Re: Google flags Immich sites as dangerous
#359Earlier quoted context omitted.
I think google is crumbling under the weight of their size. They are no longer able to process the requested commercials with due diligence.
I see the same scam/deepfake ad(s) pretty much persistently. Maybe they actually differ slightly (they are AI gen mostly), but it's pretty obvious what they are, and I'm sure they get flagged a lot. They just need to introduce a basic deposit to post ads, and you lose it if you put up a scam ad. Would soon pay for the staff needed to police it, and prevent scammers from bypassing admin by trivially creating new accou…
Re: Google flags Immich sites as dangerous
#360Earlier quoted context omitted.
Use one of the forks. librewolf, waterfox, zen. Firefox itself lost trust when Mozilla tried to push the new Terms of Use earlier this year. That was so aggressively user-hostile that nobody should trust Mozilla ever again. Using a fork puts an insulation layer between you and Mozilla. Librewolf is just a directly de-mozillaed and privacy-enhanced Firefox, similar to Ungoogled Chromium. I've been trying to get in the…
> Firefox itself lost trust when Mozilla tried to push the new Terms of Use earlier this year. Those terms of use aren't in place any longer. I'm surprised that listening to the users is viewed as something bad.
Their marketing and legal departments lost it long before the terms of service debacle.