Earlier quoted context omitted.
I think it's somewhat tribal webdev knowledge that if you host user generated content you need to be on the PSL otherwise you'll eventually end up where Immich is now. I'm not sure how people not already having hit this very issue before is supposed to know about it beforehand though, one of those things that you don't really come across until you're hit by it.
I’ve been doing this for at least 15 years and it’s the first I heard of this. Fun learning new things so often but I never once heard of the public suffix list. That said, I do know the other best practices mentioned elsewhere
Google flags Immich sites as dangerous
81–90 of 713 posts
Re: Google flags Immich sites as dangerous
#82The one thing I never understood about these warnings is how they don't run afoul of libel laws. They are directly calling you a scammer and "attacker". The same for Microsoft with their unknown executables. They used to be more generic saying "We don't know if its safe" but now they are quite assertive at stating you are indeed an attacker.
No they're not. The word "scammer" does not appear. They're saying attackers on the site and they use the word "might".
This includes third-party hackers who have compromised the site.
They never say the owner of the site is the attacker.
I'm quite sure their lawyers have vetted the language very carefully.
Re: Google flags Immich sites as dangerous
#83google: we make going to the DMV look delightful by comparison!
Re: Google flags Immich sites as dangerous
#84Earlier quoted context omitted.
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.
Right, for postgres I would use unnest for inserting a non-static amount of rows.
We probably should have been partitioning the data instead of inserting it twice, but I never got around to fixing that.
COPY is likely a better option if you have access to the host, or provider-specific extensions like aws_s3 if you have those. I'm sure a data engineer would be able to suggest a better ETL architecture than "shove everything into postgres", too.
Re: Google flags Immich sites as dangerous
#85I know that I can bypass the warning, but the photo album I sent to my mother-in-law is now effectively inaccessible.
Re: Google flags Immich sites as dangerous
#86If you block those internal subdomains from search with robots.txt, does Google still whine?
Re: Google flags Immich sites as dangerous
#87Earlier quoted context omitted.
"The engineering equivalent of a car made of duct tape" Kind of. But do you have a better proposition?
A part of the issue is IMO that browsers have become ridiculously bloated everything-programs. You could take about 90% of that out and into dedicated tools and end up with something vastly saner and safer and not a lot less capable for all practical purposes. Instead, we collectively are OK with frosting this atrocious layer cake that is today's web with multiple flavors of security measures of sometimes questionabl…
Re: Google flags Immich sites as dangerous
#88I 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…
It's scary how much control Google has over which content people can access on the web - or even on their local network!
Re: Google flags Immich sites as dangerous
#89Earlier quoted context omitted.
Please point me to where GoDaddy or any other hosting site mentions public suffix, or where Apple or Google or Mozilla have a listing hosting best practices that include avoiding false positives by Safe Browsing…
>GoDaddy or any other hosting site mentions public suffix They don't need to mention it because they handle it on behalf of the client. Them recommending best practices like using separate domains makes as much sense as them recommending what TLS configs to use. >or where Apple or Google or Mozilla have a listing hosting best practices that include avoiding false positives by Safe Browsing… Since were those sites the…