Google Makes Push To Turn Product Searches Into Cash (reuters.com)

Reuters reports of how Google is working to turn product searches into cash by partnering with some of the largest retailers in the United States: Under a new program, retailers can list their products on Google Search, as well as on the Google Express shopping service, and Google Assistant on mobile phones and voice devices. In exchange for Google listings and linking to retailer loyalty programs, the retailers pay Google a piece of each purchase, which is different from payments that retailers make to place ads on Google platforms. The listings will appear under sponsored shopping results and will not affect regular search results on Google, the company said. Google's pitch to retailers is a better chance to influence shoppers' purchasing decisions, a move that is likely to help them compete with rival Amazon. Google hopes the program helps retailers capture more purchases on desktop, cell phones and smart home devices with voice search -- the next frontier for e-commerce. The previously unreported initiative sprang from Google's observation that tens of millions of consumers were sending image searches of products, asking "Where can I buy this?" "Where can I find it?" "How can I buy it?" "How do I transact?" Daniel Alegre, Google's president for retail and shopping, told Reuters exclusively.

Comments

Re:So much Google

[rtb61]

I am starting to forget google even exists I am having to look it up https://duckduckgo.com/?q=goog... all of the time. It's a choice, be the consumer slave or make digital companies your bitch, your choice, digital slave or ifreeman ;D.

Re:Need Linux help

[Anonymous Coward]

Wayland (display server protocol) From Wikipedia, the free encyclopedia Wayland Wayland Logo.svg Screenshot of a Wayland demonstration Screenshot of a Wayland demonstration Original author(s) Kristian Høgsberg Developer(s) freedesktop.org et al. Initial release 30 September 2008; 9 years ago[1] Stable release Wayland: 1.14.0[2], Weston: 3.0.0[3] / 8 August 2017; 7 months ago Preview release Wayland: 1.13.93, Weston: 2.99.93[4] Repository https://cgit.freedesktop.org/w... Edit this at Wikidata Development status Active Written in C Operating system Linux, FreeBSD, DragonFly BSD Type Windowing system Display server License MIT License[5][6][7] Website wayland.freedesktop.org Wayland is a computer protocol that specifies the communication between a display server (called a Wayland compositor[clarification needed]) and its clients, as well as a reference implementation of the protocol in the C programming language.[8] Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open community-driven project with the aim of replacing the X Window System with a modern, simpler windowing system in Linux and other Unix-like operating systems.[8] The project's source code is published under the terms of the MIT License, a permissive free software licence.[9][5] As part of its efforts, the Wayland project also develops a reference implementation of a Wayland compositor called Weston.[8] Contents 1 Overview 2 Software architecture 2.1 Protocol architecture 2.2 Protocol overview 2.2.1 Wayland core interfaces 2.2.2 Wayland extension interfaces 2.3 Extension protocols to the core protocol 2.3.1 XDG-Shell protocol 2.3.2 IVI-Shell protocol 2.4 Rendering model 3 Comparison with other window systems 3.1 Differences between Wayland and X 3.2 Compatibility with X 4 Wayland compositors 4.1 Weston 4.2 libinput 4.3 Wayland Security Module 5 Adoption 5.1 Desktop Linux distributions 5.2 Toolkit support 5.3 Desktop environments 5.4 Other software 5.5 Mobile and embedded hardware 6 History 6.1 Releases 7 See also 8 References 9 External links Overview The evdev module of the Linux kernel gets an event and sends it to the Wayland compositor. The Wayland compositor looks through its scenegraph to determine which window should receive the event. The scenegraph corresponds to what is on screen and the Wayland compositor understands the transformations that it may have applied to the elements in the scenegraph. Thus, the Wayland compositor can pick the right window and transform the screen coordinates to window local coordinates, by applying the inverse transformations. The types of transformation that can be applied to a window is only restricted to what the compositor can do, as long as it can compute the inverse transformation for the input events. As in the X case, when the client receives the event, it updates the UI in response. But in the Wayland case, the rendering happens by the client via EGL, and the client just sends a request to the compositor to indicate the region that was updated. The Wayland compositor collects damage requests from its clients and then re-composites the screen. The compositor can then directly issue an ioctl to schedule a pageflip with KMS. In recent years,[when?] Linux desktop graphics has moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance".[10] Kristian Høgsberg could have

Who are these people

[mukinrestak]

Who are these people that search for "How do I transact?"

I'm willing to bet not one person on God's green earth has EVER searched google for "How do I transact?"

And if if Google can tell me how to transact, can they follow through and tell me how to transact my transactable transactions in the most self transactualizing transactivations of my transactionless office? I didn't think so!