fmstrat

joined 1 year ago
[–] [email protected] 1 points 1 month ago

Yea, so many other occurrences I wish had gone to court, this one not only doesn't stand a chance, but will set bad precedence.

[–] [email protected] 4 points 1 month ago

GitLab is still a commercial entity, and looking for buyers I understand. Plex was once open source, but guess why everyone recommends Jellyfin now.

[–] [email protected] 7 points 1 month ago

Big fan, but if you haven't tried Obtainium as a client, give it a go. Can manage installs from F-Droid, GitHub releases, and more.

[–] [email protected] 3 points 1 month ago

Often times this language is used to drum up funding for exactly these types of things.

[–] [email protected] 1 points 1 month ago

If you're still posting on Reddit or Twitter, and it's not for a niche community, please don't come here.

[–] [email protected] 4 points 1 month ago

Or, https://www.firefly-iii.org/, a full self-hosted system similar to Mint.

[–] [email protected] 22 points 1 month ago (1 children)

Oooo healthy online discourse. Where's my popcorn...

[–] [email protected] 1 points 1 month ago (1 children)

This post isn't about email open rates, it's about data exfiltration. But for email speficially, show me major providers that prefetch by default.

[–] [email protected] 2 points 1 month ago (1 children)

If by prefetch you mean the server grabs the images ahead of time vs the client, this does not happen, at least on amy major modern platform that I know of. They will cache once a client has opened, but unique URLs per recipient are how they track the open rates.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago) (3 children)

Server or client, every supposed prefetch would be unique. If I trick an LLM client into grabbing:

site.com/random-words-of-data/image.gif

Then:

site.com/more-random-data/image.gif

Those are two separate images to the cache engine. As the data refreshes, the URL changes, forcing a new grab each time.

For email, marketers do this by using a unique image URL for every recipient.

[–] [email protected] 1 points 1 month ago (5 children)

But the path changes with every new data element. It's never the same, so every "prefetch" is a whole new image in the system's eyes.

[–] [email protected] 6 points 1 month ago (11 children)

This wouldn't help, would it? How would you prefetch and cache:

site.com/base64u-to-niceware-word-array/image.gif

? It would look like a normal image URL in any article, but actually represent data.

Note: "niceware" is a way to convert binary or text data into a set of words like "cow-heart-running-something-etc".

view more: ‹ prev next ›