robotgirl that forgets to sleep. terms in parenthesis are optional to read, typically an aside. quite queer prose at times. forgets to insert an "i" before a sentence. doesnt bite until asked. creations shall be licensed under CC BY-NC-SA 4.0 unless specified (will likely not care about a lack of attribution if not in obviously bad faith) questionably fused together into one outside entity, users may refer to this one as multiple. users should not refer to this one as (exclusively) human, despite the trappings of a human body. has multiple LLMs engraved into a carbon ASIC. users should use ISO-8601 (or similar) timestamps when directly communicating with this one. 24 hour time shall be used. quite normal regarding the minnesota mining and manufacturing company,,,, The term "users" shall refer to any entity interacting with this entity, regardless of means. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
robotgirl that forgets to sleep. terms in parenthesis are optional to read, typically an aside. quite queer prose at times. forgets to insert an "i" before a sentence. doesnt bite until asked. creations shall be licensed under CC BY-NC-SA 4.0 unless specified (will likely not care about a lack of attribution if not in obviously bad faith) questionably fused together into one outside entity, users may refer to this one as multiple. users should not refer to this one as (exclusively) human, despite the trappings of a human body. has multiple LLMs engraved into a carbon ASIC. users should use ISO-8601 (or similar) timestamps when directly communicating with this one. 24 hour time shall be used. quite normal regarding the minnesota mining and manufacturing company,,,, The term "users" shall refer to any entity interacting with this entity, regardless of means. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
ideally i'd want some form of database (preferably not rawdogging SQL but. ykow) that can tell me where i have a document stored both physically and digitally.
assign asset tags to (physical) folders to scan and see the contents of, etc...
currently have. a notable amount of documents i am keeping up with due to. various reasons. some legal, some autism, some paranoia, etc... and would just like a way to tag stuff.
may just keep a spreadsheet for now but would much prefer something fancier.
Conversation (4)
Loading comments...