Possible duplicate thread https://news.ycombinator.com/item?id=21606188
Google Kills Cloud Print
81–90 of 567 posts
Re: Google Kills Cloud Print
#82We very nearly built our app's printing subsystem on Google Cloud Print, but went with PrintNode instead. So glad, PN has been great to work with.
Re: Google Kills Cloud Print
#83Currently one of two on the front page: https://news.ycombinator.com/item?id=21606188 .
Re: Google Kills Cloud Print
#84Currently one of two on the front page: https://news.ycombinator.com/item?id=21606049 .
Re: Google Kills Cloud Print
#85I'm confused on what the replacement is. Historically, ChromeOS hasn't been able to print at all unless using Google Cloud Print in some form. To my knowledge there are two existing forms: * a Google Cloud Print-ready printer, or * a computer that can run Chrome and bridge non-Google Cloud Print-ready printers to Google Cloud Print.[0] So the ancient WPS printer in my garage is entirely unsupported without deploying…
The article link takes you to the "Google Chrome Enterprise Help" section of their support site, so all the help articles linked in there are going to be geared towards Chrome Enterprise. Maybe you'll have better luck finding answers in the "Chromebook Help" area? https://support.google.com/chromebook/answer/7225252?hl=en&r...
That's link [3] in my comment. That appears to be the new CUPS capabilities that Google has added to ChromeOS. Excited to try it out.
Re: Google Kills Cloud Print
#86I know Microsoft gets a lot of flak for their historical support of legacy systems, but on the flip-side it means that as an enterprise you trust that they won't abruptly deprecate something you use.
Re: Google Kills Cloud Print
#87Whatever happened to good old CUPS? Why did they have to introduce so many layers including Google's servers between the user and the printer?
CUPS is exactly what Google is switching Chrome OS to, as a replacement for Cloud Print. But the reason to have Google's (or someone's) servers involved is so that you don't need to be on the same network (e.g., you can print to your home printer, behind a firewall/NAT, while you're at a coffeeshop, also behind a firewall/NAT).
We previously had one of those ol Reliable Brother printers that would last for a decade. When we last moved, we left it behind and on the rare occasions we need to print something we email the doc to a FedEx email address and pick it up from the printer at FedEx office (you enter a unique hex code to retrieve after dipping your card for payment).
It seems like the use cases of printing to your home printer from anywhere is few and far between.
Re: Google Kills Cloud Print
#88What are some other solutions for securing the network connections between computer and printer?
Are there any good and reasonably-inexpensive network-enabled printers with e.g. LetsEncrypt SSL/TLS certs and SSO/LDAP/AD/WebID/DID authentication and authorization support in actively maintained firmware?
Could Cloud Print support (with private servers) just be merged into CUPS now?
Re: Google Kills Cloud Print
#89” We recommend that over the next year, you identify an alternative solution and execute a migration strategy.” Another Google product killed, another migration strategy to execute. What's next?
Quit Google and start paying for services that you value.
I thought that service was part of the Google Enterprise suite (i.e. a paid service)
Re: Google Kills Cloud Print
#90Whatever happened to good old CUPS? Why did they have to introduce so many layers including Google's servers between the user and the printer?
CUPS is exactly what Google is switching Chrome OS to, as a replacement for Cloud Print. But the reason to have Google's (or someone's) servers involved is so that you don't need to be on the same network (e.g., you can print to your home printer, behind a firewall/NAT, while you're at a coffeeshop, also behind a firewall/NAT).
Does CUPS support securely printing over the network, or can you only do it with a VPN?