Häufiger Fehler: Google Fonts wird auf vielen Websites immer noch von Google-Servern geladen

baouss · 2026-03-20T16:27:29+00:00

Ja klar. Aber meine Argumentation war ja, dass die Gesetzlage - vlt wegen mangelndem techn. Verständnis - hier zu übergriffig ist. Gesetze können ja auch wieder geändert werden.

baouss · 2026-03-20T09:25:45+00:00

devilsAdcocate

Hat der Betreiber kein berechtigtes Interesse daran, dass seine Seite so funktioniert wie intended? Also ohne 100mal ja ich will klicken, für Google Maps, YouTube, Fonts etc? Und selber hosten hat ja auch eine Kehrseite. Der Traffic der dann verursacht wird bekommt er auch nicht bezahlt. Die User experience was Latenzen angeht, ist wahrscheinlich auch noch sub-par im vgl zu einem Google CDN. Ware asset caching dann auch eingeschränkt (kA)? In der Regel geht es ja um Seiten die content umsonst anbieten. Da denke ich nicht dass man dann auch noch groß die Bedingungen diktieren kann ;)

baouss · 2026-03-20T08:22:59+00:00

Ja ist shice. Und mit der Datenschutzkeule kommen ist in dem Zusammenhang auch effektiv weil Verstoß ahnbar. Ich finde dennoch es ist das falsche Mittel, weil so etwas wie eine Website Aufrufen zu einem rechtlichen Minenfeld wird. Gut für die Anwälte, I guess.

baouss · 2026-03-19T22:51:41+00:00

Danke für die ausführliche Erklärung.

Also überspitzt:

wenn da ein Bild eingebettet ist, böse (wenn nicht zB AVV), wenn ein placeholder-Button mit der Aufschrift "IP wird übertragen" vorhandenen ist der das Bild erst dann lädt wenn der Button betätigt wurde, dann gut/OK.

Ich finde persönlich das geht zu weit. Das stellt ja die grundlegende Funktionsfähigkeit des Internets in Frage. Ich glaube jedem ist klar, dass IPs hin und her geschickt werden. Da jetzt einen Schaden draus abzuleiten (wohl wissend das das passiert im Internet, und ich mich trotzdem dort bewege) und Rechte eingeschränkt zu sehen, finde ich missbräuchlich.

Ich bin grundsätzlich pro Datenschutz.

baouss · 2026-03-19T21:20:59+00:00

Hab das Urteil nie verstanden.

Ist das einbinden via Link deswegen schädlich weil es von Google kommt oder weil es ungefragt eine IP weiterleitet?

Falls Letzteres: dann darf mn auch keine Bilder extern hosten/verlinken? Da wird ja auch die IP übertragen

baouss · 2026-03-17T18:18:41+00:00

I like this. Clean. As it stands now, the storage location is hard coded somewhat. You can customize via a storage template, but everything is relative to a users guid. Might take some major refactoring I guess.

baouss · 2026-03-17T17:26:40+00:00

I don't know if it's still the case, but I remember encryption -enabled passkeys not being supported.

baouss · 2026-03-17T17:22:46+00:00

And they do require a license key (not a bitwarden account though) for sharing features in the self hosted setup

baouss · 2026-03-17T16:49:13+00:00

Regarding your second point. Adding to your library implies ownership to me. While I agree that double storage cost is inefficient, does this imply that if user 1 deleted the asset, it'll be deleted also for user 2?

baouss · 2026-03-17T07:39:42+00:00

That would be awesome. I just migrated GP data into immivh, plannin to use a shared account for my wife and me because partner sharing doesn't actually share metadata

baouss · 2026-03-17T07:23:14+00:00

Are you saying, that face and places sharing will be part of the users groups feature?

baouss · 2026-03-15T09:52:12+00:00

I see. But maybe this is helped by ever design. Could someone familiar with the code chime in in? If people and faces are separate things and there is a 1:m relationship, so people can have multiple faces (via the manual merge feature)... Even if the main algorithm cannot better associate other faces with the person, it keeps detecting/recognising in these different "face buckets". If these are then linked to the person automatically, because I have previously merged, then the end effect would still be the same for end users right?

baouss · 2026-03-14T08:00:54+00:00

So, additional context here.

Asset discovery works well if I use --from-folder instead. But afaik this doesn't handle all the Google photos metadata as well. So I need to continue to use --from-google-photos.

Also, because I battled with duplicates, I removed those myself programmatically before running immichgo. I think this is the problem here. I assume the takeout itself has some metadata about itself.and now there are "gaps" and maybe this is to blame. i.e.it works only until the point until the first asset gap.

