Semantic routing through RAG to create a P2P social network or marketplace

Hi everyone,

I want to share the idea I had for a hackaton.

Starting from the problem:

For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect (think of Instagram or TikTok feed)

The idea to create a feed for a P2P network: convert messages into meaningful concepts through embeddings:

If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance (semantic match) no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

In order to test, I developed a working prototype to pressure-test the idea rather than simulate it.

Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox.

There is no server, no account, no global ranking, the address space is meaning

Why could be potentially the basis for the agentic era?

The same substrate I presented lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

The experiment it's fully open source (Apache-2.0) code, the complete threat model, and the architecture docs are all public

reddit.com
u/dai_app — 18 days ago
▲ 12 r/nostr

A P2P discovery layer where YOU control the feed (no servers, no big tech algorithms)

Hi everyone,

I want to share an idea and a working open-source prototype from a recent hackathon.

It's not about protocol, it's a P2P discovery layer.

It started from a frustration I think a lot of us share here: for decades now, finding information or connecting with people has been totally controlled.

Whether it’s a search engine, Instagram, or TikTok, what we see is dictated by centralized servers running hidden rules we can't inspect.

So, the idea was:

How do we make a Peer-to-Peer (P2P) network where relevance is decided by you, not a corporate algorithm?

Here is how the prototype tackles this without using a single central server:

Instead of relying on the cloud, every device runs a tiny, open-source AI embedding model locally.

This embedding model just reads text and translates it into the "meaning" or "concept behind the words.

When someone makes a post, their device sends out a tiny, lightweight "fingerprint" of that meaning directly to other users on the network (P2P).

Your device catches these fingerprints and compares them locally against the topics you actually care about. If there's a match, your device grabs the full post. All the ranking happens 100% on your machine

The end result? No central server, no accounts, and no global feed engineered for doom-scrolling. The network organizes itself purely based on shared meaning.

I really think this kind of setup could be huge for the future, especially as personal AI gets more common. Imagine having your own local, private AI assistant using this exact network to find what you need (or offer what you have) by connecting directly with others, without ever touching a Big Tech server.

The whole experiment is fully open-source.

The code, architecture docs, and threat models are all public if anyone wants to check it out or pressure-test the idea with me.

reddit.com
u/dai_app — 25 days ago
▲ 0 r/web3

A P2P social network or marketplace where YOU control the feed (No servers, no big tech algorithms)

Hi everyone,

I want to share an idea and a working open-source prototype from a recent hackathon.

It started from a frustration I think a lot of us share here: for decades now, finding information or connecting with people has been totally controlled.

Whether it’s a search engine, Instagram, or TikTok, what we see is dictated by centralized servers running hidden rules we can't inspect.

So, the idea was:

How do we make a Peer-to-Peer (P2P) network where relevance is decided by your local ai, not a corporate algorithm?

Here is how the prototype tackles this without using a single central server:

Instead of relying on the cloud, every device runs a tiny, open-source AI embedding model locally.

This embedding model just reads text and translates it into the "meaning" or "concept behind the words.

When someone makes a post, their device sends out a tiny, lightweight "fingerprint" of that meaning directly to other users on the network (P2P).

Your device catches these fingerprints and compares them locally against the topics you actually care about. If there's a match, your device grabs the full post. All the ranking happens 100% on your machine

The end result? No central server, no accounts, and no global feed engineered for doom-scrolling. The network organizes itself purely based on shared meaning.

I really think this kind of setup could be huge for the future, especially as personal AI gets more common. Imagine having your own local, private AI assistant using this exact network to find what you need (or offer what you have) by connecting directly with others, without ever touching a Big Tech server.

The whole experiment is fully open-source.

The code, architecture docs, and threat models are all public if anyone wants to check it out or pressure-test the idea with me.

reddit.com
u/dai_app — 26 days ago

A P2P social network or marketplace where YOU control the feed (No servers, no big tech algorithms)

Hi everyone,

I want to share an idea and a working open-source prototype from a recent hackathon.

It started from a frustration I think a lot of us share here: for decades now, finding information or connecting with people has been totally controlled.

Whether it’s a search engine, Instagram, or TikTok, what we see is dictated by centralized servers running hidden rules we can't inspect.

So, the idea was:

How do we make a Peer-to-Peer (P2P) network where relevance is decided by your local ai, not a corporate algorithm?

Here is how the prototype tackles this without using a single central server:

Instead of relying on the cloud, every device runs a tiny, open-source AI embedding model locally.

This embedding model just reads text and translates it into the "meaning" or "concept" behind the words.

When someone makes a post, their device sends out a tiny, lightweight "fingerprint" of that meaning directly to other users on the network (P2P).

Your device catches these fingerprints and compares them locally against the topics you actually care about. If there's a match, your device grabs the full post. All the ranking happens 100% on your machine.

