TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Why is communication among physically nearby devices still impractical?

23 pointsby mmrasheedalmost 10 years ago
Why is peer to peer ad hoc communication among physically nearby commercially available end user devices still impractical in the 21st century? Why 5+ smart devices sitting on my desk and 20+ smart devices around my house can&#x27;t communicate, sync or exchange information without going through servers thousands of miles away? What stops companies implementing simple both way fm radio, or ad hoc wlan communication, or mesh of all the smart devices? Even, IoT which once came with the promise to remove this digital divide is now forming on infrastructure centered model. Smart devices now a days mean always-connected-to-the-infrastructure devices. What is the reason behind the huge gap between physically nearby and digitally nearby for today&#x27;s smart devices?<p>Possible reasons that come to my mind are-<p>. Technically not feasible.<p>. Significantly less value from business perspective.<p>. Government(s) discourage companies to improve significantly in peer to peer ad hoc technology for security reasons.<p>Any idea? What&#x27;s going on?

8 comments

icefoxalmost 10 years ago
Bonjour on the mac was really cool when everyone was implementing it. I could goto a conference and open iChat and instantly be able to chat with anyone else in the room. I could browse photos taken by my wife at home that were on her computer. I had a little mp3 &quot;radio&quot; that would play music from local users that had itunes (or itunes like) running. My router would just appear in my browsers list of local devices. Interacting at home was nice and handy, but interacting out in public was where it just magically &quot;worked&quot;.<p>I am going to say that the cloud killed this. If companies can get you to interact with your friends and family in your own house through their cloud service than they get a lock in strategy which is a bit of an incentive to kill their local stuff. It also doesn&#x27;t help that the major device that you would like to have talking is your cell phone which has a major company behind it pushing their cloud for all it is worth.
fragmedealmost 10 years ago
It&#x27;s there, if you look. AirDrop between Apple devices, for example, seems to do just fine.<p>DLNA orchestrates media between disparate (non-Apple) devices as another example. My desktop downloads a video, my NAS shares it, I press play on my Android phone, and the video is output on the TV.<p>So my various devices <i>can</i> talk to each other, but it took Sony and Intel an untold amount of resources to achieve. For something as simple as copy and paste of text, there&#x27;s no such body dedicated to making that work.
评论 #9642185 未加载
oppositelockalmost 10 years ago
Interoperability is a lot of work, and requires agreements on interchange formats, which is even more time consuming, and it won&#x27;t sell more devices, and once you have this, you now have to worry about security.<p>Technically, it&#x27;s certainly feasible and you do have specialized deployments where devices use mesh networking.<p>Governments don&#x27;t really limit peer to peer tech.<p>There&#x27;s simply better return for R&amp;D dollars developing other features.
codeonfirealmost 10 years ago
Mobile device makers don&#x27;t want it. In their mind each person has one device. A person with five devices is not their target market. Users don&#x27;t want it. They probably have one device and don&#x27;t want to worry that someone else is thumbing through their pictures. There is also no compensation system for expending energy to carry ad-hoc traffic. If I have a bottle of water in the middle of the desert I am going to charge a large amount for it. If I have a mobile device far from a city I want to charge a lot to transfer ad-hoc traffic. There is hardly any use case where users want to communicate with random nearby people, so the ad-hoc traffic will usually be through traffic.
jefflinwoodalmost 10 years ago
I built a peer-to-peer ad-hoc iOS app based on multipeer connectivity called MapRhino that&#x27;s meant for use in the car on road trips - that and airplanes are basically the only places left with no reliable wifi&#x2F;network connections that people gather.<p>Maybe there are a few other use cases, like large outdoor music festivals with overloaded connections, but there just isn&#x27;t a real use case for most of these services.<p>Come up with a compelling use case for peer-to-peer&#x2F;mesh technology, and I think you&#x27;ll see widespread adoption.
zeeedalmost 10 years ago
there&#x27;s security and then there&#x27;s maintainability and scalability. it&#x27;s much easier to maintain and fix a centralized (cloud-based) tech than it is to release a stable bluetooth stack. and when it&#x27;s centralized, there&#x27;s a business case.
j_salmost 10 years ago
The recent discussion of the Google Tone Chrome extension¹ proved that technical infeasibility is not the issue.<p>¹<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9575291" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9575291</a>
mottialmost 10 years ago
There&#x27;s a lot of work and movement on <a href="http:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;Wi-Fi_Direct" rel="nofollow">http:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;Wi-Fi_Direct</a>