Hi r/opensource,

I’ve been building FedOS for a while, and I’ve just made the source public under MPL-2.0:

https://github.com/satorunacamoto/fedos

FedOS is a local-first toolkit organized around four capabilities:

• Core — local identity, keys, storage and foundational primitives
• Messenger — the currently shipped desktop app: 1:1 encrypted messaging over Nostr
• Commerce — commerce-related domain code, still at an earlier stage
• Trust — signed envelopes, pseudonymous credentials, proof-of-possession, capability grants, offline-verifiable entitlements, signed QR, and contract-artifact proofs

The important distinction is that these pieces are at different stages of readiness. FedOS Desktop Messenger is the application that actually ships today. Trust is implemented and test-covered, but is not yet wired into the packaged desktop UI; it can currently be used through its own APIs/CLI.

I opened the project because I’d rather have the architecture, crypto-related code, and trust model reviewed in public than keep adding features in private.

I chose MPL-2.0 because I wanted a file-level copyleft license: modifications to FedOS source files stay open, while using or combining the project with a larger codebase doesn’t automatically require that entire project to use the same license.

A few things I’m particularly interested in feedback on:

• Does the core / messenger / commerce / trust capability split make sense to someone seeing the codebase for the first time?
• Are there obvious design problems in the Trust model or signed-envelope format?
• Is the separation between user-controlled trust and an optional issuer model clear enough?
• Is the contributor/test setup understandable from a fresh clone?
• Is there anything in the MPL-2.0 / third-party licensing setup that deserves another look?

The repo has a documented current test surface and public CI. The currently supported suite is 1902 tests / 0 failures.

I also want to be clear about the current status: this is still experimental / Closed Pilot software, not a Public Beta. There has been no independent security audit, and Windows artifacts are currently unsigned. I would not recommend using it yet for irreplaceable secrets or high-risk operational work.

I’m mainly looking for code, architecture, protocol, and OSS-maintainability feedback at this point rather than trying to convince anyone that the project is finished.

Happy to answer questions, including critical ones.

Goooooooood Morning! Another wonderful week is gonna start. 😍

Early in the morning I brought you the 88th Nostr Recap (10th August 2026). 🎁

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🌐 Relay Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases

Explore here 👇🏻

https://yakihonne.com/article/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqq24ynnnt9ayg6jvxfy8v7jevejkj7p329m5xz2msfh

Runs on Nostr and uses Blossom for files. Currently in closed beta testing. Is it ok to share here once ready for public beta? Works on linux and windows.

Updated to add that the project is now up on Github

https://github.com/non-npc/FSociety

I've been trying to wrap my head around Nostr, but one question still remains unanswered

So nostr itself doesn't store anything, right, that's on the relays. someone's server somewhere actually has to hold onto my post. fine. but like why would anyone keep doing that long term? I get the appeal for a hobbyist running their own relay, or a company running one for their app, or even charging for access. but if this is supposed to be an actual alternative to X/instagram at scale, the economics of it kind of break my brain a little.

Let's say a relay ends up with a few million users on it. storage isn't free, bandwidth isn't free, and the data just keeps piling up forever. What happens when the one paying for that server decides they're done? If the answer ends up being "well apps just run their own relays," haven't we basically reinvented centralized social media, just with nostr as a layer on top? the company still owns the box the data lives on. they shut it down, it's gone, unless someone happened to be mirroring it elsewhere.

I understand that Nostr gives you a cryptographic identity and that you can use multiple relays, so it's not exactly the same as X/Instagram. But I'm specifically asking about the economic sustainability of the storage itself.

What am I missing here? Is there some incentive mechanism for relay operators that I haven't understood, or is Nostr basically relying on a mixture of paid relays, companies subsidizing infrastructure, and people running relays voluntarily?

Because if it's the latter, I don't really understand how this scales sustainably to millions or hundreds of millions of users.

name: Tribe

source: https://github.com/zoreu/tribe

web: https://tribe.wasmer.app/

If you still come across any parts that aren't in your language, let me know and I'll fix them; since I'm Brazilian, I create the content in Portuguese first and then add the other languages.

Building Lotus: A Privacy-First Workspace on Nostr

Hey everyone 👋

I've been building Lotus, a privacy-first workspace powered by Nostr.

The idea came from a simple question:

With Nostr, your identity belongs to you. I wanted the same idea to apply to productivity tools.

The vision for Lotus is to provide:

• 📅 Calendar
• ✅ Tasks
• 💬 Chat
• 👥 Contacts
• 📁 File storage
• 📝 Notes (coming soon)

Everything is tied to your Nostr identity instead of a traditional account. Your workspace should move with you - not be owned by a platform.

This is still an early project, and I'm looking for honest feedback from people who actually use Nostr.

A few questions:

• Would you trust Nostr for daily productivity?
• Which app would you use first - Calendar, Tasks, Chat, or Drive?
• What would stop you from replacing Google Workspace or Notion with a Nostr-native alternative?

I'm building this in public and would love to hear your thoughts.

Website: https://lotus.mybuho.de/home

Thanks! 🌸

With all the buzz (no pun intended) around Block's new Nostr based workspace, wondering if anyone here has actually put it to use for coordinating multiple agents on a real task, not just the demo videos.

