twisterarmy / twister-core Goto Github PK

For example
https://github.com/twisterarmy/twister-core/blob/master/doc/building-on-ubuntu-debian.md

merged with TA branch by mistake, must to be original mirror of https://github.com/miguelfreitas/twister-core

By the fact, it is possible to store posts in the blockchain using mining feature as the alternative to unstable DHT swarms. Just hard-fork thoughts for separated blockchain to not abuse current eco-system.

This model able to increase quantity of miners and implement the pay-for-post model, without coin/market model implementation
Related post #1

Or, maybe better to implement some optional, third-party storage integration on the twister-core level, e.g. distributed kevacoin database. When data not accessible trough DHT, it could be loaded from alternative source. Related thoughts for client-side/twister-html twisterarmy/twister-html#23

May to confuse new users when they are trying to send first message

miguelfreitas#146
miguelfreitas#255

According to miguelfreitas#455

Not sure that current protocol implementation allow to hide user connection, as especially on the low network activity that is possible to collect peer's data using swarm emulation and available RPC API to collect the profile fingerprint.

According to:
miguelfreitas#445 and https://groups.google.com/g/twister-dev/c/gpEaKwH153I

I'm sure for project future, the core architecture should be protected by mine-for-post or watch-ads-to-post principles.