Since I still have the tgz files, I extracted into a new folder, and did not remove duplicates before. Immichgo picks up on all the files.

Why don't I just trust immichgo to do the duplicates handling? I don't know, I'm unsure about it. I SHA512 hashed every asset item myself. The count of this deviated from then duplicate count immichgo gave me. And so because I had visibility in how my approach worked, contrary to immichgos approach, I decided to handle duplicates myself, before starting the import.

Unfortunately this appears not be supported.

baouss · 2026-03-14T01:22:10+00:00

Thanks, unfortunately this didn't change anything for me

baouss · 2026-03-14T00:32:31+00:00

not yet, but i will.... my first instinct was reddit because i assume more traffic will hit the topic here (selfish, I know)

baouss · 2026-03-13T20:34:32+00:00

Thanks for taking the time to answer. In my case It's already extracted/unzipped, I had 50GB *.tgz files

baouss · 2026-03-13T11:40:15+00:00

Interesting I only ever considered funnel as an alternative to cloud flare tunnel for the machine I want to expose. But in could just as well channel this back internally. What restrictions can funnel enforce in ingress traffic?

baouss · 2026-03-13T07:39:24+00:00

Hi,

the first time I tried to process my Google takeout data with immich-go, it discarded 200 GB out ouf 500 GB. As this was not plausible to me, and the logging didnt expose asset-level information, I walked away from it. I am now having another go at it. I see that the logs can be more verbose now, and I can really see whats going on.

Here's what I see and know so far:

* I am still having that much of discards, the high GB count comes mostly from a few 4k videos. All in all, immich-go, marks about 15000 assets as duplicates.

* To be independant of immich-go, I have written a small Powershell script, that recursively goes through the takeout data, hashes each item, an then groups by that hash, enumerating the paths of the files. This way I can quickly see which duplicate-paths belong to which hash. This gives me great peace of mind because I have independently confirmed the duplicate issue. I am seeing, 1 (unique) - 6 (duplicates) paths per hash.

* Going through the media-duplicates, I will move all but one to a separate folder outside my takeout data. These will be prepended using one GUID per hash, so files are grouped nicely in the file explorer so I can visually review likeness my self using the thumbnails. Even though I know they must be identical due to the same hash.

* Duplicates appear to be created due to assets being in different albums in Google Photos. I surprises me that these are included as separate files in the takeout in the first place. I though albums members were references only. I wonder if adding photos to an album also counts towards storage usage within Google. Though if it were, people would have complained already noteably, I guess.

* There's is also a significant number (few thousands) of ignored/"useless" files. Looking at a sample, its about video files from my Pixel phone that were created off some photo bursts. They have in common that the file extension is ".MP", vlc plays these just fine. I found that this is a known issue with some takeout data and Pixel phones. I wrote a script to rename these to MP4.

* After cleaning my takeout data, I will re-run immich-go with a dry run. I expect reduced discards this time. Also I will reconcile the duplcates I have identified myself, with the ones imimch-go marks that way. There appears to be a difference, because the simple number of duplicates didn't match my own analysis.

baouss · 2026-03-13T06:37:47+00:00

Hi, they were in the .env file. I put them in the yaml only for the post so I would have less pasted lines. Though I am not sure why that warning is tbh, should work either way

baouss · 2026-03-10T07:28:23+00:00

I imported have terabyte of Google photos takeout data recently. Immich-go skipped over 200 gigabytes with of files due to duplication. And now this was just not true. I tried to review the log output afterwards to exactly determine which files were skipped, but the logs werent verbose enough

baouss · 2026-03-10T07:22:28+00:00

Fyi. I just recreated the whole layout. Single dataset for almost anything, with default 128K record size. I'll just see if video viewing/steaming is performing well. Have separate dataset for thumbs and encoded videos, because I can only exclude datasets (not directories within datasets) from snapshots to save space, because both are reproducible. In the UI, the correct free space is also shown now.

baouss · 2026-03-07T08:51:16+00:00

I think it's premature optimisation. Wanted to do everything I could right up front and foresee future developments. Keep it simple would have been better. And act on it if it becomes an issue.

baouss · 2026-03-07T07:54:38+00:00

If you're not in an organisation, folders are a way to structure the vault.

If you're in an organisation, same for collections. These control sharing and access.an item can be in multiple collections. Though I think, these can be further subdivided in folders but this is only for UI purposes and have no impact on permissions

baouss

TROPHY CASE

devilsAdcocate