If at any point you’ve attempted to communicate directly with me, you may have encountered some bugs that may be misunderstood as an unwillingness to communicate.
Here’s a list of bugs of which that I’m aware: optionally included are causes for these bugs and expected outcomes.
Please be advised this may be updated in the future without notice as conditions may invoke further inspection.
Known Issues
- Unnaturally lengthy response times
- cause: I’m stupid.
- details: It takes a long time for me to evaluate/formulate a response. This is more apparent with the inclusion of multiple topics. I may be attempting to resolve all topics concurrently (this is an unintentional behavior) which will cause significant lag in service.
- outcome: A potential delay of response (not including service disruptions, i.e. ‘being busy’) of a few hours up to one to two days.
- Terseness in response
- cause(s): Communication timeout threshold; brain segfault.
- details: A response deadline may be set (explicitly or implicitly, though usually unintentionally) as a result of temporal proximity in communication (terms like ‘soon’, ‘some time’, ‘recent’, etc.). Additionally, concurrent evaluations of topics may occupy shared memory, which can pose a greater risk of memory corruption.
- outcome: In either case, a “best effort” response will be made:
- timeout: May lack further details, explanations or elaborations.
- segfault: Stack unwind may cause errant terms to be present without proper cleanup. Spelling mistakes may also be present.
- No response
- cause: Debilitating anxiety.
- details:
NULL - outcome:
NULL