From efcfe3e18a8f5d69590364ff840e374525555e23 Mon Sep 17 00:00:00 2001
From: Timur Ismagilov <bouncepaw2@ya.ru>
Date: Sat, 13 Jan 2024 12:00:10 +0000
Subject: [PATCH] Sync Sat Jan 13 12:00:10 UTC 2024

---
 35.myco                | 14 --------------
 99.myco                |  3 +++
 Bearer Token RFC.myco  | 14 --------------
 Complex contagion.myco |  3 +++
 4 files changed, 6 insertions(+), 28 deletions(-)
 delete mode 100644 35.myco
 create mode 100644 99.myco
 delete mode 100644 Bearer Token RFC.myco
 create mode 100644 Complex contagion.myco

diff --git a/35.myco b/35.myco
deleted file mode 100644
index 1b44c49..0000000
--- a/35.myco
+++ /dev/null
@@ -1,14 +0,0 @@
-= 35
-https://datatracker.ietf.org/doc/html/rfc6750
-
-> [[https://datatracker.ietf.org/doc/html/rfc6750#section-1.2 | 1.2]].  Terminology
-> 
->    Bearer Token
->       A security token with the property that any party in possession of
->       the token (a "bearer") can use the token in any way that any other
->       party in possession of it can.  Using a bearer token does not
->       require a bearer to prove possession of cryptographic key material
->       (proof-of-possession).
-> 
->    All other terms are as defined in "The OAuth 2.0 Authorization
->    Framework" [[[https://datatracker.ietf.org/doc/html/rfc6749 | RFC6749]]].
\ No newline at end of file
diff --git a/99.myco b/99.myco
new file mode 100644
index 0000000..2e29dd6
--- /dev/null
+++ b/99.myco
@@ -0,0 +1,3 @@
+= 99
+https://en.wikipedia.org/wiki/Complex_contagion
+
diff --git a/Bearer Token RFC.myco b/Bearer Token RFC.myco
deleted file mode 100644
index 05ae22d..0000000
--- a/Bearer Token RFC.myco	
+++ /dev/null
@@ -1,14 +0,0 @@
-= Bearer Token RFC
-https://datatracker.ietf.org/doc/html/rfc6750
-
-> [[https://datatracker.ietf.org/doc/html/rfc6750#section-1.2 | 1.2]].  Terminology
-> 
->    Bearer Token
->       A security token with the property that any party in possession of
->       the token (a "bearer") can use the token in any way that any other
->       party in possession of it can.  Using a bearer token does not
->       require a bearer to prove possession of cryptographic key material
->       (proof-of-possession).
-> 
->    All other terms are as defined in "The OAuth 2.0 Authorization
->    Framework" [[[https://datatracker.ietf.org/doc/html/rfc6749 | RFC6749]]].
\ No newline at end of file
diff --git a/Complex contagion.myco b/Complex contagion.myco
new file mode 100644
index 0000000..eb5ebc0
--- /dev/null
+++ b/Complex contagion.myco	
@@ -0,0 +1,3 @@
+= Complex contagion
+https://en.wikipedia.org/wiki/Complex_contagion
+