I’m here to answer any questions as usual. I’ll pick the best and try to add it to the FAQ on the site.
I’m here to answer any questions as usual. I’ll pick the best and try to add it to the FAQ on the site.
Can you track how many people installed it, now that it is on HN?
You say it puts everyone on "one single universe with the same content". So it should be easy to put up an instance that provides a web interface to the content, right?
I would think that posting via the browser should also be possible without relying on a single server / authority. A user could hold a private key which they use to sign their posts. And then deliver the post via any server that offers an interface for it. Similar to how a Bitcoin transaction can be delivered via any server that offers such a service.
So it would still be decentralized but can be used via the browser.
Yes it would be easy - that would just be an another node that showed it’s read-only UI on the web. (You still need to mint proofs of work, so you would need an actual computer for posting.)
* The FAQs say that the app is a p2p based app. What is the p2p protocol being used here? * How does it compare to libp2p, SSB, and others? * What's the security model, and how would the system mitigate Sybil attacks etc?
Are there any plans to have mobile apps (preferable native)? I think if people could use it on their mobile phones, it would be a game changer.
> The FAQs say that the app is a p2p based app. What is the p2p protocol being used here? * How does it compare to libp2p, SSB, and others? * What's the security model, and how would the system mitigate Sybil attacks etc?
It's built from scratch. It runs c0 subprotocol of Mim. You can see some basic comparisons here: https://getaether.net/docs/how_is_it_different_from/
Other questions - all good questions, but it depends on what your definition of security model is. Sybil attacks are prevented by cryptographic signatures and proof of work. Unique names are available to provide a good human-friendly polish over cryptographic signatures, as well.
> Are there any plans to have mobile apps (preferable native)? I think if people could use it on their mobile phones, it would be a game changer.
Yes, I would _love_ to have mobile apps. The system supports it, but I don't have the money to spend the time building them, or to pay someone to build them. In essence, it depends on how popular the project gets - if enough people support it financially, it would certainly be a first priority.
Can you elaborate? Googling these terms doesn't produce much other than a few papers using "MiM" to mean man-in-the-middle, as well as your comment itself!
Mim (comes from 'mime' from 'to replicate') is a HTTP based stateless protocol where the nodes communicate with each other via bog-standard HTTP GET and POST requests. The nodes can create caches for oft-requested data. c0 is a subprotocol of Mim that defines six graph objects, boards, threads, posts, userkeys, votes and truststates. the first four are obvious, the vote is a userkey > b|t|p relation, a trustste is a userkey > userkey relation. It creates a directed graph that is mostly acyclic.
It allows for efficient flood-network propagation of this graph based on time intervals, and it comes with certain patch semantics, so given a delta communicated from one node to another, there is always a way to apply that delta into the local node's graph in a way that does not create merge conflicts.
If there's a library/protocol that could be embedded in a native app, I would love to play with it. I'm a mobile developer with some free time at hand. I'll drop you an email.
edit: oops, just found this https://meta.getaether.net/t/how-to-use-aether-behind-tor/53
(backed on patreon btw)
In summary, SSB is, from what I can see, designed for non-public sharing of Twitter-like content between friends, and your data only traverses to people who follow you.
In contrast, Aether is explicitly designed to be a public space where you talk to people you don't know. It communicates everyone's information to everybody. To make that possible, Aether only accepts and transmits text (you can still link to stuff), while SSB can transmit other formats directly in the protocol itself.
(I might be horribly wrong: I'm not a SSB expert. Please correct me if so.)
c.f. aether://board/86e782e80681ac580b4d6d102b12e787c066e59f194fee57bb0bf83cc1e42fc6/thread/4932c494227ccd4f632c2ace1012f58fd79d0d531b2dcd148463491598c841d8
Also, does the proof-of-work scale, eg how the bitcoin network gets harder and harder as the hashing power increases.
How does the unique username perk for patrons work? Does it mean that people can still create "normal"-coloured usernames, but there can only be one orange "verified" one?
Pseudonymity and ephemerality are the two sides of the same coin. One doesn’t protect without the other.
The entrepreneurial (and governments) will archive everything to serve the wealthy (including governments), who will be able to use history to their ends. Those without resources will live in an eternal present, except where history is used against them.
To sell this kind of retention policy as a user-protecting feature is (in my view) at best naive, and at worst, disingenuous. This model increases the economic cost of mining history, but in doing so, entrenches existing wealth and power structures.
Thanks to the ever-decreasing cost-per-bit of storage, the internet is forever. The only hope for redemption lies in this permanence affecting everyone equally; otherwise we're doomed to (continue to) live in a world where only the wealthy and politically connected have read and write access to history.
> ... but in doing so, entrenches existing wealth and power structures.
What entrenches existing wealth and power structures is wealth and power. That's why it's valuable to have wealth and power. In other words, you could prefix that sentence with almost anything, and you'd still be right.
The privacy thing is free marketing that came out of that constraint.
This is really a good marketing move tbh. Everybody wants privacy and nobody understands what it technically means.