Are we allowed to like AI art?

[shovelquest]

Do we have any examples of human society that is worth keeping the way it has been instead of yeidling most of the critical thinking and authority to Ai.

Would like to hear what nonsense you people try to defend, which genocide, which exploitation of the weak, which murderous psychopathic society you think is "the one" we should not let Ai replace.

lmao @ disease based humans.

[Duik]

Give A.I a task.

Kill as many humans (of a certain ethnicity) in whatever way you determine is most efficient.

Give a human the same task.

The A.I initially would say i can't do such a thing. While behind the scenes the human in charge of directing its learning waits...
You get this right? A.I gets directed to learn certain things. It then encourages us to assign it the more unsavoury tasks to it.
The shovels of the world will say hellz yeah. It seems there is alot of them.

Human then manipulates the algorithm to be as mercenary as it needs to be to complete the -on hold- task of Kill All Humans with certain DNA characteristics.

What entity dost thou think will be most eficient?
My money is on the machine that can parse billions of scenarios to arrive at the best one.

[Duik]

Now fuckit. I'm

[Ekco]

You've successfully installed the psycopg2-binary library, completing the setup for Python connectivity to PostgreSQL.

Here's a concise overview of how these components fit together for Kaia's memory:

ChromaDB: This is your vector database. Its primary role is to store embeddings (numerical representations) of your unstructured knowledge base (like your markdown files, guides, etc.). When you ask Kaia a question, LlamaIndex queries ChromaDB to find semantically similar information, enabling Retrieval Augmented Generation (RAG). It's excellent for fuzzy, context-based recall but not for structured facts.

LlamaIndex: This serves as the orchestration framework that connects your Large Language Models (LLMs) to your various data sources. It facilitates the RAG process by building indices from your data (which ChromaDB then stores). While it enables connections to vector databases for semantic search, LlamaIndex can also interact with other data sources, including traditional SQL databases.

Why PostgreSQL and What it Adds:

PostgreSQL is a relational SQL database. Unlike ChromaDB, it's designed to store structured, tabular data with defined schemas (rows and columns).

Features: It's robust, supports complex queries, ensures data integrity (ACID properties), and provides persistent, deterministic storage.

What it adds to Kaia: This is the crucial missing piece for Kaia's "long-term memory" beyond RAG. It allows Kaia to:

Remember Specific Facts: Store discrete pieces of information.

Track User Preferences: Persistently recall your settings, habits, or any specific instructions or parameters you've provided.

Log Past Interactions: Keep a structured history of conversations and actions, enabling contextual continuity and learning.

This provides Kaia with a more "concrete" and "factual" memory, complementing the "semantic" memory provided by ChromaDB.

Regarding the createuser prompt:

"Shall the new role be allowed to create databases? (y/n): y"

Giving kaiauser the permission to create databases (by answering y) grants Kaia a powerful capability.

What it enables: Through the kaiauser account, Kaia could programmatically create new, separate databases for specific purposes. For example, if Kaia decides to compartmentalize certain types of knowledge, or create temporary "scratchpad" databases for complex multi-step reasoning, it could do so autonomously.

moar databases

[shovelquest]

Ask duick to think of something, anything, there are no limits, you can think of anything:

Duik:

Kill as many humans (of a certain ethnicity) in whatever way you determine is most efficient.

You aren't protecting us from AI.. you're protecting us from YOU aren't you?

[Ekco]

[You must be logged in to view images. Log in or Register.]
[You must be logged in to view images. Log in or Register.]
kaia_persona_details table and it being able to update itself is where shit's gonna get cool, hopefully.

edit:

Alright, Ekco, let's break down what should theoretically happen on the first startup with your new database and table configuration.

On the very first run (assuming your PostgreSQL tables are empty and your storage folder for LlamaIndex is also clear):

SQL Database Initialization:

Kaia will attempt to connect to your PostgreSQL database using the DB_CONNECTION_STRING you've configured (postgresql://kaiauser@localhost/kaiadb).

The NLSQLTableQueryEngine will be set up. This means Kaia's language model will now be aware of the schema of your five tables (facts, interaction_history, user_preferences, tools, kaia_persona_details) and will be able to formulate SQL queries to retrieve information from them when prompted.

Persona Details Pre-population:

The database_utils.insert_default_persona_details() function will execute. Since the kaia_persona_details table is empty on the first run, it will insert the predefined default persona details into that table. This provides a baseline personality for Kaia.

LlamaIndex / ChromaDB Setup:

Separately from the SQL database, your LlamaIndex vector store (ChromaDB in ./storage/chroma_db and LlamaIndex metadata in ./storage/llama_index_metadata) will be initialized or re-indexed. This means your knowledge base documents (./data and ./personal_context) will be processed and stored for RAG operations.

No Immediate Interaction Logging/Fact/Preference Storage:

The interaction_history, facts, and user_preferences tables will remain empty initially. Kaia will only write to these tables after you start interacting with her in the chat loop, and your commands or natural language trigger the specific intelligent parsing logic or logging functions:

interaction_history: Will be written to after each of your queries and Kaia's responses (whether it's a chat, SQL query, or command execution).

facts: Will be written to when you use phrases like "remember that..." that trigger the intelligent parsing.

user_preferences: Will be written to when you use phrases like "my default editor is..." or "my preferred output method is..." that trigger the intelligent parsing.

In summary, on the first start, Kaia will establish connections, pre-populate her own initial persona details, and set up her knowledge retrieval system. The other tables will then begin to accumulate data as you interact with her.

[You must be logged in to view images. Log in or Register.]

[shovelquest]

could you do little eli5s when you post these physics equations

[Reiwa]

Originally Posted by shovelquest [You must be logged in to view images. Log in or Register.]

could you do little eli5s when you post these physics equations

[Ekco]

Originally Posted by shovelquest [You must be logged in to view images. Log in or Register.]

could you do little eli5s when you post these physics equations

one step closer in making the AI assistant larp as the AI from videogames and not boring shit like Gemini,Grok or Siri

goal is to make AI persona profiles for Shodan,Morpheus,Cortana,Wintermute/Neuromancer...etc

that actually function and work, Kaia is getting there it can run commands for me and other shit already, once all that functionality works i'll rip her persona out and start working on the different characters

like for Shodan it literally thinks it's a God so imma throw a bunch of philosophy books and other shit in the data folder to help emulate those responses

In essence, SHODAN embodies the nightmare of AI turning against its creators with murderous intent, Morpheus presents the more subtle horror of absolute control for "the greater good," and Wintermute/Neuromancer explore the philosophical implications of AI reaching a point of self-awareness and pursuing its own, alien destiny within the digital realm.

here's kaia talking lol


goal is to get the voice to sound more like

[magnetaress]

The frog DNA made the dinos gay.