HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aethereans
aether-app
JavaScript2013–2023
aethereans / aether-app

aether-app

Aether client app with bundled front-end and P2P back-end

12Distinct people
19Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Aether client app with bundled front-end and P2P back-end

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 1:57:11 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 year19 dated mentions

Observed mentions: 2013-11-23 22:53:42 UTC to 2023-06-13 06:51:00 UTC.

02468102013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC110
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC10010
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

2 sources
We have something similar to this, Aether. https://getaether.net. (code at github.com/nehbit/aether) Always glad to see more eyeballs on the space, so I wish then the best. Here are a few differences I can see at the first glance: - Aether is decentralised (as in torrent) this appears to be federated. That means Aether truly has no servers and every user is a peer, while federated means there are smaller ‘Reddits’ as servers that talk to each other. - By proxy that means we can’t really have a web app unfortunately (working on it by the way of running a daemon on a raspberry pi) and they can - we need a native app running on your machine and seeding context to the network. - By another proxy, this means Aether avoids the issue of having a ‘middle management’ in the form of the ownership of your home server that federated networks have. Yo
Read the rest
u are the home server, so no one can control what you see. We call this user sovereignty - In Aether we have elections which elect mods based on popular vote and you control who is a mod, precisely because the ‘social compiler’ runs on your machine and allows you to compile it however you want. Two people with two different mod lists for the same community can see drastically different communities - We have a mod audit log and have had it for a while - everyone’s mod actions are visible to everyone (this I think they also have) - Lastly, we have made the decision to not monetise Aether itself and create a team communication app called Aether Pro, and monetise that. This creates a ‘Chinese wall’ between where we make our money and the P2P network, which means it’s a shield against drifting towards trying to make money from a social network. The code bases are separate but similar, so that also means work done on the Pro helps Aether as well. We have gotten some funding for the Pro, and we consider the P2P version a ‘marketing / goodwill expense’ in the context of that funding. That aligns us towards making sure Aether is long-term viable, well maintained and monetisation-free. In contrast I think they’ve gotten money to work directly on this, which has both good and more hazardous sides. In summary, we opted for a long term structure that has less moral hazard (in my opinion, of course), in favour of a more stable app without a need for monetisation that has fewer, more stable releases. For context, here's how a recent thread looks on my Aether client: https://i.imgur.com/45tXQEO.png
In Lemmy, an open-source federated Reddit alternative, gets funding for development

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.