• Skip to main content
  • Skip to primary sidebar
  • Home
  • ActingWeb
    • ActingWeb – More In-Depth
    • The ActingWeb Reference Library
    • The ActingWeb Specification
    • The History of ActingWeb
  • Cisco Webex Teams Army Knife
    • The Army Knife Code
  • Engineering Leadership Series
    • For Developers
    • For Managers
    • For Leaders
  • Blog Posts
    • Development Processes
    • Cisco Webex Teams
    • Next-Gen Media Architecture
  • ActingWeb Support

Stuff

Greger's rantings on innovation, software development, leadership, and making great stuff

You are here: Home / ActingWeb – Bringing Internet of Things to People

ActingWeb – Bringing Internet of Things to People

actingweb logo

Remember the visions of the future where smart services on the Internet would know everything about you and advice you real time and do things for you automatically?!

Technology is no longer the limitation. The limitation is how comfortable you, and other people, are with sharing sensitive and important information about yourself and your life and with whom.  Yes, it would be über-cool if the Google location information your phone continuously tracks could make the door to your house unlock automatically when you got close, or lock the door for you when you left your home and nobody else is at home. But to make it happen, who do you need to trust? And what can go wrong?

In fact, Google hasn’t even deared to make this information available to anybody else except you.  There are just too many privacy issues (you can download it though).

faucet-actingweb-smallThink about the physical key to your house. If you give that key to somebody, they can access your entire house, whenever they want. But what if you could give the plumber a special key that only allows access to the sink, the pipes, and the master valve for the water? He wouldn’t even see what else you have in the room. If he does a great job, maybe you want him to just keep the key, so he can take responsibility for any maintenance needed? In a digital world where the plumber can “service your sink and pipes” remotely, it opens up for entirely new services.

This is exactly the core idea behind ActingWeb. Tiny applications that work for you and only you, and that can give very tailored access only to other tiny applications you trust. And you can at any time stop that access. Going back to the Google location and door lock example, a tiny ActingWeb app could give access ONLY to information about whether you are close by your home or not (and how close maybe), and a tiny ActingWeb door lock app could allow access to unlocking and locking your door. Those two apps, working only for you (your location and your door) can connect to each other, exchange information and make it happen. The two apps could live anywhere, at the door lock company, at Google, or at your home security company. The “I’m at home” app can be used by any other service you trust to know this specific information: “I’m at home, turn up the heat.” “I’m at home and it’s day time, redirect all calls to my mobile.” If you want to understand more in-depth how it works, read the More In-depth article.

Acting Web is a project Greger has been working on since 2007.  It is an approach to Internet of Things that ties things together with people.  Back in 2007, it didn’t really fly, too many technical things were immature. Since then, services like IFTTT, Zapier, and others have created connectors to tie together services and things. ActingWeb is not a service like these, but rather something that could have powered IFTTT and Zapier, i.e. a framework and a protocol for developers to tie things and people together. (Read more about the history of ActingWeb.)

The Acting Web specification has all the details of the REST protocol needed for the app to app communication, as well as the application model that enables the extreme focus on a specific user or “thing”.

The specification is backed by working code in the form of a reference implementation in python. It is also in itself an ActingWeb mini-app. The reference implementation is at all times running at https://demo.actingweb.io (you can even use it to test your own apps).

Primary Sidebar

Recent Posts

  • Why the World Needs More Female Software Engineers
  • The Two Most Common Execution Mistakes in Tech Acquisitions
  • Learn Emotional Self-Regulation In Four Steps
  • Complete re-write of the original Flutter first_app starter app post!
  • A Production-Quality Flutter Starter App (the original from July 2019)

Topic Series

acquisitions ActingWeb Collaboration Development Processes Devops Distributed System Architectural Debt Equality Innovation Leadership Next-generation Media Architecture People Management Personal Development Spark Tinkering

Categories

agile apis appengine architecture assorted browser business objectives CLUE code codecs collaboration definition devops distributed system architecture debt elasticity engineering skills feature-driven development flow debt flutter hybrid bridge IETF interoperability layering debt MCU media multistream organisational issues people protocol debt python real-time RTCWEB scheduling simulcast SIP spark SVC team dynamics technical debt telepresence TIP video video bridge video conferencing Web 2.0

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Archives

  • March 2021 (1)
  • February 2021 (1)
  • July 2020 (4)
  • June 2020 (2)
  • April 2020 (2)
  • February 2020 (1)
  • January 2020 (1)
  • October 2019 (1)
  • August 2019 (1)
  • July 2019 (1)
  • June 2019 (1)
  • August 2017 (2)
  • April 2017 (2)
  • December 2016 (2)
  • November 2016 (2)
  • October 2016 (2)
  • July 2016 (1)
  • June 2016 (2)
  • March 2016 (2)
  • February 2016 (1)
  • January 2016 (3)
  • August 2015 (2)
  • July 2015 (2)
  • November 2014 (1)
  • October 2014 (1)
  • September 2014 (1)
  • August 2014 (1)
  • July 2014 (3)
  • June 2014 (2)
  • May 2014 (1)
  • April 2014 (2)
  • May 2011 (1)
  • April 2011 (1)
  • February 2011 (1)
  • January 2011 (1)
  • December 2010 (1)
  • November 2009 (5)
  • June 2007 (2)
  • April 2007 (2)
  • February 2007 (1)
  • January 2007 (5)
  • November 2006 (1)
  • October 2006 (1)
  • September 2006 (2)
  • August 2006 (2)
  • July 2006 (1)
  • June 2006 (1)
  • May 2006 (1)

Copyright, Greger Teigre Wedel, 2007-2019