Hey there, im making an AI chat

[Inoi]

Spoiler: RU version

You don't have permission to view the spoiler content. Log in or register now.

Aaand thanks chatGpt to this translate - version now xD

Hey f95!

I got inspired to write this post thanks to a random thread by some awesome person here working on their own game. I've been using this fantastic site for quite a while now, but only as a reader. I figured, where better to share this than here?

Ever since ChatGPT came out, I've been having fun with it for sexting, to varying degrees. I even got one of my accounts banned by OpenAI. Then I messed around with Tavern and some other niche resources, including ones advertised here, but none of them really clicked for me.

At some point, I decided this could be good practice and a way to learn some cool, modern tech. So, I dove deep into Stable Diffusion (SD) and eventually decided to create my own sexting API. I've been working on it for about three months now, pretty consistently.

Right now, I've got the server-side stuff set up. It's an ASP .NET API app where I've been honing my development skills, focusing on proper design, separating business logic, domain entities, and all that technical jazz. I'm using two databases: MSSQL via EF for core data and MongoDB for messages and SD-generated image chunks. I've refactored it a couple of times, and it's probably the best part of my app right now, though some API endpoints still need a bit of work.

The frontend is my first serious attempt at React, so it's probably a bit rough in terms of component design and overall aesthetics, as I came up with the design on the fly. AIs - I'm using SD with a model I painstakingly selected, along with a few additional Lora models for characters (just test ones for now) and a fine-tuned merge of Llama with something else I can’t remember. It's not the best I've seen – for instance, Command-R seemed cooler, but since I run everything on my home PCs, Command-R is just too slow on my 3080.

The frontend interacts with my API, which in turn connects with the AIs, DeepL API, and Google Translate – the first for translating text to and from the user's language, and the latter for translating user prompts for the SD.

Why I'm writing this here
Sadly, among my friends, I seem to be the only one using something like f95. The rest are a bit more innocent. They're curious, some even tried it out a couple of times, but it's hard to get into something when you're not the target audience, so to speak.

I thought maybe here, I could find someone interested in checking this out. Perhaps offer advice or feedback (especially on AI character description patterns – that would be super helpful). Maybe even a user review or interface suggestions.

This is my first serious attempt at working with AI at this level, so I have tons of questions about how to improve things and how they are perceived by others. My main goal is to make something better than what I've seen, as I think I have a lot of ideas for the future that could take AI sexting to a more interesting level. When it comes to text, I'd love to hear about your experiences writing prompts for characters, especially if you've done something similar for Tavern. I'm keen on making something truly great, and I feel confident about my ideas and the process, but I'm still figuring out the character prompt part.

Right now, it's still in development, very alpha, but the basic functionality works. My two home PCs are chugging along, and they can definitely handle a couple of people if anyone's interested.

I haven't set up any Boosty, Patreon, or anything like that – it doesn’t feel right to me. But before writing this post, I did set up a new Discord channel. If it’s okay to share a link,

You must be registered to see the links

it is.

I'd be thrilled to read any advice, opinions, or recommendations right here too.

Cheers!

 

[Inoi]

So, here's a little more info about what we have now and how it works. First, a few images:

Spoiler: Login - reg page

You don't have permission to view the spoiler content. Log in or register now.

Spoiler: Character select

You don't have permission to view the spoiler content. Log in or register now.

Spoiler: Main UI

You don't have permission to view the spoiler content. Log in or register now.

Of course, almost everything here is still sketches, without the involvement of designers, and I will likely continue to redo many elements. I’ve already completely refactored the design once (though the general concept remained the same).

A bit of technical stuff:

This is my first-ever React application.

Spoiler: dunno wat im doing

You don't have permission to view the spoiler content. Log in or register now.

On the front end, it's Vite+React, Tailwind for styling, and SWR for data mutations and revalidation that I get from the backend. There's also I18next for multilingual support - it's more of a groundwork, but it's already fully functional, and the interface language switches completely. SWR was fine-tuned by my front-end developer when he refactored my code - initially, I wasn't revalidating data dynamically at all.