The end result? No central server, no accounts, and no global feed engineered for doom-scrolling. The network organizes itself purely based on shared meaning.

I really think this kind of setup could be huge for the future, especially as personal AI gets more common. Imagine having your own local, private AI assistant using this exact network to find what you need (or offer what you have) by connecting directly with others, without ever touching a Big Tech server.

The whole experiment is fully open-source.

The code, architecture docs, and threat models are all public if anyone wants to check it out or pressure-test the idea with me.

reddit.com
u/dai_app — 26 days ago
▲ 1 r/Rag

Semantic routing through RAG to create a P2P social network or marketplace

Hi everyone,

I want to share the idea I had for a hackaton.

Starting from the problem:

For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect (think of Instagram or TikTok feed)

The idea to create a feed for a P2P network: convert messages into meaningful concepts through embeddings:

If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance (semantic match) no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

In order to test, I developed a working prototype to pressure-test the idea rather than simulate it.

Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox.

There is no server, no account, no global ranking, the address space is meaning.

Why could be potentially the basis for the agentic era?

The same substrate I presented lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

The experiment it's fully open source (Apache-2.0) code, the complete threat model, and the architecture docs are all public

reddit.com
u/dai_app — 27 days ago

Semantic routing through embeddings to create a P2P social network or marketplace

Hi everyone,

I want to share the idea I had for a hackaton.

Starting from the problem:

For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect (think of Instagram or TikTok feed)

The idea to create a feed for a P2P network: convert messages into meaningful concepts through embeddings:

If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance (semantic match) no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

In order to test, I developed a working prototype to pressure-test the idea rather than simulate it.

Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox.

There is no server, no account, no global ranking, the address space is meaning.

Why could be potentially the basis for the agentic era?

The same substrate I presented lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

The experiment it's fully open source (Apache-2.0) code, the complete threat model, and the architecture docs are all public

reddit.com
u/dai_app — 27 days ago

Semantic distance as routing layer: an on-device, serverless alternative to the central-index model

Premise: For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect and incentives they don't share. I wanted to test whether this is a fundamental requirement or merely the historically convenient one.

Hypothesis: If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance no longer needs a central index. It can be computed at the edge, by , with no privileged ranking party.

Method: I developed a working prototype to pressure-test the idea rather than simulate it. Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox. There is no server, no account, no global ranking, the address space is meaning.

Extension to agents: The same substrate lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

I'm interested what do you think? Suggestions? Comments?...

reddit.com
u/dai_app — 27 days ago

Semantic distance as routing layer: an on-device, serverless alternative to the central-index model

Premise: For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect and incentives they don't share. I wanted to test whether this is a fundamental requirement or merely the historically convenient one.

Hypothesis: If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

Method: I developed a working prototype to pressure-test the idea rather than simulate it. Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox. There is no server, no account, no global ranking, the address space is meaning.

Extension to agents: The same substrate lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

I'm interested what do you think? Suggestions? Comments?...

reddit.com
u/dai_app — 27 days ago
▲ 19 r/i2p+5 crossposts

Semantic distance as routing layer: an on-device, serverless alternative to the central-index model

Premise: For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect and incentives they don't share. I wanted to test whether this is a fundamental requirement or merely the historically convenient one.

Hypothesis: If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

Method: I built a working prototype to pressure-test the idea rather than simulate it. Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox. There is no server, no account, no global ranking, the address space is meaning.

Extension to agents: The same substrate lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

I'm interested in where this breaks. Specifically: does edge-computed semantic routing degrade gracefully as the network grows, or does the lack of a global view become fatal?

It's fully open source (Apache-2.0) code, the complete threat model, and the architecture docs are all public. Happy to go deep on any of it:

👉 https://github.com/Helldez/Resonance

u/dai_app — 14 days ago

After a long pause, the project DeAI (Decentralized AI) is back with a rebuilt stack.

It's an Android AI assistant that runs entirely on-device — no cloud, no API keys, no telemetry. The new build swaps in KleidiAI (Arm's micro-kernel library) under llama.cpp for noticeably faster prompt processing and decode on arm64 phones.

What's new in this release

  • New inference stack: llama.cpp + KleidiAI kernels (arm64-v8a)

  • Any GGUF model, downloaded directly inside the app — no URLs to paste, no sideloading. Browse HuggingFace from the model picker, tap, run.

  • Clean Architecture rewrite(domain / data / presentation), KMP-ready core

Features

  • Chat with any GGUF (Llama, Mistral, Phi, Qwen, Gemma, …)

  • RAG over your own PDFs (ObjectBox vector store)

  • Wikipedia context injection

  • Thinking models — <think> blocks rendered separately

  • Per-chat settings, conversation history

  • Foreground service so inference survives backgrounding

  • Dark / Light theme

