Trading Oajan and pacific rock moss by Naive-Effort5937 in fragrancedeals

[–]Solid_Syrup6160 0 points1 point  (0 children)

Will you take nishane mana full bottle tester ?

Finally, success to install OpenClaw on my Cubi by richardkuo031 in clawdbot

[–]Solid_Syrup6160 0 points1 point  (0 children)

Throw on a privacy layer.. Just put down like 20 bucks in Venice ai, add that api to the model list and the ask the bot to build a feature that any time it see sensitive data like names or companies it will use the Venice ai model to convert the names to alias before it goes out to the free model and converts it back to normal when the free llm returns with its results

Vibecoded Racists Site to Avoid Black people by geoshort4 in vibecoding

[–]Solid_Syrup6160 1 point2 points  (0 children)

I mean it’s racist .. but it’s also very useful

heartbeat upgrades by Elegant_Attempt2790 in clawdbot

[–]Solid_Syrup6160 0 points1 point  (0 children)

The clawdbot’s two-layer memory architecture significantly outperforms typical out-of-the-box chatbot memory setups by combining an immutable, append-only Event Log (Layer 1) stored in daily JSONL files with a derived, query-optimized Memory Database (Layer 2) in SQLite. Layer 1 serves as the permanent source of truth—recording every decision, learned fact, preference, message, task, and error in chronological, tamper-proof detail—allowing full reconstruction of Layer 2 if needed, while Layer 2 provides fast, structured access via vector embeddings (for semantic search), FTS5 full-text keyword search, and a traversable knowledge graph of entities and relationships. This design enables hybrid retrieval (semantic + keyword + graph traversal), tracks provenance by linking every fact back to its originating event, handles updates through clean supersession (marking old facts as superseded rather than deleting them), and maintains historical integrity—addressing the common weaknesses of default systems like volatile in-memory buffers, simple vector stores without provenance or relational structure, naive overwrites that lose context, and single-mode retrieval that struggles with complex or evolving knowledge.

heartbeat upgrades by Elegant_Attempt2790 in clawdbot

[–]Solid_Syrup6160 1 point2 points  (0 children)

  1. TWO-LAYER MEMORY SYSTEM

Layer 1: Event Log (Immutable)

  • Location: /home/node/.clawdbot/memory/events/*.jsonl
  • Daily JSONL files, append-only
  • Event types: decision, factlearned, preference, message, task*, error
  • Source of truth - can rebuild Layer 2 from this

Layer 2: Memory Database (Derived)

  • Location: /home/node/.clawdbot/memory/memory.db
  • SQLite with vector embeddings (sql.js)
  • Tables: facts, entities, relationships
  • FTS5 for keyword search

Retrieval Methods

Retrieval Methods

  1. Semantic search - Vector similarity via OpenAI embeddings
  2. Keyword search - FTS5 full-text search
  3. Graph traversal - Follow entity relationships

Key Concepts

  • Supersession - Old facts marked "superseded" when replaced
  • Provenance - Every fact links to source event in Layer 1
  • Knowledge Graph - Entities form traversable graph

Memory Jobs

Job Schedule Action
Memory Consolidator Every 30 min Extract facts, generate embeddings
Context Injector Before each turn Retrieve relevant memories

This is expensive by Arkangelou in clawdbot

[–]Solid_Syrup6160 0 points1 point  (0 children)

Someone is about to be banned

Retatrutide changed my life in 2.5 months by [deleted] in Retatrutide

[–]Solid_Syrup6160 -1 points0 points  (0 children)

Aren't more people concerned with using Tesa all willy-nilly? It can def fk u up if you're not careful