You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it looks aesthetic to match the avatar to the tone of the posted message. This was a happy accident but as we can imagine, if its an error, then a red avatar appears. We can have a few different authentications/apps with different branding to indicate the "mood" of the AI. In case we need unique names, then we can do something like:
I suppose that this would require a first-class integration inside of our logger. We also will need to figure a way to deal with the private keys so we can post.
This would be used internally in Ubiquity mostly for showcasing/product demos, as I think it could be annoying for partners to install every different app. We could make the logger fallback to posting with default authentication in case the correct app is not found for the class of message. For example, if warning bot is not installed, then it would post the warning authenticated as normal ubiquity-os[bot]
The text was updated successfully, but these errors were encountered:
@gentlementlegen how long do you think it would take to clean up the logger internal code to accomodate this with first-class support? I think thats the bulk of the work.
I think it looks aesthetic to match the avatar to the tone of the posted message. This was a happy accident but as we can imagine, if its an error, then a red avatar appears. We can have a few different authentications/apps with different branding to indicate the "mood" of the AI. In case we need unique names, then we can do something like:
ubiquity-os[bot]
normal/green/blueubiquity-os-debug[bot]
purpleubiquity-os-warning[bot]
yellowubiquity-os-error[bot]
redStatus message color reference https://gist.github.com/0x4007/c17c46cd206970f46115a7ef5c465924
I suppose that this would require a first-class integration inside of our logger. We also will need to figure a way to deal with the private keys so we can post.
This would be used internally in Ubiquity mostly for showcasing/product demos, as I think it could be annoying for partners to install every different app. We could make the logger fallback to posting with default authentication in case the correct app is not found for the class of message. For example, if warning bot is not installed, then it would post the warning authenticated as normal
ubiquity-os[bot]
The text was updated successfully, but these errors were encountered: