Live data from Hacker News

Google Home

home.google.com

411–420 of 468 posts

Re: Google Home

#411

Please, please, please be a completely open, extensible platform... I want to be able to control my Apple TV with my Google Home device. I want to be able to control my Phillips Hue and LiFX bulbs. I want to be able to build my own custom home automation server endpoints and point my Google Home commands at them. I want to be able to remote start my car with a voice command. I want to be able to control my Harmony re…

> If Google Home can deliver on these points, I would switch from Amazon Echo in a heartbeat.

I think it will mostly deliver ads.

Re: Google Home

#412
post #199

Google, thanks for shutting down Freebase.com on 2 May 2016. By taking it offline, and using it (Knowledge Graph) for Google Home you effectively locked out all competitors. WikiData is a far cry and a fraction of the size of what was Freebase. Freebase was a large collaborative knowledge base consisting of data composed mainly by its community members. It was an online collection of structured data harvested from ma…

Freebase data dump is available for download for free. And so is Wikipedia and Dbpedia. And so i common crawl and webdatacommons dumps

What are you doing with that ?

- https://developers.google.com/freebase/#freebase-rdf-dumps - http://wiki.dbpedia.org/ - http://webdatacommons.org/ - https://dumps.wikimedia.org/

Re: Google Home

#413

Earlier quoted context omitted.

I have only two wishes: > Please, please, please be a completely open, extensible platform... That's one. The second one is, please make it self-hosted. No cloud bullshit. I know I'll probably never live to see the second one coming true.

> please make it self-hosted I rather suspect that the knowledge graph it uses is a rather hefty dataset. Probably not suitable for a home installation. And how would you keep it up-to-date without the cloud? Would you have it scrape websites and consume feeds itself?

> Would you have it scrape websites and consume feeds itself?

Let me introduce you to PuSH: https://en.wikipedia.org/wiki/PubSubHubbub

Re: Google Home

#414
post #391

Earlier quoted context omitted.

The email we've all been using is not all open-source and end-to-end encrypted, though there are open-source clients, some of which support end-to-end encryption.

em... the only thing that is valid to support end-to-end encryption is the end client. Otherwise it's not end-to-end.

Yes, and the end clients many people have been using don't support end-to-end encryption. So, we haven't all been using a e2e encrypted system already. We've been using a system over which e2e can be layered, and very few have been layering that over it. And many using it in a way where even with an e2e protocol, it wouldn't be secure, since they are using an third-party, remotely provided client that can be changed without their notice (webmail).

Re: Google Home

#415
post #390
post #348

Earlier quoted context omitted.

"In restricted grammar mode" That's a key limitation, though. But we're getting close to the point where you can do some of this. For example - http://arxiv.org/pdf/1603.03185.pdf - LSTM speech recognition running on a Nexus 5. The more serious problem with this is that it's going to be expensive -- and somewhat wasteful. There's a lot of pressure to keep consumer devices as cheap as possible, and the cloud is an awe…

> "In restricted grammar mode" > That's a key limitation, though. Why would it be? Sophisticated exchange of theorems and not essential for this scenario, is it?

Depends if you want to support things like "OK Google, invite Pawel Moczydłowski to my barbecue" and "OK Google, how do you spell d'Artagnan?"

Re: Google Home

#416

Earlier quoted context omitted.

I'm thinking my nexus will be my last Android device, not decided yet what I want to replace it with but dumb phone is looking likely, I'm either at home, the office or somewhere I can use my laptop so don't really have the need for a tablet, I might been able to google the odd thing now and again when out and about but that's a once or twice a week thing for me. I've come to resent carrying a phone all the time, I r…

What I like about the tablet is the size, the battery life, the switching between landscape (generally: composing w/ keyboard) and portrait (generally: reading long-form content) modes. A 10" form factor plus bluetooth keyboard is sufficient for some Real Work (though that's hugely crippled by system and software limitations). As a comms device, on a sufficiently fast WiFi/broadband connection, it's also useful. I've…

