mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.8K
active users

@what @cwebber let me know if this helps: we're trying to do for p2p, decentralized apps what things like rails and django did for web 2.0 apps. that is: we want to give you a technology stack that lets you focus on the business logic of your app and have the output be both secure and decentralized.

@dthompson @what @cwebber

I can highly recommend taking a look at the pear runtime. If you are familiar with nodejs javascript, all it takes is:

`npm install pear -g`

and then

`pear run pear://runtime`

to get started. Just follow instructions.

This runtime is part of the @dat_ecosystem and JS was choosen to exactly provide an easy way for anyone to get started with p2p.

an example cross platform app is keet.io

runtime docs are here docs.pears.com

have fun 🙂

keet.ioKeet - The Peer to Peer Chat AppKeet is a peer-to-peer chat application that allows users to communicate directly with each other. 100% end-to-end encrypted. Never on a server.

@serapath @what @cwebber @dat_ecosystem I am looking at the docs and it appears to be blockchain based, or at least uses something similar? is that correct? specifically looking at hypercore as it appears to be the central component docs.pears.com/building-blocks

docs.pears.comHypercore | Pears.com

@dthompson @serapath @what @cwebber

dat started in 2013 and is a 501c3 public good organisation. the initial dat grew into a protocol, then into a project, then into a foundation hosting multiple projecys, into an ecosystem of projects with the dat a.k.a hyper stack having its own peer to peer runtime, much closer to the original nodejs vision of the early days.
The dat stack or hyper-stack including hypercore is open source and does not and will never use any blockchain.

@dat_ecosystem @serapath @what @cwebber thanks for clarifying. is it correct though that hypercore is the foundational piece here? I see "append-only log" and "signed merkle tree" in the project readme.

𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇬🇧)

@dthompson @dat_ecosystem @what @cwebber

The foundational piece is hard to say in a hyper modular ecosystem.

If i would need to list the main pieces, i'd say its the interaction between the following modules:

p2p networking:
1. hyperdht
2. hyperswarm
3. hyperdht-relay

data replication protocol:
1. hypercore
2. corestore

data structures
1. hyperbee
2. hyperblob
3. hyperdrive
4. hyperdb

multiwriter
1. autobase

There are many more useful modules build and maintained by many ecosystem devs

@dthompson @dat_ecosystem @what @cwebber

And the most interesting way to start using them is probably the `bare runtime` if you want something low level

...or the pear runtime if you want to build cross platform apps and have a more electron like batteries included runtime.

pear runtime extends bare runtime

keet.io is an example app built with the stack and does not involve ANY servers or ANY cloud. ...it features text, image and file sgaring, video and audio calls

keet.ioKeet - The Peer to Peer Chat AppKeet is a peer-to-peer chat application that allows users to communicate directly with each other. 100% end-to-end encrypted. Never on a server.

@serapath @dat_ecosystem @what @cwebber I found this tutorial which was helpful for understanding things a little better. docs.pears.com/guides/making-a

I see that networking uses dht: hyperswarm -> hyperdht -> dht-rpc

what's the serialization format for messages (peer.write in the tutorial)? is it json?

docs.pears.comMaking a Pear Desktop Application | Pears.com

@dthompson @dat_ecosystem @what @cwebber

you can do json if you want.
in hypercore its binary blocks ...encoded however you like. and its all streaming