3 ms·

NostrP2P: Pure P2P Distributed Microblogging System

29 points by ryo_grid 2y ago

xrd 2y ago
I went to read this to understand how P2P can share a blog post and the assets associated with that. For example, how does this work when the HTML file is available, but the other assets (say an image the post) might be relatively available (meaning they also need to be stored P2P) but there might be css assets that are available on a non-P2P CDN. It wasn't obvious from this post how that is achieved. Anyone know?
- cchance 2y ago
  IPFS is the p2p standard or it was for decentralized file storage, i'd imagine something similar
- ryo_grid 2y ago
  I am author of this article :) In general of pure P2P architecture, shareing blog post text and assosicated assets is not impossible technically. For example, blog post message (data) shared between nodes can include all of assets for the post though the design may be not good. In NostrP2P, users should want to attach image file to post. In the case, users upload image file to any server (image uploading service or GitHub or etc are also OK) and insert hyper link to the file to his or her post. Then client of NostrP2P show the image file (but not implemented yet...). This approach is adopted in (general and not pure P2P) Nostr protcol based microbrogging application. Is it not pure P2P? OK. I suggest users to upload image file to IPFS :)
aabbcc1241 2y ago
I read it use push based approach and assume the receivers are online when there is new messages. Is there design to recall accumulated messages when restore from offline?
- ryo_grid 2y ago
  Yes there is. I firstly planned place sub server (other user's severs) mechanism which receives messages as same as main server and these can pass data to main server when it become online. But it is complicated to implement. So, it is not implemented now. Additionaly, accumulating messages from following users servers when become online can be implemented. But, this feature leads non ignoreable increase of machine/network resource consumption. So this is not implemented too.

29 points by ryo_grid 2y ago

xrd 2y ago

I went to read this to understand how P2P can share a blog post and the assets associated with that. For example, how does this work when the HTML file is available, but the other assets (say an image the post) might be relatively available (meaning they also need to be stored P2P) but there might be css assets that are available on a non-P2P CDN. It wasn't obvious from this post how that is achieved. Anyone know?

cchance 2y ago
IPFS is the p2p standard or it was for decentralized file storage, i'd imagine something similar
ryo_grid 2y ago
I am author of this article :) In general of pure P2P architecture, shareing blog post text and assosicated assets is not impossible technically. For example, blog post message (data) shared between nodes can include all of assets for the post though the design may be not good. In NostrP2P, users should want to attach image file to post. In the case, users upload image file to any server (image uploading service or GitHub or etc are also OK) and insert hyper link to the file to his or her post. Then client of NostrP2P show the image file (but not implemented yet...). This approach is adopted in (general and not pure P2P) Nostr protcol based microbrogging application. Is it not pure P2P? OK. I suggest users to upload image file to IPFS :)

aabbcc1241 2y ago

I read it use push based approach and assume the receivers are online when there is new messages. Is there design to recall accumulated messages when restore from offline?

ryo_grid 2y ago
Yes there is. I firstly planned place sub server (other user's severs) mechanism which receives messages as same as main server and these can pass data to main server when it become online. But it is complicated to implement. So, it is not implemented now. Additionaly, accumulating messages from following users servers when become online can be implemented. But, this feature leads non ignoreable increase of machine/network resource consumption. So this is not implemented too.