Browse Source

Initial commit

main
Marie-Joseph 1 year ago
commit
4fcfe9c462
  1. 1
      .gitignore
  2. 675
      LICENSE.md
  3. 8
      README.md
  4. 52
      app.hy
  5. 24
      blog.hy
  6. 2
      requirements.txt
  7. 2
      setup-flask
  8. 7
      shim.py
  9. BIN
      static/favicon.ico
  10. 67
      static/styles.css
  11. 8
      templates/blog-post.html
  12. 16
      templates/blog.html
  13. 251
      templates/blog/2021-04-29.html
  14. 106
      templates/blog/2021-05-04.html
  15. 95
      templates/blog/LICENSE.md
  16. 9
      templates/index.html
  17. 29
      templates/layout.html
  18. 13
      templates/projects.html

1
.gitignore vendored

@ -0,0 +1 @@
__pycache__

675
LICENSE.md

@ -0,0 +1,675 @@
### GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 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 General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is 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. We, the Free Software Foundation, use
the GNU General Public License for most of our software; it applies
also to any other work released this way by its authors. You can apply
it to your programs, too.
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.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you
have certain responsibilities if you distribute copies of the
software, or if you modify it: responsibilities to respect the freedom
of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so. This is fundamentally incompatible with the
aim of protecting users' freedom to change the software. The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products. If such problems arise substantially in
other domains, we stand ready to extend this provision to those
domains in future versions of the GPL, as needed to protect the
freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish
to avoid the special danger that patents applied to a free program
could make it effectively proprietary. To prevent this, the GPL
assures that patents cannot be used to render the program non-free.
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 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. Use with the GNU Affero General Public License.
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 Affero 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 special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
#### 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions
of the GNU 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 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 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 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 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 General Public License for more details.
You should have received a copy of the GNU 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 the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands \`show w' and \`show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
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 GPL, see <https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
please read <https://www.gnu.org/licenses/why-not-lgpl.html>.

8
README.md

@ -0,0 +1,8 @@
# Trees' Street
This is the source code for my personal website and blog.
It's written using Flask in [Hy](https://docs.hylang.org), a Lisp which compiles to
Python AST, thence to Python bytecode. Yep, plain old Flask, written in a Lisp! Neat, huh?
## TODO
* RSS feed?

52
app.hy

@ -0,0 +1,52 @@
"""
tree.st
"""
(import re)
(import [flask [Flask redirect render-template request session url-for]])
(import [blog [retrieve-posts]])
(setv app (Flask __name__))
(setv post-name-regex (.compile re r"\d{4}-\d{2}-\d{2}"))
#@(app.after-request
(defn after-request [response]
"""
Ensure CSS is reloaded on every page refresh.
This just exists for development purposes.
It should be removed or commented out before deployment.
"""
(setv (. response headers ["Cache-Control"])
"no-cache, no-store, must-revalidate")
(setv (. response headers ["Expires"]) 0)
(setv (. response headers ["Pragma"]) "no-cache")
response))
#@((.route app "/")
(defn index []
"""
Path to the landing page
"""
(render-template "index.html")))
#@((.route app "/blog" :methods ["GET" "POST"])
#@((.route app "/blog/<string:post_name>")
(defn blog [[post-name None]]
"""
Path to the blog
"""
(cond
;; This should eventually parse a list of posts visible to the user
;; sent with the request and add 5-10 more posts onto it.
[(= (. request method) "POST")
(render-template "blog.html"
:posts (retrieve-posts post-name))]
[(= (. request method) "GET")
(if (and (not (none? post-name)) ; Make sure the user is requesting a valid date.
(none? (.match re
post-name-regex
post-name)))
(redirect (url-for "blog")) ; If not, just send them back to the blog.
(render-template "blog.html"
:posts (retrieve-posts post-name)))]))))

24
blog.hy

@ -0,0 +1,24 @@
"""
Blog helper functions
"""
(import [os [listdir]])
(defn test-retrieve-posts [post-name]
(assert (= (first (retrieve-posts post-name)) (+ "blog/" post-name ".html")))
(assert (= (retrieve-posts None) (lfor post (listdir "templates/blog/")
:if (.endswith post ".html")
(+ "blog/" post)))))
(defn retrieve-posts [post-name]
"""
Retrieve post-name or all posts in blog directory
"""
(setv posts-prefix "templates/")
(setv posts-dir "blog/")
(setv posts-suffix ".html")
(if (none? post-name)
(lfor post (listdir (+ posts-prefix posts-dir))
:if (.endswith post posts-suffix)
(+ posts-dir post))
[(+ posts-dir post-name posts-suffix)]))

2
requirements.txt

@ -0,0 +1,2 @@
Flask>=1.1.2
hy>=1.0a1

2
setup-flask

@ -0,0 +1,2 @@
export FLASK_ENV=development
export FLASK_APP=shim.py

7
shim.py

@ -0,0 +1,7 @@
"""
This file serves as the entrypoint for Flask
to properly bootstrap Hy.
"""
import hy
from app import *

BIN
static/favicon.ico

Binary file not shown.

After

Width:  |  Height:  |  Size: 894 B

67
static/styles.css

@ -0,0 +1,67 @@
/* General styling */
* {
box-sizing: border-box;
}
html {
font-family: sans-serif;
background-color: tan;
}
body {
margin: 0rem;
padding: 0rem;
}
/* Header styling */
header {
background-color: forestgreen;
font-family: serif;
text-align: center;
padding: 1rem;
}
nav {
font-family: sans-serif;
padding-bottom: 1rem;
text-align: left;
}
.nav-item {
padding: .25rem;
color: black;
}
/* Content styling */
main {
width: 75%;
max-width: 50rem;
margin: 0 auto 0 auto;
padding: 3rem;
text-align: center;
background-color: brown;
}
footer {
text-align: center;
margin-top: 5rem;
}
/* Blog styling */
.blog-post {
text-align: left;
border-bottom: dotted;
padding: 0rem 0rem 2.5rem 1rem;
}
.blog-title a {
color: black;
}
.blog-show-more {
margin-top: 1rem;
}

8
templates/blog-post.html

@ -0,0 +1,8 @@
<h2 class="blog-title">
<a href="{{ url_for('blog', post_name=self.date()) }}">
{% block title %}{% endblock %}
</a>
</h2>
<h4 class="blog-date">{% block date %}{% endblock %}</h4>
<summary class="blog-summary">{% block summary %}{% endblock %}</summary>
<details class="blog-content">{% block content %}{% endblock %}</details>

16
templates/blog.html

@ -0,0 +1,16 @@
{% extends "layout.html" %}
{% block main %}
<div class="blog-feed">
{% for post in posts %}
<article class="blog-post" id={{ post.lstrip("blog/").rstrip(".html") }}>
{% include post %}
</article>
{% endfor %}
<!--
<form method="post">
<button class="blog-show-more">Show more</button>
</form>
-->
</div>
{% endblock %}

251
templates/blog/2021-04-29.html

@ -0,0 +1,251 @@
{% extends "blog-post.html" %}
{% block title %}A Couple Weeks with the PinePhone{% endblock title %}
{% block date %}2021-04-29{% endblock date %}
{% block summary %}
<p>
I got my <a href="https://mobian-project.org">Mobian</a> Community Edition
<a href="https://pine64.com/product/pinephone-beta-edition-linux-smartphone/">PinePhone</a>
around mid-May and have been living
with it as my only smartphone ever since. In this post, I'd like to discuss a
bit of that experience, the positives and negatives, and some of my hopes for
the future of PinePhones broadly and Mobian specifically.
</p>
{% endblock summary %}
{% block content %}
<p class="blog-paragraph">
Firstly, let's just be honest about what the PinePhone is at the moment. Right
now, the PinePhone is a fully-functional smartphone, meaning it can make
phone calls, receive and send text messages (though not, as of now, MMS),
access maps using GPS (although not directed GPS navigation - yet), and access
the internet via browsers and apps. However, what the PinePhone lacks is a well-developed
app ecosystem such as those of Android or iOS. For example, I have yet to find
a way to access Facebook Messenger from my phone, a communication app that was
previously one of the central pillars of my digital communications. Additionally,
I can't use Snapchat or Instagram or Venmo or CashApp or any of the other apps
that are staples on almost any young person's (and most any older person's) phone
these days. In fact, I would argue that it's better to think of a PinePhone as a tiny Linux
computer that can make phone calls and send text messages and use mobile data.
</p>
<p class="blog-paragraph">
Now, for those familiar with Linux, this might not sound so bad. There's at
least one program for almost anything a computer can do, often many more; that's
a pretty big app ecosystem! Alas, Linux developers are stretched incredibly thin
and there is as-of-yet little support for the kind of adaptive/reactive scaling
needed to make apps usable on a tiny screen like that of the PinePhone. While
Mobian's default shell, phosh, provides `scale-to-fit`, and other shells
provide similar functionality, this just makes the actual elements of the app
GUI smaller. So, for example, if you `scale-to-fit` GNOME Calendars, it will
all fit on the screen, but each day of the month will be miniscule, the
headerbar will be virtually unusable due to size, and so on.
</p>
<p class="blog-paragraph">
Fortunately, this is changing. The recent libadwaita from the GNOME project -
which is functionally GTK 4, a graphical user interface (GUI) toolkit library - includes elements from
libhandy, a GTK 3-friendly GUI library that helps develop reactive apps. Personally,
I've tried to develop with libhandy in the past, and while it's fairly simple
to do using the old-fashioned method of handwriting code to layout one's GUI,
it's much less friendly to the now-preferred GNOME development method of using
XML files to layout an app interface (somewhat like writing a website in HTML
then scripting it with JavaScript). Unfortunately, the GNOME XML format is far
less friendly to handwriting than HTML, and libhandy has to be specially compiled
to work with Glade, the GNOME tool for laying out interfaces, which in turn may
not support libhandy as a first-class citizen depending on version, and so on
and so on. In other words, libhandy was difficult to use due to tooling issues.
As libadwaita displaces GTK 3 and, presumably, libhandy, this should change,
and as it does, apps should be rewritten to be more friendly to mobile usage
by default. Very exciting stuff if you ask me!
</p>
<p class="blog-paragraph">
That's about all the knowledge I have of developing for the PinePhone, so let's
turn to my preferred OS and its shell, that being Mobian and phosh. Mobian itself
(linked above) is just <a href="https://debian.org">Debian</a> with necessary
changes to run on the PinePhone. In fact, the project launched on the PinePhone!
The overall goal of the project is to, first of all, make a mainline Linux distro
that is geared towards the PinePhone. What "mainline" means here is that one can
simply install the vanilla versions of programs - such as the Linux kernel itself -
and they will work without any patches or changes. Secondarily, it would like to
become an official Debian Spin, which means it would be supported by Debian as
a whole. For those unfamiliar with the GNU/Linux world, this is a big deal -
Debian is one of the oldest and most venerable distributions of the operating
system, and it serves as the base for most other major distros, notably Ubuntu
and therefore anything based on Ubuntu. In other words, by becoming part of the
Debian project, Mobian would demonstrate to the world that the PinePhone is a
first-class Linux platform worthy of being developed for, and provide it the
support that implies.
I chose Mobian simply because I love Debian. Further, I prefer to keep my software
as vanilla as possible, something Debian and by extension Mobian both share.
</p>
<p class="blog-paragraph">
Phosh is simply a spinoff of the GNOME Shell geared towards mobile devices. It
was originally developed by <a href="https://puri.sm">Purism</a> for their own
Linux smartphones, but has achieved broader community acceptance in large part
thanks to the PinePhone. As a disclaimer, Purism have demonstrated themselves
tolerant of a variety of bigotry on their social media and communications
platforms, all under the guise of defending "free speech," and therefore I
consciously avoid direct interaction with them or anyone representing them.
Thanks to free software, however, I can benefit from their work without supporting
them. Cool!
</p>
<p class="blog-paragraph">
At this point you might be saying, "That's all very neat and cool, Trees, but
what's the PinePhone <em>actually like?!</em>" And to that I say, "Well, hold on
and I'll tell you!" Frankly, the PinePhone is great. I've annoyed my partner
and others in my life because of its quirks - not having Venmo and Messenger,
for example - but I personally would rather not use those sorts of programs anyway,
what with their obsession with tracking users and selling the data gained. That
said, there are some notable problems about which I've made a point of keeping notes.
</p>
<p class="blog-paragraph">
Before I get too far away from discussing phosh, let me just talk about what
the actual interface is like. When you press the power button to turn on the
phone screen, by default you'll see the time, the date, an indicator of any
data/wifi connections, and a graphic of the battery state, with an arrow and
the instruction to "slide up to unlock" at the bottom. Upon sliding up, you're
greeted with a number pad for your PIN and a simple "unlock" button. From there,
you'll see the app tray, with local search bar and your "favorites" apps shown by their icons in
a top section, and everything else shown as icons and names below it. When I
first booted my PinePhone, I was able to close this and simply see the wallpaper
and headerbar, but this has since been changed. At the top of the logged-in
screen at all times is your headerbar, as is common for the smartphone metaphor,
which shows, from left to right, data connectivity, wifi, date and time, current
keyboard language (if you use more than one), and battery indicator. If you tap
this bar, you will see icons for, from left to right and top to bottom, data,
wifi, bluetooth, battery, screen rotation, notification on/off, the flashlight
(although this only works under Purism's OS), and whether the phone is docked
(that is, connected to a screen and keyboard so as to function as a computer).
Below this are two sliders, the top one for sound and the bottom one for screen
brightness. Now, on to complaints!
</p>
<p class="blog-paragraph">
On the hardware side, there are a few things which might be annoying to most
users. Most glaringly, the actual CPU and chipsets are older - they come from
2015 and were roughly mid-tier even then. Perhaps more painfully, the battery
is pretty small, and kernels earlier than 5.10 have pretty terrible power usage
optimization for the PinePhone. I've heard 5.11 is supposed to change this,
but due to the Debian Bullseye freezes, I've yet to try it myself. The next major
issue - and one which does bother me - is the camera. Now, I'd become habituated
to the quality of Pixel phones, which combine excellent physical cameras (for
smartphones, anyway) with Google AI which optimizes them to be even better. The
PinePhone camera, by contrast, is 5 megapixels, and the Mobian camera app,
Megapixels, requires some C hacking that ultimately passes images to a shell script. This means the
pictures it takes tend to be rather lackluster. Don't get me wrong, they're
sufficient for just snapping a quick pic of an interesting scene, but you probably
won't be doing artistic or professional photography on it, at least not yet.
</p>
<p class="blog-paragraph">
Megapixels brings me to the software problems I've encountered. Megapixels itself
has a habit of freezing up the phone while saving a picture, and sometimes the
saving itself fails. Other times, it crashes or phosh itself. When it does
work, though, it's... Fine. There are no fine-tuning controls yet, settings aren't
enabled, and the GUI doesn't recognize screen orientation. Additionally, if one
has a preferred format for saving their pictures, it's not obvious that
this has to be changed in the actual script - and some formats require
other programs to work properly.
</p>
<p class="blog-paragraph">
On the note of crashes, while writing this,
the podcast app I use, GNOME Podcasts, just crashed phosh, so let's talk
about it a bit. I drive for my job, so I listen to a lot of podcasts, and the
only app I've found in the GNOME ecosystem that has paid attention to smaller
screens is GNOME Podcasts. This would be fine, except for a few things. Firstly,
it's only available (on Mobian so far) as a Flatpak. This means it has higher
on-disk overhead and runtime overhead than something downloaded through the
Debian package manager apt - although updates are nicer because it only downloads
the binary data that has actually changed. The other problem with this is that,
as of now, it doesn't disable suspend, so the phone will go to sleep without some
help to make it see that something's being played. I use <a href="https://src.jayvii.de/Hobby/PinePhoneScripts/src/branch/main/sguard">
Suspend Guard</a>. However, I've noticed that when podcasts are playing, the
phone becomes less responsive - it takes longer to load the login screen, it
takes longer to register my PIN, and sometimes it doesn't work at all or
crashes randomly if I try to login while something is playing. Additionally,
there are odd bugs around phone calls - I usually can't hear the other person
if I receive a call, and sometimes the system doesn't switch back to the
rear speaker after a phone call. I suspect this is a side-effect of the
interaction between Flatpak and Suspend Guard.
</p>
<p class="blog-paragraph">
I mention these two programs together because they are exceptions which should
disappear as more development time goes into the broader PinePhone ecosystem,
but which are exceptionally annoying for the time being. Other than these,
there are really only two complaints I have about the default Mobian software,
both related to the keyboard, Squeekboard. The French Squeekboard layout lacks
guillamettes, the French equivalent of quotation marks. While modern French
people tend to use guillamettes and quotation marks interchangeably, I prefer
the more classic notation, so I find this bothersome. Of course, Squeekboard
layouts can be modified by the user, so I could simply add these to the French
keyboard layout and open a pull request to have them merged into the mainline
app - probably not a bad idea. The other complaint is that the Squeekboard
emoji set is relatively limited, but this is a very minor issue that, again, I
could theoretically resolve myself with just a bit of research and typing.
</p>
<p class="blog-paragraph">
There is one major failure of Mobian and, as far as I know, all PinePhone
operating systems at the moment which must be noted. Namely, there is
little to no accessibility software. This came to my attention when a
blind user on Mastodon mentioned it in a broader thread on the failures of
the FOSS community to take into account the needs of disabled people,
specifically himself, when writing software and developing systems. Indeed,
some of the responses to that thread were so hostile, tone-deaf, or ignorant
that they serve as perfect examples of the stereotype that FOSS developers are, as a
rule, assholes. I care about this for two reasons. First and foremost, I
truly believe in the ideals behind software freedom, which initially and
most fundamentally seeks to ensure that everyone may use any software.
Indeed, the GNU Project came into being to ensure everyone would have
access to the Unix operating system, or at least something very similar
to it. By failing or outright refusing to make the necessary accommodations
for disabled users, these developers are failing to live up to that most
fundamental ideal. Secondly, I will one day - should I live long enough -
lose my sight. I would like for that not to kick me out of the FOSS club,
too. If you are a developer reading this, please take into account all the
challenges your users may face, whether those be vision, hearing, motor
control, developmental, or any other, insofar as you are able. Seek out the
input of users from the broadest spectrum of humanity that you can (within
reason - there's no need to consult laypeople on, say, software used for
quantum physics research, for example). In doing so, you will help live up
to the core, implicit, beautiful ideals which have created so much of the
world's software today.
</p>
<p class="blog-paragraph">
As for the future, I think all of us are looking forward to a PinePhone 2 with
more modern and, ideally, performant hardware. I know I'll gladly upgrade even
if the PinePhone 2 costs significantly more. In the meantime, there is <em>a lot</em>
of optimization to be done on the software front. As I already mentioned, battery
support is improving, as is mainline kernel support; apps are being transitioned
to more friendly GUI toolkits; and there are plenty of things most people expect
from a smartphone which have yet to be implemented for the PinePhone. For example,
just the other day someone asked me about OTP apps. I don't use this technology
and so couldn't point them to a solution, but from what I can tell their usecase
isn't yet supported. The other major thing I'm looking for in terms of PinePhone
development is a *BSD-based OS. While the BSDs tend to lack the kinds of things
smartphones - especially budget-tier smartphones like the PinePhone - need -
namely power optimization and respect for limited hardware - the overall design
of BSDs tends to be more stable and efficient from the start. There are no
duplicate syscalls as in the Linux kernel, for example. Besides, Darwin underlies
iOS and is a fork of FreeBSD, so there's already a demonstrated success story
for a BSD on a smartphone.
</p>
<p class="blog-paragraph">
I can't really think of anything else to say about the PinePhone at the moment,
so to summarize, the PinePhone, specifically running Mobian, is a cheap, low-powered
Linux smartphone that can do pretty much all the basic things a phone is supposed
to do while existing in the broader Linux ecosystem. If you're looking for a
new phone and aren't deeply bought into the Google or Apple ecosystems - and
don't mind waiting for pre-orders to go to production and then ship, which may
take several months - I'd say go ahead and get one. The regular package is only
$150 US before shipping, so for a lot of people this wouldn't be a ridiculous
investment even as a secondary phone. And if you're a developer, you'll be able
to participate in the birth of a new smartphone ecosystem, helping shepherd it
into the mainstream. On the other hand, if you regularly use your phone for
photography or use a lot of proprietary, smartphone-specific apps, you might
want to give it a pass, at least for now. While many apps also have websites,
the fact that the phone is the size of a phone and its browsers report themselves
as Android or iOS means it's very difficult to use most of them from the phone.
If you want to see if there are compatible apps for your usecase, check out
<a href="https://linmobapps.frama.io">this list</a>.
</p>
<p class="blog-paragraph">
Well, thanks for stopping by Trees' Street; I hope you've found something helpful
here. Until next time!
</p>
{% endblock content %}

106
templates/blog/2021-05-04.html

@ -0,0 +1,106 @@
{% extends "blog-post.html" %}
{% block title %}What a Hy!{% endblock title %}
{% block date %}2021-05-04{% endblock date %}
{% block summary %}
<p>I rewrote my website. In Lisp! In two hours!! Using Flask!!! WTF????</p>
{% endblock summary %}
{% block content %}
<p class="blog-paragraph">
Recently, I've been listening to a lot of <a href="https://fossandcrafts.org/">
FOSS and Crafts</a>, a podcast about free software and broader free culture as well
as a variety of other nerdy topics hosted by Morgan Lemmer-Webber, an art historian
studying Roman textiles, and her spouse Chris, who you may know from their work on
the <a href="https://wikipedia.org/wiki/ActivityPub">ActivityPub</a> standard and the
<a href="https://spritelyproject.org">Spritely project</a>. This latter (or, rather, a
talk on it where Chris mentioned using <a href="https://racket-lang.org">Racket</a>)
inspired me to try to pick up Racket, and
I decided to start by working my way through <a href="https://htdp.org">How to Design
Programs</a> second edition (2htdp). Long story short, the
<a href="https://wikipedia.org/wiki/Lisp_(programming_language)">Lisp</a>-y language
used for teaching in that book led
me to really fall in love with Lisps (even though, disclaimer! I'm still very much new
to them). While working my way from Wikipedia article to Wikipedia article on the
various Lisp families and implementations, I came across
<a href="https://docs.hylang.org">Hy</a>, a Lisp which runs on the
<a href="https://python.org">Python</a> interpreter.
Seeing that it could use Python modules just like normal, and given my newfound interest
in Lisps, I decided to rewrite my website in it. And, being the FOSS-y advocate I am, I
figured I should write about the experience. So here's that write-up!
</p>
<p class="blog-paragraph">
Firstly, let's discuss Hy a bit because I think it's pretty kick-ass. Basically, the
language core parses traditional Lisp
<a href="https://wikipedia.org/wiki/S-expression">S-Expressions</a> and translates them
into a Python Abstract Syntax Tree (AST). This AST is then handed off to the Python
interpreter which compiles it into bytecode (files in the <code>__pycache__</code>
directory). This code can then be called from regular Python as long as the Hy module
has been imported.
</p>
<p class="blog-paragraph">
It would be easier to show than explain, so here's a function written in Hy which
produces a Fibonacci sequence:
<pre><code>
<!---->(defn fib [l n]
<!----> """
<!----> Produce a list of Fibonacci numbers
<!----> using the list l as the preceding numbers
<!----> and n as the limit
<!----> """
<!----> (if (&lt; (len l) n)
<!----> (fib (+ l
<!----> [(+ (get l -2) (get l -1))])
<!----> n)
<!----> l))
</code></pre>
And here's how you would use that in regular Python, assuming it's in <code>fib.hy</code>:
<pre><code>
<!---->from fib import fib
<!---->print(fib([1, 1], 8))
</code></pre>
Super simple, right? For good measure, here's the above code in Hy:
<pre><code>
<!---->(import [fib [fib]])
<!---->(print (fib [1 1] 8))
</code></pre>
</p>
<p class="blog-paragraph">
So with that little example in mind, it shouldn't be too surprising that one can use
Hy to write a <a href="https://flask.palletsprojects.com">Flask</a> app like this
website. In fact, the only requirement as far as Flask itself goes is to have a Python
"shim". Here's mine:
<pre><code>
<!---->import hy
<!---->from app import *
</code></pre>
In this case, "app" refers to a file called <code>app.hy</code>. I just stuck the above
code in <code>shim.py</code> and pointed the <code>FLASK_APP</code> environment
variable at it. Everything else is the same from the Flask perspective.
</p>
<p class="blog-paragraph">
The actual code translation was pretty simple, too. Besides switching to the Hy syntax
and adjusting some value testing to take advantage of Hy built-ins like <code>none?</code>,
I didn't have to change anything. And even the syntax translation was quite simple
since, firstly, this website is extremely simple (if it weren't for some features of
this blog which are as-yet unimplemented, I could just make it a static site), and,
secondly, I already had tried to use a more functional style of coding I'd learned
from 2htdp. The only problem I ran into was a strange parsing bug that I discovered
was caused by a typo in one of my route decorators. Rather than setting the homepage
URL extension to "/", I set it to "index", which was incorrect no matter the language.
</p>
<p class="blog-paragraph">
Overall, my limited experience with Hy has been wonderful, and I'm very excited to use
it more in the future. Given my discovery of my love for s-expression syntax, I'll be
reaching for Hy anytime I previously may have reached for Python. And, Hy is quite
mature; the version I'm using right now is 1.0a1 - or in English, the alpha release
of 1.0. Hopefully in the next couple months the 20-ish outstanding issues will be
cleared up and this delicious Lisp will be a full-fledged release language. I for one
am looking forward to it. If you're looking for a Lisp to pick up with a great standard
library, I would highly suggest giving Hy a look. It can even be run on
<a href="https://www.pypy.org">PyPy</a>!
</p>
<p class="blog-paragraph">
Well, that's all I've got for now. Thanks for stopping by, and as I have a habit of
saying, have a good one!
</p>
{% endblock content %}

95
templates/blog/LICENSE.md

@ -0,0 +1,95 @@
Creative Commons Attribution-ShareAlike 4.0 International Public License
By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
Section 1 – Definitions.
Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.
Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.
Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
Licensor means the individual(s) or entity(ies) granting rights under this Public License.
Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
Section 2 – Scope.
License grant.
Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
reproduce and Share the Licensed Material, in whole or in part; and
produce, reproduce, and Share Adapted Material.
Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
Term. The term of this Public License is specified in Section 6(a).
Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
Downstream recipients.
Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
Other rights.
Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
Patent and trademark rights are not licensed under this Public License.
To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
Section 3 – License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the following conditions.
Attribution.
If You Share the Licensed Material (including in modified form), You must:
retain the following if it is supplied by the Licensor with the Licensed Material:
identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
a copyright notice;
a notice that refers to this Public License;
a notice that refers to the disclaimer of warranties;
a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
ShareAlike.
In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.
You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
Section 4 – Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
Section 5 – Disclaimer of Warranties and Limitation of Liability.
Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
Section 6 – Term and Termination.
This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
Section 7 – Other Terms and Conditions.
The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
Section 8 – Interpretation.
For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.

9
templates/index.html

@ -0,0 +1,9 @@
{% extends "layout.html" %}
{% block main %}
<div class="about-text">
<p>
Hello and welcome to Trees' Street! Here's where I put the stuff I do. Enjoy!
</p>
</div>
{% endblock %}

29
templates/layout.html

@ -0,0 +1,29 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<link href="{{ url_for('static', filename='styles.css') }}" rel="stylesheet">
<link href="{{ url_for('static', filename='favicon.ico') }}" rel="shortcut icon">
<title>Trees' Street</title>
</head>
<body>
<header>
<h1>You find yourself on a winding path deep in the forest...</h1>
<nav>
<a class="nav-item" href="{{ url_for('index') }}">Home</a>
<a class="nav-item" href="{{ url_for('blog') }}">Blog</a>
<a class="nav-item" href="https://github.com/Marie-Joseph">Projects</a>
</nav>
</header>
<main>
{% block main %}{% endblock %}
</main>
<footer><small>
All code (Hy, HTML, Jinja, CSS) for this website is licensed under the <a href="https://www.gnu.org/licenses/gpl-3.0-standalone.html">GPLv3</a>
and available <a href="https://github.com/Marie-Joseph/hy-website">here</a>.<br />
All blog posts (the raw text) are licensed <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">CC-BY-SA 4.0</a>.
</small></footer>
</body>
</html>

13
templates/projects.html

@ -0,0 +1,13 @@
{% extends "layout.html" %}
{% block main %}
<div class="projects">
<p>
Here are some assorted projects I feel like sharing. This will evolve as I do,
so check back now and then!
</p>
<ul>
<li>TODO</li>
</ul>
</div>
{% endblock %}