Re: [briar-devel] Gnunet

[Michael R. <mi...@br...>]

On 14/08/17 12:34, t3sserakt wrote:
> I only know of a GNUnet devloper who made GNUnet running on Sailfish OS.

Great, maybe Android's not out of the question then.

> Is there some documentation available how to write a transport plugin?

At the moment I'm afraid the only documentation is the code.

In short, you write a class that implements either SimplexPlugin or
DuplexPlugin, and a factory that implements SimplexPluginFactory or
DuplexPluginFactory. Then add the factory to the PluginConfig. The
PluginManager will call the factory at startup to create a plugin, start
the plugin, poll it for connections periodically, and stop it at shutdown.

https://code.briarproject.org/akwizgran/briar/tree/master/bramble-api/src/main/java/org/briarproject/bramble/api/plugin

> How does briar do multicast in a forum?

Each forum starts out with one subscriber, the user who created it. Any
subscriber can share the forum with chosen contacts, so the forum
spreads through the social graph and the subscribers form a subgraph of
the social graph. We say that two users are syncing the forum if there's
an edge between them in the subgraph. In other words they both
subscribe, and one of them shared the forum with the other, and the
other accepted. (It's possible that they both subscribe but they're not
syncing the forum, ie there's no edge between them in the subgraph.)

Whenever a subscriber receives a new forum post - either one that she
wrote herself or one that she received from a contact - she offers it to
any contacts she's syncing the forum with. If they haven't already seen
it, they request it and she sends it. So the post is flooded through the
subgraph without sending any redundant copies.

Blogs use the same mechanism, except that posts have to be signed by the
blog's author, so any subscriber can share the blog, but only the author
can create posts that the subscribers will accept and propagate.

Private groups are also similar to forums, except the creator is the
only subscriber who's allowed to share the group. Each subscriber's
messages must be rooted in a join message co-signed by the creator, so
nobody else can create messages that the subscribers will accept and
propagate.

Happy to go into more detail if you're interested. :-)

Cheers,
Michael