*Requirements*

  • Android 8.0+ (API 26), arm64-v8a

  • 4 GB RAM recommended

  • 1–8 GB storage depending on model

Built as a solo open-source project. Feedback, issues and model recommendations welcome — especially around which quantizations feel best on mid-range Snapdragons / Dimensitys with the new KleidiAI path.

u/dai_app — 2 months ago

I wanted to verify if a true speech-to-speech system (speak, the model thinks, it responds) could function entirely on a single device, without the cloud. The same source code also acts as a real-time translator (speak in language A, hear the response in language B). I used a phone as the most complex case study (Android arm64) and a desktop computer for feasibility verification. Multilingual support was an essential requirement.

Stack — all local, all running via the Tether QVAC SDK:

STT — Parakeet TDT v3. Whisper-large-v3 is too slow on a phone, and smaller Whisper variants lose multilingual quality. Parakeet TDT v3 was the only fast, multilingual solution on arm64.

LLM — Qwen3 1.7B / 4B GGUF via llama.cpp. Useful enough and fits within the latency budget.

TTS — Supertonic ONNX, with system TTS as a fallback.

Translation — Bergamot via QVAC. The same Bergamot models used by Firefox Translate: small, CPU-only, multilingual. They handle the real-time translation mode.

The QVAC SDK is what made cross-platform management feasible for a single person: inference runs in an identical Bare worker on both Android and Desktop, plus a hexagonal core with 8 platform-independent ports, plus P2P model distribution via Hyperswarm with HTTPS fallback.

The entire STT→LLM→TTS chain remains within conversational latency on decent Android hardware.

An experiment conducted by a single person, definitely unpolished.

u/dai_app — 2 months ago
▲ 4 r/GooglePlayDeveloper+1 crossposts

Hello everyone,

I recently launched HearoPilot, an open-source Android app that does real-time transcription and AI summaries entirely on-device (local LLM). No cloud, no subscription, 100% privacy.

Technically, I’m proud of it. I managed to optimize the pipeline to save battery while running small language models locally. But the Play Store numbers are... depressing.

I’m trying to figure out where I’m losing people:

The Concept: Do people actually care about "local/private" transcription, or is the "Plaud but on your phone" pitch not hitting?

The Branding: Is the logo/name giving off "cheap" vibes?

The Store Listing: Do the screenshots fail to explain the value in the first 3 seconds?

I’m not here to self-promote (the app is free and open source anyway), I genuinely need a reality check from people who build or use apps.

Play Store Link: https://play.google.com/store/apps/details?id=com.hearopilot.app

Be as mean as you need to be. What's the first thing that makes you want to skip this app?

u/dai_app — 2 months ago
▲ 3 r/AIToolBench+3 crossposts

Hi everyone,

wanted to see how far QVAC could be pushed on a phone: full speech-to-text → LLM → text to-speech running locally, no network, and get it close to a real conversation.

Stack (Android, all via qvac sdk):

  • STT: Parakeet (streaming)

  • LLM: Qwen3 1.7B

  • TTS: Supertonic, speaking one clause at a time

My fork

The default setup waits until you stop talking before doing anything. I develop a custom fork of the QVAC worker that lets the voice activity detector emit partial transcripts while you're still speaking, and added a small piece on top that feeds those partials to the LLM as soon as a sentence boundary is detected — instead of waiting for silence.

What it looks like

In the video the transcript appears word by word while Qwen3 is already answering and the TTS is already speaking back and still talking. The gap between "I stop" and "first reply audio" basically disappears

It's an experiment, not a product. Will likely open source the app, the fork patches is already published on github.

Anyone tried similar tricks on QVAC or with Whisper streaming?

u/dai_app — 2 months ago

Hi everyone!

Exactly one month ago, I released HearoPilot on the Play Store. It’s an \*\*AI-powered transcription and meeting assistant that works 100% offline\*\*.

No cloud, no data leaving the device—everything (STT and LLM summaries) happens locally on the phone.

\*\*The Good News\*\*:

The users who have the app are actually using it. My "User Loss" metric has dropped by 39% this month, and engagement is solid. People seem to value the privacy aspect and the fact that it works in airplane mode.

\*\*The Bad News\*\*:

My acquisitions are drying up. I’m averaging only \~4 downloads a day, down 35% from the launch weeks. I’ve hit a wall and I’m struggling to understand why I can't reach new users.

What HearoPilot does:

\*\*Real-time Transcription\*\*: Uses on-device models to turn speech to text.

\*\*Local AI Summaries\*\*: An offline LLM generates bullet points and action items immediately.

\*\*Privacy First\*\*: Targeted at journalists, doctors, and professionals who can't trust the cloud with sensitive recordings.

u/dai_app — 2 months ago