Client-side content encryption

#1

Post by abraham » Tue, Apr 28, 2020, 5:40 AM UTC

Client-side content encryption
blog.amp.dev

Re: Client-side content encryption

#2

Post by freakynit » Tue, Apr 28, 2020, 6:16 AM UTC

One more attempt by Google to gather more control over content publication and consumption. Idea nonetheless in nothing new.

The only thing that makes this practical is Google's existing know-how of billions of it's users, and offloading of content encryption on server-side using Google's services

Re: Client-side content encryption

#3

Post by asplake » Tue, Apr 28, 2020, 6:18 AM UTC

Not so much user-friendly as normalising the user-hostile

Re: Client-side content encryption

#4

Post by thereyougo » Tue, Apr 28, 2020, 6:19 AM UTC

The article talks too much about the problem, and when it comes to solving it, it gives very shallow information.

Re: Client-side content encryption

#5

Post by endgame » Tue, Apr 28, 2020, 6:33 AM UTC

Buzz off, Google. Stop making the web worse.

Re: Client-side content encryption

#6

Post by kohtatsu » Tue, Apr 28, 2020, 6:36 AM UTC

Woo DRM for websites! Thanks Google!

Re: Client-side content encryption

#7

Post by mirimir » Tue, Apr 28, 2020, 6:45 AM UTC

kohtatsu wrote: post #6

Woo DRM for websites! Thanks Google!

Indeed, just what we needed. /s

So why not instead come up with a workable micropayment system?

Re: Client-side content encryption

#8

Post by noizejoy » Tue, Apr 28, 2020, 6:47 AM UTC

I find it quite hostile to send user inaccessible content down the pipe, thereby cluttering up bandwith and local storage.

Re: Client-side content encryption

#9

Post by three_seagrass » Tue, Apr 28, 2020, 6:54 AM UTC

noizejoy wrote: post #8

I find it quite hostile to send user inaccessible content down the pipe, thereby cluttering up bandwith and local storage.

Prefetching content is a W3C standard.

The user is also trying to access that content so they probably don't find preloading it aggressive, especially if they're on a low-bandwidth connection and they don't have to load the page twice.

Re: Client-side content encryption

#10

Post by sarakayakomzin » Tue, Apr 28, 2020, 7:03 AM UTC

three_seagrass wrote: post #9

noizejoy wrote: post #8

I find it quite hostile to send user inaccessible content down the pipe, thereby cluttering up bandwith and local storage.

Prefetching content is a W3C standard. The user is also trying to access that content so they probably don't find preloading it aggressive, especially if they're on a low-bandwidth connection and they don't have to load the page twice.

> Prefetching content is a W3C standard.

When that content is valid for the user... fetching garbage content over a network isn't "pre" anything.