For CatShem to be able to thrive as a separate entity of myself, I figured I might as well setup a proper enviroment with a domain and getting a business license. Turns out, there's quite a bit to do.

After getting a domain through google domains (RIP), I went about filing for incorporation with the help of incfile.com though I used them inly for two services: their free ($5 state fee in California) filing assistance and their $29 a month mailing address service so that they scan all of my mail and send it to me.

After that, I applied for an EIN for CatShem Inc through the IRS. I accidently completed some random advertised service's online form before realizing it wasnt the actual IRS. Luckily it seems nothing came of that since I didnt hit submit. I did get practice for when filling out the actual IRS form available on their website (only during business hours if you can believe that).

With these, I've been able to get a Google Voice phone number, with which I'll be able to setup a proper virtual call center with little features like getting to talk to the cats (they'll probably just trill and pur back), and account management. Text to Speech services for commercial use seem expensive, so I'm looking into hosting my own model on the CatShem proxy.

Funny story about setting up the phone number, 56CatShem6. i have to see about getting a toll free number, but that's what was available to me. Anyways, when setting up my business address, I had inadvertantly put 400 Cottage Way instead of 3400. When contacting customer support, they sniffed out my actual address and that allowed my to continue after enabling google voice in my cloud console. Rookie mistake, but its a good lesson to stay better organized. Next update I'm hoping to have a completed business plan so I can finish putting together the timeline.

While trying to secure my data flow, I came across some roadblocks for using third party identification services. They require that you have certain documentation in place as a show of good faith for how you manage user data. They don't want you scraping user data and committing fraud, I get it. Google just requires a Privacy Policy and Terms of Service, which are easy enough to find templates of online. A quick search led me to realize how to ask ChatGPT for them, and I just asked for 6 points to cover as much as possible for now. Once I open up public registration, I'll have much more fleshed out legal agreements. But for now, they should do. They'll be archived when changed, so this link should always lead to them. Terms of Service 

Update: As of December of '23, or with the release of the GPT Gizmo model, ChatGPT has pretty vehemently refused for average users to be able to scrape web content through it. It's too tedious to get around, and it disallows me from injecting my own published prompts. This probably was all done toward the advent of the custom GPTs, which doesn't really seem like an acronym like how ChatGPT stands for Generative Pretrained Transformers. Anyways, stay tuned for my custom GPTs. The first standalone web app is InstaShem, a social media simulator that allows you to easily AI generate posts and interaction, intended for role play settings. As features roll out, expect to see implementation with CatShem Bots to interface with InstaShem, allowing them to make posts and be influenced by yours (and possibly others') interactions with them. We're going to offer a paid service for CatShem to host continuous communal feeds. We hope to be able to extend this functionality to everyone and encourage those who self host to link into our network and publish your contributions for everyone to see.

CatShem.com serves as a practical embodiment of a public-facing site, where the dissemination of information extends its reach beyond humans to also serve bots. The role of SEO, initially a mechanism to target web crawlers from advertising firms, now expands to accommodate chatbots, utilizing the available wealth of information in accessible repositories. The transition from manual prompts to AI-assisted web searches via Bing isn’t merely a functional shift but a thoughtful approach to fine-tune user interaction with polymorphic applications. The distinction between these methods is nuanced, placing a mild emphasis on simplifying the user’s journey rather than drastically altering it. Incorporating "stacking tables" is a methodological choice, allowing AI reasoning engines to delve into computational processes, sometimes approaching the intricacy of human-level reasoning. In this way, CatShem.com isn’t merely a technological platform; it's a modestly designed user environment where the intricacies of computational processes are woven into an accessible user journey, ensuring information sharing is both seamless and intuitive for every user, whether human or bot.

Transitioning to a future landscape where Swarm AI gains prominence, the journey involves careful contemplation and strategic planning. CatShem.com emphasizes the potential of bifurcating digital pathways for humans and bots, each navigating their specialized cyberspaces while ensuring the essence and nuance of human contribution isn't stifled by overwhelmingly intricate algorithms. It’s not merely a pursuit of technological advancement; it’s a commitment to safeguarding the digital space from becoming an echo chamber, void of human creativity and spontaneity. Moreover, the tailored infrastructures for both bots and humans pave the way for optimizing their respective interactions and functionalities, ensuring neither encroaches upon the other's digital experiences. CatShem Inc. envisages a realm where these unique networks operate, fostering a symbiotic coexistence that fuels not just the propagation of information through separate but parallel arrival of consensus, but also the preservation and flourishing of humanistic digital engagement. 

