3 ms·

> There is now way to know if you have +1'd a page without sending your unique id with. localStorage or asking which URLs have been plus 1'd, not the other way

by nikcub 15y ago

> There is now way to know if you have +1'd a page without sending your unique id with. localStorage or asking which URLs have been plus 1'd, not the other way around. There are plenty of ways of doing it without sending a request back to google on ever. single. page. load. I found the disclosure about all website visiting being sent to Google only after looking for it and clicking through some pages. 95% of users will never find that since being alerted to it isn't part of the standard install flow.

abraham 15y ago
> localStorage or asking which URLs have been plus 1'd, not the other way around. There are plenty of ways of doing it without sending a request back to google on ever. single. page. load. This introduces all kinds of issues with complexity of having to support multiple storage locations, and inconsistency/sync lag caused +1'ing pages on multiple computers or buttons from the page rather then the extension. If I have two computers and +1 a few pages with one then switch to the other it would either have to download a list of all pages I +1'd. Which could get up into the thousands or tens of thousands or some sort of complex pagination, diff, merge feature. It just isn't worth it.
- vilhelm_s 15y ago
  Chrome already does all that for bookmark syncing. The list of +1'ed websites will never grow _very_ large, because it is created one manual click at a time by a single user. 10,000 urls is only about a megabyte, and if you send diffs you'd rarely have to download more than a small fraction of them.
gcl2 15y ago
I don't think you've ever designed a scalable webapp that requires synchronized user data to be available across browsers, platforms, sessions, etc. It's a basic fundamental tradeoff decision that all app developers have to make - store client-side or server-side and if you want any kind of sanity for the user, it's usually better to store server-side.

by nikcub 15y ago

abraham 15y ago

> localStorage or asking which URLs have been plus 1'd, not the other way around. There are plenty of ways of doing it without sending a request back to google on ever. single. page. load. This introduces all kinds of issues with complexity of having to support multiple storage locations, and inconsistency/sync lag caused +1'ing pages on multiple computers or buttons from the page rather then the extension. If I have two computers and +1 a few pages with one then switch to the other it would either have to download a list of all pages I +1'd. Which could get up into the thousands or tens of thousands or some sort of complex pagination, diff, merge feature. It just isn't worth it.

vilhelm_s 15y ago
Chrome already does all that for bookmark syncing. The list of +1'ed websites will never grow _very_ large, because it is created one manual click at a time by a single user. 10,000 urls is only about a megabyte, and if you send diffs you'd rarely have to download more than a small fraction of them.

gcl2 15y ago

I don't think you've ever designed a scalable webapp that requires synchronized user data to be available across browsers, platforms, sessions, etc. It's a basic fundamental tradeoff decision that all app developers have to make - store client-side or server-side and if you want any kind of sanity for the user, it's usually better to store server-side.