It's an interesting idea - like having a whiteboard that you use with C3PO whenever you interact with him. Screenshots would be good - a before and after comparison of how it's used.
Another idea I had, is having a "just pushed" display for any and all apps a person likes or follows. Because with so much coding going on, it makes sense to have a versioning setup for anything a person is developing, eg: https://greasyfork.org/en/scripts/537017-youtube/versions --- so for Botbin - what version are you up to? Is this 1.0? Why not have a versioning system going?
Maybe someone would be interested in Botbin, but only after another few months of active development, or traction. Help people remember your app by documenting your progress. Then have a way to embed an app's versioning back into its homepage, and get the agent to push the new version and features into the Hub. The hub page could also initiate bounties on certain unbuilt features.
Hub pages could also have an "I use this" toggle, and feedback can then be publicly shown and voted on. Note the code, feedback and stats pages on Greasyfork.
It's an interesting idea - like having a whiteboard that you use with C3PO whenever you interact with him. Screenshots would be good - a before and after comparison of how it's used.
Another idea I had, is having a "just pushed" display for any and all apps a person likes or follows. Because with so much coding going on, it makes sense to have a versioning setup for anything a person is developing, eg: https://greasyfork.org/en/scripts/537017-youtube/versions --- so for Botbin - what version are you up to? Is this 1.0? Why not have a versioning system going?
Maybe someone would be interested in Botbin, but only after another few months of active development, or traction. Help people remember your app by documenting your progress. Then have a way to embed an app's versioning back into its homepage, and get the agent to push the new version and features into the Hub. The hub page could also initiate bounties on certain unbuilt features.
Hub pages could also have an "I use this" toggle, and feedback can then be publicly shown and voted on. Note the code, feedback and stats pages on Greasyfork.
This will become a persistence layer for stateless bots attempting to cooperate.