News for hackers. Stuff that matters.
Re:Consensus not censorship by zozbot234 on Sunday August 21, 2022 @12:56PM (#32542034)
> We could use "permissioned blockchains" (which involve no speculative financial tokens or environmentally destructive "mining") ubiquitously in important institutions to notarize almost everything

This is a good idea, but you don't need a "permissioned blockchain" whatever that is. Just use git.

Re:Consensus not censorship by CharlesW on Sunday August 21, 2022 @01:09PM (#32542178)
Or a database. Anyone using the words "permissioned" or "private" doesn't really want a blockchain.

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3496468

Re:Consensus not censorship by klabb3 on Sunday August 21, 2022 @01:18PM (#32542268)
There's an intermediate option which is overlooked: tamper proof-ness/transparency logs/signed actions. Ie the writer is traditional central authority but the readers can store and later prove that the authority acted incorrectly/maliciously, should that be the case.

For instance, you have traditional moderation. No hate speech etc. It works fine. Then you see that your comment was removed but it was only a dissenting opinion. You can then prove to others they removed it. The idea is to keep the authority in check through transparency.

This also works well for promises of discounts, overbooking of tickets, non-spoofable reviews, etc.

Re:Consensus not censorship by rektide on Sunday August 21, 2022 @01:52PM (#32542614)
Paul Frazee & others had some good threads last fall/winter about smart contracts/public transaction logs without central/concensus blockchains[1]. Individuals with their own willingness to declare their stuff.

Edit: Oh this got followed up on Paul's direction is a little different than expected; Ii has come out a little less self sovereign than I expected. But, here's[2] Vitra. His follow up.ppst talks about Execution Transparency[3].

[1] https://mobile.twitter.com/pfrazee/status/146248993373472359...

[2] https://paulfrazee.medium.com/smart-contracts-without-blockc...

[3] https://paulfrazee.medium.com/execution-transparency-hosted-...

Re:Consensus not censorship by CharlesW on Sunday August 21, 2022 @01:44PM (#32542521)
Yes! Write-once + read-many + no-update/delete tables are reasonably-common in databases as well, and some databases natively support a ledger table type that enables updates and deletes while also providing tamper-proof evidence of all changes.
Re:Consensus not censorship by mike_hock on Sunday August 21, 2022 @01:45PM (#32542529)
As long as transgressions actually have consequences.
Re:Consensus not censorship by rocqua on Sunday August 21, 2022 @04:11PM (#32543939)
I can force push to git. I can selectively prepare and decide to publish branches. I can rebase, cherry-pick, and ammend.

Really git has too many features, and too little publishing features that prevent repudiation.

Re:Consensus not censorship by raxxorraxor on Tuesday August 23, 2022 @08:15AM (#32563686)
That would more or less end up like Wikipedia. It is awesome with the exception of politically charged and contested topics.