Skip to content

Normalised madness | the TOS section | Checks and balances #14

Description

@6r1d

This part of #13

I will do something else. I will ask you, if you honestly believe that a random document that nobody reads or /can/ read and provide an informed consent to, should be legally binding. Suppose the "terms of service" associated to that restaurant contained fine print instead of this being an unrelated document, should it then result in the right to have their rights be defended in court be diminished.

in context of the checks and balances, makes me remember our discussions of Filecoin.
Maybe ideal in terms of incentives is very hard to achieve, but at the very least, they made a dynamic system that can change and even change how it changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions