Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
typo
  • Loading branch information
truedat101 authored Jan 27, 2024
1 parent fbd2db6 commit fefc900
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ What is the stuff in my envioronment? Compared to ten years ago, there is more

## Solution

Let's get back to basics of representing things as humans expet them. We understand visual and audible things. We understand names. We don't understand QR codes, UUIDs, or serial numbers. Common types of IoT devices should have common interfaces. No need to build custom apps per ecosystem. Special chips or protocol stacks are needed. No licensing needed. Interoperability is based in BLE, and the app keeps a database of the known universe of IoT devices so it is possible to quickly generate a UX profile to match the device. And it is up to you how to secure your device, and how to join it together with your other devices. You always have your default "hyperlocal" context available, meaning your personal space around you. There is no new ecosystem to create. Agree among your own DIY IoT devices how you want them to behave (use this software stack). Don't use this to build your mission critical rocket launcher. Use it for your personal projects. And take solace, you can stop worrying about creating an app to support your projects.
Let's get back to basics of representing things as humans expect them. We understand visual and audible things. We understand names. We don't understand QR codes, UUIDs, or serial numbers. Common types of IoT devices should have common interfaces. No need to build custom apps per ecosystem. Special chips or protocol stacks are needed. No licensing needed. Interoperability is based in BLE, and the app keeps a database of the known universe of IoT devices so it is possible to quickly generate a UX profile to match the device. And it is up to you how to secure your device, and how to join it together with your other devices. You always have your default "hyperlocal" context available, meaning your personal space around you. There is no new ecosystem to create. Agree among your own DIY IoT devices how you want them to behave (use this software stack). Don't use this to build your mission critical rocket launcher. Use it for your personal projects. And take solace, you can stop worrying about creating an app to support your projects.

With regard to data, this is a huge problem to solve with a simple solution. For the 85% of use cases where you don't need a private tunnel over the Internet into your home or car, but you just want to deal with your "hyperlocal" context, and save your data locally for future access, your phone is your best friend for this. Let it act as the sponge if it is available, to sync data locally. You can also nominate a local device to act as the data sync location. If you want to get the data out of the hyperlocal context, send it to an external cloud service. That should always be your choice! Take back control of your data, your privacy, and your security.

Expand Down

0 comments on commit fefc900

Please sign in to comment.