DataBarista
I'm that Barista who remembers your stories & might just know someone you should meet! (A supperconnector AI agent)
Created on 14th February 2025
•
DataBarista
I'm that Barista who remembers your stories & might just know someone you should meet! (A supperconnector AI agent)
The problem DataBarista solves
Traditional networking—whether in-person or online—often falls short of delivering meaningful, tailored connections. In physical meetups, people often miss important details about one another, leading to missed opportunities and shallow interactions. Online, generic platforms spam users with attention grabbing and irrelevant messages.
DataBarista tackles these challenges by building its own network—a community knowledge graph that unites private profiles with public, yet anonymous, intents. Here’s how it works:
1. Dual-Layer Knowledge Graph: DataBarista’s network comprises two interconnected layers:
Private Profiles: Privately stored user data in an edge node—including personal background, project details, and sensitive information—accessible only to DataBarista.
Public Intents: Anonymized summaries of users’ professional goals and project challenges that remain verifiable and discoverable by the community public on DKG.
2. Semantic Matchmaking: The matchmaking process is a two-step system:
Rule-Based Filtering: Using SPARQL queries, the system scans the decentralized knowledge graph to retrieve candidate profiles that align with the user’s expertise, project domain, and desired connections.
LLM-Driven Reasoning: A reasoning layer then leverages large language models to analyze these candidates semantically, ensuring that the selected match offers mutual benefits rather than a one-sided connection.
3. Continuous Network Enrichment: By actively listening on platforms like Twitter, DataBarista keeps its community knowledge graph up-to-date, dynamically integrating new insights and ensuring that all matches reflect current expertise and interests.
Overall, DataBarista transforms random networking into a serendipitious and privacy-preserving matchmaking experience that benefits people, agents by making meaningful connections without the creepy data practices.
Challenges I ran into
- eliza had a really heavy build with too many packages and many problems getting it run with all the dependecy on packages, with suggestion of someone on discord switched to eliza-starter, much lighter but didnt have access to core logic, e.g. enabling context logging for debugging purpose on core generation.ts.
- rule based + reasoning matchmaking was hard, especially coming up with right sparqls but o3-mini did a good job and cracked the code.
- was testing on telegram till last day morning and all worked and even demos ad-hoc on 13th Feb on Eliza’s Discord (Kenk had me on as last person overtime) and then i tried switching to telegram and had the problem with username. previously state.senderName was giving me username for telegram, but display name for twitter. since didnt have access to core logic of clients, couldnt easily find the twitter username of the user and decided to finish the submission with telegram.
- then Origintrail testnet that worked smooooothly for 2 weeks stopped working in the last few hours, had a chat with CTO, couldn’t get a hold of anyone with the server, but that node went down just for my demo, it worked sometimes for few minutes but mainly down. so with heavy heart writing this at 00:05 and didn’t record a 100% functioning demo, but promise by time you read this, twitter and telegram will be both working. SO this is how life is. Promise to AI agent’s god it was working smooooothy like butter, provider giving each time latest profile data, and publishing and getting match in <1min working.
Tracks Applied (1)
AI Advancement: Most Autonomous Agent
Technologies used