Conversation
|
|
||
| ## TLSNotary is a Growth Accelerator for the Ethereum ecosystem | ||
|
|
||
| * **Unlocking the "Private Data" Ocean**: Ethereum is the ultimate "Trust Machine," but it currently runs primarily on public data. TLSNotary provides "super-fuel" by unlocking the 99% of world data currently hidden in "walled gardens" (bank records, social graphs, and identity), enabling a massive new class of useful applications. |
There was a problem hiding this comment.
Can we try to avoid the use of "walled garden", it has negative connotation. We only support the user unlocking the data which legally belongs to them, without violating TOS.
There was a problem hiding this comment.
I'd keep the "walled garden" metaphor. I like it, but I'll add a brief disclaimer to clarify our intent.
| ## TLSNotary is a Growth Accelerator for the Ethereum ecosystem | ||
|
|
||
| * **Unlocking the "Private Data" Ocean**: Ethereum is the ultimate "Trust Machine," but it currently runs primarily on public data. TLSNotary provides "super-fuel" by unlocking the 99% of world data currently hidden in "walled gardens" (bank records, social graphs, and identity), enabling a massive new class of useful applications. | ||
| * **Battling "Enshittification" via Portability**: It restores market pressure by enabling a Permissionless Exit. If users can leave a platform while taking their data and reputation with them to an Ethereum alternative, the "walled gardens" lose their monopoly power. |
There was a problem hiding this comment.
same here, we are a neutral project. Sometimes it is in the platform's TOS that the user's are not allowed legally to take their data elsewhere. We respect those TOS.
|
|
||
| * **Unlocking the "Private Data" Ocean**: Ethereum is the ultimate "Trust Machine," but it currently runs primarily on public data. TLSNotary provides "super-fuel" by unlocking the 99% of world data currently hidden in "walled gardens" (bank records, social graphs, and identity), enabling a massive new class of useful applications. | ||
| * **Battling "Enshittification" via Portability**: It restores market pressure by enabling a Permissionless Exit. If users can leave a platform while taking their data and reputation with them to an Ethereum alternative, the "walled gardens" lose their monopoly power. | ||
| * **Solving the Cold Start Problem**: New dApps no longer have to start from zero. They can build on the "data capital" of incumbents, allowing users to import a 10-year reputation or credit history onto Ethereum on Day 1. |
There was a problem hiding this comment.
build on the "data capital" of incumbents
Mentioning incumbents can also be avoided.
| * **Unlocking the "Private Data" Ocean**: Ethereum is the ultimate "Trust Machine," but it currently runs primarily on public data. TLSNotary provides "super-fuel" by unlocking the 99% of world data currently hidden in "walled gardens" (bank records, social graphs, and identity), enabling a massive new class of useful applications. | ||
| * **Battling "Enshittification" via Portability**: It restores market pressure by enabling a Permissionless Exit. If users can leave a platform while taking their data and reputation with them to an Ethereum alternative, the "walled gardens" lose their monopoly power. | ||
| * **Solving the Cold Start Problem**: New dApps no longer have to start from zero. They can build on the "data capital" of incumbents, allowing users to import a 10-year reputation or credit history onto Ethereum on Day 1. | ||
| * **Scaling without Permission or Censorship**: It allows Ethereum to scale into real-world use cases without needing "API blessings" or permission from corporate gatekeepers. |
|
I agree with Dan that our documentation should remain "matter of fact"/neutral. We can keep rhetorical/motivational content within the blog |
|
I agree with keeping the documentation “matter-of-fact” and neutral. That said, I see the Motivation page as an exception. If this is a strict requirement for you, I can move the motivation page out of the docs folder, next to About. |
|
@heeckhau this was merged without addressing @themighty1 and my concerns |
|
@sinui0 see #40 (comment) |
No description provided.