Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Kills Cloud Print

support.google.com

Post reply on HN
Print view View original

51–60 of 567 posts

Re: Google Kills Cloud Print

#51

Post by tyingq »

londons_explore wrote: post #50
tyingq wrote: post #24

Would be nice if they could open source it, though I suppose it depends on Google internal frameworks and services none of us has.

I think they should opensource it in a non-compiling, non-working state, as a gesture of openness. I bet someone would go to the effort of patching it up and getting it to run. Only disadvantage is probably that "cloudprint.google.com" is probably hardcoded into millions of printers worldwide, so even if you could run it on your own server, your printer will never work with it.

Smart DNS relay at the router...

Re: Google Kills Cloud Print

#52

Post by londons_explore »

tyingq wrote: post #51
londons_explore wrote: post #50

Earlier quoted context omitted.

I think they should opensource it in a non-compiling, non-working state, as a gesture of openness. I bet someone would go to the effort of patching it up and getting it to run. Only disadvantage is probably that "cloudprint.google.com" is probably hardcoded into millions of printers worldwide, so even if you could run it on your own server, your printer will never work with it.

Smart DNS relay at the router...

Would Google be happy to sign HTTPS certificates for anyone to spoof cloudprint.google.com though?

Re: Google Kills Cloud Print

#53

Post by tyingq »

londons_explore wrote: post #52
tyingq wrote: post #51

Earlier quoted context omitted.

Smart DNS relay at the router...

Would Google be happy to sign HTTPS certificates for anyone to spoof cloudprint.google.com though?

Ahh, yeah. But I wouldn't be surprised if many printers skipped client side validation.

Re: Google Kills Cloud Print

#59

Post by geofft »

blantonl wrote: post #55

I wonder what this means for the Google Chrome hardware ecosystem...

https://support.google.com/chrome/a/answer/9633006

Chrome OS now has basically full-featured support for CUPS like a normal Linux machine, so you no longer need Cloud Print to print to local printers, and they're adding features to let you use a remote CUPS server.

Re: Google Kills Cloud Print

#60

Post by ianhawes »

My business includes printing, signing, and mailing certain documents, so it was crucial for our efficiency to automate the process of printing.

Our first "fancy" printer included support for Google Cloud Print - except it would periodically "deauthenticate" and require manual setup, which in turn would change certain printer IDs that we needed to send jobs to the printer.

Our next "fancy" printer from Xerox also included support for Google Cloud Print. For whatever reason, we could never enable Google Cloud Print on that model.

We switched to PrintNode and have never looked back. We were able to integrate our label printers with PrintNode as well, so we could automate the process of printing shipping labels. The biggest downside is that we needed a dedicated computer (server in our case) to be connected to the printers in order to route the PrintNode jobs. Not the biggest downside in our case, but to its credit, Google Cloud Print usually connected directly from the printer.

Post reply on HN