Viewing a response to: @cylonmaker2053/steemit-infrastructure-security-scalability-and-points-of-failure
<html> <p>Glad to see folks thinking ahead! As a lawyer, I'm less concerned about the legal issues you raise and more concerned about the security issues, perhaps because my grasp of the latter is wanting.</p> <p>Legally, state censorship of Steemit would be incredibly difficult, at least once it reaches sufficient scale. Judges cannot order individuals to do things beyond their control. For instance, a judge cannot legally order me to paint the sky red. And, reversing entries on a sufficiently secure blockchain is the rough digital equivalent of painting the sky red. To the extent that such a reversal is possible at all, it could only be done by a large group of people (called "witnesses" in the Steemit system, I think) acting in concert. Provided that this group is sufficiently large and sufficiently distributed across multiple legal jurisdictions, successful state censorship becomes very, very unlikely. </p> <p>It's also unlikely that a judge (in the US at least) could compel a person to write code. Code is speech, and speech is Constitutionally protected. So, targeting developers probably isn't a winning strategy for the state either. </p> <p>Nonetheless there will be community policing and community censorship to some degree via the down voting process. It will be fascinating to see how that works and evolves. I imagine that organizations like ISIS would get down voted to irrelevance, but perhaps not. And perhaps they can find ways of gaming the system to work in their favor. </p> </html>
| author | sean-king |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t143424871z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:34:24 |
| last_update | 2016-06-22 14:34:24 |
| depth | 1 |
| children | 1 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 66.796 HBD |
| curator_payout_value | 66.796 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,638 |
| author_reputation | 84,123,051,136,467 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,430 |
| net_rshares | 38,943,639,373,300 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| dantheman | 0 | 19,020,464,696,957 | 100% | ||
| tombstone | 0 | 19,247,528,200,000 | 100% | ||
| sean-king | 0 | 331,180,322,290 | 100% | ||
| cylonmaker2053 | 0 | 344,424,654,264 | 100% | ||
| brianreecegreen | 0 | 41,499,789 | 100% |
I've already seen evidence of bad stuff being downvoted. As long as the hive is sane then the hive thrives.
| author | stellabelle |
|---|---|
| permlink | re-sean-king-re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t200307307z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 20:03:09 |
| last_update | 2016-06-22 20:03:09 |
| depth | 2 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.055 HBD |
| curator_payout_value | 0.055 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 107 |
| author_reputation | 516,061,669,130,124 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,720 |
| net_rshares | 323,671,536,951 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| sean-king | 0 | 323,478,454,330 | 100% | ||
| herethengone | 0 | 193,082,621 | 100% |
hiveblocks