HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
subconsciousnetwork
noosphere
Rust2022–2023
subconsciousnetwork / noosphere · Archived

noosphere

Noosphere is a protocol for thought; let's discover it together!

2Distinct people
7Mentions
0Explicit recommenders
699GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Noosphere is a protocol for thought; let's discover it together!

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week7 dated mentions

Observed mentions: 2022-11-01 18:26:41 UTC to 2023-06-01 15:39:46 UTC. Weeks start Monday, UTC.

012342022-10-31 00:00:00 UTC to 2022-11-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 312022-11-07 00:00:00 UTC to 2022-11-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-14 00:00:00 UTC to 2022-11-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-21 00:00:00 UTC to 2022-11-28 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-11-28 00:00:00 UTC to 2022-12-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-05 00:00:00 UTC to 2022-12-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-12 00:00:00 UTC to 2022-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-19 00:00:00 UTC to 2022-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-26 00:00:00 UTC to 2023-01-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-02 00:00:00 UTC to 2023-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-09 00:00:00 UTC to 2023-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-16 00:00:00 UTC to 2023-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-23 00:00:00 UTC to 2023-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-30 00:00:00 UTC to 2023-02-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-06 00:00:00 UTC to 2023-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-13 00:00:00 UTC to 2023-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 132023-02-20 00:00:00 UTC to 2023-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-27 00:00:00 UTC to 2023-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-06 00:00:00 UTC to 2023-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-13 00:00:00 UTC to 2023-03-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-20 00:00:00 UTC to 2023-03-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-27 00:00:00 UTC to 2023-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 00:00:00 UTC to 2023-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-10 00:00:00 UTC to 2023-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-17 00:00:00 UTC to 2023-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-24 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-05-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-05-08 00:00:00 UTC to 2023-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-15 00:00:00 UTC to 2023-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-22 00:00:00 UTC to 2023-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-29 00:00:00 UTC to 2023-06-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 29

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 312022-10-31 00:00:00 UTC2022-11-07 00:00:00 UTC101
Nov 72022-11-07 00:00:00 UTC2022-11-14 00:00:00 UTC000
Nov 142022-11-14 00:00:00 UTC2022-11-21 00:00:00 UTC000
Nov 212022-11-21 00:00:00 UTC2022-11-28 00:00:00 UTC404
Nov 282022-11-28 00:00:00 UTC2022-12-05 00:00:00 UTC000
Dec 52022-12-05 00:00:00 UTC2022-12-12 00:00:00 UTC000
Dec 122022-12-12 00:00:00 UTC2022-12-19 00:00:00 UTC000
Dec 192022-12-19 00:00:00 UTC2022-12-26 00:00:00 UTC000
Dec 262022-12-26 00:00:00 UTC2023-01-02 00:00:00 UTC000
Jan 22023-01-02 00:00:00 UTC2023-01-09 00:00:00 UTC000
Jan 92023-01-09 00:00:00 UTC2023-01-16 00:00:00 UTC000
Jan 162023-01-16 00:00:00 UTC2023-01-23 00:00:00 UTC000
Jan 232023-01-23 00:00:00 UTC2023-01-30 00:00:00 UTC000
Jan 302023-01-30 00:00:00 UTC2023-02-06 00:00:00 UTC000
Feb 62023-02-06 00:00:00 UTC2023-02-13 00:00:00 UTC000
Feb 132023-02-13 00:00:00 UTC2023-02-20 00:00:00 UTC000
Feb 202023-02-20 00:00:00 UTC2023-02-27 00:00:00 UTC000
Feb 272023-02-27 00:00:00 UTC2023-03-06 00:00:00 UTC000
Mar 62023-03-06 00:00:00 UTC2023-03-13 00:00:00 UTC000
Mar 132023-03-13 00:00:00 UTC2023-03-20 00:00:00 UTC000
Mar 202023-03-20 00:00:00 UTC2023-03-27 00:00:00 UTC000
Mar 272023-03-27 00:00:00 UTC2023-04-03 00:00:00 UTC000
Apr 32023-04-03 00:00:00 UTC2023-04-10 00:00:00 UTC000
Apr 102023-04-10 00:00:00 UTC2023-04-17 00:00:00 UTC000
Apr 172023-04-17 00:00:00 UTC2023-04-24 00:00:00 UTC000
Apr 242023-04-24 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 12023-05-01 00:00:00 UTC2023-05-08 00:00:00 UTC101
May 82023-05-08 00:00:00 UTC2023-05-15 00:00:00 UTC000
May 152023-05-15 00:00:00 UTC2023-05-22 00:00:00 UTC000
May 222023-05-22 00:00:00 UTC2023-05-29 00:00:00 UTC000
May 292023-05-29 00:00:00 UTC2023-06-05 00:00:00 UTC101

What Hacker News says

