▲ | smelendez 4 days ago | ||||||||||||||||
It's a little worse than email. With email, you normally use unique image and link URLs for each recipient, so you generally know who's opened the email and what they've clicked and can map that to their email address and whatever other information you have about them. With RSS, you generally don't have any information about who's accessing the feed other than an IP address. It is possible to require users to log in and receive a unique RSS URL, which is what podcasts often do to give paid subscribers access to paywalled episodes, but that's not common for web RSS. | |||||||||||||||||
▲ | Gormo 4 days ago | parent | next [-] | ||||||||||||||||
The exact same techniques used for email can be used for RSS. You could generate unique links for RSS too, based on requester headers, in the same way way web fingerprinting works. There'd be a bit of computational overheard in comparison to serving a static XML file, but it seems easily doable. | |||||||||||||||||
| |||||||||||||||||
▲ | DamonHD 3 days ago | parent | prev [-] | ||||||||||||||||
I really really really object to being tracked in emails with poisoned links (without being told or having a sensible opt-out, usually, so also illegal under GDPR I believe) and it is one reason that I will not sign up to them. |