• 1 Post
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle








  • I remember using Mosaic on Silicon Graohics machines back in the early ‘90s. It’s was fab for the time.

    And yes, Mosaic became Netscape, became Firefox. From the wiki page at https://en.m.wikipedia.org/wiki/Netscape_Navigator

    The business demise of Netscape was a central premise of Microsoft’s antitrust trial, wherein the Court ruled that Microsoft’s bundling of Internet Explorer with the Windows operating system was a monopolistic and illegal business practice. The decision came too late for Netscape, however, as Internet Explorer had by then become the dominant web browser in Windows. The Netscape Navigator web browser was succeeded by the Netscape Communicator suite in 1997. Netscape Communicator’s 4.x source code was the base for the Netscape-developed Mozilla Application Suite, which was later renamed SeaMonkey.[4] Netscape’s Mozilla Suite also served as the base for a browser-only spinoff called Mozilla Firefox.






  • That’s because the explanation is often a bit disingenuous. There’s practically no difference between “listening locally” and “constantly processing what you’re saying”. The device is constantly processing what you’re saying, simply to recognise the trigger word. That processing just isn’t shared off device until the trigger is detected. That’s the claim by the manufacturers, and so far it’s not been proved wrong (as mentioned elsewhere, plenty of people are trying). It’s hard to prove a negative but so far it seems not enough data is leaving to prove anything suspect.

    I would put money on a team of people working for Amazon / Google to extract value from that processed speech data without actually sending that data off device. Things like aggregate conversation topic / sentiment, logging adverts heard on tv / radio for triangulation, etc. None of that would invalidate the “not constantly recording you” claim.