lam
lam on Hacker News
Why was this down-voted? S/he seems to be making valid comments.
To find cofounders, may I suggest that you add in your profile your interests and some ways to reach out to you (e.g., email)?
Hi there. I am trying to reach you to ask about sclerals. Would you DM please? gmail: vinhvlam
It's for softening. The process breaks up the meat fibers both for easier chewing and for absorbing your saliva into the fibers. The latter makes it tastier when you chew it longer.
You can find similar dried fish / squids in Korean and Vietnamese grocery stores. Roast them slightly and they go really well with beers.
In another thread discussing BLE, you mentioned your profile contained your email addr. I checked your profile and couldn't find it -- maybe it's not made public? Would love to follow up. My email is in my profile.
Which BLE chip do you use? On the nRF51, it actually remaps -40dBm to -30dBm. With the newer nRF52, you can use NFC for OOB authentication for more security. I'd love to know more what you're working on.
I had the same problem as you have. I think you may be delighted to see what I have built. DM me
[email protected].
Hi. I think you may be delighted to see what I have built. I would love to get your thoughts on it if you're in a related field. I can also let you try it if you'll give me feedback. How can I reach out to you? My contact is my username @opdig.com.
Hi. I've got something to show you. I have the same problem as what you describe, and that's the inspiration for what I've built. I can let you try it if you'll give me feedback. How can I reach out to you? My contact is my username @opdig.com.
Some VCs do not recommend companies to go thru the crowdfunding route early on because of the distraction involved. I wonder if you would share your thoughts on what kind of companies should or should not try crowdfunding.
This is great for diff'ing Gerber files or images of them.
This is just an FYI. The Android issue you pointed out is actually an app issue. In Android, there is a mechanism for saving the state of your app, so that you can get back to the same place when you switch away from and then back to the app. Some apps don't implement that (as a good practice), and it is quite annoying when you run into it. I've seen that issue often, even in apps built by large well-known companies.
I know what you mean regarding copy/paste. Maybe it is due to the touch-based interface, but it is annoying regardless of whether it is on iOS or Android.
Has anyone given presentations directly from your phone or tablet? I'd love to hear your experience with the process -- setting up, projecting, navigating, presenting.
More generally, I'd like to know if we have gotten to the point where work (maybe not yet for coding and other heavy-duty stuffs) can be done on phones and tablets, so you don't need to lug around your laptops. What are the main hindrances? Screen size?
Sorry, my mistake forgetting that HN does not have PM capability. You can email me at
[email protected], and we'll continue from there. Thanks.
Interesting thoughts. We're building a device along the line of what you're thinking. PM me and we can talk more.
Did you annotate the cardiograph manually as you watched the event? Thanks!
Interesting techniques to gather forensic info on firmware.
We depend on our FW in protecting some of our IP as we contract our HW to be built oversea. What are some good techniques to make it harder to reverse-engineer FW?
I am curious to know the current limitations to classifying other hand gestures, such as a thumb-to-middle-finger gesture. Is the limitation due to processing of (possibly alias) signals?
It's not that embarrassing if they get it to work well, write several patents on it, and then get Google, Samsung, et al to pay royalties for licensing them. On the other hand, MS could build their own wearable devices and use the technology.
Manual text input per se may not be the most important interaction with wearables. But getting this to work may be an important first step toward building, for example, a gesture-based method to interact in general with wearable devices that are resource-constraint (eg, small screen, limited voice/camera capabilities, etc).
Seems like you have some thoughts on other methods to input text when you say "we need to think of different ways to input text".
But isn't a pointer already provided by controllers like those made by Sixense already?
John Carmack said the controller is the missing link. For those who have been developing / testing DK1 or DK2, I wonder what are you thoughts on existing controllers that you've been using? What are they lacking, and what would be nice to have in a controller for VR (or AR)?
The article is not accurate in some places. E.g., some coin cells are rechargeable such as the LIR2032.
It seems like a better solution to the pie-cutting conundrum is the following:
0. Given 3 children: C1, C2, C3
1. C1 gets to cut a piece but not to choose yet.
2. C2 or C3 gets to cut the remaining cake but not to choose any of the pieces yet. Let's say C2 gets to cut.
3. C3 gets to choose one of the 3 pieces.
4. C1 gets to choose one of the remaining 2 pieces.
5. C2 gets the last piece.
They're also called maestros (to disambiguate for those technically inclined). Great ones are heard instead of being seen. By the time we see them on stages, most of the things great conductors do have already been done, and they're basically metronomes. The even better ones have a showmanship in them to help the audience to appreciate the music even more. Check out (rehearsal) performances by Szell, Solti, von Karajan, and our very own Michael Tilson Thomas.
Maybe it's a good time to update some of those figures. Eg, NFC range now goes up to 10cm-12cm or longer. Also, it would be nice to include power consumption from the ucontrollers that are used with those wireless transmitters to be more representative.
That's because you're using Chrome?
Stupid engineer...just draw the thing in an 11-dimensional space, and he would have gotten transparency and perpendicularity. No wonder he got talked down by management.
Good start in pointing out those disparate UIs. As you have pointed out, though, devs/manufacturers feel they have an incentive to create something different. From a user's POV what's needed is just one UI that he's familiar with. Maybe one solution is creating a UI (HW/SW/etc) that knows how to map functionalities automatically for different devices/apps.