親カテゴリー: Distributed computing.

Decentralisation with P2P software

How can we use Peer 2 peer software to accomplish distribution


Centralisation maximizes the chance people will use your software. The problem is that it's brittle and not really fair for the people who have to maintain it on servers they pay for or maintain by themselves.

We could have a federated platform for distribution of processing and data storage. This category is to cover ideas related to decentralisation.

I recommend the decentralise community redecentralize for ideas on decentralisation


投票 (不必要) (通知しない) (不必要)


Yeah, this is definitely an important category, and a link. Will have to describe a few ideas here, that are on other places or within the mind.



分散キー値ストアは、SQLデータベースなどのストレージバックエンドの基盤になります。 https://GitHub.com/samsquire/hash-dbでSQLバックエンドとしてのキー値ストレージの使用を示しました



I think the ideas of Kademlia are still relevant today.


A distributed key value store can be the basis of a storage backend such as a SQL database. I have demonstrated use of keyvalue storage as SQL backend on https://GitHub.com/samsquire/hash-db

I don't want to use this to share big files like copyrighted music and films but as a backend for apps like 0oo.li or DAOs.

One problem of Kademlia or distribution is security. We have a problem of bad actors and spammers. So we need some sort of web of trust system so your app isn't overloaded with spam. We can achieve this by verifying hosts by marking them as trusted and then we see their content. This way nobody can force you to store spam. If you see spam, you unverify the server and your view goes back to nonspam. Everybody hosts their own information.

    :  -- 
    : Mindey
    :  -- 


正確にはセキュリティ。コミュニティモジュールを安全に実行する方法はありません。セキュリティを確保する唯一の方法は、ピアレビューのシステムです。従来のセキュリティモデルは、独自の境界のシステムです。スキームが透明性に欠けているため、Alla's、それらの所有者は信頼できないことが証明されました。 このテーマについて別のスレッドを開始し、他の人からの意見をお待ちしていますが、レビュー担当者がサービスと経済の一部に対して支払いを受け、コードの品質を確保するbc経済を開発することで解決策が見られます。もちろん、レビュアーとそのレビューの質の問題もあります。

Security, precisely. There's no way to run a community module safely. The only way to ensure security is a system of peer review. The traditional security model is a system of proprietary boundaries. Alla's, those proprietors proven not to be trustworthy, for the scheme lacks transparency. I'll start a separate thread on the subject and would really appreciate to hear from others, but I see the solution in developing a bc economy where reviewers are paid for their services and part of the economy, ensuring quality of code. Of course, there's an issue of quality of reviewers and their reviews, and on and on.

信頼できないコードの実行は、信頼できないデータソースのクエリとは別の問題です。 1つは簡単に確認できます。不良データのソースを信頼できないものとしてマークし、計算に含めないでください。すべてのデータの横にボタンを配置して、データのソースを示すことができます。そのため、ワンクリックでサーバーのデータを簡単にブロックまたは除外できます。


Running untrustworthy code is a different problem from querying untrusted sources of data. One is easy to verify - just mark the source of bad data as untrustworthy and do not include it in calculations. You could have a button next to every piece of data to indicate the data's source. So you can easily block or filter out a server's data with one click.

I suspect some form of virtual machine can be created to limit the primitives of data processing for arbitrary code execution. If you had a simple language that can do mathematical operations and call out to a limited runtime. Read-only SQL queries can be safe to run. Write queries such as delete and insert should go to the app host server. You would have communication partners be limited in the runtime so arbitrary traffic cannot be produced. You may want to tie loop execution to data queries so arbitrary busy loops cannot run.

独自のランタイムと言語を持つインターネットコンピュータをdfinityへのリンクを追加しました。 https://dfinity.org/

Have added a link to dfinity the internet computer which has its own runtime and language. https://dfinity.org/