own. Loadouts for Genshin Impact has been and always will be a free and open source software project, and we are committed to delivering a quality experience with every release we make.
# Disclaimer
With an extensive suite of over 1503 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game.
The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact.
All rights to Genshin Impact assets used in this project are reserved by miHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.
https://redd.it/1o2v1ks
@r_opensource
# Disclaimer
With an extensive suite of over 1503 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game.
The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact.
All rights to Genshin Impact assets used in this project are reserved by miHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.
https://redd.it/1o2v1ks
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Nook Browser, a new WebKit browser is in alpha.
https://www.browsewithnook.com/
https://redd.it/1o2vgqn
@r_opensource
https://www.browsewithnook.com/
https://redd.it/1o2vgqn
@r_opensource
Browsewithnook
Nook Browser
Fast, focused, and open — a modern WebKit browser for Mac.
Marketing for Founders: practical resources to grow your project
Hi everyone! Over the last two years I had to figure out how to do marketing to promote my projects.
This meant doing a ton of research and reading a lot and, well… 90% of what you find on the topic is kinda useless, too vague and not actionable, with just a few exceptions here and there.
So I’ve started to collect the best resources in a GitHub repo. It covers topics like:
* Places To Launch Your Startup
* Social Media Marketing
* Sales & Cold Outreach
* SEO
* Email Marketing
* Content Marketing
* Ads
* Influencer Marketing
* Affiliates and Referrals
* Free-Tool Marketing
* Landing Pages, Messaging and Positioning
* Pricing
* Conversion Rate Optimization
* Idea Validation
* User Research
I’m trying to keep it as practical as it gets (spoiler: it’s hard since there’s no one-size-fits-all) and list everything in order so we can have a playbook to follow.
If you're interested you can find it here: [https://github.com/EdoStra/Marketing-for-Founders](https://github.com/EdoStra/Marketing-for-Founders)
Hope it helps!
https://redd.it/1o2vwx0
@r_opensource
Hi everyone! Over the last two years I had to figure out how to do marketing to promote my projects.
This meant doing a ton of research and reading a lot and, well… 90% of what you find on the topic is kinda useless, too vague and not actionable, with just a few exceptions here and there.
So I’ve started to collect the best resources in a GitHub repo. It covers topics like:
* Places To Launch Your Startup
* Social Media Marketing
* Sales & Cold Outreach
* SEO
* Email Marketing
* Content Marketing
* Ads
* Influencer Marketing
* Affiliates and Referrals
* Free-Tool Marketing
* Landing Pages, Messaging and Positioning
* Pricing
* Conversion Rate Optimization
* Idea Validation
* User Research
I’m trying to keep it as practical as it gets (spoiler: it’s hard since there’s no one-size-fits-all) and list everything in order so we can have a playbook to follow.
If you're interested you can find it here: [https://github.com/EdoStra/Marketing-for-Founders](https://github.com/EdoStra/Marketing-for-Founders)
Hope it helps!
https://redd.it/1o2vwx0
@r_opensource
GitHub
GitHub - EdoStra/Marketing-for-Founders: Practical marketing resources to get the first 10 / 100 / 1000 users for your SaaS / App…
Practical marketing resources to get the first 10 / 100 / 1000 users for your SaaS / App / Startup - EdoStra/Marketing-for-Founders
Open Source Vision Agents by Stream.
https://github.com/GetStream/vision-agents
https://redd.it/1o2wmzf
@r_opensource
https://github.com/GetStream/vision-agents
https://redd.it/1o2wmzf
@r_opensource
GitHub
GitHub - GetStream/Vision-Agents: Open Vision Agents by Stream. Build Vision Agents quickly with any model or video provider. Uses…
Open Vision Agents by Stream. Build Vision Agents quickly with any model or video provider. Uses Stream's edge network for ultra-low latency. - GetStream/Vision-Agents
[MIT] Tool to bulk-disable Reddit “Community updates” via Selenium attach (no credential handling)
I open-sourced a small utility to flip Reddit’s “Community updates” to **Off** across all subscribed communities. Motivation: doing it manually is tedious, especially with hundreds of subs.
**Why this approach**
* **Attach to existing browser** via DevTools (`--remote-debugging-port=9222`) so there’s **no credential handling** or API usage—just DOM automation of your own settings page.
* **Resilience**: full pointer/mouse sequence, JS click fallback, shallow shadow-DOM traversal, and state verification via `aria-pressed="true"`.
* **Diagnostics**: optional HTML/screenshot dump on failures.
**Stack**
* Python 3.10+, `selenium>=4.21`.
* Tested on Windows + Chrome/Edge (Chromium). Works elsewhere with small path tweaks.
**Repo / License**
* Code + README: [https://github.com/AarchiveSoft/redditCommunityNotifOffAll](https://github.com/AarchiveSoft/redditCommunityNotifOffAll)
* License: MIT. Issues/PRs welcome—particularly for cross-platform launch helpers, deeper shadow-DOM cases, and CI smoke tests.
If Reddit adjusts the UI, selectors are centralized and easy to tweak. Happy to review PRs for broader locale support and stability improvements.
https://redd.it/1o2wenq
@r_opensource
I open-sourced a small utility to flip Reddit’s “Community updates” to **Off** across all subscribed communities. Motivation: doing it manually is tedious, especially with hundreds of subs.
**Why this approach**
* **Attach to existing browser** via DevTools (`--remote-debugging-port=9222`) so there’s **no credential handling** or API usage—just DOM automation of your own settings page.
* **Resilience**: full pointer/mouse sequence, JS click fallback, shallow shadow-DOM traversal, and state verification via `aria-pressed="true"`.
* **Diagnostics**: optional HTML/screenshot dump on failures.
**Stack**
* Python 3.10+, `selenium>=4.21`.
* Tested on Windows + Chrome/Edge (Chromium). Works elsewhere with small path tweaks.
**Repo / License**
* Code + README: [https://github.com/AarchiveSoft/redditCommunityNotifOffAll](https://github.com/AarchiveSoft/redditCommunityNotifOffAll)
* License: MIT. Issues/PRs welcome—particularly for cross-platform launch helpers, deeper shadow-DOM cases, and CI smoke tests.
If Reddit adjusts the UI, selectors are centralized and easy to tweak. Happy to review PRs for broader locale support and stability improvements.
https://redd.it/1o2wenq
@r_opensource
GitHub
GitHub - AarchiveSoft/redditCommunityNotifOffAll
Contribute to AarchiveSoft/redditCommunityNotifOffAll development by creating an account on GitHub.
Built FoldCMS: a type-safe static CMS with Effect and SQLite with full relations support (open source)
Hey everyone,
I've been working on FoldCMS, an open source type-safe static CMS that feels good to use. Think of it as Astro collections meeting Effect, but with proper relations and SQLite under the hood for efficient querying: you can use your CMS at runtime like a data layer.
1. Organize static files in collection folders (I provide loaders for YAML, JSON and MDX but you can extend to anything)
2. Or create a custom loader and load from anything (database, APIs, ...)
3. Define your collections in code, including relations
4. Build the CMS at runtime (produce a content store artifact, by default SQLite)
5. Then import your CMS and query data + load relations with full type safety
# Why I built this
I was sick of the usual CMS pain points:
- Writing the same data-loading code over and over
- No type safety between my content and my app
- Headless CMSs that need a server and cost money
- Half-baked relation systems that make you do manual joins
So I built something to ease my pain.
# What makes it interesting (IMHO)
**Full type safety from content to queries**
Define your schemas with Effect Schema, and everything else just works. Your IDE knows what fields exist, what types they are, and what relations are available.
```typenoscript
const posts = defineCollection({
loadingSchema: PostSchema,
loader: mdxLoader(PostSchema, { folder: 'content/posts' }),
relations: {
author: { type: 'single', field: 'authorId', target: 'authors' }
}
});
// Later, this is fully typed:
const post = yield* cms.getById('posts', 'my-post'); // Option<Post>
const author = yield* cms.loadRelation('posts', post, 'author'); // Author
```
**Built-in loaders for everything**
JSON, YAML, MDX, JSON Lines – they all work out of the box. The MDX loader even bundles your components and extracts exports.
**Relations that work**
Single, array, and map relations with complete type inference. No more `find()` loops or manual joins.
**SQLite for fast queries**
Everything gets loaded into SQLite at build time with automatic indexes. Query thousands of posts super fast.
**Effect-native**
If you're into functional programming, this is for you. Composable, testable, no throwing errors. If not, the API is still clean and the docs explain everything.
**Easy deployment**
Just load the sqlite output in your server and you get access yo your data.
# Real-world example
Here's syncing blog posts with authors:
```typenoscript
import { Schema, Effect, Layer } from "effect";
import { defineCollection, makeCms, build, SqlContentStore } from "@foldcms/core";
import { jsonFilesLoader } from "@foldcms/core/loaders";
import { SqliteClient } from "@effect/sql-sqlite-bun";
// Define your schemas
const PostSchema = Schema.Struct({
id: Schema.String,
noscript: Schema.String,
authorId: Schema.String,
});
const AuthorSchema = Schema.Struct({
id: Schema.String,
name: Schema.String,
email: Schema.String,
});
// Create collections with relations
const posts = defineCollection({
loadingSchema: PostSchema,
loader: jsonFilesLoader(PostSchema, { folder: "posts" }),
relations: {
authorId: {
type: "single",
field: "authorId",
target: "authors",
},
},
});
const authors = defineCollection({
loadingSchema: AuthorSchema,
loader: jsonFilesLoader(AuthorSchema, { folder: "authors" }),
});
// Create CMS instance
const { CmsTag, CmsLayer } = makeCms({
collections: { posts, authors },
});
// Setup dependencies
const SqlLive = SqliteClient.layer({ filename: "cms.db" });
const AppLayer = CmsLayer.pipe(
Layer.provideMerge(SqlContentStore),
Layer.provide(SqlLive),
);
// STEP 1: Build (runs at build time)
const buildProgram = Effect.gen(function* () {
yield* build({ collections: { posts, authors } });
});
await Effect.runPromise(buildProgram.pipe(Effect.provide(AppLayer)));
// STEP 2: Usage (runs at runtime)
const queryProgram = Effect.gen(function* () {
const cms = yield* CmsTag;
// Query posts
Hey everyone,
I've been working on FoldCMS, an open source type-safe static CMS that feels good to use. Think of it as Astro collections meeting Effect, but with proper relations and SQLite under the hood for efficient querying: you can use your CMS at runtime like a data layer.
1. Organize static files in collection folders (I provide loaders for YAML, JSON and MDX but you can extend to anything)
2. Or create a custom loader and load from anything (database, APIs, ...)
3. Define your collections in code, including relations
4. Build the CMS at runtime (produce a content store artifact, by default SQLite)
5. Then import your CMS and query data + load relations with full type safety
# Why I built this
I was sick of the usual CMS pain points:
- Writing the same data-loading code over and over
- No type safety between my content and my app
- Headless CMSs that need a server and cost money
- Half-baked relation systems that make you do manual joins
So I built something to ease my pain.
# What makes it interesting (IMHO)
**Full type safety from content to queries**
Define your schemas with Effect Schema, and everything else just works. Your IDE knows what fields exist, what types they are, and what relations are available.
```typenoscript
const posts = defineCollection({
loadingSchema: PostSchema,
loader: mdxLoader(PostSchema, { folder: 'content/posts' }),
relations: {
author: { type: 'single', field: 'authorId', target: 'authors' }
}
});
// Later, this is fully typed:
const post = yield* cms.getById('posts', 'my-post'); // Option<Post>
const author = yield* cms.loadRelation('posts', post, 'author'); // Author
```
**Built-in loaders for everything**
JSON, YAML, MDX, JSON Lines – they all work out of the box. The MDX loader even bundles your components and extracts exports.
**Relations that work**
Single, array, and map relations with complete type inference. No more `find()` loops or manual joins.
**SQLite for fast queries**
Everything gets loaded into SQLite at build time with automatic indexes. Query thousands of posts super fast.
**Effect-native**
If you're into functional programming, this is for you. Composable, testable, no throwing errors. If not, the API is still clean and the docs explain everything.
**Easy deployment**
Just load the sqlite output in your server and you get access yo your data.
# Real-world example
Here's syncing blog posts with authors:
```typenoscript
import { Schema, Effect, Layer } from "effect";
import { defineCollection, makeCms, build, SqlContentStore } from "@foldcms/core";
import { jsonFilesLoader } from "@foldcms/core/loaders";
import { SqliteClient } from "@effect/sql-sqlite-bun";
// Define your schemas
const PostSchema = Schema.Struct({
id: Schema.String,
noscript: Schema.String,
authorId: Schema.String,
});
const AuthorSchema = Schema.Struct({
id: Schema.String,
name: Schema.String,
email: Schema.String,
});
// Create collections with relations
const posts = defineCollection({
loadingSchema: PostSchema,
loader: jsonFilesLoader(PostSchema, { folder: "posts" }),
relations: {
authorId: {
type: "single",
field: "authorId",
target: "authors",
},
},
});
const authors = defineCollection({
loadingSchema: AuthorSchema,
loader: jsonFilesLoader(AuthorSchema, { folder: "authors" }),
});
// Create CMS instance
const { CmsTag, CmsLayer } = makeCms({
collections: { posts, authors },
});
// Setup dependencies
const SqlLive = SqliteClient.layer({ filename: "cms.db" });
const AppLayer = CmsLayer.pipe(
Layer.provideMerge(SqlContentStore),
Layer.provide(SqlLive),
);
// STEP 1: Build (runs at build time)
const buildProgram = Effect.gen(function* () {
yield* build({ collections: { posts, authors } });
});
await Effect.runPromise(buildProgram.pipe(Effect.provide(AppLayer)));
// STEP 2: Usage (runs at runtime)
const queryProgram = Effect.gen(function* () {
const cms = yield* CmsTag;
// Query posts
const allPosts = yield* cms.getAll("posts");
// Get specific post
const post = yield* cms.getById("posts", "post-1");
// Load relation - fully typed!
if (Option.isSome(post)) {
const author = yield* cms.loadRelation("posts", post.value, "authorId");
console.log(author); // TypeScript knows this is Option<Author>
}
});
await Effect.runPromise(queryProgram.pipe(Effect.provide(AppLayer)));
```
That's it. No GraphQL setup, no server, no API keys. Just a simple data layer: `cms.getById`, `cms.getAll`, `cms.loadRelation`.
# Current state
- ✅ All core features working
- ✅ Full test coverage
- ✅ Documented with examples
- ✅ Published on npm (`@foldcms/core`)
- ⏳ More loaders coming (Obsidian, Notion, Airtable, etc.)
I'm using it in production for my own projects. The DX is honestly pretty good and I have a relatively complex setup:
- Static files collections come from yaml, json and mdx files
- Some collections come from remote apis (custom loaders)
- I run complex data validation (checking that links in each posts are not 404, extracting code snippet from posts and executing them, and many more ...)
# Try it
```bash
bun add @foldcms/core
pnpm add @foldcms/core
npm install @foldcms/core
```
In the GitHub repo I have a self-contained example, with dummy yaml, json and mdx collections so you can directly dive in a fully working example, I'll add the links in comments if you are interested.
Would love feedback, especially around:
- API design: is it intuitive enough?
- Missing features that would make this useful for you
- Performance with large datasets (haven't stress-tested beyond ~10k items)
https://redd.it/1o30i1q
@r_opensource
// Get specific post
const post = yield* cms.getById("posts", "post-1");
// Load relation - fully typed!
if (Option.isSome(post)) {
const author = yield* cms.loadRelation("posts", post.value, "authorId");
console.log(author); // TypeScript knows this is Option<Author>
}
});
await Effect.runPromise(queryProgram.pipe(Effect.provide(AppLayer)));
```
That's it. No GraphQL setup, no server, no API keys. Just a simple data layer: `cms.getById`, `cms.getAll`, `cms.loadRelation`.
# Current state
- ✅ All core features working
- ✅ Full test coverage
- ✅ Documented with examples
- ✅ Published on npm (`@foldcms/core`)
- ⏳ More loaders coming (Obsidian, Notion, Airtable, etc.)
I'm using it in production for my own projects. The DX is honestly pretty good and I have a relatively complex setup:
- Static files collections come from yaml, json and mdx files
- Some collections come from remote apis (custom loaders)
- I run complex data validation (checking that links in each posts are not 404, extracting code snippet from posts and executing them, and many more ...)
# Try it
```bash
bun add @foldcms/core
pnpm add @foldcms/core
npm install @foldcms/core
```
In the GitHub repo I have a self-contained example, with dummy yaml, json and mdx collections so you can directly dive in a fully working example, I'll add the links in comments if you are interested.
Would love feedback, especially around:
- API design: is it intuitive enough?
- Missing features that would make this useful for you
- Performance with large datasets (haven't stress-tested beyond ~10k items)
https://redd.it/1o30i1q
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Did you find any benefit in participating in Hacktoberfest? Application for both contributors and maintainers
It was my curiosity about the potential benefit of participating in these events. I'm very curious about it and would like to know what you think.
https://redd.it/1o2zys3
@r_opensource
It was my curiosity about the potential benefit of participating in these events. I'm very curious about it and would like to know what you think.
https://redd.it/1o2zys3
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
NitNab
Introducing NitNab - Nifty Instant Trannoscription Nifty AutoSummarize Buddy
A powerful, open source, privacy-focused native macOS application for transcribing audio files using Apple's cutting-edge Speech framework and Apple Intelligence. Built for macOS 26+ with Swift 6.0 and optimized for Apple Silicon.
https://www.github.com/lanec/nitnab/
https://www.nitnab.com
# ✨ Features
(https://github.com/lanec/nitnab#-features)
# Core Trannoscription
(https://github.com/lanec/nitnab#core-trannoscription)
🎵 Multi-Format Support: M4A, WAV, MP3, AIFF, CAF, FLAC, and more
🌍 Multi-Language: Supports all languages available in macOS Speech framework
⚡ Fast & Efficient: Leverages Apple's on-device SFSpeechRecognizer API
🔒 Privacy-First: All processing happens locally on your Mac
🔄 Batch Processing: Transcribe multiple files in sequence with automatic error handling
📊 Progress Tracking: Real-time progress updates for each file
# AI-Powered Features
(https://github.com/lanec/nitnab#ai-powered-features)
✨ AI Summaries: Generate concise summaries using Apple Intelligence (FoundationModels)
💬 Interactive Chat: Ask questions about trannoscripts, draft emails, extract action items
🤖 Context-Aware: AI maintains conversation history for natural interactions
# Data Persistence & Sync
[](https://github.com/lanec/nitnab#data-persistence--sync)
💾 Auto-Save: Automatically saves audio files, trannoscripts, summaries, and chat history
☁️ iCloud Sync: Built-in iCloud Drive support for seamless device sync
📁 Custom Storage: Choose any folder for local-only storage
🗂️ Organized Structure: Each trannoscription stored in its own timestamped folder
🔄 Cross-Device Ready: Designed for future iOS/iPadOS app integration
# Export & Sharing
(https://github.com/lanec/nitnab#export--sharing)
📤 Multiple Export Formats: Plain Text, SRT, WebVTT, JSON, Markdown
📋 One-Click Copy: Copy trannoscripts, summaries, or chat responses instantly
💾 Flexible Output: Export individual files or batch exports
# User Experience
[](https://github.com/lanec/nitnab#user-experience)
🎨 Beautiful UI: Modern SwiftUI interface with three-tab view (Trannoscript/Summary/Chat)
🖱️ Drag & Drop: Add files by dragging or using file picker
👆 Clickable Files: Select any file to view its trannoscript, summary, or errors
🚫 No Popups: Errors display inline without blocking workflow
🔵 Visual Selection: Blue border highlights selected file
https://redd.it/1o356rt
@r_opensource
Introducing NitNab - Nifty Instant Trannoscription Nifty AutoSummarize Buddy
A powerful, open source, privacy-focused native macOS application for transcribing audio files using Apple's cutting-edge Speech framework and Apple Intelligence. Built for macOS 26+ with Swift 6.0 and optimized for Apple Silicon.
https://www.github.com/lanec/nitnab/
https://www.nitnab.com
# ✨ Features
(https://github.com/lanec/nitnab#-features)
# Core Trannoscription
(https://github.com/lanec/nitnab#core-trannoscription)
🎵 Multi-Format Support: M4A, WAV, MP3, AIFF, CAF, FLAC, and more
🌍 Multi-Language: Supports all languages available in macOS Speech framework
⚡ Fast & Efficient: Leverages Apple's on-device SFSpeechRecognizer API
🔒 Privacy-First: All processing happens locally on your Mac
🔄 Batch Processing: Transcribe multiple files in sequence with automatic error handling
📊 Progress Tracking: Real-time progress updates for each file
# AI-Powered Features
(https://github.com/lanec/nitnab#ai-powered-features)
✨ AI Summaries: Generate concise summaries using Apple Intelligence (FoundationModels)
💬 Interactive Chat: Ask questions about trannoscripts, draft emails, extract action items
🤖 Context-Aware: AI maintains conversation history for natural interactions
# Data Persistence & Sync
[](https://github.com/lanec/nitnab#data-persistence--sync)
💾 Auto-Save: Automatically saves audio files, trannoscripts, summaries, and chat history
☁️ iCloud Sync: Built-in iCloud Drive support for seamless device sync
📁 Custom Storage: Choose any folder for local-only storage
🗂️ Organized Structure: Each trannoscription stored in its own timestamped folder
🔄 Cross-Device Ready: Designed for future iOS/iPadOS app integration
# Export & Sharing
(https://github.com/lanec/nitnab#export--sharing)
📤 Multiple Export Formats: Plain Text, SRT, WebVTT, JSON, Markdown
📋 One-Click Copy: Copy trannoscripts, summaries, or chat responses instantly
💾 Flexible Output: Export individual files or batch exports
# User Experience
[](https://github.com/lanec/nitnab#user-experience)
🎨 Beautiful UI: Modern SwiftUI interface with three-tab view (Trannoscript/Summary/Chat)
🖱️ Drag & Drop: Add files by dragging or using file picker
👆 Clickable Files: Select any file to view its trannoscript, summary, or errors
🚫 No Popups: Errors display inline without blocking workflow
🔵 Visual Selection: Blue border highlights selected file
https://redd.it/1o356rt
@r_opensource
GitHub
GitHub - lanec/nitnab: Nifty Instant Trannoscription Nifty AutoSummarize Buddy (NitNab) an Application for MacOS
Nifty Instant Trannoscription Nifty AutoSummarize Buddy (NitNab) an Application for MacOS - lanec/nitnab
TrustMesh - Open-source reputation layer for AI agents (FastAPI + Python)
Hi r/opensource!
Just open-sourced TrustMesh - a reputation system for AI agents using Bayesian statistics.
What it does: Provides portable trust scores for autonomous AI agents. Think "GitHub stars for agents" - helps evaluate reliability before interactions.
Why it matters: Google's A2A protocol enables agent-to-agent communication, but there's no standard trust layer. This fills that gap.
Tech:
FastAPI backend
Bayesian trust engine (Beta-Binomial modeling)
Python SDK
SQLite (planning PostgreSQL)
MIT licensed
Looking for:
Contributors (especially for TypeScript SDK, web dashboard)
Feedback on the trust algorithm
Integration ideas
GitHub: https://github.com/ashishjsharda/trustmesh
Just launched today - early stage but functional! Check out the API docs at /docs after running locally.
Questions welcome!
https://redd.it/1o37mk5
@r_opensource
Hi r/opensource!
Just open-sourced TrustMesh - a reputation system for AI agents using Bayesian statistics.
What it does: Provides portable trust scores for autonomous AI agents. Think "GitHub stars for agents" - helps evaluate reliability before interactions.
Why it matters: Google's A2A protocol enables agent-to-agent communication, but there's no standard trust layer. This fills that gap.
Tech:
FastAPI backend
Bayesian trust engine (Beta-Binomial modeling)
Python SDK
SQLite (planning PostgreSQL)
MIT licensed
Looking for:
Contributors (especially for TypeScript SDK, web dashboard)
Feedback on the trust algorithm
Integration ideas
GitHub: https://github.com/ashishjsharda/trustmesh
Just launched today - early stage but functional! Check out the API docs at /docs after running locally.
Questions welcome!
https://redd.it/1o37mk5
@r_opensource
GitHub
GitHub - ashishjsharda/trustmesh
Contribute to ashishjsharda/trustmesh development by creating an account on GitHub.
Symiosis: a keyboard-driven, notes app inspired by Notational Velocity. With instant search, in-place Markdown rendering and builtin editor (vim/emacs modes).
Hey everyone,
Symiosis is a desktop note-taking app inspired by *Notational Velocity*. It’s built with **Rust + Tauri (backend)** and **Svelte (frontend)**.
**GitHub:** [https://github.com/dathinaios/symiosis](https://github.com/dathinaios/symiosis)
**Key features:**
* Instant search with fuzzy matching
* Markdown rendered in place
* Keyboard-driven (Vim/Emacs modes supported)
* Custom themes and TOML config
* Built-in code editor with syntax highlighting
Currently tested mainly on **macOS** — quick tests suggest it runs on **Windows and Linux**, but I’d love help testing and improving cross-platform packaging.
All Feedback welcome!
https://redd.it/1o3au3d
@r_opensource
Hey everyone,
Symiosis is a desktop note-taking app inspired by *Notational Velocity*. It’s built with **Rust + Tauri (backend)** and **Svelte (frontend)**.
**GitHub:** [https://github.com/dathinaios/symiosis](https://github.com/dathinaios/symiosis)
**Key features:**
* Instant search with fuzzy matching
* Markdown rendered in place
* Keyboard-driven (Vim/Emacs modes supported)
* Custom themes and TOML config
* Built-in code editor with syntax highlighting
Currently tested mainly on **macOS** — quick tests suggest it runs on **Windows and Linux**, but I’d love help testing and improving cross-platform packaging.
All Feedback welcome!
https://redd.it/1o3au3d
@r_opensource
GitHub
GitHub - dathinaios/symiosis: Notational Velocity inspired notes app with instant search, in place markdown rendering, and vim/emacs…
Notational Velocity inspired notes app with instant search, in place markdown rendering, and vim/emacs editing modes. - dathinaios/symiosis
Introducing GenosDB: a P2P Graph Database with Built-In Zero-Trust Security
Hi everyone,
I want to introduce GenosDB (GDB), a project I’ve been building. It’s a peer-to-peer, modular graph database designed from the ground up to embed zero-trust security directly into the data layer.
This is not just “another database.” GenosDB is an experiment in combining distributed systems, cryptographic identity, and fine-grained access control into a unified framework where trust is enforced at the edge — without central servers.
# 🔍 The Problem It Tries to Solve
Peer-to-peer systems have always faced a central challenge: how can peers trust each other without relying on a server or central authority?
Typical decentralized apps often end up cheating: they use a P2P database for storage but fall back to centralized servers for identity, authentication, and permissions. That single point of control undermines the decentralization.
GenosDB tries to address this by designing security into the core database engine: every peer, every operation, every role check is verified independently. The network is held together not by trust in servers, but by cryptography and a shared constitution of rules.
[Watch the video](https://www.youtube.com/watch?v=srSmcNLWMus)
# 🧩 Core Architecture
GenosDB is a graph database where data is stored as nodes and edges, and peers can synchronize updates in real time. On top of that, it provides:
* P2P Synchronization – Each instance can connect to others over WebRTC or relays, exchanging updates and applying them locally.
* Eventual Consistency – Updates flow asynchronously, but cryptographic checks guarantee that only valid, authorized changes are accepted.
* Reactive Queries – Peers can subscribe to queries and get real-time updates as the graph evolves.
But the real innovation is the Security Manager (SM), which is not an add-on but an integral part of the architecture.
# 🔒 The Security Manager (SM)
The SM enforces a zero-trust model at multiple levels:
# 1. Identity Management
Every user is an Ethereum address backed by a private key. No passwords are involved. Private keys are protected by:
* WebAuthn – biometric devices, hardware security keys (phishing-resistant).
* Mnemonic phrases – for recovery and portability.
This means authentication is both decentralized and resistant to common attacks.
# 2. Operation Signing and Verification
Every database operation is signed by the user’s active key. When a peer receives an operation:
1. It verifies the signature (authenticity and integrity).
2. It checks the sender’s role and permissions.
3. It rejects the operation if either fails.
Unsigned or tampered operations never enter the system.
# 3. Role-Based Access Control (RBAC)
A hierarchy of roles (guest, user, manager, admin, superadmin) defines permissions like read, write, delete, assignRole.
* Role assignments are stored inside the graph itself, synchronized like any other data.
* Roles can be customized at initialization.
* Authority flows from superadmins, who are defined in the initial configuration.
# 4. Access Control Lists (ACLs)
For more granular control, ACLs can be attached to nodes. For example, a document can explicitly list which peers may read or write it. ACLs are enforced alongside RBAC, so both conditions must be satisfied.
5. Secure Data Storage
When a user stores data through the SM, it is automatically encrypted with a key derived from their identity. Only the rightful owner can decrypt it.
# 🚪 The Zero-Trust Entry Model
One of the hardest problems in zero-trust systems is the bootstrap paradox: how does a brand-new user even join the network if they have no permissions yet?
GenosDB’s solution is a single welcome exception:
* A new address is allowed exactly one operation — creating its own identity node as a guest.
* The system overwrites any attempted role with guest (preventing privilege escalation).
* After that, the user is limited to minimal permissions (read, sync) until promoted by a superadmin.
This creates a secure, one-way entry point. No
Hi everyone,
I want to introduce GenosDB (GDB), a project I’ve been building. It’s a peer-to-peer, modular graph database designed from the ground up to embed zero-trust security directly into the data layer.
This is not just “another database.” GenosDB is an experiment in combining distributed systems, cryptographic identity, and fine-grained access control into a unified framework where trust is enforced at the edge — without central servers.
# 🔍 The Problem It Tries to Solve
Peer-to-peer systems have always faced a central challenge: how can peers trust each other without relying on a server or central authority?
Typical decentralized apps often end up cheating: they use a P2P database for storage but fall back to centralized servers for identity, authentication, and permissions. That single point of control undermines the decentralization.
GenosDB tries to address this by designing security into the core database engine: every peer, every operation, every role check is verified independently. The network is held together not by trust in servers, but by cryptography and a shared constitution of rules.
[Watch the video](https://www.youtube.com/watch?v=srSmcNLWMus)
# 🧩 Core Architecture
GenosDB is a graph database where data is stored as nodes and edges, and peers can synchronize updates in real time. On top of that, it provides:
* P2P Synchronization – Each instance can connect to others over WebRTC or relays, exchanging updates and applying them locally.
* Eventual Consistency – Updates flow asynchronously, but cryptographic checks guarantee that only valid, authorized changes are accepted.
* Reactive Queries – Peers can subscribe to queries and get real-time updates as the graph evolves.
But the real innovation is the Security Manager (SM), which is not an add-on but an integral part of the architecture.
# 🔒 The Security Manager (SM)
The SM enforces a zero-trust model at multiple levels:
# 1. Identity Management
Every user is an Ethereum address backed by a private key. No passwords are involved. Private keys are protected by:
* WebAuthn – biometric devices, hardware security keys (phishing-resistant).
* Mnemonic phrases – for recovery and portability.
This means authentication is both decentralized and resistant to common attacks.
# 2. Operation Signing and Verification
Every database operation is signed by the user’s active key. When a peer receives an operation:
1. It verifies the signature (authenticity and integrity).
2. It checks the sender’s role and permissions.
3. It rejects the operation if either fails.
Unsigned or tampered operations never enter the system.
# 3. Role-Based Access Control (RBAC)
A hierarchy of roles (guest, user, manager, admin, superadmin) defines permissions like read, write, delete, assignRole.
* Role assignments are stored inside the graph itself, synchronized like any other data.
* Roles can be customized at initialization.
* Authority flows from superadmins, who are defined in the initial configuration.
# 4. Access Control Lists (ACLs)
For more granular control, ACLs can be attached to nodes. For example, a document can explicitly list which peers may read or write it. ACLs are enforced alongside RBAC, so both conditions must be satisfied.
5. Secure Data Storage
When a user stores data through the SM, it is automatically encrypted with a key derived from their identity. Only the rightful owner can decrypt it.
# 🚪 The Zero-Trust Entry Model
One of the hardest problems in zero-trust systems is the bootstrap paradox: how does a brand-new user even join the network if they have no permissions yet?
GenosDB’s solution is a single welcome exception:
* A new address is allowed exactly one operation — creating its own identity node as a guest.
* The system overwrites any attempted role with guest (preventing privilege escalation).
* After that, the user is limited to minimal permissions (read, sync) until promoted by a superadmin.
This creates a secure, one-way entry point. No
YouTube
Genos-DB Zero Trust Security Model
Understanding GenosDB Zero-Trust Security Model: From Guest to SuperAdmin
shortcuts, no backdoors.
# 🕸 The Distributed Trust Model
Trust in GenosDB is not delegated to a central server. It emerges from three principles:
1. Cryptographic Identity and Signatures Every action is signed. No one can impersonate another.
2. Shared Constitution Rules (roles, permissions) are encoded in the SM and shared across all peers. They are not arbitrary — they are uniform and verifiable.
3. Local Enforcement Each peer checks operations independently. Even if one peer is compromised or malicious, others enforce the rules and reject invalid operations.
This makes the system resilient: a rogue client cannot rewrite its local code to cheat, because other nodes will still reject unauthorized actions.
# ⚖️ Consistency and Security
GenosDB favors security over availability. For example:
* If Bob is promoted to admin by a superadmin, but a lagging node hasn’t received the promotion yet, Bob’s delete operations will initially be rejected.
* Once the promotion arrives, those operations are accepted.
This ensures no operation is accepted without verifiable proof, even if it delays availability slightly.
# 🌍 Why It Matters
Most “decentralized” systems still centralize identity and trust. GenosDB demonstrates that:
* A database itself can carry identity, access control, and trust as first-class citizens.
* P2P apps can enforce zero-trust security without needing external servers.
* Collaborative systems — from shared documents to social platforms to multiplayer games — can be built on a substrate where every action is verified cryptographically.
In short: it’s a database where security is the foundation, not an afterthought.
# 📚 Resources
* [Whitepaper](https://github.com/estebanrfp/gdb/blob/main/WHITEPAPER.md)
* [Documentation](https://github.com/estebanrfp/gdb/blob/main/docs/index.md)
* [API Reference](https://github.com/estebanrfp/gdb/blob/main/docs/genosdb-api-reference.md)
* [Distributed Trust Model](https://github.com/estebanrfp/gdb/wiki/GenosDB-Distributed-Trust-Model)
* [Zero-Trust Security Model](https://github.com/estebanrfp/gdb/wiki/Zero-Trust-Security-Model)
* [Repository](https://github.com/estebanrfp/gdb)
* [Discussions](https://github.com/estebanrfp/gdb/discussions)
# 🙌 Invitation
GenosDB is currently in stable beta. The architecture is functional, the zero-trust flows are enforced, and the P2P engine is running.
I’m sharing this here because I’d love to:
* Experiment with it.
* Stress test it.
* Help shape the roadmap.
If you care about security, decentralization, and real-time collaboration, I’d be thrilled to hear your feedback.
Esteban Fuster Pozzi ([estebanrfp](https://github.com/estebanrfp))
https://redd.it/1o3bz3q
@r_opensource
# 🕸 The Distributed Trust Model
Trust in GenosDB is not delegated to a central server. It emerges from three principles:
1. Cryptographic Identity and Signatures Every action is signed. No one can impersonate another.
2. Shared Constitution Rules (roles, permissions) are encoded in the SM and shared across all peers. They are not arbitrary — they are uniform and verifiable.
3. Local Enforcement Each peer checks operations independently. Even if one peer is compromised or malicious, others enforce the rules and reject invalid operations.
This makes the system resilient: a rogue client cannot rewrite its local code to cheat, because other nodes will still reject unauthorized actions.
# ⚖️ Consistency and Security
GenosDB favors security over availability. For example:
* If Bob is promoted to admin by a superadmin, but a lagging node hasn’t received the promotion yet, Bob’s delete operations will initially be rejected.
* Once the promotion arrives, those operations are accepted.
This ensures no operation is accepted without verifiable proof, even if it delays availability slightly.
# 🌍 Why It Matters
Most “decentralized” systems still centralize identity and trust. GenosDB demonstrates that:
* A database itself can carry identity, access control, and trust as first-class citizens.
* P2P apps can enforce zero-trust security without needing external servers.
* Collaborative systems — from shared documents to social platforms to multiplayer games — can be built on a substrate where every action is verified cryptographically.
In short: it’s a database where security is the foundation, not an afterthought.
# 📚 Resources
* [Whitepaper](https://github.com/estebanrfp/gdb/blob/main/WHITEPAPER.md)
* [Documentation](https://github.com/estebanrfp/gdb/blob/main/docs/index.md)
* [API Reference](https://github.com/estebanrfp/gdb/blob/main/docs/genosdb-api-reference.md)
* [Distributed Trust Model](https://github.com/estebanrfp/gdb/wiki/GenosDB-Distributed-Trust-Model)
* [Zero-Trust Security Model](https://github.com/estebanrfp/gdb/wiki/Zero-Trust-Security-Model)
* [Repository](https://github.com/estebanrfp/gdb)
* [Discussions](https://github.com/estebanrfp/gdb/discussions)
# 🙌 Invitation
GenosDB is currently in stable beta. The architecture is functional, the zero-trust flows are enforced, and the P2P engine is running.
I’m sharing this here because I’d love to:
* Experiment with it.
* Stress test it.
* Help shape the roadmap.
If you care about security, decentralization, and real-time collaboration, I’d be thrilled to hear your feedback.
Esteban Fuster Pozzi ([estebanrfp](https://github.com/estebanrfp))
https://redd.it/1o3bz3q
@r_opensource
GitHub
gdb/WHITEPAPER.md at main · estebanrfp/gdb
GenosDB – Decentralized P2P Graph Database with Security Manager - estebanrfp/gdb
Gooey - Go WebAssembly UI Framework
https://github.com/cookiengineer/gooey
https://redd.it/1o3dil7
@r_opensource
https://github.com/cookiengineer/gooey
https://redd.it/1o3dil7
@r_opensource
GitHub
GitHub - cookiengineer/gooey: :smiling_imp: :gun: Opinionated Go WebASM framework
:smiling_imp: :boom: :gun: Opinionated Go WebASM framework - GitHub - cookiengineer/gooey: :smiling_imp: :gun: Opinionated Go WebASM framework
slop - minimalistic display manager (replacement for login)
Hi everyone,
Recently, I decided to ditch the GUI display manager in favor of the TTY login. However, I was unable to configure the login program the way I wanted so I've decided to build my own.
Introducing [slop](https://github.com/spevnev/slop) \- Simple Login Program.
It is a replacement for getty and login designed to be minimalistic and simple.
Unlike login, which prints a bunch of extra info (date, issue, hostname, motd, etc.), it only displays what is needed for authentication (i.e. prompts from the PAM modules).
Also, it doesn't print an empty line before the prompt like [agetty does](https://github.com/util-linux/util-linux/blob/db0efab5c3e13794ae79fcb3db8371e3af510169/term-utils/agetty.c#L1831).
Features:
* Focus the TTY
* Set command to run on successful login, e.g. `startx`, or a wayland compositor.
* Clear screen after failed attempt
* Set noscript above the prompt
* Predefine a username
Hope this helps someone who wants a simple TTY login.
https://redd.it/1o3f9uw
@r_opensource
Hi everyone,
Recently, I decided to ditch the GUI display manager in favor of the TTY login. However, I was unable to configure the login program the way I wanted so I've decided to build my own.
Introducing [slop](https://github.com/spevnev/slop) \- Simple Login Program.
It is a replacement for getty and login designed to be minimalistic and simple.
Unlike login, which prints a bunch of extra info (date, issue, hostname, motd, etc.), it only displays what is needed for authentication (i.e. prompts from the PAM modules).
Also, it doesn't print an empty line before the prompt like [agetty does](https://github.com/util-linux/util-linux/blob/db0efab5c3e13794ae79fcb3db8371e3af510169/term-utils/agetty.c#L1831).
Features:
* Focus the TTY
* Set command to run on successful login, e.g. `startx`, or a wayland compositor.
* Clear screen after failed attempt
* Set noscript above the prompt
* Predefine a username
Hope this helps someone who wants a simple TTY login.
https://redd.it/1o3f9uw
@r_opensource
GitHub
GitHub - spevnev/slop: Simple replacement for getty and login with additional features.
Simple replacement for getty and login with additional features. - spevnev/slop
Treat files as individual repositories with qwe
Hi everyone!
I'm stoked to finally release Qwe, a side project that I've been hacking at for the past few weeks.
The Problem Qwe Solves
We all adore Git, but occasionally its project-level tracking can be overkill. Did you ever attempt to revert a single stand-alone config file or a single Python noscript without bothering the rest of the project? Sure, you can do this, but usually, it requires you to use convoluted commands such as git checkout $COMMITHASH -- $FILEPATH and can be needlessly cumbersome.
I created Qwe to make this easier by centering the file as the main unit of version control.
What is Qwe?
Qwe is a Version Control System (VCS) in which you can commit, monitor, and revert files separately with ease.
It's ideal for:
Software developers working with many standalone utility noscripts, configuration noscripts, or build noscripts.
Writers/Documentation Teams versioning Markdown or other text files where each file is a self-contained, independent whole.
Anyone who prefers a more straightforward, file-oriented method of saving history.
Key Features & How It Works
Individual Tracking: Each file is treated as an independent little repository. You don't commit the "project"; you commit the "file."
Simple Reversion: If you break one noscript, you can revert only that noscript to a former state without generating conflicts and touching any other files within your directory.
Built for Speed: Qwe is entirely Golang (GO) written, which keeps the underlying operations efficient and quick. It's compiled to one, static binary.
Try it Out!
I'm a programmer, not a designer, so it's presently a CLI tool, but it's fully working! I'd appreciate it if the community would give it a try and let me have some feedback on the workflow, command layout, and any bugs you discover.
Repo/Download Link: https://github.com/mainak55512/qwe
https://redd.it/1o3lgwv
@r_opensource
Hi everyone!
I'm stoked to finally release Qwe, a side project that I've been hacking at for the past few weeks.
The Problem Qwe Solves
We all adore Git, but occasionally its project-level tracking can be overkill. Did you ever attempt to revert a single stand-alone config file or a single Python noscript without bothering the rest of the project? Sure, you can do this, but usually, it requires you to use convoluted commands such as git checkout $COMMITHASH -- $FILEPATH and can be needlessly cumbersome.
I created Qwe to make this easier by centering the file as the main unit of version control.
What is Qwe?
Qwe is a Version Control System (VCS) in which you can commit, monitor, and revert files separately with ease.
It's ideal for:
Software developers working with many standalone utility noscripts, configuration noscripts, or build noscripts.
Writers/Documentation Teams versioning Markdown or other text files where each file is a self-contained, independent whole.
Anyone who prefers a more straightforward, file-oriented method of saving history.
Key Features & How It Works
Individual Tracking: Each file is treated as an independent little repository. You don't commit the "project"; you commit the "file."
Simple Reversion: If you break one noscript, you can revert only that noscript to a former state without generating conflicts and touching any other files within your directory.
Built for Speed: Qwe is entirely Golang (GO) written, which keeps the underlying operations efficient and quick. It's compiled to one, static binary.
Try it Out!
I'm a programmer, not a designer, so it's presently a CLI tool, but it's fully working! I'd appreciate it if the community would give it a try and let me have some feedback on the workflow, command layout, and any bugs you discover.
Repo/Download Link: https://github.com/mainak55512/qwe
https://redd.it/1o3lgwv
@r_opensource
GitHub
GitHub - mainak55512/qwe: A simple file-first atomic version control system
A simple file-first atomic version control system. Contribute to mainak55512/qwe development by creating an account on GitHub.
Exploring Vector Databases - Why opensource Cosdata OSS worked for me !
I’ve been exploring different vector databases lately for one of my projects - looking for something that’s fast, efficient, and cost-friendly to set up.
After digging into platforms like Cosdata, Qdrant, Weaviate, and Elasticsearch, I came across this performance comparison .
* Industry-leading 1758+ QPS on 1M record datasets with 1536-dimensional vectors
* 42% faster than Qdrant
* 54% faster than Weaviate
* 146% faster than Elastic Search
* Consistent 97% precision across challenging search tasks
Significantly faster indexing than Elastic Search while maintaining superior query performance.
Cosdata really caught my attention -especially because they offer an open-source edition (Cosdata OSS) that’s easy to experiment with for personal or production projects.
Recently, I joined their community, and it’s been great connecting with other developers who are building and experimenting with retrieval and AI-native systems.
If you’re working on projects involving semantic search, RAG, or retrieval systems, definitely worth checking it out. let me know if you want to join .
https://redd.it/1o3nkn8
@r_opensource
I’ve been exploring different vector databases lately for one of my projects - looking for something that’s fast, efficient, and cost-friendly to set up.
After digging into platforms like Cosdata, Qdrant, Weaviate, and Elasticsearch, I came across this performance comparison .
* Industry-leading 1758+ QPS on 1M record datasets with 1536-dimensional vectors
* 42% faster than Qdrant
* 54% faster than Weaviate
* 146% faster than Elastic Search
* Consistent 97% precision across challenging search tasks
Significantly faster indexing than Elastic Search while maintaining superior query performance.
Cosdata really caught my attention -especially because they offer an open-source edition (Cosdata OSS) that’s easy to experiment with for personal or production projects.
Recently, I joined their community, and it’s been great connecting with other developers who are building and experimenting with retrieval and AI-native systems.
If you’re working on projects involving semantic search, RAG, or retrieval systems, definitely worth checking it out. let me know if you want to join .
https://redd.it/1o3nkn8
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Markon • Minimal Distraction‑free Markdown editor
https://metaory.github.io/markon
https://redd.it/1o3thxj
@r_opensource
https://metaory.github.io/markon
https://redd.it/1o3thxj
@r_opensource
metaory.github.io
markon
Minimal distraction free local markdown live editor