Re: Manually storing DHT content

[TheJackiMonster]

On Wed, 2021-02-17 at 14:12 +0100, Schanzenbach, Martin wrote:
> Sounds a bit like you want to build something on top of messenger and
> fs actually.
> 
> Storing blog posts (e.g. html pages) in fs seems reasonable to me.
> And using
> the messenger feature for propagation/notifications of updates and
> possibly comments would allow you to
> build a content platform around it.

Something like this should be quite forward. The messenger service
supports sending file-messages which will allow sending files fully
encrypted inside of a group.

Otherwise it would be totally up to the application if these blogs are
only available for a selected group (using a shared secret) or making
it public by sharing the secret/(CADET port) with everyone.

> 
> Br
> Martin
> 
> > On 17. Feb 2021, at 14:09, Danny <danny.de.jong@protonmail.com>
> > wrote:
> > 
> > Hmmm, that's definitally interresting.
> > 
> > I was actually more concerned with a blog-like situation where
> > messages
> > can be considered to be posts and are available to the public,
> > preferably indefinetally. My objective in this case is freedom of
> > speech, not so much confidentiality.
> > 
> > I don't know how long the messages in a chat-room remain available,
> > but
> > I'm guessing the messages are encrypted for the other participants
> > that
> > were in the room at the moment the message was sent?

The messages will be sent through CADET. So they are encrypted via
CADET transport-layer. I've also added the possibility to encrypt
messages explicitly but this feature is for private chats mostly
because you had to encrypt for every individual receiver otherwise
which is quite resource heavy.

The messages get stored on every members peer until they leave the room
which they don't have to do at all (even going offline doesn't imply
leaving the room, so other peers can send you the missed messages later
on).

> > 
> > But anyway, good to see such a system is being integrated as well.
> > :)

Sharing files will still require some work on the API making the
encryption and storage of the encrypted files automatic. For demo
purposes you could try cadet-gtk already. This allows sharing files in
a very similar way using CADET and FS.

I'm also planning to add application specific messages for more custom
features but for now I have to optimize the message graph. ^^'

Happy hacking
Jacki

> > 
> > Danny.
> > 
> > On Wed, 2021-02-17 at 13:19 +0100, TheJackiMonster wrote:
> > > Hey Danny,
> > > 
> > > if you want to share small content as text messages inside of a
> > > group
> > > of people, you could take a look at the messenger service, I am
> > > working
> > > on.
> > > 
> > > It could be possible that it already fills your needs. You can
> > > open
> > > something like a chat-room on peers to exchange messages in a
> > > decentralized way. These messages get signed and can even be
> > > requested
> > > from other members when the original author is offline.
> > > 
> > > It's not completely finished but some tests for message exchange
> > > between peers are already succeeding. (Just notice that there is
> > > only
> > > doxygen as documentation at the moment. I'm still working on a
> > > proper
> > > manual and such. ^^')
> > > 
> > > Happy hacking,
> > > Jacki
> > > 
> > > On Wed, 2021-02-17 at 12:01 +0000, Danny wrote:
> > > > Hey Christian,
> > > > 
> > > > First of all thank you for the answer.
> > > > 
> > > > Actually, I'm thinking of creating a `social blog` application
> > > > in
> > > > which
> > > > friends connect to friends.
> > > > I was hoping for some way of ensuring persistence of content
> > > > across
> > > > a
> > > > (social) network. The friend peers could best be providing for
> > > > the
> > > > storage of the content, doing away with the need of random
> > > > unrelated
> > > > peers providing the storage.
> > > > The thing is, I'm expecting the content to be small text
> > > > messages a
> > > > lot
> > > > of the time.
> > > > I think the filesharing subsystem might be a little bit to much
> > > > overhead for this, considering that file blocks are 1024 bytes,
> > > > and
> > > > there is a lot of functionality that I don't need for this.
> > > > 
> > > > Any ideas? Otherwise, I will probably have to create my own
> > > > subsystem
> > > > for this I guess. I was just looking at DHT and hoping it would
> > > > fit
> > > > my
> > > > use case. If I had the ability to have the friend peers store
> > > > the
> > > > content without the need of the originator of the content to be
> > > > online,
> > > > I would have been there.
> > > > 
> > > > Thanks.
> > > > Danny
> > > > 
> > > > 
> > > > 
> > > > On Wed, 2021-02-17 at 12:29 +0100, Christian Grothoff wrote:
> > > > > Nope, datastore is _only_ for the file-sharing subsystem,
> > > > > datacache
> > > > > is
> > > > > for the DHT (alas DATACACHE does not have such an API, you
> > > > > must
> > > > > use
> > > > > the
> > > > > GNUNET_DHT_put-API).
> > > > > 
> > > > > Happy hacking!
> > > > > 
> > > > > Christian
> > > > > 
> > > > > On 2/17/21 11:57 AM, Danny wrote:
> > > > > > Hey guys,
> > > > > > 
> > > > > > Quick question.
> > > > > > Can I use GNUNET_DATASTORE_put for manually storing content
> > > > > > that
> > > > > > would
> > > > > > be available by DHT GET requests from others nodes?
> > > > > > 
> > > > > > Thanks!
> > > > > > Danny
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > 
> > 
> > 
> > 
>

signature.asc
Description: This is a digitally signed message part