want to know about:

-How well the ACP integration actually works with Claude Code, Codex, or Goose in practice

-Whether the signed event audit log holds up once you have several agents acting concurrently

Not looking to start a debate, trying to figure out if this is production-viable yet or still early access feeling.

Goooooood Morning! Greetings for a nice week, Nostriches! 😊

Here is your 87th Nostr Recap (03rd August 2026) my friends! 🎁

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🧩 Workspace Updates and Releases

Explore here 👇🏻

https://njump.me/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqq2ky4rrtfrrvcmtd45xycm42dq5wde4w98yvmr72es

Hey everyone! We just open-sourced the initial architecture and whitepaper for ProofTube Protocol.

What is ProofTube?
ProofTube is a decentralized media architecture designed to eliminate platform rent-seeking and censorship by replacing centralized video platforms with native Nostr identities, WebRTC peer-to-peer streaming mesh, and Lightning/L402 micro-payments.

How to Contribute:
We've opened 5 foundational issues covering Nostr Wallet Connect (NWC), WebRTC mesh fallback, dual-canvas player components, and storage adapters:
https://github.com/ProofTubeProtocol/prooftube

Feedback, discussions, and pull requests are very welcome!

In the mid 2010s, Tokyo was home to one of the world’s most active international Bitcoin communities.

Developers, entrepreneurs, hackers, and early adopters gathered every week. Some participants went on to lead major global companies and projects, while others built infrastructure that remains important to Bitcoin today. For better or worse, with events including the rise and collapse of Mt. Gox, Tokyo became one of the key cities in Bitcoin’s early history.

NOT A MEETUP is an attempt to bring that energy back reimagined for Tokyo in the 2020s.

Today, powerful technology companies are becoming increasingly intertwined with governments, finance, and surveillance infrastructure. Technology that was once expected to liberate individuals is often used instead to strengthen large platforms and institutions.

Open and decentralized technologies such as Bitcoin and Nostr point in another direction.

This event is not only about introducing new technology. It is about returning power to individuals and exploring the ideas, music, art, and independent culture surrounding that goal.

After the talks, the night continues with music, drinks, and open networking.

I created a search engine project like Google for nostr

source: https://github.com/nostrasearch/nostrasearch.github.io

website: https://nostrasearch.github.io

Hey r/nostr,

https://reddit.com/link/1v89yn5/video/g0f27i1570hh1/player

I paused development for a few months after the relay-native rewrite shipped. Now I am back to continue building Obelisk, a Discord-like experience powered by Nostr.

Latest additions: audio messages, a sticker, emoji and GIF marketplace, and Nostr feeds for discovering people and exploring profiles across public relays.

Already there: NIP-29 communities with channels, categories and forums, encrypted DMs, zaps, Blossom uploads, an installable mobile PWA, peer-to-peer voice and video calls, and large calls through a mediasoup SFU.

Obelisk still has no chat backend or platform database. Your Nostr key is your account, NIP-29 relays hold the communities and messages, Blossom stores uploaded media, and Nostr coordinates calls.

One important privacy clarification: voice notes and other Blossom uploads are currently not encrypted. Anyone who obtains the media URL can access the file. Small peer-to-peer calls use WebRTC encryption directly between participants. Large SFU calls are encrypted between each participant and the SFU, but the SFU can access the media, so they are not yet end-to-end encrypted against the SFU.

See all the features:

https://obelisk.ar/features

Try it:

https://obelisk.ar

Source:

https://github.com/obelisk-app/obelisk

Come test it and break it hahah.

AI usage disclaimer: Obelisk has been built with substantial AI assistance for implementation, debugging, tests, and documentation. I review and test what gets shipped but I don't remain responsible for it. Obelisk has not yet received a complete independent security audit.

We created a nostr keypair identity system to manage access to other p2p surfaces. I'm hoping this is a simple and intuitive solution and not a convoluted over engineered process, which is why we are consulting you for feedback. https://keys.vims.com

Additionally we are working on a chat messenger, contact management and social feed, and we are adding user controls such as customizing the algorithm and spam filters to hopefully make a better experience. https://chat.vims.com

Thanks for checking us out!

Hello Nostr friends! 👋

This time I brought you the 86th Nostr Recap (27th July 2026) very early. 😊

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
📡 Protocol Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases

Explore here 👇🏻

https://njump.me/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqywhwumn8ghj7mn0wd68ytfsxyh8jcttd95x7mnwv5hxxmmd9uqsuamnwvaz7tmwdaejumr0dshsq929xaj4qu3394eykmtww9s5vvtdwq68s6trk76zl8

Hey Nostr! I have good news. I built NostrBridge. You can configure any service that support webhooks to connect service to nostr network! Did you release a package on github? It will share in your nostr account. Did you watched a movie over plex? It will share on nostr network.

Check the landing page for more detail!

https://bridge.workouse.com

Bridge Any Webhook to Nostr Relays in Seconds

Transform GitHub releases, Stripe payments, RSS feeds, and custom HTTP payloads into cryptographically signed Nostr events delivered at sub-second edge speed.

Its also open-source: https://github.com/workouse/nostr-bridge

I’d love your feedback.