Sorry about the lack of posts. I am cooking up a little demonstration project and am making all the big decision that one needs to make before implementing the design such as: Should I integrate the system with SteemIt?
My goal for the day was to implement steemit oauth and haven't found any decent documentation. I have found a huge number of incomplete implementations and fundamentally flawed implementations. Apparently, I need to go through SteemConnect.com. SteemConnect asks for 3 STEEM. SteemConnect was merged into Busy and I haven't figured out the implications of that. Using SteemConnect might create a dependency to an unsupported project. I've made that mistake before.
I've been checking out different authentication libraries on GitHub. People writing such libraries seem to be laboring under the notion that authentication must be done using object-like syntax (ie the class structure in c++, java, etc.).
I am a fan of object design; however, I realized early on that authentication between different computers is best done with simple procedures. Computer to computer authentication involves sending discrete, well defined bundles of data between computers.
This is funny. The Wikipedia page for OpenId calls oauth a pseudo-authentication model. Oauth is primarily a protocol for allowing a client computer access to resources of a host server.
The problem with oauth is that it forces the clients using oauth to be subordinate to the host. I am actually thinking that I should develop my application completely independent of oauth or OpenId and to add these features in a later release after I discover if people are interested in the project.
I am still interested in trying to implement steemconnect. I guess I will have to power down so that I can get the 3 STEEM to register the application.
The picture shows me cooking on the rocket stove. The flame is from a small hand full of twigs.
