"Whatever is in user's browser gets signed & published to relays ".

This is the problem. For paywalled content, how can we be sure that there is no beacon stored somewhere in the page (DOM, js, html) that identifies the subscriber?

Reply to this note

Please Login to reply.

Discussion

Let's focus on regular content and cross that bridge if we get there.

The main issue is that the big services are centralized and the self-hosted stuff isn't syndicated.

are paywalling services doing that - and punishing the user for screenshotting etc?

hahahahahahahshahahaha

that’s so crazy if so. wow

They're trying everything in their power to make water not wet.

i would have for sure read that years ago, but a great reminder ty gigi

i knew they try were trying to use this on music but i didnt realise they were embedding gotcha code so they can police how the user uses their computer, and heaven forbid, copies something. fucking hilarious.

hard to imagine why they’re dying such a quick death 😂

they’re suiciding themselves. making their product shit all because they cant come to terms with the characteristics of water.

i guess we should thank them

talk about failing the ego test

I don't think the goal has ever been to make data impossible to copy. The goal is most likely to make copying certain data more difficult. DRM has done that, whether you like it or not. The industry wouldn't do it if it didn't work to some degree.

But I also hate DRM and how it works. Totally agree on that.

Futile action by a dying industry.

not a dying industry… the players will just change and the rules of engagement will evolve

How that’s Archive do it?