]> git.r.bdr.sh - rbdr/blog.unlimited.pizza/commitdiff
blog-sync-up-1670761332852
authorRuben Beltran del Rio <redacted>
Sun, 11 Dec 2022 12:22:12 +0000 (12:22 +0000)
committerRuben Beltran del Rio <redacted>
Sun, 11 Dec 2022 12:22:12 +0000 (12:22 +0000)
archive/1670761332784/linkblog-2022-12-11.gmi [new file with mode: 0644]
archive/1670761332784/metadata.json [new file with mode: 0644]
posts/0/linkblog-2022-12-11.gmi [new file with mode: 0644]
posts/0/metadata.json
posts/1/metadata.json
posts/1/more-blog-tooling.gmi [moved from posts/0/more-blog-tooling.gmi with 100% similarity]
posts/2/blog-tooling.gmi [deleted file]
posts/2/linkblog-2022-12-09.gmi [moved from posts/1/linkblog-2022-12-09.gmi with 100% similarity]
posts/2/metadata.json

diff --git a/archive/1670761332784/linkblog-2022-12-11.gmi b/archive/1670761332784/linkblog-2022-12-11.gmi
new file mode 100644 (file)
index 0000000..6384429
--- /dev/null
@@ -0,0 +1,6 @@
+# A link for 2022-12-11
+
+=> https://newpublic.substack.com/p/-metafilters-rule-laden-mini-utopia ðŸŒ„ MetaFilter’s rule-laden mini-utopia
+This idea of purposeful barriers to entry is one that I really like. I think my first experience with it was on b3ta, where you have to wait until tuesday to post, and it worked really well!
+
+I had lost track of MetaFilter, but after reading this I'm very curious to join the community and see how it plays out!
\ No newline at end of file
diff --git a/archive/1670761332784/metadata.json b/archive/1670761332784/metadata.json
new file mode 100644 (file)
index 0000000..17d9ba8
--- /dev/null
@@ -0,0 +1,4 @@
+{
+  "id": "1670761332784",
+  "createdOn": 1670761332784
+}
\ No newline at end of file
diff --git a/posts/0/linkblog-2022-12-11.gmi b/posts/0/linkblog-2022-12-11.gmi
new file mode 100644 (file)
index 0000000..6384429
--- /dev/null
@@ -0,0 +1,6 @@
+# A link for 2022-12-11
+
+=> https://newpublic.substack.com/p/-metafilters-rule-laden-mini-utopia ðŸŒ„ MetaFilter’s rule-laden mini-utopia
+This idea of purposeful barriers to entry is one that I really like. I think my first experience with it was on b3ta, where you have to wait until tuesday to post, and it worked really well!
+
+I had lost track of MetaFilter, but after reading this I'm very curious to join the community and see how it plays out!
\ No newline at end of file
index 5a1820b2a807400f9f99e91e5c3b66b09f038b5d..17d9ba84fde70fbb159d4ee77d4c7c94638ed14f 100644 (file)
@@ -1,4 +1,4 @@
 {
-  "id": "1670625662876",
-  "createdOn": 1670625662876
+  "id": "1670761332784",
+  "createdOn": 1670761332784
 }
\ No newline at end of file
index 732ff3473040710a190574a5570310a41e50bfa3..5a1820b2a807400f9f99e91e5c3b66b09f038b5d 100644 (file)
@@ -1,4 +1,4 @@
 {
-  "id": "1670605596209",
-  "createdOn": 1670605596209
+  "id": "1670625662876",
+  "createdOn": 1670625662876
 }
\ No newline at end of file
diff --git a/posts/2/blog-tooling.gmi b/posts/2/blog-tooling.gmi
deleted file mode 100644 (file)
index 9f7900f..0000000
+++ /dev/null
@@ -1,77 +0,0 @@
-# Blog Tooling
-
-With so many of the bloggers I follow talking about the the latest release of MarsEdit[1], I've been getting tooling envy. While my blog[2] is a full-featured enterprise-grade state-of-the-art piece of software, it's not compatible with any of these tools :(. Surely, a lack of appropriate tooling is the real reason why I don't update as often.
-
-=> https://redsweater.com/marsedit/ [1] MarsEdit
-=> https://git.sr.ht/~rbdr/blog [2] Blog
-
-After a dozen misguided minutes of reading the atompub spec[3], I decided to integrate my tooling directly to my editor of choice: `nvim`.
-
-=> https://datatracker.ietf.org/doc/rfc5023/ [3] The atompub spec
-
-Thanks to the marvels of VimScriptâ„¢ I can now add a text file to my blog with `:Blog add`, update the latest post with `:Blog update`, and publish to staging and live with `:Blog stage` and `:Blog publish`. And all it took was a couple of hours of searching how to write commands in vim[4], learning the difference between `<args>` and `<q-args>`, and a ton of sunken cost bias.
-
-=> https://vimhelp.org/usr_40.txt.html#40.2 [4] How to write commands in vim
-
-Here you can see the code in its entirety (with a couple replacements):
-
-
-```
-command -nargs=? Blog :call Blog(<q-args>)
-
-function! Blog(...)
-
-  let command = get(a:, 1, 0)
-  let path = expand("%:p")
-
-  if command == "add"
-    if path == ""
-      echo "This buffer is not a text file"
-    else
-      echo "Adding ".path." to blog"
-      call system("blog --add ".path)
-    endif
-    return
-  endif
-
-  if command == "update"
-    if path == ""
-      echo "This buffer is not a text file"
-    else
-      echo "Updating ".path." to blog"
-      call system("blog --update ".path)
-    endif
-    return
-  endif
-
-  if command == "stage"
-    echo "Publishing blog to staging"
-    call system("blog --publish <staging_url>")
-    return
-  endif
-
-  if command == "publish"
-    echo "Publishing blog"
-    call system("blog --publish <blog_url>")
-    call system("blog --publish-archive <gemini_url>")
-    return
-  endif
-
-  if command == "help"
-    echo "Available commands:"
-    echo "\tadd\t\tadds current file to blog"
-    echo "\tupdate\t\tupdates latest entry of blog with current file"
-    echo "\tstage\t\tpublish blog to staging"
-    echo "\tpublish\t\tpublish blog to production"
-    echo "\thelp\t\tthis message"
-    return
-  endif
-
-  echo "Unknown command, run :Blog help for help"
-
-endfunction
-```
-
-Surely, this is all I need to form a publishing habit.
-
-Written, published, edited, republished, debugged, and republished with nvim.
index 87de549d7ca7bc0ea4d696f4031183205d35c4f3..732ff3473040710a190574a5570310a41e50bfa3 100644 (file)
@@ -1,4 +1,4 @@
 {
-  "id": "1669903029203",
-  "createdOn": 1669903029203
+  "id": "1670605596209",
+  "createdOn": 1670605596209
 }
\ No newline at end of file