4 sources
Currently we have a CLI that demonstrates multi-device synchronization in principle. You can install it using `cargo install noosphere-cli` (it installs a binary called "orb"). We also have pre-built binaries of orb for x86_64 Linux that you can find on our releases on Github (e.g., https://github.com/subconsciousnetwork/noosphere/releases/ta...). We'll be expanding our pre-built binaries to include other platforms soon. Also, we have recently released a Swift package that gives a path to easily install our project as a dependency in XCode. We're turning the corner on offering the same FFI backing implementation as a TypeScript + WASM package, too. But, as I mentioned it's early days for us, so set your expectations accordingly. The best way to stay up to date with new things you can do is join our Discord. I make regular announcements th
Read the rest
ere about our technical progress.
In Noosphere, a Protocol for Thought
Anytype seems to be playing in the same general space that we are. But, all I know about it is what I can glean from their website, so I can't say for sure how similar it is in concrete terms. To offer one distinction: while both projects are at an early stage and undergoing development, Noosphere has been open source from the beginning. You can scrutinize our work and kick the cans on it today (warning: very alpha / do not use in production). We invite active participation from all who are interested, and welcome contributions to our Github projects. https://github.com/subconsciousnetwork/noosphere
In Noosphere, a Protocol for Thought
Hi there, I work with Gordon (OP) on Subconscious and Noosphere. This is a topic that we take seriously and think about a lot together. We've had some good discussions in our Discord, and some of our motivating goals have manifested as issues on Github: https://github.com/subconsciousnetwork/noosphere/issues?q=is... Our work is open source, and we are building it in the open hand-in-hand with our community. I personally respond to as many issues and stray comments on Discord as I can. If this is a topic that you care about, your feedback, comments and ideas would be very welcome. > I would push the protocol authors to fully consider the ramifications of doxxing, harassment, accidental self-disclosure, etc—especially in authoritarian nations. If they don't have a story for how they'll handle this, it's not an appropriate foundation for the
Read the rest
internet of ideas. My personal opinion is that we need more than a story. Our users need tools that empower them to be in control of their data, and that includes being able to keep private data private, fix mistakes and execute countermeasures when they are threatened with abuse. And it's true: immutable data is a double-edged sword. The primary benefit we seek from it is content addressing, which enables us to look up some data in a way that makes data providers fungible. This has an advantage when it comes to censorship: if censored network A can't give you your data, you may be able to find it on uncensored network B as long as your know the content address. It also presents a challenge: sometimes a user may rightly wish for data to be removed from the network; content addressing creates the possibility that an abuser may have access to data in a way that further dis-empowers users who are already vulnerable today. Here is a strong opinion (weakly held) that I have about mutability: the "mutability" of the hypertext web has not spared us from the kinds of danger described above. We have leaned on mutability as a privacy crutch, and in turn we have excused ourselves from providing capabilities and interfaces that enable real privacy and agency for users under threat. For example, a user may think a Snap message is extra private - from their perspective, the message is ephemeral - but others will still find ways to make copies and propagate the data across the network, and Snap the company certainly has access to the data (perhaps in perpetuity). What recourse does that user have once their data escapes the mutable sandbox? It's possible that immutable data will enable us to build better tools for taking pro-active action against abuse. For example: today on the hypertext web, the recourse for most users to head off the propagation of harmful data is to reach out to service providers individually, file abuse claims and hope that the content is eventually removed. Victims are burdened with both identifying that the data is stored with a provider, and also the clerical task of reporting the abuse over and over again. In a world with content addressing, anti-abuse filters full of content addresses may propagate fluidly from provider to provider, which suggests a far less burdensome process for the abuse victim - they don't need to know that the content has surfaced on some provider in the distance, because the provider is already aware of the abuse claim and can pro-actively refuse to propagate the data. In the end, I think the best solutions to the problems of this kind of abuse will be social/legal ones, supported by a technical foundation that can enable pro-active countermeasures. All that said, I'm not an expert on this topic, I just like to spend a lot of time thinking about it. If you or someone else reading this is an expert, and you have some time to spare, please come hang out in our Discord or on Github and teach us what you know!
In Noosphere, a Protocol for Thought
This looks like really cool technology, but what is the use case for "normal" users? The Subconscious site [1] which leverages this library lists the key value propositions as "Own Your Data," "Decentralized," and "Open Source," which are three things average users demonstrably don't care about. I'm also concerned about the immutability of information stored in this way. [2] There are a number of reasons why immutability (in this case a fully public version history) is an anti-feature, with significant real-world risks. I would push the protocol authors to fully consider the ramifications of doxxing, harassment, accidental self-disclosure, etc—especially in authoritarian nations. If they don't have a story for how they'll handle this, it's not an appropriate foundation for the internet of ideas. [1]: https://subconscious.network [2]: http
Read the rest
In Noosphere, a Protocol for Thought

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.