HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
athensresearch
athens
Clojure2020–2023
athensresearch / athens

athens

Athens is no longer maintainted. Athens was an open-source, collaborative knowledge graph, backed by YC W21

34Distinct people
42Mentions
0Explicit recommenders
6.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Athens is no longer maintainted. Athens was an open-source, collaborative knowledge graph, backed by YC W21

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM 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 year42 dated mentions

Observed mentions: 2020-05-15 09:09:50 UTC to 2023-02-13 21:46:29 UTC.

051015202020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 21 mentions; 2 submissions, 19 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023

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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC17215
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC21219
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211

What Hacker News says

42 sources
I cam across two alternatives for Roam Research: Foam. Built on Visual Studio Code and GitHub, Foam is early but already powerful. Write your content in markdown, use [[page]] for internal links, and explore your content with an interactive graph. The Backlinks Explorer lets you find all notes that link to a specific note. Foam also makes it easy to back up your notes on GitHub. [1] Athens. Quite ambitious, Athens aims to offer a full open-source version of Roam. Built with Clojure. It's founder wanted to work for Roam but was rejected because he didn't know Clojure. So he learned Clojure and started writing an open source alternative. Roam was rejected by YC but AThens was accepted. [2] [1] https://foambubble.github.io/foam/ [2] https://github.com/athensresearch/athens
In How to build a second brain as a software developer
I am a design technologist [1], so I end up doing things when specialists are too busy or unavailable or they don't exist. I do research, build prototypes, design interfaces, and even write growth strategies. Over the years, I have to learn things ASAP to get things in place before world breaks loose. I follow an approach that I call : SPOTS. It stands for Survey, Prioritise, Organise, Test, Show. Lets go through it one by one : 1. Survey : Collect all possible things you need to know about a new topic or thing. Make a mind-map. Do not forget to check out academic sources for possible models. Reddit and HN are cool places to look. This should be done in a time boxed manner. 2. Prioritise : Now we bring the goal and see our mind map in context. So, you want to build an app and you know, say, Nuxtjs. How can you do it so you have to acquire
Read the rest
as little skills as possible. Or you want to write a research protocol for conducting a simple user test for a product. This step will help you find possible ways to reach goal. Now, you have a prioritised way to achieve the goal and maybe have a sense of how things could be. 3. Organise: This step is very important. The prioritised 'knowledge elements' have to be revisited again and again. Using a small notes app or Athens[2] you can make a list of key steps or if its a tutorial, the major steps. In short, take notes. This will help you bring more clarity in terms of various approaches you can use the knowledge elements. Say, you need to use low power mode on ESP32, you have the documentation + sample code and you know how it works. 4. Test ( or Try) : Now you need to keep trying and testing the various arrangements of knowledge elements and what works and what not. Dont get attached to any particular way. Keep figuring out. With code etc it is easier, with research (and human things), test things with friends or cousins. The idea is to be iterative and see if we are able to get to the goal. Iteration is the key. Sometimes you might need new 'knowledge elements' that you might have missed out. 5. Show : This is the most important and something all good humans should do, as philosophers would say, further the epistemological understanding of humans— write a f#$king blog, post a documentation, or answer a stack overflow, heck at least make a tik-tok. This will make sure, if someone gets stuck solving the same problem in the future, your knowledge element will help them. Also, it cements the concepts for you as well. sings "You may say, I am dreamer...But, I am not the only one" [1] http://rohitg.in/portfolio/ or http://rohitg.in [2] https://github.com/athensresearch/athens
In Ask HN: How Do You Learn?
I started using https://github.com/athensresearch/athens I quickly fill with lot of information, I miss code feauteres like markdown github fencing ```, but so far is great, searh is fast, adding new data is good, refereces links and back links really adds to the information, and the daily page is useful. I just would like to have more features about code It has a developer mode, where you can run clojuru to query the nodes, I'm starting to use it to create code references between nodes, nothing useeful, but you definitevely can start playing with it
In Why Young Developers Don’t Get Knowledge Graphs
We can speculate around someone's motivations all day, but no one can speak for this engineer but themself, and it sounds like they would (understandably) prefer to keep private matters private. At the end of the day he probably got an offer more favorable than his current package in some dimension that's important to him. Boring answer but it is what is. Earlier stage often means opportunity for more equity... That said, Roam itself appears really small and only to have just raised 9M ~9 months ago. So they are likely either raising their next round now / imminently. As someone with no horse in the race, I do not think it says anything about Roam itself. The average employee tenure at a startup is ≤ 12 months and I want to say the actual figure is ~9 months so this isn't particularly unusual. One potentially interesting question migh
Read the rest
t be, does Roam have a non-compete [and will they attempt to enforce it]? But it looks like they are based in SF... so probably not. Another potentially angle is to research the background of the new startup's founders. It looks like Athens' product is open source [1] while Roam's is not. That can be substantial to a lot of the engineers at the end of the day. [1]: https://github.com/athensresearch/athens
In Ask HN: What does it mean if lead engineer moves to competition?

Showing the 15 most recent of 42 sources. Enable JavaScript to search and browse every indexed mention.

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.