add web, windows

2 files changed, 99 insertions, 0 deletions

diff --git a/2023/talks/web.md b/2023/talks/web.md
new file mode 100644
index 00000000..315553b0
--- /dev/null
+++ b/2023/talks/web.md
@@ -0,0 +1,40 @@
+[[!meta title="Emacs saves the Web"]]
+[[!meta copyright="Copyright © 2023 Yuchen Pei"]]
+[[!inline pages="internal(2023/info/web-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Emacs saves the Web
+Yuchen Pei (he/him, pronounced: "eww-churn pay"), IRC: dragestil, <mailto:id@ypei.org>
+
+[[!inline pages="internal(2023/info/web-before)" raw="yes"]]
+
+On one hand, Emacs is the crown jewel of the GNU Project for its
+customisability and the ability to effortlessly convert users to
+hackers. On the other hand, today many of the sticky issues with
+proprietary software proliferation stems from the web, including the
+Javascript trap[1] on the client side and the SaaSS trap[2] on the
+server side. So enters the topic of this talk. I will briefly talk
+about these issues and existing solutions, followed by ideas and
+demonstrations on how Emacs can fix user freedom on the web, including
+(from realistic to dreamy): emacs clients for specific websites and
+services i.e. replacing read-only javascript forced on your browser
+with hackable free elisp packages, emacs-based browsers aka universal
+frontends and elisp version of users-cripts / greasemonkey / haketilo,
+write-once-run-everywhere elisp programs (e.g. the emacs web server
+and (nonexistent?) emacs mobile app UI framework), and remote emacs
+servers that can be shared by a group of hackers running server
+programs written in elisp, thus eliminating the SaaSS trap.
+
+[1] <https://www.gnu.org/philosophy/javascript-trap.html>
+[2] <https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html>
+
+
+
+[[!inline pages="internal(2023/info/web-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/web-nav)" raw="yes"]]
+
+
diff --git a/2023/talks/windows.md b/2023/talks/windows.md
new file mode 100644
index 00000000..2e7a213e
--- /dev/null
+++ b/2023/talks/windows.md
@@ -0,0 +1,59 @@
+[[!meta title="Windows into Freedom"]]
+[[!meta copyright="Copyright &copy; 2023 Corwin Brust"]]
+[[!inline pages="internal(2023/info/windows-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Windows into Freedom
+Corwin Brust (He/Him) - Core-win Brew-st, IRC: corwin, <mailto:corwin@bru.st>
+
+[[!inline pages="internal(2023/info/windows-before)" raw="yes"]]
+
+-   A Brief History of the windows port
+    
+    When (and why?) was the windows port added?  Was that contentious? How
+    about now?  (5m)
+
+-   Acquire Binaries
+    
+    There are lots of ways for Windows users to get pre-compiled Emacs
+    binaries. I'll mention some and get into the particulars of Emacs as
+    found on GNU FTP. (2m)
+
+-   Build Sources
+    
+    I'll talk about how building for Windows differs from building for
+    other platforms, where to find documentation, important configuration
+    options to consider, requirements for the build machine.  After that
+    I'll show build commands and good and not-so-good outputs, ultimately
+    covering the complete process, both using the latest release tarball
+    (from GNU FTP) as well as for building the main development branch
+    from emacs.git (hosted on GNU Savannah).  (20m)
+
+-   Make an Installer
+    
+    I'll show how to use the NSIS script contained within
+    admin/nt/dist-build in the Emacs source tree to create an executable
+    self-installer of Emacs for Windows. (2m)
+
+-   Share
+    
+    I'll describe the requirements of the GNU Public License as related to
+    sharing binary versions of Emacs, and talk about what I do to comply,
+    command by command. (1m)
+
+-   Automate
+    
+    I'll introduce scripting I use to automate publishing binaries
+    tracking a given Emacs branch, and a couple other related tools, thus
+    recapping most topics. (10m)
+
+
+
+[[!inline pages="internal(2023/info/windows-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/windows-nav)" raw="yes"]]
+
+