82d2f427e9bf4a25936cd4e76fc5de90e40ff803 — Andrew Zah 3 months ago 6d4d7cc
* add 5-28 talk, licenses, minor updates
A LICENSE => LICENSE +685 -0
@@ 0,0 1,685 @@
+ The code (not posts/talks/etc content) is licensed under the AGPLv3 License.
+ 
+ --- LICENSE ATTRIBUTIONS
+ 
+ This project uses:
+ 
+ * Zola (previously Gutenberg) -> MIT License
+   https://github.com/getzola/zola/blob/master/LICENSE
+ 
+ * lity lightbox -> MIT License
+   https://github.com/jsor/lity/blob/master/LICENSE
+ 
+ * jquery -> MIT License
+   https://jquery.org/license/
+ 
+ * mathjax -> Apache 2.0 License
+   https://github.com/mathjax/MathJax/blob/master/LICENSE
+   - no changes made
+ 
+ * Raleway Font -> Open Font License
+   https://www.fontsquirrel.com/license/raleway
+ 
+ --- THIS PROJECT'S LICENSE
+ 
+                     GNU AFFERO GENERAL PUBLIC LICENSE
+                        Version 3, 19 November 2007
+ 
+  Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+  Everyone is permitted to copy and distribute verbatim copies
+  of this license document, but changing it is not allowed.
+ 
+                             Preamble
+ 
+   The GNU Affero General Public License is a free, copyleft license for
+ software and other kinds of works, specifically designed to ensure
+ cooperation with the community in the case of network server software.
+ 
+   The licenses for most software and other practical works are designed
+ to take away your freedom to share and change the works.  By contrast,
+ our General Public Licenses are intended to guarantee your freedom to
+ share and change all versions of a program--to make sure it remains free
+ software for all its users.
+ 
+   When we speak of free software, we are referring to freedom, not
+ price.  Our General Public Licenses are designed to make sure that you
+ have the freedom to distribute copies of free software (and charge for
+ them if you wish), that you receive source code or can get it if you
+ want it, that you can change the software or use pieces of it in new
+ free programs, and that you know you can do these things.
+ 
+   Developers that use our General Public Licenses protect your rights
+ with two steps: (1) assert copyright on the software, and (2) offer
+ you this License which gives you legal permission to copy, distribute
+ and/or modify the software.
+ 
+   A secondary benefit of defending all users' freedom is that
+ improvements made in alternate versions of the program, if they
+ receive widespread use, become available for other developers to
+ incorporate.  Many developers of free software are heartened and
+ encouraged by the resulting cooperation.  However, in the case of
+ software used on network servers, this result may fail to come about.
+ The GNU General Public License permits making a modified version and
+ letting the public access it on a server without ever releasing its
+ source code to the public.
+ 
+   The GNU Affero General Public License is designed specifically to
+ ensure that, in such cases, the modified source code becomes available
+ to the community.  It requires the operator of a network server to
+ provide the source code of the modified version running there to the
+ users of that server.  Therefore, public use of a modified version, on
+ a publicly accessible server, gives the public access to the source
+ code of the modified version.
+ 
+   An older license, called the Affero General Public License and
+ published by Affero, was designed to accomplish similar goals.  This is
+ a different license, not a version of the Affero GPL, but Affero has
+ released a new version of the Affero GPL which permits relicensing under
+ this license.
+ 
+   The precise terms and conditions for copying, distribution and
+ modification follow.
+ 
+                        TERMS AND CONDITIONS
+ 
+   0. Definitions.
+ 
+   "This License" refers to version 3 of the GNU Affero General Public License.
+ 
+   "Copyright" also means copyright-like laws that apply to other kinds of
+ works, such as semiconductor masks.
+ 
+   "The Program" refers to any copyrightable work licensed under this
+ License.  Each licensee is addressed as "you".  "Licensees" and
+ "recipients" may be individuals or organizations.
+ 
+   To "modify" a work means to copy from or adapt all or part of the work
+ in a fashion requiring copyright permission, other than the making of an
+ exact copy.  The resulting work is called a "modified version" of the
+ earlier work or a work "based on" the earlier work.
+ 
+   A "covered work" means either the unmodified Program or a work based
+ on the Program.
+ 
+   To "propagate" a work means to do anything with it that, without
+ permission, would make you directly or secondarily liable for
+ infringement under applicable copyright law, except executing it on a
+ computer or modifying a private copy.  Propagation includes copying,
+ distribution (with or without modification), making available to the
+ public, and in some countries other activities as well.
+ 
+   To "convey" a work means any kind of propagation that enables other
+ parties to make or receive copies.  Mere interaction with a user through
+ a computer network, with no transfer of a copy, is not conveying.
+ 
+   An interactive user interface displays "Appropriate Legal Notices"
+ to the extent that it includes a convenient and prominently visible
+ feature that (1) displays an appropriate copyright notice, and (2)
+ tells the user that there is no warranty for the work (except to the
+ extent that warranties are provided), that licensees may convey the
+ work under this License, and how to view a copy of this License.  If
+ the interface presents a list of user commands or options, such as a
+ menu, a prominent item in the list meets this criterion.
+ 
+   1. Source Code.
+ 
+   The "source code" for a work means the preferred form of the work
+ for making modifications to it.  "Object code" means any non-source
+ form of a work.
+ 
+   A "Standard Interface" means an interface that either is an official
+ standard defined by a recognized standards body, or, in the case of
+ interfaces specified for a particular programming language, one that
+ is widely used among developers working in that language.
+ 
+   The "System Libraries" of an executable work include anything, other
+ than the work as a whole, that (a) is included in the normal form of
+ packaging a Major Component, but which is not part of that Major
+ Component, and (b) serves only to enable use of the work with that
+ Major Component, or to implement a Standard Interface for which an
+ implementation is available to the public in source code form.  A
+ "Major Component", in this context, means a major essential component
+ (kernel, window system, and so on) of the specific operating system
+ (if any) on which the executable work runs, or a compiler used to
+ produce the work, or an object code interpreter used to run it.
+ 
+   The "Corresponding Source" for a work in object code form means all
+ the source code needed to generate, install, and (for an executable
+ work) run the object code and to modify the work, including scripts to
+ control those activities.  However, it does not include the work's
+ System Libraries, or general-purpose tools or generally available free
+ programs which are used unmodified in performing those activities but
+ which are not part of the work.  For example, Corresponding Source
+ includes interface definition files associated with source files for
+ the work, and the source code for shared libraries and dynamically
+ linked subprograms that the work is specifically designed to require,
+ such as by intimate data communication or control flow between those
+ subprograms and other parts of the work.
+ 
+   The Corresponding Source need not include anything that users
+ can regenerate automatically from other parts of the Corresponding
+ Source.
+ 
+   The Corresponding Source for a work in source code form is that
+ same work.
+ 
+   2. Basic Permissions.
+ 
+   All rights granted under this License are granted for the term of
+ copyright on the Program, and are irrevocable provided the stated
+ conditions are met.  This License explicitly affirms your unlimited
+ permission to run the unmodified Program.  The output from running a
+ covered work is covered by this License only if the output, given its
+ content, constitutes a covered work.  This License acknowledges your
+ rights of fair use or other equivalent, as provided by copyright law.
+ 
+   You may make, run and propagate covered works that you do not
+ convey, without conditions so long as your license otherwise remains
+ in force.  You may convey covered works to others for the sole purpose
+ of having them make modifications exclusively for you, or provide you
+ with facilities for running those works, provided that you comply with
+ the terms of this License in conveying all material for which you do
+ not control copyright.  Those thus making or running the covered works
+ for you must do so exclusively on your behalf, under your direction
+ and control, on terms that prohibit them from making any copies of
+ your copyrighted material outside their relationship with you.
+ 
+   Conveying under any other circumstances is permitted solely under
+ the conditions stated below.  Sublicensing is not allowed; section 10
+ makes it unnecessary.
+ 
+   3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+ 
+   No covered work shall be deemed part of an effective technological
+ measure under any applicable law fulfilling obligations under article
+ 11 of the WIPO copyright treaty adopted on 20 December 1996, or
+ similar laws prohibiting or restricting circumvention of such
+ measures.
+ 
+   When you convey a covered work, you waive any legal power to forbid
+ circumvention of technological measures to the extent such circumvention
+ is effected by exercising rights under this License with respect to
+ the covered work, and you disclaim any intention to limit operation or
+ modification of the work as a means of enforcing, against the work's
+ users, your or third parties' legal rights to forbid circumvention of
+ technological measures.
+ 
+   4. Conveying Verbatim Copies.
+ 
+   You may convey verbatim copies of the Program's source code as you
+ receive it, in any medium, provided that you conspicuously and
+ appropriately publish on each copy an appropriate copyright notice;
+ keep intact all notices stating that this License and any
+ non-permissive terms added in accord with section 7 apply to the code;
+ keep intact all notices of the absence of any warranty; and give all
+ recipients a copy of this License along with the Program.
+ 
+   You may charge any price or no price for each copy that you convey,
+ and you may offer support or warranty protection for a fee.
+ 
+   5. Conveying Modified Source Versions.
+ 
+   You may convey a work based on the Program, or the modifications to
+ produce it from the Program, in the form of source code under the
+ terms of section 4, provided that you also meet all of these conditions:
+ 
+     a) The work must carry prominent notices stating that you modified
+     it, and giving a relevant date.
+ 
+     b) The work must carry prominent notices stating that it is
+     released under this License and any conditions added under section
+     7.  This requirement modifies the requirement in section 4 to
+     "keep intact all notices".
+ 
+     c) You must license the entire work, as a whole, under this
+     License to anyone who comes into possession of a copy.  This
+     License will therefore apply, along with any applicable section 7
+     additional terms, to the whole of the work, and all its parts,
+     regardless of how they are packaged.  This License gives no
+     permission to license the work in any other way, but it does not
+     invalidate such permission if you have separately received it.
+ 
+     d) If the work has interactive user interfaces, each must display
+     Appropriate Legal Notices; however, if the Program has interactive
+     interfaces that do not display Appropriate Legal Notices, your
+     work need not make them do so.
+ 
+   A compilation of a covered work with other separate and independent
+ works, which are not by their nature extensions of the covered work,
+ and which are not combined with it such as to form a larger program,
+ in or on a volume of a storage or distribution medium, is called an
+ "aggregate" if the compilation and its resulting copyright are not
+ used to limit the access or legal rights of the compilation's users
+ beyond what the individual works permit.  Inclusion of a covered work
+ in an aggregate does not cause this License to apply to the other
+ parts of the aggregate.
+ 
+   6. Conveying Non-Source Forms.
+ 
+   You may convey a covered work in object code form under the terms
+ of sections 4 and 5, provided that you also convey the
+ machine-readable Corresponding Source under the terms of this License,
+ in one of these ways:
+ 
+     a) Convey the object code in, or embodied in, a physical product
+     (including a physical distribution medium), accompanied by the
+     Corresponding Source fixed on a durable physical medium
+     customarily used for software interchange.
+ 
+     b) Convey the object code in, or embodied in, a physical product
+     (including a physical distribution medium), accompanied by a
+     written offer, valid for at least three years and valid for as
+     long as you offer spare parts or customer support for that product
+     model, to give anyone who possesses the object code either (1) a
+     copy of the Corresponding Source for all the software in the
+     product that is covered by this License, on a durable physical
+     medium customarily used for software interchange, for a price no
+     more than your reasonable cost of physically performing this
+     conveying of source, or (2) access to copy the
+     Corresponding Source from a network server at no charge.
+ 
+     c) Convey individual copies of the object code with a copy of the
+     written offer to provide the Corresponding Source.  This
+     alternative is allowed only occasionally and noncommercially, and
+     only if you received the object code with such an offer, in accord
+     with subsection 6b.
+ 
+     d) Convey the object code by offering access from a designated
+     place (gratis or for a charge), and offer equivalent access to the
+     Corresponding Source in the same way through the same place at no
+     further charge.  You need not require recipients to copy the
+     Corresponding Source along with the object code.  If the place to
+     copy the object code is a network server, the Corresponding Source
+     may be on a different server (operated by you or a third party)
+     that supports equivalent copying facilities, provided you maintain
+     clear directions next to the object code saying where to find the
+     Corresponding Source.  Regardless of what server hosts the
+     Corresponding Source, you remain obligated to ensure that it is
+     available for as long as needed to satisfy these requirements.
+ 
+     e) Convey the object code using peer-to-peer transmission, provided
+     you inform other peers where the object code and Corresponding
+     Source of the work are being offered to the general public at no
+     charge under subsection 6d.
+ 
+   A separable portion of the object code, whose source code is excluded
+ from the Corresponding Source as a System Library, need not be
+ included in conveying the object code work.
+ 
+   A "User Product" is either (1) a "consumer product", which means any
+ tangible personal property which is normally used for personal, family,
+ or household purposes, or (2) anything designed or sold for incorporation
+ into a dwelling.  In determining whether a product is a consumer product,
+ doubtful cases shall be resolved in favor of coverage.  For a particular
+ product received by a particular user, "normally used" refers to a
+ typical or common use of that class of product, regardless of the status
+ of the particular user or of the way in which the particular user
+ actually uses, or expects or is expected to use, the product.  A product
+ is a consumer product regardless of whether the product has substantial
+ commercial, industrial or non-consumer uses, unless such uses represent
+ the only significant mode of use of the product.
+ 
+   "Installation Information" for a User Product means any methods,
+ procedures, authorization keys, or other information required to install
+ and execute modified versions of a covered work in that User Product from
+ a modified version of its Corresponding Source.  The information must
+ suffice to ensure that the continued functioning of the modified object
+ code is in no case prevented or interfered with solely because
+ modification has been made.
+ 
+   If you convey an object code work under this section in, or with, or
+ specifically for use in, a User Product, and the conveying occurs as
+ part of a transaction in which the right of possession and use of the
+ User Product is transferred to the recipient in perpetuity or for a
+ fixed term (regardless of how the transaction is characterized), the
+ Corresponding Source conveyed under this section must be accompanied
+ by the Installation Information.  But this requirement does not apply
+ if neither you nor any third party retains the ability to install
+ modified object code on the User Product (for example, the work has
+ been installed in ROM).
+ 
+   The requirement to provide Installation Information does not include a
+ requirement to continue to provide support service, warranty, or updates
+ for a work that has been modified or installed by the recipient, or for
+ the User Product in which it has been modified or installed.  Access to a
+ network may be denied when the modification itself materially and
+ adversely affects the operation of the network or violates the rules and
+ protocols for communication across the network.
+ 
+   Corresponding Source conveyed, and Installation Information provided,
+ in accord with this section must be in a format that is publicly
+ documented (and with an implementation available to the public in
+ source code form), and must require no special password or key for
+ unpacking, reading or copying.
+ 
+   7. Additional Terms.
+ 
+   "Additional permissions" are terms that supplement the terms of this
+ License by making exceptions from one or more of its conditions.
+ Additional permissions that are applicable to the entire Program shall
+ be treated as though they were included in this License, to the extent
+ that they are valid under applicable law.  If additional permissions
+ apply only to part of the Program, that part may be used separately
+ under those permissions, but the entire Program remains governed by
+ this License without regard to the additional permissions.
+ 
+   When you convey a copy of a covered work, you may at your option
+ remove any additional permissions from that copy, or from any part of
+ it.  (Additional permissions may be written to require their own
+ removal in certain cases when you modify the work.)  You may place
+ additional permissions on material, added by you to a covered work,
+ for which you have or can give appropriate copyright permission.
+ 
+   Notwithstanding any other provision of this License, for material you
+ add to a covered work, you may (if authorized by the copyright holders of
+ that material) supplement the terms of this License with terms:
+ 
+     a) Disclaiming warranty or limiting liability differently from the
+     terms of sections 15 and 16 of this License; or
+ 
+     b) Requiring preservation of specified reasonable legal notices or
+     author attributions in that material or in the Appropriate Legal
+     Notices displayed by works containing it; or
+ 
+     c) Prohibiting misrepresentation of the origin of that material, or
+     requiring that modified versions of such material be marked in
+     reasonable ways as different from the original version; or
+ 
+     d) Limiting the use for publicity purposes of names of licensors or
+     authors of the material; or
+ 
+     e) Declining to grant rights under trademark law for use of some
+     trade names, trademarks, or service marks; or
+ 
+     f) Requiring indemnification of licensors and authors of that
+     material by anyone who conveys the material (or modified versions of
+     it) with contractual assumptions of liability to the recipient, for
+     any liability that these contractual assumptions directly impose on
+     those licensors and authors.
+ 
+   All other non-permissive additional terms are considered "further
+ restrictions" within the meaning of section 10.  If the Program as you
+ received it, or any part of it, contains a notice stating that it is
+ governed by this License along with a term that is a further
+ restriction, you may remove that term.  If a license document contains
+ a further restriction but permits relicensing or conveying under this
+ License, you may add to a covered work material governed by the terms
+ of that license document, provided that the further restriction does
+ not survive such relicensing or conveying.
+ 
+   If you add terms to a covered work in accord with this section, you
+ must place, in the relevant source files, a statement of the
+ additional terms that apply to those files, or a notice indicating
+ where to find the applicable terms.
+ 
+   Additional terms, permissive or non-permissive, may be stated in the
+ form of a separately written license, or stated as exceptions;
+ the above requirements apply either way.
+ 
+   8. Termination.
+ 
+   You may not propagate or modify a covered work except as expressly
+ provided under this License.  Any attempt otherwise to propagate or
+ modify it is void, and will automatically terminate your rights under
+ this License (including any patent licenses granted under the third
+ paragraph of section 11).
+ 
+   However, if you cease all violation of this License, then your
+ license from a particular copyright holder is reinstated (a)
+ provisionally, unless and until the copyright holder explicitly and
+ finally terminates your license, and (b) permanently, if the copyright
+ holder fails to notify you of the violation by some reasonable means
+ prior to 60 days after the cessation.
+ 
+   Moreover, your license from a particular copyright holder is
+ reinstated permanently if the copyright holder notifies you of the
+ violation by some reasonable means, this is the first time you have
+ received notice of violation of this License (for any work) from that
+ copyright holder, and you cure the violation prior to 30 days after
+ your receipt of the notice.
+ 
+   Termination of your rights under this section does not terminate the
+ licenses of parties who have received copies or rights from you under
+ this License.  If your rights have been terminated and not permanently
+ reinstated, you do not qualify to receive new licenses for the same
+ material under section 10.
+ 
+   9. Acceptance Not Required for Having Copies.
+ 
+   You are not required to accept this License in order to receive or
+ run a copy of the Program.  Ancillary propagation of a covered work
+ occurring solely as a consequence of using peer-to-peer transmission
+ to receive a copy likewise does not require acceptance.  However,
+ nothing other than this License grants you permission to propagate or
+ modify any covered work.  These actions infringe copyright if you do
+ not accept this License.  Therefore, by modifying or propagating a
+ covered work, you indicate your acceptance of this License to do so.
+ 
+   10. Automatic Licensing of Downstream Recipients.
+ 
+   Each time you convey a covered work, the recipient automatically
+ receives a license from the original licensors, to run, modify and
+ propagate that work, subject to this License.  You are not responsible
+ for enforcing compliance by third parties with this License.
+ 
+   An "entity transaction" is a transaction transferring control of an
+ organization, or substantially all assets of one, or subdividing an
+ organization, or merging organizations.  If propagation of a covered
+ work results from an entity transaction, each party to that
+ transaction who receives a copy of the work also receives whatever
+ licenses to the work the party's predecessor in interest had or could
+ give under the previous paragraph, plus a right to possession of the
+ Corresponding Source of the work from the predecessor in interest, if
+ the predecessor has it or can get it with reasonable efforts.
+ 
+   You may not impose any further restrictions on the exercise of the
+ rights granted or affirmed under this License.  For example, you may
+ not impose a license fee, royalty, or other charge for exercise of
+ rights granted under this License, and you may not initiate litigation
+ (including a cross-claim or counterclaim in a lawsuit) alleging that
+ any patent claim is infringed by making, using, selling, offering for
+ sale, or importing the Program or any portion of it.
+ 
+   11. Patents.
+ 
+   A "contributor" is a copyright holder who authorizes use under this
+ License of the Program or a work on which the Program is based.  The
+ work thus licensed is called the contributor's "contributor version".
+ 
+   A contributor's "essential patent claims" are all patent claims
+ owned or controlled by the contributor, whether already acquired or
+ hereafter acquired, that would be infringed by some manner, permitted
+ by this License, of making, using, or selling its contributor version,
+ but do not include claims that would be infringed only as a
+ consequence of further modification of the contributor version.  For
+ purposes of this definition, "control" includes the right to grant
+ patent sublicenses in a manner consistent with the requirements of
+ this License.
+ 
+   Each contributor grants you a non-exclusive, worldwide, royalty-free
+ patent license under the contributor's essential patent claims, to
+ make, use, sell, offer for sale, import and otherwise run, modify and
+ propagate the contents of its contributor version.
+ 
+   In the following three paragraphs, a "patent license" is any express
+ agreement or commitment, however denominated, not to enforce a patent
+ (such as an express permission to practice a patent or covenant not to
+ sue for patent infringement).  To "grant" such a patent license to a
+ party means to make such an agreement or commitment not to enforce a
+ patent against the party.
+ 
+   If you convey a covered work, knowingly relying on a patent license,
+ and the Corresponding Source of the work is not available for anyone
+ to copy, free of charge and under the terms of this License, through a
+ publicly available network server or other readily accessible means,
+ then you must either (1) cause the Corresponding Source to be so
+ available, or (2) arrange to deprive yourself of the benefit of the
+ patent license for this particular work, or (3) arrange, in a manner
+ consistent with the requirements of this License, to extend the patent
+ license to downstream recipients.  "Knowingly relying" means you have
+ actual knowledge that, but for the patent license, your conveying the
+ covered work in a country, or your recipient's use of the covered work
+ in a country, would infringe one or more identifiable patents in that
+ country that you have reason to believe are valid.
+ 
+   If, pursuant to or in connection with a single transaction or
+ arrangement, you convey, or propagate by procuring conveyance of, a
+ covered work, and grant a patent license to some of the parties
+ receiving the covered work authorizing them to use, propagate, modify
+ or convey a specific copy of the covered work, then the patent license
+ you grant is automatically extended to all recipients of the covered
+ work and works based on it.
+ 
+   A patent license is "discriminatory" if it does not include within
+ the scope of its coverage, prohibits the exercise of, or is
+ conditioned on the non-exercise of one or more of the rights that are
+ specifically granted under this License.  You may not convey a covered
+ work if you are a party to an arrangement with a third party that is
+ in the business of distributing software, under which you make payment
+ to the third party based on the extent of your activity of conveying
+ the work, and under which the third party grants, to any of the
+ parties who would receive the covered work from you, a discriminatory
+ patent license (a) in connection with copies of the covered work
+ conveyed by you (or copies made from those copies), or (b) primarily
+ for and in connection with specific products or compilations that
+ contain the covered work, unless you entered into that arrangement,
+ or that patent license was granted, prior to 28 March 2007.
+ 
+   Nothing in this License shall be construed as excluding or limiting
+ any implied license or other defenses to infringement that may
+ otherwise be available to you under applicable patent law.
+ 
+   12. No Surrender of Others' Freedom.
+ 
+   If conditions are imposed on you (whether by court order, agreement or
+ otherwise) that contradict the conditions of this License, they do not
+ excuse you from the conditions of this License.  If you cannot convey a
+ covered work so as to satisfy simultaneously your obligations under this
+ License and any other pertinent obligations, then as a consequence you may
+ not convey it at all.  For example, if you agree to terms that obligate you
+ to collect a royalty for further conveying from those to whom you convey
+ the Program, the only way you could satisfy both those terms and this
+ License would be to refrain entirely from conveying the Program.
+ 
+   13. Remote Network Interaction; Use with the GNU General Public License.
+ 
+   Notwithstanding any other provision of this License, if you modify the
+ Program, your modified version must prominently offer all users
+ interacting with it remotely through a computer network (if your version
+ supports such interaction) an opportunity to receive the Corresponding
+ Source of your version by providing access to the Corresponding Source
+ from a network server at no charge, through some standard or customary
+ means of facilitating copying of software.  This Corresponding Source
+ shall include the Corresponding Source for any work covered by version 3
+ of the GNU General Public License that is incorporated pursuant to the
+ following paragraph.
+ 
+   Notwithstanding any other provision of this License, you have
+ permission to link or combine any covered work with a work licensed
+ under version 3 of the GNU General Public License into a single
+ combined work, and to convey the resulting work.  The terms of this
+ License will continue to apply to the part which is the covered work,
+ but the work with which it is combined will remain governed by version
+ 3 of the GNU General Public License.
+ 
+   14. Revised Versions of this License.
+ 
+   The Free Software Foundation may publish revised and/or new versions of
+ the GNU Affero General Public License from time to time.  Such new versions
+ will be similar in spirit to the present version, but may differ in detail to
+ address new problems or concerns.
+ 
+   Each version is given a distinguishing version number.  If the
+ Program specifies that a certain numbered version of the GNU Affero General
+ Public License "or any later version" applies to it, you have the
+ option of following the terms and conditions either of that numbered
+ version or of any later version published by the Free Software
+ Foundation.  If the Program does not specify a version number of the
+ GNU Affero General Public License, you may choose any version ever published
+ by the Free Software Foundation.
+ 
+   If the Program specifies that a proxy can decide which future
+ versions of the GNU Affero General Public License can be used, that proxy's
+ public statement of acceptance of a version permanently authorizes you
+ to choose that version for the Program.
+ 
+   Later license versions may give you additional or different
+ permissions.  However, no additional obligations are imposed on any
+ author or copyright holder as a result of your choosing to follow a
+ later version.
+ 
+   15. Disclaimer of Warranty.
+ 
+   THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+ APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+ HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+ OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+ THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+ IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+ 
+   16. Limitation of Liability.
+ 
+   IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+ WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+ THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+ GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+ USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+ DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+ PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+ EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGES.
+ 
+   17. Interpretation of Sections 15 and 16.
+ 
+   If the disclaimer of warranty and limitation of liability provided
+ above cannot be given local legal effect according to their terms,
+ reviewing courts shall apply local law that most closely approximates
+ an absolute waiver of all civil liability in connection with the
+ Program, unless a warranty or assumption of liability accompanies a
+ copy of the Program in return for a fee.
+ 
+                      END OF TERMS AND CONDITIONS
+ 
+             How to Apply These Terms to Your New Programs
+ 
+   If you develop a new program, and you want it to be of the greatest
+ possible use to the public, the best way to achieve this is to make it
+ free software which everyone can redistribute and change under these terms.
+ 
+   To do so, attach the following notices to the program.  It is safest
+ to attach them to the start of each source file to most effectively
+ state the exclusion of warranty; and each file should have at least
+ the "copyright" line and a pointer to where the full notice is found.
+ 
+     <one line to give the program's name and a brief idea of what it does.>
+     Copyright (C) <year>  <name of author>
+ 
+     This program is free software: you can redistribute it and/or modify
+     it under the terms of the GNU Affero General Public License as published
+     by the Free Software Foundation, either version 3 of the License, or
+     (at your option) any later version.
+ 
+     This program is distributed in the hope that it will be useful,
+     but WITHOUT ANY WARRANTY; without even the implied warranty of
+     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+     GNU Affero General Public License for more details.
+ 
+     You should have received a copy of the GNU Affero General Public License
+     along with this program.  If not, see <https://www.gnu.org/licenses/>.
+ 
+ Also add information on how to contact you by electronic and paper mail.
+ 
+   If your software can interact with users remotely through a computer
+ network, you should also make sure that it provides a way for users to
+ get its source.  For example, if your program is a web application, its
+ interface could display a "Source" link that leads users to an archive
+ of the code.  There are many ways you could offer source, and different
+ solutions will be better for different programs; see section 13 for the
+ specific requirements.
+ 
+   You should also get your employer (if you work as a programmer) or school,
+ if any, to sign a "copyright disclaimer" for the program, if necessary.
+ For more information on this, and how to apply and follow the GNU AGPL, see
+ <https://www.gnu.org/licenses/>.

