sushant2mainali

One of the main feature is that it is free for developers and end users which we hope will attract developers. Also we plan to cold call small-medium sized businesses to get to our first 100 customers. Along with that we will invest time and resource to be active in blogs and forums and programmers circle so that more hobbyists and casual programmers are attracted to our platform.

got a rejection now.

We have not received any email either.

thanks. will definitely check out the conference.

Ok. Thanks.

Thanks for the feedback.

Do the people who are not accepted also receive an email? Or if you don't receive an interview email, does it imply that you did not get selected to interview?

nice! wanted to install mysql-python and was stuck here!! Thanks.

Waiting impatiently. Please could someone give me some feedback on my idea and the name. Is someone working on something similar? Any ideas on what features I should try to implement on day one. Thanks.

https://news.ycombinator.com/item?id=11448299

I was wondering how this is different from what Westlaw from thomson reuters is doing.

http://thomsonreuters.com/en/products-services/legal/large-l...

May be you could compete on price? Or what is your strategy?

As of now we here is our plan: 1. Devices can either be always connected ( using websockets / ajax / any other technology) or 2. Devices can define what is the maximum time before which a device is deemed as disconnected ( could be secs / hours / days). If they don't send data in a certain period of time or if they don't respond in a certain period of time. 2.a. For devices following this - the time will depend on internal memory and how much they can store and process, as whenever they have connection, they can send time stamped data in bulk. We need a way to determine how to acknowledge since we may lose connection after getting the data but before sending ack. At that point, we may just discard the data ( but there might be a better solution ) and device can send data ( not very effective). 2.b. The developers can determine the timeout in sending commands and also do they want to queue up all pending commands or just send the latest one.For instance, if I want to turn on something, and I send 100 'on' commands; do we have to send 100 of them or just the last one and for how long is the command effective before it is determined a timeout and we can flag a connection lost. The developer will be able to define all of that and for starters with simple application, they can just leave all that to default as most of the times it will just work.

How the h/w implements it, is up to the hardware developers ( we plan on developing some ourselves using different technologies and hardware ( raspberry PI, Intel Edison, some using sim cards, etc and using different protocols) and others can leverage off of that). The server side: receiving data, sending data, analyzing data, displaying data and detecting disconnection is what we will handle and the phone app / website for all of that.

In my opinion IP addressing may still be feasible for some time no (thanks to IPV6). But I clearly see a future where the internet and its protocols that exist now not working for connected devices. This internet was created with humans in mind and now by adding protocols like MQTT etc, it has tried to become a hybrid system. I would love to see a new network just for devices.

And as far as going into interfaces for VR, we do not have plans for that yet. We plan to support data streaming though. As a startup, we don't have the resources required for that. But if there is demand and we grow, we would love to look into that. Business is all about evolving.

We don't have plans for that right now. However we have plans for data streaming. Good suggestion though. We can keep that as a feature we might want once we start growing. Right now, with our resources, we might not have the bandwidth to implement that. Surely a future feature we can look into if it generates enough interest.

Thanks for your feedback. I like the private/public idea and that is what we are doing. However, we are implementing it slightly differently and that is subject to change as we go along. You don't share a device with your friends. You become friends with devices (and IOs of that device), which is a unique concept. So each device has its own friends vs friends sharing their devices with friends.

May be National Geographic can plant an Internet Connected thermometer in a volcano and we might have many many friends/followers of that device.

So, if I have 10 devices ( each with 3 data points); each device might have different friends with different levels of access to each of the data points on the 10 devices. The devil lies in the implementation though. If we make an excellent interface to manage the sharing and becoming friends with devices, we will win. And the sharing becomes crucial not for home devices but for commercial devices like may be a weather station at an airport (which the entire city may be interested) or like I mentioned the weighing machine of Kim Kardashian ( lol ) or may be goods on a commercial truck, the real time location of which is needed by 7/30 employees in a company. I want to develop this framework into something more than just for devices inside a home (which is where a lot of IOT focus is right now).

Since we would have the data, we can do stuff with it. Have not thought about what, but we plan to make it to good use.

Thanks for feedback on the name, we love positive criticism. We will look into that and research more.