librejs/submitpatches: remove some transitions
parent
d12d40bc1e
commit
26203dfc16
28
talk.tex
28
talk.tex
|
@ -185,23 +185,23 @@
|
|||
browser sends an HTTP request to the host requesting the
|
||||
resource.}
|
||||
|
||||
\item<3-> Server responds with resource
|
||||
\only<3>{\gnuresp}
|
||||
\item<4-> Server responds with resource
|
||||
\only<4>{\gnuresp}
|
||||
\lecture{The server responds with the resource or an error.}
|
||||
|
||||
\item<4-> Browser recursively loads all resources referenced by
|
||||
\item<5-> Browser recursively loads all resources referenced by
|
||||
the resource
|
||||
\begin{itemize}
|
||||
\item<4-> Stylesheets, Images, Scripts, etc.
|
||||
\item<5-> Stylesheets, Images, Scripts, etc.
|
||||
\end{itemize}
|
||||
\only<4>{\includegraphics[width=\textwidth]{images/gnu-resources.png}}
|
||||
\only<5>{\includegraphics[width=\textwidth]{images/gnu-resources.png}}
|
||||
\lecture{This is the meat of the talk. The browser then recursively
|
||||
processes all resources referenced by \emph{that}
|
||||
resource. Most often, these include images, stylesheets,
|
||||
and scripts.}
|
||||
\end{enumerate}
|
||||
|
||||
\item<5-> Distributed network (``web'') of computers
|
||||
\item<6-> Distributed network (``web'') of computers
|
||||
\lecture{So fundamentally, the web is a distributed network of
|
||||
computers that serve resources. Resources can be anything
|
||||
from your conventional web page, to a program that runs in
|
||||
|
@ -459,7 +459,9 @@
|
|||
has bad intentions---you also have hackers that just want to
|
||||
show you their cool new programs. And some of those are also
|
||||
the ones that find it silly to disable JavaScript---how else
|
||||
would you be able to witness their hard work?}
|
||||
would you be able to witness their hard work? And I think a
|
||||
lot of people fall into this group---I don't think many of them
|
||||
are being intentionally malicious.}
|
||||
\end{center}
|
||||
\end{frame}
|
||||
|
||||
|
@ -1165,19 +1167,19 @@ k.handler.guid||(k.handler.guid=c.guid)),e?m.splice(m.delegateCount++,0,k)
|
|||
|
||||
|
||||
\begin{frame}{LibreJS}
|
||||
\begin{itemize}[<+->]
|
||||
\item Blocks execution of non-free JavaScript
|
||||
\begin{itemize}
|
||||
\item<1-> Blocks execution of non-free JavaScript
|
||||
\lecture{LibreJS blocks the execution of non-free JavaScript. But how
|
||||
does it determine what is non-free?}
|
||||
|
||||
\item JavaScript should ideally contain {\tt @license} tags
|
||||
\item<2-> JavaScript should ideally contain {\tt @license} tags
|
||||
\lecture{A couple ways. Ideally, the JavaScript should be wrapped in
|
||||
license tags. It can identify the license in a number of
|
||||
ways, including the full license header you'd see in source
|
||||
files, or a magnet link, which is much more ideal for
|
||||
minified sources.}
|
||||
|
||||
\item Hashes of common libraries recognized as free
|
||||
\item<2-> Hashes of common libraries recognized as free
|
||||
\lecture{But the Web is full of \emph{existing} software like
|
||||
libraries that don't contain those labels. So LibreJS also
|
||||
maintains a list of file hashes for popular libraries. For
|
||||
|
@ -1185,7 +1187,7 @@ k.handler.guid||(k.handler.guid=c.guid)),e?m.splice(m.delegateCount++,0,k)
|
|||
showed would be recognized as free, even though it doesn't
|
||||
contain licensing information.}
|
||||
|
||||
\item Web Labels map scripts to corresponding source code
|
||||
\item<3-> Web Labels map scripts to corresponding source code
|
||||
\lecture{It then has a method called Web Labels---which is a simple
|
||||
HTML table---that is intended to be a machine-readable way to
|
||||
map scripts to their source code.}
|
||||
|
@ -1198,7 +1200,7 @@ k.handler.guid||(k.handler.guid=c.guid)),e?m.splice(m.delegateCount++,0,k)
|
|||
|
||||
|
||||
\begin{frame}{Submit Patches To Projects!}
|
||||
\begin{itemize}[<+->]
|
||||
\begin{itemize}
|
||||
\item Patch your own projects!
|
||||
\item Submit patches to add headers to projects
|
||||
\item Patches for minifiers (e.g. UglifyJS)
|
||||
|
|
Loading…
Reference in New Issue