The external storage thing is an accident of history, with perhaps some MAFIAA meddling.

When the first Android device shipped, all internal storage was dedicated to OS and apps. But OEMs wanted to advertise that they had X gigs onboard. And thus they started partitioning internal storage, and mounting one part as if it was removable memory.

Problem is that apps could not go on removable memory, so people bought a device only to find that a few apps was enough to max out that side of the partition.

And thus Google came up with "move to SD".

But then that got into trouble with USB data transfers, as the "SD" had to be unmounted on the Android side before it could be mounted by the PC over the cable.

So somewhere around 3.x Google adopted MTP, and union mounts to emulate a FAT partitioned SD (for legacy reasons).

But at the same time they introduced new access permissions, but reserved write permission to actual removable storage for system level apps. Thus you could use your PC to transfer music and such onto a SD, but you could not officially do so from within Android. Various OEMs, Samsung for example, modified the permissions file so that their devices retained the old behavior.

Since then Google has in fits and starts modified the MTP support so that it can also be used by internal apps to write to removable storage without having to deal with permissions. At the same time they have tried to lock down access to the "SD" even further as various dumb app devs have used it to store sensitive user data for any other app to see.

Thing is that going via the MTP subsystem invites DRM, as the apps talk to a database that then talk to the FS. And that database can be incomplete, or the subsystem can outright lie to the apps. And it so happens that Google adopted MTP along the same time as they introduced Play Music and Play Movies.

Then again, the consumer UI/UX designers have long been tilting the windmills over the whole files and folders thing. For some reason they see it as a failure of UX, and thus something that needs to be at least hidden from the user, if not outright abolished. See numerous attempts at replacing files and folders with a grand database of metadata, that will "magically" pull out everything you have stored related to that company project or aunt Tillie as needed.

Re: Google Home

#417

Earlier quoted context omitted.

> (Sorry for this quasi-manifestoish tone...) Don't be. I think it was very well said, and while I've been a bit of a Free Software hippie for a while it keeps hitting me over and over just how far ahead they saw.

It's amazing to me that free software is still strong after all of these years. I can remember back in the early 90s being fed propaganda from my college professors about "the communist" Stallman and his friends. They had made plenty of enemies back then and countless more since. Yet, they kept to their principles and moved things forward to the benefit of billions of people.

They made enemies, because oh so many wanted to bootstrap from academia into business by putting proprietary wrappers around freely shared code.

But the GPL basically forbids that.

Re: Google Home

#418

Earlier quoted context omitted.

>But do you think that free software can keep up against these giants? On an algorithmic front, definitely. The key areas where free software is kneecapped against large corporate interests are in marketing, which free software has never been good at, and in training set gathering. In the case of the latter, google, facebook and microsoft have a major advantage in gathering data to do things like improve accent recog…

Don't forget UI and UX, in general. The free software pipeline has traditionally been wacky in this front, and is something that matters a lot to users.

I think the whole UX thing is overrated. People will like what they are accustomed to, and dislike what they are not accustomed to. Just look at all the flak Facebook gets when they move things around.

Re: Google Home

#419

Earlier quoted context omitted.

Don't forget UI and UX, in general. The free software pipeline has traditionally been wacky in this front, and is something that matters a lot to users.

I think the whole UX thing is overrated. People will like what they are accustomed to, and dislike what they are not accustomed to. Just look at all the flak Facebook gets when they move things around.

Or look at medical secretaries and their opinions about the new "user friendly" interfaces that replaced the keyboard driven programs of previous generations.

Re: Google Home

#420

Earlier quoted context omitted.

It's scary how close this is to being one of 1984's telescreen devices. I might even argue that it basically _is_ a telescreen considering Google's previous dealings with state actors, though with some of the 451-style "you asked for this" as opposed to the 1984-style "this is forced on you".

Surely a laptop is closer? What with webcams being standard equipment and all.

Well, the laptop doesn't necessarily send everything you say near it to Google HQ.
Post reply on HN