Live data from Hacker News

Google flags Immich sites as dangerous

immich.app

21–30 of 713 posts

Re: Google flags Immich sites as dangerous

#21

This seems related to another hosting site that got caught out by this recently: https://news.ycombinator.com/item?id=45538760

Not quite the same (other than being an abuse of the same monopoly) since this one is explicitly pointing to first-party content, not user content.

Re: Google flags Immich sites as dangerous

#22
post #7

If you block those internal subdomains from search with robots.txt, does Google still whine?

I’ve heard anecdotes of people using an entirely internal domain like “plex.example.com” even if it’s never exposed to the public internet, google might flag it as impersonating plex. Google will sometimes block it based only on name, if they think the name is impersonating another service. Its unclear exactly what conditions cause a site to get blocked by safe browsing. My nextcloud.something.tld domain has never be…

I'm almost positive GMail scanning messages is one cause. My domain got put on the list for a URL that would have been unknowable to anyone but GMail and my sister who I invited to a shared Immich album. It was a URL like this that got emailed directly to 1 person:

https://photos.example.com/albums/xxxxxxxx-xxxx-xxxx-xxxx-xx...

Then suddenly the domain is banned even though there was never a way to discover that URL besides GMail scanning messages. In my case, the server is public so my siblings can access it, but there's nothing stopping Google from banning domains for internal sites that show up in emails they wrongly classify as phishing.

Think of how Google and Microsoft destroyed self hosted email with their spam filters. Now imagine that happening to all self hosted services via abuse of the safe browsing block lists.

Re: Google flags Immich sites as dangerous

#23
post #8

If 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....

Aw. I saw Jothan Frakes and briefly thought my favorite Starfleet first officer's actor had gotten into writing software later in life.

Re: Google flags Immich sites as dangerous

#24
post #14

Be sure to see the team's whole list of Cursed Knowledge. https://immich.app/cursed-knowledge

The Postgres query parameters one is funny. 65k parameters is not enough for you?!

As it says, bulk inserts with large datasets can fail. Inserting a few thousand rows into a table with 30 columns will hit the limit. You might run into this if you were synchronising data between systems or running big batch jobs.

Sqlite used to have a limit of 999 query parameters, which was much easier to hit. It's now a roomy 32k.

Re: Google flags Immich sites as dangerous

#25

[flagged]

As someone who doesn't like Google and absolutely thinks they need to be broken up, no probably not. Google's algorithms around security are so incompetent and useless that stupidity is far more likely than malice here.

Callous disregard for the wellbeing of others is not stupidity, especially when demonstrated by a company ostensibly full of very intelligent people. This behavior - in particular, implementing an overly eager mechanism for damaging the reputation of other people - is simply malicious.

Re: Google flags Immich sites as dangerous

#26

I think the other very interesting thing in the reddit thread[0] for this is that if you do well-known-domain.yourdomain.tld then you're likely to get whacked by this too. It makes sense I guess. Lots of people are probably clicking gmail.shady.info and getting phished. 0: https://old.reddit.com/r/immich/comments/1oby8fq/immich_is_a...

So we can't use photos or immich or images or pics as a sub-domain, but anything nondescript will be considered obfuscated and malicious. Awesome!

Re: Google flags Immich sites as dangerous

#27

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?

I think only collaborators can add labels on github, so not quite. Does seem a bit hazardous though (you could submit a legit PR, get the label, and then commit whatever you want?).

Exposure also extends not just to the owner of the PR but anyone with write access to the branch from which it was submitted. GitHub pushes are ssh-authenticated and often automated in many workflows.

Re: Google flags Immich sites as dangerous

#28
post #24
post #14

Earlier quoted context omitted.

The Postgres query parameters one is funny. 65k parameters is not enough for you?!

As it says, bulk inserts with large datasets can fail. Inserting a few thousand rows into a table with 30 columns will hit the limit. You might run into this if you were synchronising data between systems or running big batch jobs. Sqlite used to have a limit of 999 query parameters, which was much easier to hit. It's now a roomy 32k.

COPY is often a usable alternative.

Re: Google flags Immich sites as dangerous

#29

I tried to submit this, but the direct link here is probably better than the Reddit thread I linked to: https://old.reddit.com/r/immich/comments/1oby8fq/immich_is_a... I had my personal domain I use for self-hosting flagged. I've had the domain for 25 years and it's never had a hint of spam, phishing, or even unintentional issues like compromised sites / services. It's impossible to know what Google's black box is do…

Wonder if there would be any way to redress this in small claims court.

Re: Google flags Immich sites as dangerous

#30

Earlier quoted context omitted.

I’ve heard anecdotes of people using an entirely internal domain like “plex.example.com” even if it’s never exposed to the public internet, google might flag it as impersonating plex. Google will sometimes block it based only on name, if they think the name is impersonating another service. Its unclear exactly what conditions cause a site to get blocked by safe browsing. My nextcloud.something.tld domain has never be…

I'm almost positive GMail scanning messages is one cause. My domain got put on the list for a URL that would have been unknowable to anyone but GMail and my sister who I invited to a shared Immich album. It was a URL like this that got emailed directly to 1 person: https://photos.example.com/albums/xxxxxxxx-xxxx-xxxx-xxxx-xx... Then suddenly the domain is banned even though there was never a way to discover that URL…

[deleted]
Post reply on HN