1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
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"]]
|
