From d0846f899ae10c253f34e1948624bc624e764fde Mon Sep 17 00:00:00 2001 From: Mark Krasner <70119343+mzkrasner@users.noreply.github.com> Date: Mon, 21 Oct 2024 12:18:23 -0400 Subject: [PATCH] Better IoT use case summary Co-authored-by: Arjun Hassard --- docs/composedb/examples/taco-access-control.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/composedb/examples/taco-access-control.mdx b/docs/composedb/examples/taco-access-control.mdx index 49cc69d..1f0fd53 100644 --- a/docs/composedb/examples/taco-access-control.mdx +++ b/docs/composedb/examples/taco-access-control.mdx @@ -19,7 +19,7 @@ TACo’s encrypt/decrypt API – [taco-web](https://github.com/nucypher/taco-web - **Social networks & Knowledge Bases:** Leverage Ceramic's verifiable credentials and TACo's credential-based decryption to ensure that private user-generated content is only viewable by those who are supposed to see it, and nobody else. -- **IoT event streams:** Let sensitive data flow from sensors to legitimate recipients, without trusting an intermediary server to handle the routing and harvest metadata. For example, a medical professional can be issued a temporary access token if a patient's wearable output data rises above a certain threshold. +- **IoT event streams:** Let data flow from sensors to legitimate recipients, without trusting an intermediary server to handle the routing and harvest sensitive (meta)data. For example, a medical professional can be issued a temporary access token if the output data from a patient's wearable device rises above a certain threshold. - **LLM chatbots:** Messages to and from a chatbot should be 100% private, not mined by a UX-providing intermediary. Harness Ceramic's web-scale transaction processing and TACo's per-message encryption granularity to provide a smooth and private experience for users of LLM interfaces.