4 ms·
You can mitigate link sharing by counting the feed reader hits per link (anything more than two standard deviations is probably a shared link, which you can set
by gen220 5y ago
You can mitigate link sharing by counting the feed reader hits per link (anything more than two standard deviations is probably a shared link, which you can set a revocation policy for). You can reject requests to content that don’t have a non-revoked referrer. This way, they can only get your content by copy-pasting content and rehosting the feed, which is an unavoidable risk.
In any case, as Netflix’s early history shows, depending on your cost structure, link sharing is likely a net positive. It’s probably only worth prosecuting the feeds that get shared with 100s of people.
It definitely is more complicated, but the tools to make it simple are easy to build! Maybe we’ll see growth in this space. One can dream
- mmahemoff 5y agoYou can, albeit with some effort involved, e.g. Ben Thomson has mentioned Stratechery does some kind of link counting like that with the podcast feed. It's a good point that some amount of unauthorised sharing can be a positive. The main issue is it's hard to control without also having false positives, where the paying subscriber is annoyed by their service being revoked, having to re-auth, etc.