This is only a client-side application, entirely executed by the browser - everything else is done by the backend.

The backend is an ASP.NET API application (which ideally needs to be transitioned to sockets for a start), designed through services and various domain entities. All of them seem to be isolated from each other, working only within their own structure.

Spoiler: Ok, csharp is pretty easier 2 me

You don't have permission to view the spoiler content. Log in or register now.

What else is there? Entity Framework, AutoMapper, Mongo, and JWT for user tokens.
For data that needs constant internal connections - MSSQL.





It is assumed that most of the data inside should literally be enums, because it’s better for tag-based navigation or search. But in fact, this is not the case everywhere yet, but all connections between tables already exist, and accordingly, they are all mapped into DataAccess entities using EF. The logic for working with the database is encapsulated through UnitOfWork.

It also works with a second database, Mongo, where only messages are stored separately.

Oh, not only. Photos sent by the SD are also stored there - GridFS is used for this, which splits files into chunks and stores them in one collection, leaving metadata in another.





And the most mysterious part - Stable Diffusion, here the prompt sent to it by the backend, contains not only what the user sends but also a pre-set piece. Besides quality descriptions and negatives, there is a Name, with a specific lore - a trained SD addon, which based on around 1500 photos always draws the same character. (I didn't train them myself; these are ready-made lores that you can choose from). Accordingly, SD is operated by a single service that responds to the key phrase "send a photo" in the chat. The API endpoint is the same as for messages, of course, and then the backend processes them through the AIs.

I tried a lot text models, started with Kobolds, wasn’t impressed, tried something on Colab, and finally used the divine LM Studio, which basically does a huge part of the work itself - for example, formatting the prompt for a specific model.

A little research was done here, and I probably highlighted two cool models - this one:

You must be registered to see the links

And the one currently in use:

You must be registered to see the links

Command-R shows itself better, but it's very resource-intensive; on my 3080 and 32 GB RAM (where the model is loaded) a single response is generated in more than a minute, while TheBloke's LLaMa-based model does the same in a few seconds. Overall, it’s quite decent too.

In total, besides the hosting with the front end, there are four servers. One with server Ubuntu, with Mongo and MSSQL deployed in Docker (you can’t put MSSQL on the latest Ubuntu without a container). The second with SD for photos and its API. The third with the text AI and its API. The fourth with the backend, which communicates with all of them. The last three are on Windows.
And thats just old PCs under my table and from my friends.

Google Translate and DeepL are connected on the backend - the first translates prompts for SD, the second, more complex, translates the text chat, allowing the user to write in almost any language, translating their text into English for the AI and then back into the user's language after its response. (This is still a debatable solution that I am working on.)

Regarding AIs, the idea of integrating ChatGPT, which is obviously the best neural network for chatting, doesn’t leave me alone, but I am terrified of how many tedious conditions and filters I will have to write to protect the user from its occasional refusals to talk about certain topics, which would have to be recognized literally by words. This is not impossible, of course, but it looks daunting.

That's it.



Currently, I am working on text prompts and small extensions to the API endpoints to properly transmit JSON with multiple control strings instead of parsing key system words in one string, as I foolishly did initially. Overall, I plan to transition to sockets.

Since all of this is actually running at my home, it’s not always very fast or stable, but most of the time, if there's a desire, it can be tried out.

 

[Inoi]

Quick updates (actually big ones). I've been experimenting a lot with text models, and I've now settled on the relatively new and robust Llama 3. It still has some censorship, but I've worked hard on the prompts to make it respond the way we want. (I often start testing these things on the character Zara, as she is the most candid.) So far, I've managed to get only one refusal out of about a hundred iterations, which is great! Additionally, I've rewritten all the initial prompts and descriptions for all the characters. They now respond much more naturally and, at times, more simply (which I believe is how it should be). Moreover, the characters should now occasionally send pictures upon request, if they feel like it, without needing to press the special camera icon at the bottom. Essentially, the request for a photo is sent from one neural network, which then prompts the second neural network, effectively without direct user intervention. This feature is unfortunately somewhat unpredictable and hard to ensure works flawlessly every time, but it seems to be functioning for now. I've also fixed a few minor UI bugs, but that's minor stuff. The major work has been on the models and prompts. I'm always ready for more improvements, so feel free to share your experiences boldly.

For a better experience, please use English. However, the built-in DeepL should automatically recognize any language and translate your messages back and forth, so they are always in English for the AI and in your language for you. But DeepL sometimes can make a funny mistakes

 

[Inoi]

 

[Gone405]

Welcome to the forums! I hope the chatai is going well! I will join the discord and try to help in anyway I can! This project looks fun and very interesting! Super impressive by this all! Good job!

 

[Inoi]

Welcome to the forums! I hope the chatai is going well! I will join the discord and try to help in anyway I can! This project looks fun and very interesting! Super impressive by this all! Good job!

Thank you so much for your support!
Even just likes on my posts, and especially such support, are very important, because its always motivate me go further :3

 

[Dars]

Hi there,

You must be registered to see the links

...

 

[lir1234]

Hi! Following this and hope to try it in the future. Also, I hope it's something you can try first without paying!

So far every such chat I've tried was either too limited to try out, or if I did get to try it the AI capabilities did not make me want to make it more than just a one hour experiment.

Good luck!

 

[Inoi]

Hi! Following this and hope to try it in the future. Also, I hope it's something you can try first without paying!

So far every such chat I've tried was either too limited to try out, or if I did get to try it the AI capabilities did not make me want to make it more than just a one hour experiment.

Good luck!

Hello!

(I apologize in advance for any mistakes, I’m using a neural network to translate my stream of thoughts into English - I can handle short responses myself, but longer texts are more challenging for me)

Thank you very much for your interest, and I’ll try to address your quite reasonable complaint a bit.

I’ve also tried a huge number of similar AI chats and was very disappointed with all of them. I did pay for them, usually, the price wasn’t too high (except maybe for Foxy, but I tried that one too).

$10 a month seems like a small cost if you get some decent content for that money. However, I quickly realized that the dialogues I had with ChatGPT were far more interesting, richer, and more detailed.

Primarily, it was this - the desire to at least try to give users a somewhat better experience - that motivated me to start studying this whole thing.

For the most part, even the additional content that exists in the environment now - like voice messages or audio calls, which seem quite easy to implement, still doesn’t solve the main problem - the text dialogues themselves quickly become boring.

Models quickly go into loops, lose initiative, and in some cases, just start continuing the user’s narrative. It’s the desire to try and do better, rather than a passion for making money, that drives me

Of course, I keep in mind that a quality solution should always make money eventually; besides, neural networks do require resources. Even now, twenty simultaneous users will have to wait in line for a few minutes on my 3080 to have a proper conversation with the bot. All this infrastructure doesn’t come cheap. It’s great if it can be done well, come up with a decent subscription system, and make money.

But none of this makes any sense if you’re just making another ai-chat clone without first pushing your project’s functionality to the maximum of its capabilities.

So it’s this idea and desire to just make something really cool that has driven me all my life.

I’ve been doing entertaining pet projects on the internet for quite a while. I had an L2 server fifteen years ago with an average online presence of two thousand people, where the only donation functions were nickname color changes and special symbols in it. Not long ago, I ran a GTA5RP server, which I sold after finishing everything I wanted to create on it, and the only interface it didn’t have was a donation interface

So, of course, someday I’ll need to come up with “limits,” but right now I’m definitely not thinking about that.

Currently, as long as my home infrastructure is sufficient and I’m only developing, almost all functionality is available completely free. (Almost always because I sometimes just turn off the neural network, and there are no limits, restrictions, or even any user parameters other than the nickname on my backend yet).

That’s about it, I hope I conveyed my thoughts clearly.
Thanks again for your interest and wishes
I’m always happy and open to any advice and feedback!

P.S. and I’m also a graphomaniac

P.S.S. btw, ive been working on the mobile version for a few days:



To be honest, I don't always understand the point of it, especially since it's obvious I'll have to redraw the entire UI with a professional designer.
But I want even the test version to work well everywhere.