Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
__sy__
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
__sy__
3y ago
She's pretty cool! She's former math teacher, then PhD in stats, reconverted to scientific computing programmer (CERN, Astronomy Labs...etc), and then eventually moved over to large system / mainframe stuff. She also spent a
32.
▲
by
__sy__
3y ago
Tbh, probably not. I'll give you a few thoughts for consideration. Matter is a device-to-device protocol within a local Thread network. It's solid for getting one device to tell another device on the same Thread network to perform
33.
▲
by
__sy__
3y ago
oh! I have many, many thoughts on the W3C WoT :) At the start of Seam, we spent a lot of time reading those specs and absorbing some of the key ideas expressing in its core documents. As a result, you'll see a lot of W3C WoT terminolog
34.
▲
by
__sy__
3y ago
What if I told you that before Thread, the original comm protocol layer at Nest was called—wait for it—WEAVE!
35.
▲
by
__sy__
3y ago
awh thanks! that actually means a lot! tbh we put a lot of personal efforts into it but it's still pretty rough. We don't have a marketing or visual-design person so we kind of had to think and execute through stuff ourselves. We
36.
▲
by
__sy__
3y ago
yep! It's actually on my desk right now! ( https://imgur.com/a/3pAYfnx ). Colin, EE on our team, is building a test fixture for it in order to correctly simulate certain scenarios on it. I think we'll have the
37.
▲
by
__sy__
3y ago
This too. It's pretty important we focus on building a viable business (see current funding environment). Contrary to popular belief, building open source isn't free and takes time away from that effort. You have to make sure your
38.
▲
by
__sy__
3y ago
Duly noted on using more assertive language! I appreciate the advice :) Viam looks really cool! We didn't know about it. On making Seam more open, it's definitely not off the table. We'll have to balance this with device manu
39.
▲
by
__sy__
3y ago
We build a lot of infra/async logic to make controlling devices more reliable, handle long-running jobs...etc. So a simple library wouldn't quite work. With respect to the value prop, most of our API customers are software apps th
40.
▲
by
__sy__
3y ago
Home Assistant (which I personally use) is solid for personal use cases. But our customers generally aren't trying to connect to their own devices. They're trying to connect to their end users devices (e.g. Ecobee thermostat) and
41.
▲
by
__sy__
3y ago
Many of the integrations you'll see in Home Assistant are reversed-engineered. Usually this is done by looking at the mobile apps of many of these devices and extracting credentials, certs...etc. A few manufacturers don't love thi
42.
▲
by
__sy__
3y ago
Most of our customers today are startups and a handful of large enterprise customers. Generally they're trying to connect and control their app users' devices. A common use case is smartlock & thermostat control for Airbnb res
43.
▲
by
__sy__
3y ago
Depends on the device/brands. Z-Wave/Zigbee...etc devices will let you communicate directly with them locally. We contributed a bunch to ZWave-js and it's a great library for doing exactly that. For manufacturers' clouds
44.
▲
by
__sy__
3y ago
yes! I was discussing this exact idea yesterday with a customer with a bunch of devices locked into an old software platform. Ideally we'd want to provide both open firmware and an open backend.
45.
▲
Launch HN: Seam (YC S20) – API for IoT Devices
158 points
by
__sy__
3y ago
|
71 comments
46.
▲
by
__sy__
3y ago
I'd say much of the work to improve silicon nanowire batteries et al. happened 2010 onward. I think pre-2010, it was mostly strong proof of concept with okay-cycling performance. source: I was in the Cui group.
47.
▲
by
__sy__
4y ago
Another benign explanation: all the recruiters have been laid off.
48.
▲
by
__sy__
4y ago
Pretty common. You can check out Skyvector "World Hi" [1] to get a sense of intersecting flight routes. [1] https://skyvector.com/
49.
▲
by
__sy__
4y ago
legal, yes. judicious, no.
50.
▲
by
__sy__
4y ago
I'm terrified at the thought of all this hollow, low-on-details content that's about to hit the internet. Interestingly, if this degrades Google's search result quality, it could be an opportunity for someone else to create a
51.
▲
by
__sy__
4y ago
edit: parent comment asked "not sure what value Arm is getting from this" but this was later removed. My comment below was answering that. Tony is one of the few people out there who’s got a deep and broad understanding of how all
52.
▲
by
__sy__
4y ago
Second that. Also what guardrails look like for it :)
53.
▲
by
__sy__
4y ago
you win the internet.
54.
▲
by
__sy__
4y ago
While on the topic of Starlink, I wanted to share this cool Youtube video [1] I watched tonight on how it works (PCBA design, beam forming, orbital velocity, up/downlink bandwidth as a result...etc). It's a bit long but has some g
55.
▲
by
__sy__
4y ago
what a pleasant surprise seeing Root here! They're one of our investors. The entire firm is made up of engineers who've shipped consumer hardware products, rocket engines, dev tools...etc. They also happen to be genuinely good peo
56.
▲
by
__sy__
4y ago
Agreed. But given that legacy dispatch infra is bad/inefficient, you need rider density to support the quality of service of a London.
57.
▲
by
__sy__
4y ago
Great. Now try Tallahassee, Florida. Or Liverpool. Or the myriad of other non-global/dense city with limited public transportation infrastructure especially during off hours.
58.
▲
by
__sy__
4y ago
from the RFC: > Base58 is designed with a number of usability characteristics in mind that Base64 does not consider. First, similar looking letters are omitted such as 0 (zero), O (capital o), I (capital i) and l (lower case L). Doing so
59.
▲
by
__sy__
4y ago
**shakes fist at sky/apple**
60.
▲
by
__sy__
4y ago
this is an excellent answer. dang, Thanks as always!
More ›