From b7501b5785c4bac2f8e37b351b06b1baa7adcbf9 Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sat, 10 Apr 2021 15:39:15 +0200
Subject: [PATCH] Auto: misc.

---
 force graph.md     | 31 -------------------------------
 force-graph.md     | 44 ++++++++++++++++++++++++++++++++++++--------
 geometric-unity.md |  1 +
 3 files changed, 37 insertions(+), 39 deletions(-)

diff --git a/force graph.md b/force graph.md
index a8dab133d..3dde88894 100644
--- a/force graph.md	
+++ b/force graph.md	
@@ -1,33 +1,2 @@
 # force graph
 
-- [[go]] https://github.com/vasturiano/force-graph
-  - I think it makes sense. Seems reasonable fast at the high-thousand-nodes level; the agora is currently at 10k. And most of the visualizations I want to do are actually node-scoped plus links, so really just an issue for hugely outlier nodes degree wise (like [[person]] or [[go]]).
-  - Unfortunately it doesn't seem to provide labels for edges?
-    - False, it does: https://vasturiano.github.io/force-graph/example/text-links/
-  - Data format, JSON:
-
-```
-{
-    "nodes": [
-        {
-          "id": "id1",
-          "name": "name1",
-          "val": 1
-        },
-        {
-          "id": "id2",
-          "name": "name2",
-          "val": 10
-        },
-        (...)
-    ],
-    "links": [
-        {
-            "source": "id1",
-            "target": "id2"
-        },
-        (...)
-    ]
-}
-```
-
diff --git a/force-graph.md b/force-graph.md
index 65df70081..b5c687510 100644
--- a/force-graph.md
+++ b/force-graph.md
@@ -1,12 +1,40 @@
 # Force Graph
 
-- [[go]] https://github.com/vasturiano/force-graph
-  - [[graph drawing library]] in use by [[logseq]]: https://twitter.com/logseq/status/1322933174964428801
-- [[wiki]] https://en.wikipedia.org/wiki/Force-directed_graph_drawing
+- a [[library]]
+  - [[javascript]] [[d3]]
+  - [[wp]] https://en.wikipedia.org/wiki/Force-directed_graph_drawing
+  - [[go]] https://github.com/vasturiano/force-graph
+    - [[graph drawing library]] in use by [[logseq]]: https://twitter.com/logseq/status/1322933174964428801
+  - I think it makes sense. Seems reasonable fast at the high-thousand-nodes level; the agora is currently at 10k. And most of the visualizations I want to do are actually node-scoped plus links, so really just an issue for hugely outlier nodes degree wise (like [[person]] or [[go]]).
+  - Unfortunately it doesn't seem to provide labels for edges?
+    - False, it does: https://vasturiano.github.io/force-graph/example/text-links/
+  - Data format, JSON:
+
+```
+{
+    "nodes": [
+        {
+          "id": "id1",
+          "name": "name1",
+          "val": 1
+        },
+        {
+          "id": "id2",
+          "name": "name2",
+          "val": 10
+        },
+        (...)
+    ],
+    "links": [
+        {
+            "source": "id1",
+            "target": "id2"
+        },
+        (...)
+    ]
+}
+```
+
+
 
 
-[//begin]: # "Autogenerated link references for markdown compatibility"
-[go]: go "Go"
-[logseq]: logseq "Logseq"
-[wiki]: wiki "Wiki"
-[//end]: # "Autogenerated link references"
\ No newline at end of file
diff --git a/geometric-unity.md b/geometric-unity.md
index 1f2795764..ab320e948 100644
--- a/geometric-unity.md
+++ b/geometric-unity.md
@@ -1,4 +1,5 @@
 # geometric unity
 
 - [[go]] https://geometricunity.org
+  - https://www.math.columbia.edu/~woit/wordpress/?p=5927 has links to criticism