this.me 2.5.8 β 2.5.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -9
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -30,14 +30,14 @@ let me = require('this.me');
|
|
|
30
30
|
- [ ] Keep [i.mlearning](https://www.npmjs.com/package/i.mlearning).
|
|
31
31
|
|
|
32
32
|
|
|
33
|
+
|
|
34
|
+
This model turns the traditional web model on its head. Users no longer depend on centralized authorities for identity or data management. They hold the keys (literally) to their identity and data. Services become more user-centric, providing services based on cryptographic proofs rather than centralized databases.
|
|
35
|
+
|
|
36
|
+
While this approach offers many benefits, including enhanced privacy and user sovereignty, it's still nascent and requires a paradigm shift in development, deployment, and user education.
|
|
33
37
|
|
|
34
38
|
# Setting up your Context. ππ»ππΌππ½ππΎππΏ
|
|
35
39
|
Defining the environment and context in which your code runs, especially when you're interacting with intelligent agents or services likeΒ me.
|
|
36
|
-
Having a clear declaration of the environment and the context can have a series of implications for security, interoperability, and clarity.
|
|
37
|
-
|
|
38
|
-
The codebase is often vast, dynamic, and continually evolving.
|
|
39
|
-
|
|
40
|
-
Given the dynamic nature of such environments, ensuring the integrity of the code and data becomes paramount. You wouldn't want an agent to execute or rely on code that has been tampered with or is different from the expected version. This is where hashing comes into play.
|
|
40
|
+
Having a clear declaration of the environment and the context can have a series of implications for security, interoperability, and clarity. The codebase is often vast, dynamic, and continually evolving. Given the dynamic nature of such environments, ensuring the integrity of the code and data becomes paramount. You wouldn't want an agent to execute or rely on code that has been tampered with or is different from the expected version. This is where hashing comes into play.
|
|
41
41
|
|
|
42
42
|
The **SHA256 cryptographic hash function** is used to produce a unique, fixed-length sequence of characters (a hash) for the data. This setup does a thorough job of hashing the content of files or entire directories.
|
|
43
43
|
Even a tiny change in the content will result in a completely different hash.
|
|
@@ -79,13 +79,13 @@ console.log("Is the signature valid?", isValidSignature);
|
|
|
79
79
|
|
|
80
80
|
### Purpose:
|
|
81
81
|
|
|
82
|
-
1. Enhanced Security
|
|
82
|
+
1. **Enhanced Security**
|
|
83
83
|
- Traditional authentication systems have vulnerabilities (e.g., password breaches). `Me` ensures that without the private key, impersonation is nearly impossible.
|
|
84
|
-
2. Decentralization Ready
|
|
84
|
+
2. **Decentralization Ready**
|
|
85
85
|
- `Me` fits perfectly in a decentralized environment, where trust is established not by central entities, but by cryptographic proofs.
|
|
86
|
-
3. User Centricity
|
|
86
|
+
3. **User Centricity**
|
|
87
87
|
- The user has full control over their `Me` entity. They manage their keys and therefore their identity, making it resistant to censorship and external control.
|
|
88
|
-
4. Simplicity
|
|
88
|
+
4. **Simplicity**
|
|
89
89
|
- Instead of managing multiple credentials for different services, `Me` offers a unified identity that's recognized across the network.
|
|
90
90
|
|
|
91
91
|
### Getting Started:
|