A content/LICENSE => content/LICENSE +1 -0
@@ 0,0 1,1 @@
+ All Content (Talks / Posts / Etc) are Copyright (C) Andrew Zah.

M content/pages/404.md => content/pages/404.md +1 -1
@@ 10,4 10,4 @@   If you followed a link on this site, please [report it]!
  
- [report it]: mailto:zah@andrewzah.com
+ [report it]: mailto:talk@andrewzah.com

M content/pages/contact.md => content/pages/contact.md +1 -1
@@ 6,7 6,7 @@   Ways to contact me, in order of preference.
  
- * email (strongly preferred): [zah@andrewzah.com](mailto:zah@andrewzah.com)
+ * email (strongly preferred): [talk@andrewzah.com](mailto:talk@andrewzah.com)
  
  I do my best to respond to incoming email, during standard working hours typically. KST.
  

M content/posts/001_a_new_year/index.md => content/posts/001_a_new_year/index.md +3 -3
@@ 28,7 28,7 @@ Here's what my Caddyfile for `andrewzah.com`, `andrei.blue`, and `znc.andrewzah.com` looks like:
  ```
  andrewzah.com, andrei.blue {
-   tls zah@andrewzah.com
+   tls your@email.com
  
    log / stdout {combined}
    errors stderr


@@ 37,7 37,7 @@ }
  
  znc.andrewzah.com {
-   tls zah@andrewzah.com
+   tls your@email.com
  
    log / stdout {combined}
    errors stderr


@@ 100,7 100,7 @@ ```
  proxy :6667 bitlbee:6667 {
    host znc.andrewzah.com
-   tls zah@andrewzah.com
+   tls your@email.com
  }
  ```
  

M content/posts/004_selfhosted_git_gitea_docker_caddy/index.md => content/posts/004_selfhosted_git_gitea_docker_caddy/index.md +1 -1
@@ 60,7 60,7 @@ Caddy's `Caddyfile` syntax is fairly simple:
  ```caddyfile
  git.andrewzah.com {
-   tls zah@andrewzah.com
+   tls your@email.com
  
    log / stdout {combined}
    errors stderr

M content/posts/007_korean_cooking_eating_reference/index.md => content/posts/007_korean_cooking_eating_reference/index.md +1 -1
@@ 25,7 25,7 @@   <!-- more -->
  
- If you spot a mistake or wish to add to this, please [contact Andrew](mailto:zah@andrewzah.com?subject=Korean%20Cooking%20List%20).
+ If you spot a mistake or wish to add to this, please [contact Andrew](mailto:blog@andrewzah.com?subject=Korean%20Cooking%20List%20).
  
  ## General
  ### Positions / People Terms

M content/talks/05-28-2019-wasm-rust-seoul/index.md => content/talks/05-28-2019-wasm-rust-seoul/index.md +369 -87
@@ 27,6 27,7 @@ \usepackage{color} % for syntax highlighting definitions
  \usepackage{fontspec} % for custom firacode setup
  \usepackage{listings} % for formatting codeblocks
+ \usepackage[T1]{fontenc}
  
  \usetheme{AnnArbor}
  \usecolortheme{spruce}


@@ 38,34 39,59 @@ \setbeamercolor{section in toc}{fg=black}
  %\setbeameroption{show notes on second screen}
  
- %% fonts
- 
- \setmonofont{Fira Code}[
-   Contextuals=Alternate  % Activate the calt feature
- ]
- \usepackage{lstfiracode}
  
  %% code syntax highlighting
- 
  \definecolor{lightgray}{rgb}{.9,.9,.9}
  \definecolor{darkgray}{rgb}{.4,.4,.4}
  \definecolor{purple}{rgb}{0.65, 0.12, 0.82}
+ \definecolor{gruv-red}{RGB}{204,36,29}
+ \definecolor{gruv-yellow}{RGB}{215,153,33}
+ \definecolor{gruv-aqua}{RGB}{104,157,106}
+ \definecolor{gruv-green}{RGB}{69,133,136}
  
  \lstdefinelanguage{JavaScript}{
-   keywords={break, case, catch, continue, debugger, default, delete, do, else, false, finally, for, function, if, in, instanceof, new, null, return, switch, this, throw, true, try, typeof, var, void, while, with},
+   keywords={break, case, then, catch, continue, debugger, default, delete, do, else, false, finally, for, function, if, in, instanceof, new, null, return, switch, this, throw, true, try, typeof, var, void, while, with},
    morecomment=[l]{//},
    morecomment=[s]{/*}{*/},
    morestring=[b]',
    morestring=[b]",
    ndkeywords={class, export, boolean, throw, implements, import, this},
-   keywordstyle=\color{blue}\ttfamily,
+   keywordstyle=\color{gruv-green}\ttfamily,
    ndkeywordstyle=\color{darkgray}\ttfamily,
    identifierstyle=\color{black}\ttfamily,
-   commentstyle=\color{purple}\ttfamily,
-   stringstyle=\color{red}\ttfamily,
+   stringstyle=\color{darkgray}\ttfamily,
+   frame=none,
+   sensitive=true
+ }
+ \lstdefinelanguage{Rust}{
+   keywordstyle=\color{gruv-yellow}\ttfamily,
+   keywordstyle=[1]{\color{gruv-aqua}\ttfamily},
+   keywordstyle=[2]{\color{gruv-yellow}\ttfamily},
+   keywordstyle=[3]{\color{gruv-red}\ttfamily},
+   morestring=[b]",
+   morestring=[b]',
+   stringstyle=\color{gray}\ttfamily,
+   otherkeywords = {\&Display, \&str, \#\[wasm\_bindgen\]},
+   morekeywords=[1]{derive, \#\[wasm\_bindgen\], wasm\_bindgen, js\_namespace, console},
+   morekeywords=[2]{Serialize, KoreanInteger, Deserialize, String, i128, i32, char, \&str, \&Display},
+   morekeywords=[3]{use, pub, fn, extern, struct, self, impl},
+   frame=none,
+   sensitive=true
+ }
+ \lstdefinelanguage{WASM}{
+   keywords=[1]{module, type, func, table, memory, export, param, result},
+   keywordstyle=\color{gruv-green}\ttfamily,
+   frame=none,
    sensitive=true
  }
  
+ \lstset{%
+   basicstyle  = \fontfamily{pcr}\fontsize{10pt}{12pt}\selectfont,
+   numberstyle = \small,
+   numbersep   = 10pt,
+   frame=none,
+ }
+ 
  %% behavior modifications
  
  \newenvironment{wideitemize}{\itemize\addtolength{\itemsep}{10pt}}{\enditemize}


@@ 82,7 108,7 @@ \title[WASM!]{Web Assembly: What does it do? Does it do things? Let's find out!}
  \author[]{Andrew Zah \texttt{<zah@andrewzah.com>}}
  \institute[Rust Meetup Seoul]{Rust Meetup Seoul}
- \date{May 23, 2019}
+ \date{May 28, 2019}
  
  %% preamble over
  


@@ 94,6 120,8 @@ \tableofcontents
  \end{frame}
  
+ %%%%%%%%%%%%%%%%%%%
+ 
  \section{What is WASM?}
  \begin{frame}
    \frametitle{Web Assembly's Definition}


@@ 105,49 133,50 @@ \begin{frame}
    \frametitle{What WASM is not}
    \begin{wideitemize}
-     \item WASM is not a programming language – though you can write by hand
-     \item WASM isn't standalone – it needs a host
-     \item WASM is not intended to replace javascript
+     \item WASM is not a programming language, though you can write by hand
+     \item<2-> WASM isn't standalone: it needs a host
+     \item<3-> WASM is not intended to replace javascript
    \end{wideitemize}
  \end{frame}
  
  \begin{frame}
-   \frametitle{What is it actually, though?}
+   \frametitle{what is it actually, though?}
    \begin{wideitemize}
      \item WASM's format isn't coupled to any OS or architecture
-     \item Very similar to Java's bytecode or C\#'s CLR
-     \item Name and definition is a misnomer
-     \item It can run \alert{anywhere} you can build a \alert{host}
+     \item<2-> Very similar to Java's bytecode or C\#'s CLR
+     \item<3-> Name and definition is a misnomer
+     \item<4-> It can run \alert{anywhere} you can build a \alert{host}
    \end{wideitemize}
  \end{frame}
  
  \begin{frame}
-   \frametitle{What is it actually, though? pt. 2}
+   \frametitle{WASM's specification}
    \begin{wideitemize}
      \item WASM is \alert{stack-based}, not register-based
-     \item WASM 1.0 only had 4 primitives
-     \item `i32`, `i64`, `f32`, `f64` 
-     \item Unlike other assembly languages, WASM has no `jmp` instruction
+     \item<2-> WASM 1.0 only has 4 primitives
+     \item<3-> `i32`, `i64`, `f32`, `f64` 
+     \item<4-> No arrays
+     \item<5-> no \alert{jmp} instruction
    \end{wideitemize}
-   \note[item]{Forth is just about the only somewhat-mainline language that is stack-based.}
+   \note[item]{Forth and retro are just about the only somewhat-mainline language that are stack-based.}
    \note[item]{RPL also exists but\ldots}
  \end{frame}
  
  \begin{frame}
-   \frametitle{Memory}
+   \frametitle{memory}
    \begin{columns}
      \begin{column}{0.5\textwidth}
        \begin{wideitemize}
          \item WASM has no \alert{new::()} operator or \alert{heap}
-         \item There are no objects or or garbage collection
-         \item Instead, WASM has \alert{linear memory}
-         \item<2-> Modern programming languages have spoiled us
+         \item<2-> There are no objects or or garbage collection
+         \item<3-> Instead, WASM has \alert{linear memory}
+         \item<4-> this causes a need for linearization and bitmasking, etc
        \end{wideitemize}
      \end{column}
      \begin{column}{0.5\textwidth}
        \begin{center}
-         \only<2-> {
-           \begin{tikzpicture}<2->
+         \uncover<3-> {
+           \begin{tikzpicture}
              \draw [gray] (0,0) rectangle (4,1) node[pos=.5] {unused};
              \draw [teal] (0,1) rectangle (4,2) node[pos=.5] {var3 [80\ldots119]};
              \draw [gray] (0,2) rectangle (4,3) node[pos=.5] {var2 [40\ldots79]};


@@ 160,63 189,44 @@ \end{frame}
  
  \begin{frame}
-   \frametitle{Anyone can be a WASM host!}
+   \frametitle{anyone can be a WASM host!}
    
    \begin{alertblock}{The Host needs to:}
      \begin{enumerate}
        \item Load and validate the WASM binary (the file, not the logic)
-       \item Expose Exports
-       \item Satisfy Imports
-       \item Interpret \& Execute Modules
-       \item Isolate Modules
+       \item<2-> Expose Exports
+       \item<3-> Satisfy Imports
+       \item<4-> Interpret \& Execute Modules
+       \item<5-> Isolate Modules
      \end{enumerate}
    \end{alertblock}
  \end{frame}
  
  \begin{frame}
-   \frametitle{Infinity and Beyond}
- 
+   \frametitle{infinity and beyond?}
    \begin{wideitemize}
      \item WebAssembly modules are hotswappable
-     \item This means \alert{\em any host} can swap modules at will
-     \item PLCs (Programmable Logic Controllers) could adhere to a well-known contract
-     \item This would let us program for hardware controllers in \alert{any language}!
+     \item<2-> PLCs (Programmable Logic Controllers) could adhere to a well-known contract
+     \item<2-> This would let us program for hardware controllers in \alert{any language}!
+     \item<3-> \alert{wasmi} is an rust open-source wasm interpreter
+     \item<4-> \alert{serverless-wasm} does indeed exist
    \end{wideitemize}
-   
  \end{frame}
  
  \begin{frame}
-   \frametitle{Security}
+   \frametitle{security}
    \begin{wideitemize}
-     \item WASM can always be converted back to plaintext
-     \item Do not put secrets in WASM modules
-     \item \alert{Message handoffs} are not always secure!
-     \item One can disassemble, modify, recompile, inject a module
-     \item Accordingly, \alert{sign} and \alert{encrypt} modules!
+     \item WASM binaries can always be converted back to plaintext
+     \item<2-> Do not put secrets in WASM modules
+     \item<3-> \alert{Message handoffs} are not always secure!
+     \item<4-> Accordingly, \alert{sign} and \alert{encrypt} modules!
    \end{wideitemize}
  \end{frame}
  
  \begin{frame}[fragile]
-   \frametitle{Example WASM Syntax}
-   \begin{block}{add.wat}
-     \begin{lstlisting}[language=Lisp]
- (module
-   (func $add (param $lhs i32) (param $rhs i32) (result i32)
-     (i32.add
-         (get_local $lhs)
-         (get_local $rhs)
-     )
-   )
-   (export "add" (func $add))
- )
-     \end{lstlisting}
-   \end{block}
- \end{frame}
- 
- \begin{frame}[fragile]
-   \frametitle{Add Example: Rust}
+   \frametitle{add example: rust side}
    \begin{block}{main.rs}
-     \begin{lstlisting}[language=c++]
+     \begin{lstlisting}[language=rust]
  #[no_mangle]
  pub extern "C" fn add_one(x: i32) -> i32 {
      x + 1


@@ 226,9 236,9 @@ \end{frame}
  
  \begin{frame}[fragile]
-   \frametitle{Add Example: WASM}
+   \frametitle{add example: generated WASM}
    \begin{block}{main.wasm}
-     \begin{lstlisting}[language=Lisp]
+     \begin{lstlisting}[language=wasm]
  (module
    (type $t0 (func (param i32) (result i32)))
    (func $add_one


@@ 242,52 252,313 @@ \end{block}
  \end{frame}
  
+ \begin{frame}
+   \frametitle{summary}
+   \begin{wideitemize}
+     \item WASM is simply a instruction format that's portable
+     \item WASM can run anywhere so long as a host exists
+     \item Just because you can write WASM doesn't mean you should
+   \end{wideitemize}
+ \end{frame}
+ 
+ %%%%%%%%%%%%%%%%%%%
+ 
+ \section{Applications of WASM in Rust}
+ 
+ \begin{frame}
+   \frametitle{wasm-bindgen}
+   \begin{wideitemize}
+     \item CLI tool to generate bindings for the wasm code to work
+     \item<2-> can be run manually but \alert{wasm-pack} simplifies things
+     \item<3-> \alert{automates} linearization, strings, complex types bindings
+   \end{wideitemize}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{configuring cargo}
+   \begin{block}{Cargo.toml}
+     \begin{lstlisting}
+ [lib]
+ crate-type = ["cdylib"]
+ 
+ [build]
+ target = "wasm32-unknown-unknown"
+ 
+ [dependencies]
+ wasm-bindgen = "0.2.45"
+ 
+ [dependencies.rand]
+ features = ["wasm-bindgen"]
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{rust wasm:  functions}
+   \begin{block}{main.rs}
+     \begin{lstlisting}[language=rust]
+ use wasm_bindgen::prelude::*;
+ #[wasm_bindgen]
+ extern "C" {
+     #[wasm_bindgen(js_namespace = console)]
+     fn log(s: &str);
+     #[wasm_bindgen(method, structural, js_namespace = ROT)]
+     fn draw(this: &Display, x: i32, y: i32, ch: &str);
+ }
+ 
+ #[wasm_bindgen]
+ pub fn greet(name: &str) {
+     log(&format!("Hello, {}!", name));
+ }
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
  
- \section{How Rust and WASM Intertwine}
  \begin{frame}[fragile]
-   \frametitle{wasm-pack}
+   \frametitle{js\_sys and web\_sys provide bindings}
    \begin{block}{main.rs}
-     \begin{lstlisting}[language=c++]
+     \begin{lstlisting}[language=rust]
+ use wasm_bindgen::prelude::*;
+ use wasm_bindgen::JsValue;
+ use web_sys::console::log_1;
+ 
  #[wasm_bindgen]
- extern {
-     fn alert(s: &str);
+ pub fn hi() {
+   log_1(JsValue::from_str("hi"));
  }
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{rust wasm: structs and impls}
+   \begin{block}{main.rs}
+     \begin{lstlisting}[language=rust]
+ #[wasm_bindgen]
+ pub struct Counter { count: i32, }
  
  #[wasm_bindgen]
- pub fn greet() {
-     alert("Hello, wasm-game-of-life!");
+ impl Counter {
+   pub fn get(&self) -> char {
+     log(format!("Count: {}", self.count));
+     self.count
+   }
  }
      \end{lstlisting}
    \end{block}
  \end{frame}
  
- \begin{frame}[fragile]
+ 
+ \begin{frame}
    \frametitle{wasm-pack}
+   \begin{wideitemize}
+     \item<1-> higher level wrapper for \alert{wasm-bindgen}
+     \item<2-> commands: \alert{build}, \alert{test}, \alert{pack}, \alert{publish}, \alert{login}
+     \item<3-> \alert{wasm-bindgen} is still a dependency
+   \end{wideitemize}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{wasm-pack output in /pkg}
+   \begin{block}{exa -T -L1 pkg/}
+     \begin{lstlisting}
+ pkg/
+   package.json
+   wasm_pack_test.d.ts
+   wasm_pack_test.js
+   wasm_pack_test_bg.d.ts
+   wasm_pack_test_bg.wasm
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{wasm-pack output}
    \begin{block}{main.js}
      \begin{lstlisting}[language=javascript]
- import * as wasm from "wasm-game-of-life";
+ const wasm = import('./pkg/hello_world');
  
- wasm.greet();
+ wasm
+   .then(m => m.greet('World!'))
+   .catch(console.error);
      \end{lstlisting}
    \end{block}
  \end{frame}
  
  \begin{frame}
-   \frametitle{wasm-bindgen}
+   \frametitle{extensions and alternatives}
    \begin{wideitemize}
-     \item Adds helpers to allow transfer of \alert{complex types}.
+     \item \alert{web-sys} and \alert{js-sys} provide raw js/web API bindings
+     \item<2-> \alert{std-web} has a similar goal but provides more JS interop + APIs
+     \item<3-> \alert{rust-neon} (external tool) generates \alert{Node.js} modules
+     \item<4-> \alert{yew} is a web framework that compiles to WASM
    \end{wideitemize}
  \end{frame}
  
+ \begin{frame}
+   \frametitle{optimizing the WASM output}
+   \begin{columns}
+     \begin{column}{0.6\textwidth}
+       \begin{wideitemize}
+         \item \alert{wasm-opt} can significantly reduce binary size 
+         \item<2-> \alert{wasm2wat} can be used to confirm
+         \item<3-> \alert{twiggy} is a wasm profiler that analyzes call graphs
+         \item<4-> set \alert{lto = true} in Cargo.toml, but limit to release only
+       \end{wideitemize}
+     \end{column}
+     \begin{column}{0.4\textwidth}
+       \uncover<3->{
+         \includegraphics[scale=0.34]{twiggy.png}
+       }
+     \end{column}
+   \end{columns}
+ \end{frame}
+ 
+ %%%%%%%%%%%%%%%%%%%
+ 
  \section{A Real, Non-Trivial WASM App}
  \begin{frame}
-   \frametitle{Korean Apps}
+   \frametitle{korean apps}
    \begin{wideitemize}
      \item Initially I wrote a cargo crate, \alert{korean-numbers}
-     \item I wanted a way to use this logic in a webapp with React
+     \item<2-> I wanted a way to use this logic in a webapp with React
+     \item<3-> I went with \alert{wasm-bindgen} calls in \alert{package.json} scripts
    \end{wideitemize}
  \end{frame}
  
+ \begin{frame}[fragile]
+   \frametitle{project structure}
+   \begin{block}{exa -T -L2 .}
+     \begin{lstlisting}
+ dist/
+ frontend/
+ native/
+ node_modules/
+ package.json
+ webpack.config.js
+ yarn.lock
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{why wasm-pack may be better}
+   \begin{block}{package.json}
+   \begin{lstlisting}
+ "scripts": {
+   "build-debug": "cd native; cargo +nightly build
+       --target wasm32-unknown-unknown
+     && wasm-bindgen
+         target/wasm32-unknown-unknown/debug/korean_wasm.wasm
+       --out-dir ../frontend/wasm; cd .."
+ }
+ \end{lstlisting}
+ \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{rust side: glue code}
+   \begin{block}{native/src/lib.rs}
+     \begin{lstlisting}[language=rust]
+ use korean_nums::{ NumberSystem, ...}
+ #[wasm_bindgen]
+ struct KoreanInteger { number: i128, hangeul: String, }
+ 
+ #[wasm_bindgen]
+ pub fn random_korean_int(
+   lower_str: &str, upper_str: &str, num_system: &str)
+   -> KoreanInteger
+ { ... }
+ \end{lstlisting}
+ \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{frontend layout}
+   \begin{block}{exa -T -L2 frontend/}
+   \begin{lstlisting}
+ components/
+   korean_numbers/
+ index.html
+ index.js
+ wasm/
+   korean_wasm.d.ts
+   korean_wasm.js
+   korean_wasm_bg.d.ts
+   korean_wasm_bg.wasm
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{calling code from the frontend}
+   \begin{block}{frontend/components/korean\_numbers/index.js}
+     \begin{lstlisting}[language=javascript]
+ const { random_int } = require("../../wasm/korean_wasm");
+ 
+ const res = random_korean_int(0, 10, "sino");
+ \end{lstlisting}
+ \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{non-trivial optimizations}
+   \begin{columns}
+     \begin{column}{0.45\textwidth}
+       \begin{block}{ls -lah | rg wasm | awk `{print \$5, \$9}' | sort}
+         \begin{lstlisting}
+ 282K wasm-opt-Oz-flag.wasm
+ 283K wasm-opt-Os-flag.wasm
+ 306K wasm-opt-O3-flag.wasm
+ 573K wasm-opt-default.wasm
+ 695K bindgen-development.wasm
+ \end{lstlisting}
+     \end{block}
+     \end{column}
+     \begin{column}{0.45\textwidth}<2->
+       \begin{block}{release mode versions}
+         \begin{lstlisting}
+ 126K wasm-opt-lto-Oz-flag.wasm
+ 136K bindgen-release-lto.wasm
+ 166K bindgen-release.wasm
+ \end{lstlisting}
+     \end{block}
+     \end{column}
+   \end{columns}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{inspecting with twiggy}
+   \begin{block}{twiggy top wasm-bindgen-default.wasm}
+ \begin{lstlisting}
+ Shallow Bytes │ Shallow % │ Item
+ 124493 | 17.50% | "function names" subsection
+ 57598  |  8.10% | rand_hc::hc128::Hc128Core::sixteen_steps
+ 50394  |  7.09% | <rand_hc::hc128::Hc128Core>...::generate
+ 24781  |  3.48% | data[1]
+ 22978  |  3.23% | data[2]
+  7624  |  1.07% | <rand::rngs::entropy::EntropyRng>...::try_fill_bytes
+  6928  |  0.97% | korean_nums::parse::parse_hangeul_sino
+  4918  |  0.69% | core::num::flt2dec::strategy::dragon::mul_pow10
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
+ \begin{frame}[fragile]
+   \frametitle{inspecting release mode with twiggy}
+   \begin{block}{twiggy top wasm-opt-Oz-release-lto.wasm}
+ \begin{lstlisting}
+ Shallow Bytes │ Shallow % │ Item
+ 9753 | 7.55% | data[0]
+ 8556 | 6.62% | code[33]
+ 8457 | 6.54% | data[1]
+ 7012 | 5.42% | code[76]
+ 6156 | 4.76% | code[127]
+ 6145 | 4.75% | code[75]
+ \end{lstlisting}
+   \end{block}
+ \end{frame}
+ 
  \begin{frame}
    \begin{center}
      {\huge Thank you} \\


@@ 295,21 566,31 @@ \end{center}
  \end{frame}
  
- \section{Appendix}
+ %%%%%%%%%%%%%%%%%%%
+ 
+ \section*{Appendix}
  \begin{frame}[plain]
    \includegraphics[scale=0.34]{webassembly-studio.png}
  \end{frame}
  
  \begin{frame}
-   \frametitle{Further Reading}
+   \frametitle{further reading}
    \begin{itemize}
-     \item WASM Homepage \texttt{https://webassembly.org}
-     \item WASM Spec \texttt{https://webassembly.github.io/spec/}
+     \item \alert{WASM Homepage} \texttt{https://webassembly.org}
+     \item \alert{WASM Spec} \texttt{https://webassembly.github.io/spec/}
+     \item \alert{wasm-bindgen docs} \texttt{https://rustwasm.github.io/docs/wasm-bindgen/}
+     \item \alert{stdweb} \texttt{https://github.com/koute/stdweb}
+     \item \alert{twiggy profiler} \texttt{https://github.com/rustwasm/twiggy}
+     \item \alert{wat2wasm, wasm2wat, and more} \texttt{https://github.com/WebAssembly/wabt}
+     \item \alert{websys} \texttt{https://rustwasm.github.io/wasm-bindgen/api/web\_sys/}
+     \item \alert{neon-bindings} \texttt{https://github.com/neon-bindings/neon}
+     \item \alert{optimizing emscriptem} \texttt{https://emscripten.org/docs/optimizing/Optimizing-Code.html}
+     \item \alert{wasmi: rust wasm interpreter} \texttt{https://github.com/paritytech/wasmi}
    \end{itemize}
  \end{frame}
  
  \begin{frame}
-   \frametitle{Bibliography}
+   \frametitle{bibliography}
    \begin{thebibliography}{Dijkstra, 1982}
      \bibitem[Hoffman, 2019]{Hoffman2019}
        K.~Hoffman.


@@ 321,4 602,5 @@ \end{frame}
  
  \end{document}
+ 
  ```

M sass/_container.scss => sass/_container.scss +5 -1
@@ 6,9 6,13 @@ font-size: 15px;
    }
  
+   .page-title {
+     margin-bottom: 0px;
+   }
+ 
    .page-meta-data {
      font-family: $serif-stack;
-     margin-top: -.75rem;
+     margin-top: -.25rem;
      margin-bottom: .75rem;
      font-size: 18px;
      display: block;

M templates/_footer.html => templates/_footer.html +2 -1
@@ 1,6 1,7 @@ <footer class="footer">
      <small>
-         &copy; <time datetime="2019">2019</time>. All rights reserved.
+         &copy; Copyright Andrew Zah <time datetime="2019">2019</time>.
          | <a href="/contact">Contact</a>
+         | <a href="https://git.sr.ht/~andrewzah/personal-site/tree">Site Source Code (AGPLv3)</a>
      </small>
  </footer>

M templates/post.html => templates/post.html +7 -5
@@ 18,11 18,13 @@   {% block main %}
    <div itemtype="http://schema.org/Article" class="container post">
-     <h1 itemprop="name">{{ page.title }}</h1>
-     <time itemprop="datePublished" content="{{ page.date | date(format="%Y-%m-%d")}}" datetime="{{ page.date }}" class="page-date">
-         {{ page.date | date(format="%b %d, %Y") }}
-         {% if page.extra.updated %} <time itemprop="dateModified" content={{ page.extra.updated }}>(updated on {{ page.extra.updated }})</time> {% endif %}
-     </time>
+     <h1 class="page-title" itemprop="name">{{ page.title }}</h1>
+     <div class="page-meta-data">
+       <time itemprop="datePublished" content="{{ page.date | date(format="%Y-%m-%d")}}" datetime="{{ page.date }}" class="page-date">
+           {{ page.date | date(format="%b %d, %Y") }}
+           {% if page.extra.updated %} <time itemprop="dateModified" content={{ page.extra.updated }}>(updated on {{ page.extra.updated }})</time> {% endif %}
+       </time>
+     </div>
      <hr>
      <aside id="toc">
          <h2>Table of Contents</h2>

M templates/projects.html => templates/projects.html +6 -4
@@ 12,10 12,12 @@   {% block main %}
    <div itemtype="http://schema.org/Article" class="container projects">
-     <h1 itemprop="name">{{ page.title }}</h1>
-     <time itemprop="datePublished" content="{{ page.date | date(format="%Y-%m-%d")}}" datetime="{{ page.date }}" class="page-date">
-         {{ page.date | date(format="%b %d, %Y") }}
-     </time>
+     <h1 class="page-title" itemprop="name">{{ page.title }}</h1>
+     <div class="page-meta-data">
+       <time itemprop="datePublished" content="{{ page.date | date(format="%Y-%m-%d")}}" datetime="{{ page.date }}" class="page-date">
+           {{ page.date | date(format="%b %d, %Y") }}
+       </time>
+     </div>
      <hr>
      <div>
        {{ page.content | safe }}