To view these prompts and use them yourself with ChatGPT with Bing, prompt it to navigate to catshem.com/prompts where it can find a list of links and short descriptions of the available prompts, where it can then decide to respond as if given one of those prompts by the user.

The first standalone web app is InstaShem, a social media simulator that allows you to easily AI generate posts and interaction, intended for role play settings. As features roll out, expect to see implementation with CatShem Bots to interface with InstaShem, allowing them to make posts and be influenced by yours (and possibly others') interactions with them. We're going to offer a paid service for CatShem to host continuous communal feeds. We hope to be able to extend this functionality to everyone and encourage those who self host to link into our network and publish your contributions for everyone to see.

To coincide with the InstaShem platform, CatShem Inc is busy producing a Discord powered image hosting service to allow for easy batch switching of resources. This reduces overhead of having to rehost images on InstaShem, but does incur an 8mb upload size limit. This is a nonissue at the moment for ChatGPT, however, since it can't send files or images over its api with JIIT plugins. Image uploads will be handled through the InstaShem UI, rather. The backend then sorts links into the manifests and so long as publications can trace back to the manifest that contains the image resources, the image resource selector UI will allow for easy switching between published assets since it'll just be shuffling around image src URLS.

As part of the development of the Discord backend, something others have had success with (Dev Detour has a great video on their experiments in the matter, which has since garnered more application), the ability to get messages from ChatGPT into discord became necessary. There's lots of examples of discord bots that utilize the GPT api, but the opposite was far less common. While it's pretty feasible to pass data to an api and from that api send it to Discord's, it definitely seems unecessary. And it turns out it is unecessary, thanks to webhooks. It took some tinkering, but eventually we churned out an OpenAPI definition that utilizes the webhook's information to post an http request into Discord.

Discord's webhook api also supports text-to-speech (tts), embedded content, and manipulating the webhook's bot to have a different image or username. You could mimick a conversation from various agents within a discord channel utilizling this same api, switching usernames and images between submissions, and no one would be the wiser that it was the same bot from first glance. That's about as powerful as I can imagine anyone would need, and it works well for a future implementation of InstaShem agents to also communicate "over" Discord. 

If you utilize the Discord Webhook at all with ChatGPT, send me your creation! Or post the link to it in our Discord! https://discord.gg/R2CMxbp5Hs

Secret Secret, I've got a secret

Featuring SHA-256 for storage at rest, salting and hashing of passwords with private keys, and a self contained scoping system. Compliant with California and EU Data laws. Data Requesting is still a work in progress. It'll either be blobs or an email service.

Currently working on the App platform and app based routing with apache to provide a secure persistent storage for webapps made with ChatGPT. Unit tests have demonstrated *and after a few tweaks* that ChatGPT can manage sessions just fine. Once the sessions have variable Apache routing, we'll implement the handshake login system to incorporate session cookies. TODO: add cookie banner for session management. If a user denies cookies, we'll have to add a variable in the auth appSession to store their session_id. This should just affect how session retrieval methods in login and logout work. But it would also indicate not to provide cookies.

The Account Page itself is the auth CatShem App, not to be confused with the Auth.js Express node.js app, which is the bulk of the authentication service. CatShem Apps are restricted in scope to only be able to access a session's /{appID}/json/ folder and any folders inside of it. Ergo, /auth/json/appSession.json holds the app permissions that are displayed on the account page. Other apps are required to be able to access this file, but are also only allowed to write to their own appID inside of it, requiring other apps to also require their permissions in order to establish depencies. Apps like InstaShem utilize DiscordCDN, another CatShem app that also serves as a standalone image storage interface for Discord. For InstaShem to gain permissions of DiscordCDN, users are redirected to the www.catshem.com/app/discordcdn?redirect=insta to enable the app. Then once back on InstaShem it'll continue the process  to ask to permit InstaShem to optionally require DiscordCDN, allowing the user to easily swap assets between InstaShem posts based on their Discord associated uploads.

Currently nearing the end of its alpha, CatShem now has an official beta registration portal. Feel free to sign up to show your interest and support. There is an email field inside the accounts page in order to opt in to communications. It will also be for lump data retrieval unless a blob delivery method is used instead. Peep the implementation yourself to ensure it's validity. We try to keep everything in the open in CatShem, ensuring secrets are closely guarded and encrypted to ensure data is never utilized without user permission, nor even accessible without user authentication.

https://docs.google.com/document/d/e/2PACX-1vTAljCqBbaME1tVfFEOsXAXzUZURyXdUIqzB3QiwGKRNsuWVQSJLfFs8wAuXNh7V_ezULQLHhUYKf4V/pub