diff options
47 files changed, 1560 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..9a5adec --- /dev/null +++ b/.gitignore @@ -0,0 +1,3 @@ +output/ +blog/*upphtml + @@ -0,0 +1,186 @@ +GNU AFFERO GENERAL PUBLIC LICENSE + +Version 3, 19 November 2007 + +Copyright © 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 diff --git a/COPYRIGHT b/COPYRIGHT new file mode 100644 index 0000000..e556b4f --- /dev/null +++ b/COPYRIGHT @@ -0,0 +1,34 @@ +Copyright (C) 2025-2026 yctct + +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 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/>. + +--------------------------------------------------------------------------- + +ISC License + +mkws Copyright (c) 2021, Adrian Emil Grigore <adrian.emil.grigore@gmail.com> +mkws-plus-blog Copyright (c) 2025, kalviter + +Permission to use, copy, modify, and/or distribute this software for any +purpose with or without fee is hereby granted, provided that the above +copyright notice and this permission notice appear in all copies. + +THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + @@ -0,0 +1,20 @@ +This repository contains the source code of https://copyleftculture.com + +Usage +----- + +- clone this repository +- run ./build.sh to build the site + +Limitations +---------- + +Newly created .md files must be converted to HTML using markdown.pl, for +example + +Questions +--------- + +This README is pretty sparse. + +Feel free to email me if you are tyring to build this site. @@ -0,0 +1,11 @@ +# About this site + +<div class="main"> +<p> This website is hosted on a machine running GNU/Linux Trisquel along with Nginx, on a shared server.</p> + +<p> This work is licensed under <a href='https://creativecommons.org/licenses/by-sa/4.0/'>CC BY-SA 4.0</a><img src='https://mirrors.creativecommons.org/presskit/icons/cc.svg' alt='' style='max-width: 1em;max-height:1em;margin-left: .2em;'><img src='https://mirrors.creativecommons.org/presskit/icons/by.svg' alt='' style='max-width: 1em;max-height:1em;margin-left: .2em;'><img src='https://mirrors.creativecommons.org/presskit/icons/sa.svg' alt='' style='max-width: 1em;max-height:1em;margin-left: .2em;'></p> + +<p> This site is made with <a href='https://mkws.sh/'>mkws</a> / CSS from tilde.club</p> + +<p> Data Collection Policy: this website uses no cookies, no analytic tools, no affiliate links, no JavaScript and no trackers. Logs are kept for 7 days. </p> +</div> diff --git a/about.upphtml b/about.upphtml new file mode 100644 index 0000000..d6dadc7 --- /dev/null +++ b/about.upphtml @@ -0,0 +1,3 @@ +#! +pandoc about +#! Binary files differdiff --git a/bin/mkws b/bin/mkws new file mode 100755 index 0000000..99494c7 --- /dev/null +++ b/bin/mkws @@ -0,0 +1,78 @@ +#!/bin/sh +PATH=./bin:$PATH + +usage() { + >&2 printf "usage: %s url [path]\\n" "$(basename "$0")" + exit 1 +} + +test $# -lt 1 && usage + +export SRC="${2:-.}" +export SHARE="${MKWSTHEMEDIR:-${SRC}/share}" +export LANG=en_GB.UTF-8 + + +if ! test -f "${SRC}"/index.upphtml +then + >&2 printf "no index.upphtml file found\\n" + exit 1 +fi + +for t in "${SRC}"/*.upphtml +do + printf "Making $(basename "${t%.upphtml}".html)\n" + pp "${SHARE}"/l.upphtml "${t}" "$1" > \ + "$(basename "${t%.upphtml}".html)" +done + +printf "Clearing blog index\n" +cp "${SRC}"/blog/preamble.txt "${SRC}"/blog/index.prehtml +printf "<ul>\n" >> "${SRC}"/blog/index.prehtml +for t in $(ls "${SRC}"/blog/*.upphtml | sort -r) +do + printf "Making blog post: $(basename "${t%.upphtml}".html)\n" + pp "${SHARE}"/l.upphtml "${t}" "$1" > \ + blog/"$(basename "${t%.upphtml}".html)" + linkname=`sed -n 's/.*<h1>\(.*\)<\/h1>.*/\1/ip;T;q' "${SRC}"/blog/"$(basename "${t%.upphtml}".html)"` + #desc=`sed -n 's/.*<h2>\(.*\)<\/h2>.*/\1/ip;T;q' "${SRC}"/blog/"$(basename "${t%.upphtml}".html)"` + #printf "<li><a href=/blog/$(basename "${t%.upphtml}".html)>${linkname} - ${desc}</a></li>\n" >> "${SRC}"/blog/index.prehtml + printf "<li><a href=/blog/$(basename "${t%.upphtml}".html)>${linkname}</a></li>\n<br>\n" >> "${SRC}"/blog/index.prehtml +done +printf "Remaking blog index\n" +printf "</ul>\n" >> "${SRC}"/blog/index.prehtml +printf "</main>\n" >> "${SRC}"/blog/index.prehtml +pp "${SHARE}"/l.upphtml "${SRC}"/blog/index.prehtml "$1" > \ + "${SRC}"/blog/index.html +# cleanup +rm "${SRC}"/blog/index.prehtml + +printf "Making sitemap.xml\n" +pp "${SHARE}"/sitemap.uppxml "$1" > sitemap.xml + +printf "Updating RSS feed\n" +pp "${SHARE}"/feed.uppxml "$1" > feed.xml + +if [ ! -d "${SRC}"/output ]; +then + mkdir "${SRC}"/output + mkdir "${SRC}"/output/blog + mkdir "${SRC}"/output/assets +fi + +printf "Lazy-fying images\n" +find . -name "*.html" | xargs sed -i -e 's/<img/<img loading="lazy"/g' + +printf "Overwriting old site folder\n" +mv "${SRC}"/blog/*.html "${SRC}"/output/blog +mv "${SRC}"/*.html "${SRC}"/output +mv "${SRC}"/sitemap.xml "${SRC}"/output +mv "${SRC}"/feed.xml "${SRC}"/output +if [ -d "${SRC}"/assets ]; +then + cp -r "${SRC}"/assets/* "${SRC}"/output/assets +fi +if [ -e "${SRC}"/robots.txt ]; +then + cp "${SRC}"/robots.txt "${SRC}"/output +fi Binary files differdiff --git a/blog/md/24.md b/blog/md/24.md new file mode 100644 index 0000000..a6277a1 --- /dev/null +++ b/blog/md/24.md @@ -0,0 +1,43 @@ +# To choose an instance, is to choose who we trust | March 2025 + +Most of us fail to imagine that businesses will be willing to pay for something that is freely distributed. + +Yesterday, I had a chat with Vincent L., developer, owner-member of the cooperative 24eme[1], a software development agency working with freely distributed software only. + +A few points from our conversation: + +- using freely distributed software rebalances power between clients and software providers (to the advantage of the client). +- if 24eme shuts down, or if clients are no longer satisfied with 24eme, clients can hire other developers to carry on maintaining software 24eme has used, or clients can internalise the work by hiring developer. +- Vincent tells me it is a good thing when their clients hire developers to work on software 24eme has developed; it pushes the developers of 24eme to be more transparent, more diligent in documenting what they do, not to take shortcuts - so other developers can join in to maintain - and improve software 24eme develops. Having external developers as contributors is a remedy against regression; it helps 24eme’s developers progress. +- using freely distributed software also rebalances power between employees and employers; developers can quit and carry on working on the software they’ve gained expertise on and developed. +- other organisations in the industry can use software 24eme has developed for their clients; these new organisations might have new needs, pay for new features, then all users can benefits from improvements. +- Vincent tells me that some organisations are afraid to adopt freely distributed software; they are afraid that their competitors will adopt the same software; conversely, it is easier for organisations to adopt freely distributed software when software is not the core of their value proposition. + +24eme maintains the software signaturePDF[2] + +- friends of 24eme, and others, maintain instances of signaturePDF. +- a number of other organisations use signaturePDF; I don’t remember how many. +- an organisation, Logilab, adopted signaturePDF and has paid 24eme for the development of additional features. + +On the organisation 24eme: + +- 24eme is run and managed by developers. +- there is no project manager. +- clients communicate directly with developers. +- there is no single point of contact. +- all developers must be apt to respond to clients' enquiries. +- 24eme is a registered cooperative. +- transparency is key +- all administrative documents, including bank account statements, are public[3]; Vincent tells me it is key for trust, within the organisation, and with clients. Clients can see what they pay for; and what others pay for. +- When it comes to paying for the development of freely distributed software, clients, if they wanted to, can see which commit they paid for. + +Quote I liked: + +> [To choose an instance], is to choose who we trust.[4] + +PS: an instance is a server running a freely distributed software. + +[1] https://www.24eme.fr/ +[2] https://gh.owo.si/24eme/signaturepdf +[3] https://github.com/24eme/administratif/blob/master/README.md +[4] “C'est choisir à qui on fait confiance” diff --git a/blog/md/add-multiple-email-accounts-nextcloud.md b/blog/md/add-multiple-email-accounts-nextcloud.md new file mode 100644 index 0000000..dffcab6 --- /dev/null +++ b/blog/md/add-multiple-email-accounts-nextcloud.md @@ -0,0 +1,12 @@ +# Add multiple email accounts to Nexcloud’s mail app + +You can add multiple email accounts to the mail applications of your Nextcloud instance. + +To do so: + +- log in into your Nextcloud instance +- click on 'Mail' in the navigation bar of Nextcloud +- click on 'Mail settings' in the bottom left of the screen +- 'Mail Settings' should pop, set on the tab 'General' +- under 'Account settings', click '+ Add mail account' +- follow the instructions to [connect your mailboxes](https://copyleftculture.com/blog/set-up-your-email-application.html) diff --git a/blog/md/add-password-recovery-email-address.md b/blog/md/add-password-recovery-email-address.md new file mode 100644 index 0000000..f093f90 --- /dev/null +++ b/blog/md/add-password-recovery-email-address.md @@ -0,0 +1,13 @@ +# Mailcow: Add a recovery email address so users can reset their passwords + +- you need the admin credentials of the email system +- log into https://admin.galae.net/domainadmin/mailbox with admin credentials +- click on the tab 'Mailboxes' +- the URL should be https://admin.galae.net/domainadmin/mailbox +- find the email address for which you want to add a recovery email address +- on the row of that email address, click '+ Edit' +- you should be on the page https://admin.galae.net/edit/mailbox/username%40domain.tld +- on the row 'Password recovery email', add the recovery email address +- click 'Save changes' + + diff --git a/blog/md/add-user-to-nextcloud.md b/blog/md/add-user-to-nextcloud.md new file mode 100644 index 0000000..9d78cd3 --- /dev/null +++ b/blog/md/add-user-to-nextcloud.md @@ -0,0 +1,6 @@ +# Add a new user to your Nextcloud instance + +- log in into your Nextcloud instance +- click on your initial, in the top-right corner of the screen +- click on 'Accounts’ +- click on '+ New Account' diff --git a/blog/md/agpl.md b/blog/md/agpl.md new file mode 100644 index 0000000..6f628c3 --- /dev/null +++ b/blog/md/agpl.md @@ -0,0 +1,33 @@ +# What's the loophole for SaaS with GPL? | March 2026 + +In a conversation, the topic of licensing a software that can be running as a service came up. + +While GPL is a powerful license when it comes to making sure that the source code will remain freely distributed, it has limitations. + +GPL isn't enough to make sure that the source code will remain freely distributed. + +AGPL addresses that loophole. + +A blog post from maintainer.s who chose AGPL, sums up why: + +> What’s the issue with the GPL license? +> +> The problem with the GPL license is that it didn’t imagine cloud +> computing and how the cloud would come to dominate the world of +> software. Cloud companies download open source software, modify +> it, run it on their servers and resell it as a service. +> +> They’re not actually “distributing” the software because users +> never have the software installed on their computers. It means +> that cloud corporations have no obligations to contribute their +> modifications back to the open source community. + + AGPL is the answer to this. + +> What's the GNU AGPLv3 license? +> +> “If you make a derivative work of this, and distribute it or run it as a +> service on a server to others then you have to provide the source code +> under this license” + +Full post: https://plausible.io/blog/open-source-licenses diff --git a/blog/md/create-email-addresses.md b/blog/md/create-email-addresses.md new file mode 100644 index 0000000..1f55e06 --- /dev/null +++ b/blog/md/create-email-addresses.md @@ -0,0 +1,17 @@ +# Mailcow: How to create new email addresses + +- you need the admin credentials of the email system to add an email address +- log into https://admin.galae.net/domainadmin/mailbox with the admin credentials +- click on the tab 'Mailboxes' +- the URL should be https://admin.galae.net/domainadmin/mailbox +- click on the green button '+Add mailbox' +- you should see a pop up titled 'Add mailbox' +- on the row 'Username (left part of an email address)', add the username, e.g. if you want to create bob@example.com write 'bob' +- on the row 'Domain', select the domain name e.g. example.com +- on the row 'Password' click 'generate' +- on the row 'Quota' type '1024'; that is the size of the mailbox, for storage +- scroll to the bottom of the screen +- tick the box 'Force password update at next login' +- click 'Add' +- you should see the email address you created in the list https://admin.galae.net/domainadmin/mailbox +- send the password and email address to the user; the user will be prompted to change the password at first log in. diff --git a/blog/md/dinum-linux.md b/blog/md/dinum-linux.md new file mode 100644 index 0000000..f86a4bc --- /dev/null +++ b/blog/md/dinum-linux.md @@ -0,0 +1,7 @@ +# France's information technology directorate announced switching to Linux + +On April 8th 2026, the *direction interministérielle du numérique (DINUM)*, France's information technology directorate announced they will switch to Linux. + +In the same press release, the DINUM also mentioned that the 80,000 agents of France's Social Security will switch to Tchap, Visio and FranceTransfert, 3 open source software that governmental agencies maintain. + +Source: https://www.numerique.gouv.fr/sinformer/espace-presse/souverainete-numerique-reduction-dependances-extra-europeennes/ diff --git a/blog/md/discord-id.md b/blog/md/discord-id.md new file mode 100644 index 0000000..63863c7 --- /dev/null +++ b/blog/md/discord-id.md @@ -0,0 +1,5 @@ +# Discord seeks to implement user ID check | February 2026 + +Discord Inc. will ask some user to provide their ID or undergo a scan of their face to carry on using Discord. + +https://web.archive.org/web/20260301033743if_/https://discord.com/press-releases/discord-launches-teen-by-default-settings-globally diff --git a/blog/md/discord-loves-open-source.md b/blog/md/discord-loves-open-source.md new file mode 100644 index 0000000..db82384 --- /dev/null +++ b/blog/md/discord-loves-open-source.md @@ -0,0 +1,18 @@ +# Discord "loves Open Source", but isn't | 02nd February 2025 + +Someone asked me whether Discord is freely distributed software; indeed Discord mentions "open source" on their website; they have a page "Discord loves open source"[1] where open source projects which use Discord are listed, and Discord nudge users to join "servers", as if those servers were instances (they aren't). + +Discord isn't open source. It's proprietary (Wikipedia is a reasonable source to check the license of a software). + +Discord uses the word "server" but that does not mean instance. A "server", in Discord' jargon is just a group chat. +All the action takes place on Discord's servers. +All the users remain in Discord's walled-garden. + +One of the checks you can do, to understand whether a software is freely distributed is to check whether one can run an instance of that software. +That's the case with Mastodon, for example. +You can run your own Mastodon instance, or join the instance of someone else. + +Freely distributed alternatives to Discord are: Matrix along with the client Element which support audio, maybe Tox protocol for chatting and voice, Mumble for low-latency voice (only); some people mentioned Mattermost on the web, but based on the feedback I got from some people managing instances of Mattermost, Mattermost is making more and more features proprietary. +For chat only, there is also Gitter and IRC. + +[1] https://web.archive.org/web/20250201134938if_/https://discord.com/open-source diff --git a/blog/md/first-apps-nextcloud.md b/blog/md/first-apps-nextcloud.md new file mode 100644 index 0000000..104b869 --- /dev/null +++ b/blog/md/first-apps-nextcloud.md @@ -0,0 +1,9 @@ +# Apps to install on your newly set up Nextcloud instance + +- Workspace, so you can create folders "workspace" for each specific teams +- Contacts, so you can synchronise and share contacts across teams +- Calendar, so you can synchronise and share calendars across teams +- Appointments, so you can share a public link with calendar slots people can book (a la Calendly) +- Deck, a kaban application on Nextcloud +- Forms, to create surveys, forms via Nextcloud +- Mail, to set up your mailboxes on your Nextcloud instance diff --git a/blog/md/le-bureau.md b/blog/md/le-bureau.md new file mode 100644 index 0000000..386dacf --- /dev/null +++ b/blog/md/le-bureau.md @@ -0,0 +1,33 @@ +# 'Le Bureau': a cooperative to register domain names | 25th April 2025 + +'Le Bureau' is a cooperative that acts as an intermediary for people to buy domain names; it's not yet a *domain registrar*: an organisation that can register a domain name on the behalf of a registrant (you) with a registry. + +Examples of registrars: GoDaddy, Namecheap, or Gandi. + +Examples of registries: DENIC in Germany, Nominet in the United Kingdom + +In their FAQ, Le Bureau explains that the aim is for Le Bureau to become a registrar. + +From their FAQ: + +> Actuellement, LeBureau.coop agit en tant que revendeur de noms de domaine, le temps de développer son offre. L'objectif à terme est de devenir un bureau d'enregistrement et de traiter directement avec les registres. + +> At the moment, LeBureau.coop acts as a reseller of domain names [...]. The long-term aim is for Le Bureau to become a registrar so it can deal directly with registries. + +*Why do I think what Le Bureau does is interesting?* + +Most registrars are for-profit businesses or publicly listed companies; meaning that they cater to the interests of owners or investors. + +Some of us might have seen registrars change hands, or might have experienced a decline in the quality of customer service over time, or erratic price increase, like when Gandi got acquired a few years ago (for the second time). + +Le Bureau is a cooperative, not a for-profit, neither a non-profit; meaning that users can buy shares of the cooperative to become voting members (*sociétaires*). + +There are no investors; the cooperative cannot be sold or acquired. + +*Sociétaires* govern the cooperative, and once Le Bureau becomes a registrar of its own, users will govern the entity which registers and hold their domain names. + +More information at https://lebureau.coop (in French). + +Sources: +https://www.icann.org/resources/pages/what-2013-05-03-en +https://www.icann.org/resources/pages/registries/registries-en diff --git a/blog/md/libreoffice-crdt.md b/blog/md/libreoffice-crdt.md new file mode 100644 index 0000000..08c9b40 --- /dev/null +++ b/blog/md/libreoffice-crdt.md @@ -0,0 +1,17 @@ +# Distributed real-time collaboration for LibreOffice Writer | 27th February 2025 + +During FOSDEM 2025, a conference about freely distributed software, Thorsten +Behrens, a LibreOffice hacker, presented: + +> Distributed real-time collaboration for LibreOffice Writer - a first prototype. + +What's that? + +> This is a mode where multiple people, each with their own local copy of LibreOffice Writer running on their own machine, can all work together simultaneously on the same collaborative document. + +In essence, it's like Google Doc, but you don't need a third-party server; you don't need to work in the browser; you don't need to be online: + +> It's the same sort of functionality that you get from Google Docs. [...] +> The big difference is that such tools [Google Doc] run in a browser, so you need to be online. What makes the CRDT implementation different is that this is a local app, working on a local file, but using a network copy to keep changes in sync. The idea is to free you from keeping your apps and data on someone else's computer, without losing the handy collaborative features that web apps bring. + +Source: https://www.theregister.com/2025/02/13/libreoffice_wasm_zetaoffice/ diff --git a/blog/md/microsoft-wireguard-veracrypt.md b/blog/md/microsoft-wireguard-veracrypt.md new file mode 100644 index 0000000..185a4e9 --- /dev/null +++ b/blog/md/microsoft-wireguard-veracrypt.md @@ -0,0 +1,52 @@ +# Microsoft temporarily suspended the accounts of VeraCrypt and WireGuard + +*April 19th, 2026* + +Both, the lead maintainers of VeraCrypt and Wireguard, wrote that the accounts they use to sign the releases of drivers had been terminated or suspended. + +After some media coverage both accounts were reinstated. + +The accounts of other security software was also suspended or terminated. + +-- + +This is the message Mounir Idrassi, the lead developer of VeraCrypt, posted on the forum where users discuss VeraCrypt: + +> Hi everyone, +> +> I want to share an update following my absence over the past few months. +> +> I have encountered some challenges but the most serious one is that Microsoft terminated the account I have used for years to sign Windows drivers and the bootloader. You can see below a screenshot of the message shown when I tried to sign in. +> +> Microsoft did not send me any emails or prior warnings. I have received no explanation for the termination and their message indicates that no appeal is possible. +> +> I have tried to contact Microsoft through various channels but I have only received automated replies and bots. I was unable to reach a human. +> +> This termination impacts my work beyond VeraCrypt and has consequences for my daily job. +> +> Currently I'm out of options. +> +> Regarding VeraCrypt, I cannot publish Windows updates. Linux and macOS updates can still be done but Windows is the platform used by the majority of users and so the inability to deliver Windows releases is a major blow to the project. +> +> I'm open to proposals and help. [1] + +And a couple of messages from the lead maintainer of WireGuard: + +> This is the same problem I'm currently facing with WireGuard. No warning at all, no notification. One day I sign in to publish an update, and yikes, account suspended. Currently undergoing some sort of 60 days appeals process, but who knows. That's kind of crazy: what if there were some critical RCE in WireGuard, being exploited in the wild, and I needed to update users immediately? (That's just hypothetical; don't freak out!) In that case, Microsoft would have my hands entirely tied. +> +> If anybody within Microsoft is able to do something, please contact me -- jason at zx2c4 dot com. [2] + +And: + +> WireGuard has some big updates ready to go on Windows, our first on the platform in nearly 4 years. We've done some nice modernizations and improvements, fixed bugs, added features, updated the toolchain, and more. But our release is currently blocked by @Microsoft. +> +> The recent thread on Hacker News encouraged me to write this up, rather than just grumbling to myself privately about it as I have the last two weeks. +> +> I logged in to get the WireGuardNT driver signed -- a necessary step for driver authors -- and was greeted by this vague message that the account has been suspended. Looking further into it, it seems like they instituted an identity verification policy, didn't notify me about it, and then I guess they suspended accounts who didn't do the verification. So of course I did the ID card verification immediately, but now an appeal is necessary. The appeals process requires filing a support ticket, but filing a support ticket requires a non-suspended account... Catch-22, eventually resolved by filing one through Azure and getting it rerouted to the right department. That was two weeks ago. Now they've told me there's a 60 day appeal review period. Wish us luck! [3] +> +> [...] + +[1] https://web.archive.org/web/20260410202929/https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/ +[2] https://web.archive.org/web/20260409082249/https://news.ycombinator.com/item?id=47686549 +[3] https://xcancel.com/EdgeSecurity/status/2041872931576299888 + diff --git a/blog/md/set-up-new-domain-name-with-galae.md b/blog/md/set-up-new-domain-name-with-galae.md new file mode 100644 index 0000000..976f5ff --- /dev/null +++ b/blog/md/set-up-new-domain-name-with-galae.md @@ -0,0 +1,17 @@ +# How to set up a new domain name to create new email addresses + +- ask us to add the new domain to the interface +- go to https://galae.net +- scroll down to the footer +- click on 'generate DNS' +- enter your domain name without https:// +- go to [https://admin.galae.net/domainadmin](https://admin.galae.net/domainadmin/mailbox) +- log in with your admin credentials +- click ‘Edit’ on the domain name (after Galae’s support added it) +- scroll down +- copy the DKIM key +- go back to the config generator for DNS +- click generate +- paste the DKIM key on the DNS generator +- go to the DNS management screen of the domain name +- paste the DNS configuration in the DNS zone of the domain name diff --git a/blog/md/set-up-your-email-application.md b/blog/md/set-up-your-email-application.md new file mode 100644 index 0000000..6aa9afb --- /dev/null +++ b/blog/md/set-up-your-email-application.md @@ -0,0 +1,30 @@ +# Set up your own email applications on laptop or mobile with your work email address + +For Apple users (Macbook, iPhone, iPad), to set up the Mail application: + +- open Safari +- copy/paste this URL: <code>https://mail.galae.net/index.php?mobileconfig</code> in the navigation bar +- follow the instructions. + +For other applications, follow the instructions as per the interface of the application you'd like to use. + +Once you've found where to add a new email account, you should find the fields where you can type the following information: + +## OUTGOING SERVER + +- protocol: IMAP +- host: <code>mail.galae.net</code> +- port: 993 +- connexion/security: SSL/TLS +- authentification: normal +- username: type your email address + +## INCOMING SERVER + +- host: <code>mail.galae.net</code> +- port: 465 +- connexion/security: SSL/TLS +- authentification: normal +- username: type your email address + +Once you have set up the above you should be able to synchronise your mailbox with your preferred email application on desktop or mobile. diff --git a/blog/md/tree.md b/blog/md/tree.md new file mode 100644 index 0000000..a8b5cd8 --- /dev/null +++ b/blog/md/tree.md @@ -0,0 +1,65 @@ +# A decision tree to help your organisation adopt open source software without the hassle of managing a server | 12th March 2025 + +This is a follow up post from: + +> [Does using open source software means that I have to maintain servers myself?](https://agency.yctct.com/blog/using-open-source.html) + +In that previous post we saw that you don't necessarily need to host freely distributed and open source software yourself for your organisation to use freely distributed software. + +But, if freely distributed software need to be install or run somewhere then, + +- Where shall software run then? +- or, which server shall you use? + +This is a decision tree to help you figure how you can use freely distributed software. + +Before you use software on third-party server, you should see if you can run it locally. +So the first question of this decision tree is: + +## 1. Can I use this software locally? + +List of software of you can use locally: + +- LibreOffice +- Pluma +- Abrowser +- git +- *etc* + +Yes -> great, go on and install that software on your computer. + +No -> next question. + +## 2. Would a peer-to-peer software do the job? + +List of peer-to-peer software: + +- Tox +- Syncthing +- *etc* + +Yes -> great, go on and install that software on your computer. + +No -> next question. + +## 3. Is an organisation running an instance I can use? + +List of organisations running instances of freely distributed +software, for example: + +- Ghost: blog, (paid) newsletter +- Disroot: jitsi, Matrix, NextCloud etc +- Ouvaton: Sympa, Website, etc +- Autistici: website/blog +- *etc* + +Yes -> great, go on sign up/create an account on that instance. + +No -> next question. + +## 4. Can I find an organisation that would run that instance for me? + +List of organisations that can run a standalone instances of +freely distributed software for you: + +- Hostsharing e.G. or Pâquerette, for example diff --git a/blog/md/user-case-mmm.md b/blog/md/user-case-mmm.md new file mode 100644 index 0000000..7cb0cc8 --- /dev/null +++ b/blog/md/user-case-mmm.md @@ -0,0 +1,49 @@ +# An IT set up for a startup/SME: Nextcloud, Mattermost, Mailcow and more + +I had a client who wanted to avoid vendor lock-in. + +They wanted: + +- Mailboxes under 7 different domain names +- an alternative to Google Drive, docs, sheets +- an alternative to Slack +- an alternative to Calendly +- an alternative to Airtable +- an alternative to Zoom +- an ERP for HR and accounting +- a password management system for the whole organisation + +Solutions: + +- Mailcow +- Nextcloud +- Mattermost (MM) +- Nextcloud's applications Calendar and Appointments +- Grist +- Big Blue Button +- ERPNext +- Vaultwarden + +We customized Nextcloud as such: + +- Shared folders per team/department with 'Workspace' +- Set up collaborative documents: spreadsheet, slides/decks and documents with Collabora +- Activated Nextcloud's application Forms to run surveys +- Activated Nextcloud's Calendar and Appointments to have a booking system (alternative to Calendly) +- Connected MM and Nextcloud to share files from MM to Nextcloud +- Activated Nextcloud's application Deck, a Kaban system within Nextcloud + +For mailboxes, we use an instance of Mailcow which includes the ability for them to: + +- manage the mailboxes of multiple domain names +- create unlimited email addresses +- create common email addresses e.g. <code>contact@example.com</code> +- create wildcard email addresses e.g. <code>client-\*@example.com</code> + +Next steps are: + +- set up LibreSign to their Nextcloud instance to sign documents +- set up an instance of Grist to replace Airtable +- set up Big Blue Button and link that to their Nextcloud instance as well as a Mattermost to start calls from within either apps +- set up ERPNext for HR and accounting +- set up an instance of Vaultwarden to store, share and manage permissions of passwords diff --git a/blog/md/why-copyleft.md b/blog/md/why-copyleft.md new file mode 100644 index 0000000..24cfe46 --- /dev/null +++ b/blog/md/why-copyleft.md @@ -0,0 +1,123 @@ +# Why do I use copyleft-licensed software? | 27th March 2025 + +*This blog post is an extract of a discussion where I explain why I use copyleft-licensed software.* + +In an email conversation, someone wrote to me: + +> I'd be interested to hear you explain why – I read your site and agreed +> with much that was on this blog. I couldn't immediately understand the 'why', +> perhaps I was looking in the wrong place. + +Maybe the 2 reasons I tend to use copyleft-licensed software could be: + +First reason: + +- when I use an application, I tend to think that I contribute to that application, and that if I become dependent on it, so I don't want it to be taking away from me. + +Second reason: + +- I tend to think that copyleft-licenses are a mechanism against the asymmetry of power between controllers of software/applications and users. + +I'll elaborate on both points, and also mention some of the limitations. + +#### When you use an application, you contribute to the success of that application + +I think of my usage of a software as a contribution to that software or +application - I think of usage as contribution because, say, Facebook +would not exist without users. +Users of Facebook make Facebook possible. +No users, no Facebook. + +Then, I am thinking that if I contribute to something, and if I become dependent on this something for my everyday life, for my business for example, I want to have +some agency over it. + +I don't want this thing to be taken away from me; it's costly to build something, and then lose it. + +I always have this example in mind: a calendar application I used to use, Sunrise Calendar, that got acquired and then shut down. + +An example of a calendar application can sound trivial, but you can think of that would mean for a business. + +Sunrise became successful - because it had acquired half a million +users, and then, because it was successful, it was acquired by +Microsoft, and then shut down. + +Users, who had made Sunrise successful, were left with no application. + +This is an extract from the last blog post the team behind Sunrise published to users[1]: + +> One last note to let you know that we’re moving on for good to Outlook and +> shutting down the Sunrise apps +> +> [...] +> +> Tomorrow, you will be logged out of your account. +> +> [...] +> +> We’d like to extend a final and massive thank you to all of you who’ve +> supported us along the way. It’s been a hell of a ride. We really hope you +> enjoyed those years we spent together as much as we did. +> +> With lots of love, +> +> The Sunrise team + +You might think of other examples; in my case I also remember using Mailbox which was +acquired by Dropbox and then shut down. +Skype is another example some might remember. + +So now, if I start using a software or any digital tool, I am thinking: + +am I contributing to something which can be taken away from me? + +Permissive licenses help but don't prevent the maintainer from turning a +software proprietary, as far as I understand - so copyleft acts against this. +The source code of a copyleft-licensed software will remain freely +distributed.[2] + +*Copyleft isn't a panacea though.* + +Also, I am reluctant to use software that are copyleft-licensed, like Signal +Messenger, yet are walled-gardens. +To me, lack of interoperability is an issue. +I don't want to get trapped in a walled-garden, so I don't use Signal for that +reason, even though it's copyleft, and end-to-end encrypted and collect very +little metadata.[3] + +It's too much power in the hand of a few people, the CEO of Signal and a board probably. + +And that's also why I think copyleft helps: it's a mechanism against +asymmetry of power between controllers of software and users. + +#### Copyleft: a mechanisms against asymmetry of power + +We, as users, adopt software and sometimes tend to become dependent on it, to +run our business or keep in touch with our family for example - maintainers of these software we are dependent upon +then suddenly have a lot of power: they control a software which we can no longer +exist without. + +With proprietary software, users have little leverage to keep the hubris of providers in check; they can sell the software, get it shut down, and leave users with nothing; or they can govern what people can and cannot do *etc*. Zuckerberg and other CEOs of +large technology providers have little counter-power against them; head of states +meet them face-to-face - I am not saying it's bad or good, but they get +stronger as users become dependent on their tools. + +Relying on software whose source code is freely distributed, for me, as a user, +is a way to know that there are some mechanisms in place to keep the hubris of +maintainers (controllers of software) in check: if maintainers act in a way that displease users, then users can fork, and +carry on using a software on their own terms. +Audacity, an audio editor, is an example. Maintainers joined a corporate (the corporate now maintains Audacity), users forked and created Tenacity. + +So, in a way, I think of freely +distributed software as a mechanism to re-balance the asymmetry of power there +is between users and controllers of software. + +[1] You can find this blog post in full on archive.org: https://web.archive.org/web/20170317060955if_/http://blog.sunrise.am/ + +[2] Although there are examples of copyleft-licensed software that later +became non-free. +There is a Wikipedia page about it which I can't find right now. +How a company can switch from a copyleft-licensed software to proprietary is still unclear to me. + +[3] MM and others will answer by saying that if Signal is built this way (as a walled-garden - my own words) that's for the security of users; that's another question we could discuss: "*What do we mean by security?*" + +*Thanks to David, maintainer of blot.im, for asking me this question in the first place.* diff --git a/blog/preamble.txt b/blog/preamble.txt new file mode 100644 index 0000000..e978b25 --- /dev/null +++ b/blog/preamble.txt @@ -0,0 +1,2 @@ +<main> +<h1>Blog posts</h1> diff --git a/build.sh b/build.sh new file mode 100755 index 0000000..dfa47bb --- /dev/null +++ b/build.sh @@ -0,0 +1 @@ +bin/mkws https://copyleftculture.com @@ -0,0 +1,25 @@ +# Contact + +<div class="main" > +**EMAIL** +<tt>roman@copyleftculture.com</tt> + +**TIME ZONE** +<tt>UTC+01:00</tt> + +**PGP FINGERPRINT** +<tt>2E0F FB60 7FEF 11D0 FB45 4DDC E979 E52A 7036 7A88</tt> + +**LANGUAGES** +<tt> English, Français</tt> + +**ADDRESS** +<tt>Copyleft Culture</tt> +<tt>Gottschedstr. 4</tt> +<tt>Ex. Rotaprint Ausgang 4</tt> +<tt>13357 Berlin</tt> +<tt>Germany</tt> + +</div> + + diff --git a/contact.upphtml b/contact.upphtml new file mode 100644 index 0000000..06c88ad --- /dev/null +++ b/contact.upphtml @@ -0,0 +1,3 @@ +#! +pandoc contact +#! diff --git a/deploy.sh b/deploy.sh new file mode 100755 index 0000000..5c36f24 --- /dev/null +++ b/deploy.sh @@ -0,0 +1 @@ +rsync -a output/ root@93.95.229.191:/var/www/copyleftculture.com @@ -0,0 +1,122 @@ +# copyleft culture + +<div class="untertitel" > +## *Become digitally sovereign.* +</div> + + +</br> + +<div class="main" > + +## \# What do I do? + +I run IT infrastructures for businesses and provide them with software, digital tools and applications they need. + +- I advise +- take care of setting things up +- on-board staff +- train staff +- and remain available for support + +There is no vendor lock-in. + +-------------- + +## \# How is there no vendor lock-in? + +1. I use software any provider can host for you +2. I use software whose source code is freely distributed + +-------------- + +## \# What do I offer? + +**NEXTCLOUD** from EUR 200 per year + +*Alternative to Microsoft 365 or Google Workspace* + +- share folders across organisations; per user, per group, etc. +- collaborate on documents, spreadsheet, slides +- create forms (run surveys, etc) +- create a webpage with calendar slots others can book in your calendar +- get others to sign documents +- sync folder with your folders on your desktop automatically + +**MATTERMOST** from EUR 100 per year + +*Alternative to Slack* + +- communicate via instant message with your team +- create public channels a la Discord +- integrate with your video conference tool +- receive notifications from other applications +- use on desktop, web, iOS or android + +**BIG BLUE BUTTON** from EUR 120 per year + +*Alternative to Zoom* + +- get a dedicated URL for conferences with your name +- organise online conferences +- record conferences +- draw on white boards +- chat with participants + +**VAULTWARDEN** from EUR 100 per year + +- manage passwords for your organisation +- share passwords with others securely +- share collection of passwords +- manage passwords permissions per user, team, organisation +- send encrypted files via temporary links + +**MAILBOXES (MAILCOW)** from EUR 24 per year + +- get email addresses with your own domain name +- get unlimited addresses/mailboxes +- pay per usage (number of email sent, storage per GB) +- use your own email applications (or SoGo) +- manage shared mailboxes e.g. <tt>contact@example.com</tt> +- manage wildcard mailboxes e.g. <tt>client-*@example.com</tt> +- administrate addresses and aliases of your organisation via Mailcow +- synchronise your contacts and calendars via CardDAV and CalDAV + +Other software we offer: Discourse, Grist, Wordpress, ERPNext, Humhub, Forgejo, Etherpad, Yeswiki, Peertube, Jitsi, Matrix, Mastodon, Hedgedoc, Zammad, Snipe-IT, Uptime Kuma, Listmonk. + +-------------- + +## \# Who are you? + +- GNU/Linux system administrator +- Former go-to-market lead for startups; 1 exit +- Former entrepreneur-in-residence for a multinational +- Former public officer for digital affairs (ministry of finance) +- Researcher in epistemic security +- Essayist; essay: [Asymmetry](https://klarafranz.com/asymmetry.html) + +-------------- + +## \# What does an IT setup look like for a startup or a SME? + +Please see [this blog post](https://copyleftculture.com/blog/user-case-mmm.html). + +-------------- + +## \# What do people say? + +> *"Roman is an expert; it is great to be able to leverage his expertise and get things done"* + +-------------- + +## \# Why do you run this business? + +To finance my research in digital epistemic security and publish my work under a CC BY-SA license. + +-------------- + +## \# Contact + +See [contact page](https://copyleftculture.com/contact.html) + +</div> diff --git a/index.upphtml b/index.upphtml new file mode 100644 index 0000000..f61f862 --- /dev/null +++ b/index.upphtml @@ -0,0 +1,3 @@ +#! +pandoc index +#! diff --git a/newsletter b/newsletter new file mode 100644 index 0000000..19ea2f1 --- /dev/null +++ b/newsletter @@ -0,0 +1,9 @@ +# Newsletter + +<div class="main" > + +I send a newsletter with information to help organisations become digital sovereign. + +You can sign up <a href=" https://lists.yctct.com/wws/subscribe/copyleftculture?previous_action=info">there</a>. + +</div> diff --git a/newsletter.upphtml b/newsletter.upphtml new file mode 100644 index 0000000..d6af5d7 --- /dev/null +++ b/newsletter.upphtml @@ -0,0 +1,3 @@ +#! +pandoc newsletter +#! @@ -0,0 +1,74 @@ +# Pricing + +<div class="main" > + +## \# Nextcloud + + +| EUR 200 per year | EUR 600 per year | Price on demand | +|----------------------|-----------------------|---------------------------------| +| | | | +| | * Custom URL | * Custom URL | +| * c. 5 users<sup>1</sup> | * c. 20 users<sup>1</sup> | * More than 20 users<sup>1</sup> | +| * 10 GB storage | * 50 GB storage | * More than 50 GB of storage | +| * Calendar | * Calendar | * Calendar | +| * Contacts | * Contacts | * Contacts | +| * Files | * Files | * Files | +| | * Mail | * Mail | +| | * Forms (surveys) | * Forms (surveys) | +| | * Appointments | * Appointments | +| | * Deck | * Deck | +| | * Workspaces | * Workspaces | +| | * and more | * and more | + +## \# Mattermost + +| EUR 100 per year | EUR 400 per year | Price on demand | +|----------------------|-----------------------|---------------------------------| +| | | | +| | * Custom URL | * Custom URL | +| * c. 20 users<sup>1</sup> | * c. 150 users<sup>1</sup> | * More than 150 users<sup>1</sup> | +| * 3 GB storage | * 20 GB storage | * More than 20 GB of storage | + + + +## \# Big Blue Button + +| EUR 120 per year | EUR 600 per year | Price on demand | +|----------------------|-----------------------|---------------------------------| +| | | | +| * Custom URL | * Custom URL | * Custom URL | +| * 1 room | * 10 rooms | * More than 10 rooms | + + +## \# Mailboxes (Mailcow) + +| EUR 24 per year | EUR 384 per year | EUR 1,824 per year | +|----------------------|-----------------------|---------------------------------| +| | | | +| * Custom domains | * Custom domains | * Custom domains | +| * Unlimited mailboxes | * Unlimited mailboxes | * Unlimited mailboxes | +| * Unlimited incoming emails | * Unlimited incoming emails | * Unlimited incoming emails | +| * 5 GB of storage | * 100 GB of storage | * 1 TB of storage | +| * 35 outgoing emails per day | * 500 outgoing emails per day | * 2,000 outgoing emails per day | +| * A Mailcow admin account | * A Mailcow admin account | * A Mailcow admin account | +| * Wildcard email addresses | * Wildcard email addresses | * Wildcard email addresses | + + + +## \# Vaultwarden + +From EUR 100 per year. + + +## \# Other services + +Prices on demand. + +----- + +<sup>1</sup> The number of users stipulated is not a strict limit. We don't charge per user. This number only indicates that resources allocated to an instance best cater for a maximum of x number of simultaneous active users, that is people using the same instance at the same time. If the number of simultaneous active users were to increase beyond this limit we might need to allocate more resources to the server running your instance. Other than that, there is no limit of sign-up per se; your instance can carry as many user-accounts as you can imagine. + +</div> + + diff --git a/pricing.upphtml b/pricing.upphtml new file mode 100644 index 0000000..fa36fa0 --- /dev/null +++ b/pricing.upphtml @@ -0,0 +1,3 @@ +#! +pandoc pricing +#! diff --git a/robots.txt b/robots.txt new file mode 100644 index 0000000..0868b21 --- /dev/null +++ b/robots.txt @@ -0,0 +1,25 @@ +User-agent: * # all bots +Disallow: # allow this directory (the entire website) + +User-agent: googlebot # all Google services +Disallow: / # disallow this directory (the entire website) + +User-agent: GPTBot # ChatGPT +Disallow: / # disallow this directory (the entire website) + +User-agent: Bytespider +Disallow: / + +# on its website, Google stipulate that instructions listed in robots.txt +# file are not enough to blocking Google from indexing a webiste: +# 'it is not a mechanism for keeping a web page out of Google.' +# +# if you want to block all search indexing +# you need to add the following header to all of your pages: +# <meta name="robots" content="noindex" /> +# although Google stipulates that '[f]or the noindex rule to be effective, +# the page or resource must not be blocked by a robots.txt file' +# sound like a catch-22. idk. + + + diff --git a/share/feed.uppxml b/share/feed.uppxml new file mode 100644 index 0000000..3203ecf --- /dev/null +++ b/share/feed.uppxml @@ -0,0 +1,42 @@ +<?xml version='"1.0"' encoding='"UTF-8"'?> +<rss version='2.0' xmlns:atom='"http://www.w3.org/2005/Atom"' xmlns:content='http://purl.org/rss/1.0/modules/content/'> + <channel> + <title>Become Digitally Sovereign</title> + <link>https://copyleftculture.com</link> + <description>Blog posts on digital sovereignty</description> + <language>en-gb</language> + <atom:link href='"https://copyleftculture.com/feed.xml"' rel='"self"' type='"application/rss+xml"' /> + <ttl>60</ttl> +#! +now=`date -R` +#! + <lastBuildDate>${now}</lastBuildDate> +#! +for f in `ls -t blog/*.html` +do +if [ $(basename "${f}") != "index.html" ]; then + title=`sed -n 's/.*<h1>\(.*\)<\/h1>.*/\1/ip;T;q' ${f}` + title=${title% |*} + desc=`sed -n 's/.*<h2>\(.*\)<\/h2>.*/\1/ip;T;q' ${f}` + linque=$1/blog/$(basename "${f}") + pubDate=${f#blog/} + pubDate=${pubDate%%-*} + pubDate=`date -R -d ${pubDate}` + content=`sed -n '/<main>/,/<\/main>/{//!p;}' ${f}` +#! + <item> + <title>${title}</title> + <link>${linque}</link> + <guid>${linque}</guid> + <description>${desc}</description> + <pubDate>${pubDate}</pubDate> + <content:encoded><![CDATA[${content}]]></content:encoded> + </item> +#! +fi +done +#! + </channel> +</rss> + + diff --git a/share/l.upphtml b/share/l.upphtml new file mode 100644 index 0000000..85c8d0d --- /dev/null +++ b/share/l.upphtml @@ -0,0 +1,30 @@ +<!doctype html> +<html lang=${LANG%%_*}> + +<title>Copyleft Culture</title> + +<meta charset=${LANG##*.}> +<meta name=viewport content='width=device-width, initial-scale=1'> + +<style> +#! +pp "${SHARE:?no theme directory set}"/s.uppcss +#! +</style> + +<nav> + <div class="topnav"> + <a href="/">home</a> + <a href="/blog">blog</a> + <a href="/newsletter.html">newsletter</a> + <a href="/pricing.html">pricing</a> + <a href="/contact.html">contact</a> + <a href="/about.html">site</a> +</div> +</nav> + +#! +pp "$1" +#! + + diff --git a/share/man/man1/lmt.1 b/share/man/man1/lmt.1 new file mode 100644 index 0000000..755d69b --- /dev/null +++ b/share/man/man1/lmt.1 @@ -0,0 +1,55 @@ +.Dd Sep 4, 2020 +.Dt lmt +.Os +.Sh NAME +.Nm lmt +.Nd last modification time +.Sh SYNOPSIS +.Nm lmt +.Op Fl f Ar format +.Ar file ... +.Sh DESCRIPTION +The +.Nm +utility prints the last modification time for the given +.Ar file +to standard output. +The information displayed is obtained by calling +.Xr lstat 2 +with the given +argument and evaluating the returned structure. +.Pp +The options are as follows: +.Bl -tag -width Ds +.It Fl f Ar format +The format in which to display the time. +The format string may contain any of the conversion specifications +described in the +.Xr strftime 3 +manual page, as well as any arbitrary text. +A newline +.Pq Ql \en +character is always output after the characters specified by +the format string. +The format string for the default display is: +.Bd -literal -offset indent +%a %b %e %H:%M:%S %Z %Y +.Ed +.El +.Sh EXIT STATUS +.Ex -std +.Sh EXAMPLES +Print last modification time for +.Pa file1 +to standard output: +.Pp +.Dl $ lmt file1 +.Pp +Print last modification time for +.Pa file1 +to standard output in ISO 8601 format: +.Pp +.Dl $ lmt -f "%Y-%m-%dT%H:%M:%S%z" file1 +.Sh SEE ALSO +.Xr stat 1 +.Xr strftime 3 diff --git a/share/man/man1/mkws.1 b/share/man/man1/mkws.1 new file mode 100644 index 0000000..5ab337d --- /dev/null +++ b/share/man/man1/mkws.1 @@ -0,0 +1,91 @@ +.Dd Dec 13, 2019 +.Dt mkws 1 +.Os +.Sh NAME +.Nm mkws +.Nd make web site +.Sh SYNOPSIS +.Nm +.Ar url +.Op path +.Sh DESCRIPTION +The +.Nm +utility uses +.Xr pp 1 +and the theme files in the +.Ev MKWSTHEMEPATH +directory +to preprocess all files in +.Op path +in order to produce a static web site in the current directory. If no +.Op path +is specified, the current directory is used instead. +.Pp +The options are as follows: +.Bl -tag -width Ds +.It Ar url +The url of the web site. It is used for generating +.Pa sitemap.xml +. +.It Op path +The path where the unpreprocessed files are located. If no +.Op path +is specified, the current directory is used instead. +.El +.Sh ENVIRONMENT +.Bl -tag -width MKWSTHEMEDIR +.It Ev MKWSTHEMEDIR +The directory containing the theme files. See the +.Em FILES +section for the minimum required files for a theme. If no +.Ev MKWSTHEMEDIR +variable is set +.Pa [path]/share +wil be used. +.It Ev LANG +The language for the website. It will be parsed to fill in the +.Em lang +attribute of the +.Em html +element and then +.Em charset +.Em meta +element. +.El +.Sh FILES +.Bl -tag -width "/tmp/vi.recover +.It Pa $MKWSTHEMEDIR/l.upphtml +The layout file of the website. It contains the +.Em DOCTYPE , +.Em html , +.Em head , +.Em title , +.Em meta +, +.Em link +, +.Em body +elements. +.It Pa $MKWSTHEMEDIR/sitemap.xml +The +.Pa sitemap.txt +template. +.El +.Sh EXIT STATUS +.Ex -std +.Sh EXAMPLES +Make https://example.com web site using the unpreprocessed files in the +current directory +.Pp +.Dl $ mkws https://example.com +.Pp +Make https://example.com web site using the unpreprocessed files in the +.Ar ~/src/ws +directory +.Pp +.Dl $ mkws https://example.com ~/src/ws +.Sh SEE ALSO +.Xr sh 1 +.Xr pp 1 +.Xr locale 1 diff --git a/share/man/man1/pp.1 b/share/man/man1/pp.1 new file mode 100644 index 0000000..a552c97 --- /dev/null +++ b/share/man/man1/pp.1 @@ -0,0 +1,46 @@ +.Dd Apr 25, 2019 +.Dt pp 1 +.Os +.Sh NAME +.Nm pp +.Nd preprocessor +.Sh SYNOPSIS +.Nm pp +.Op Fl d +.Ar file +.Op args ... +.Sh DESCRIPTION +The +.Nm +utility processes +.Ar file +to produce output that is used as input to another +program. +.Pp +It executes code enclosed in +.Dq #!\en +delimiters using +.Xr sh 1 . +.Op args ... +are passed to the embbeded script and are available +via the usual +.Em $1, $2, ... +positional parameters. +.Pp +The options are as follows: +.Bl -tag -width Ds +.It Fl d +.Nm +will dump the generated +.Xr sh 1 +code instead of executing it. This is useful for debugging. +.El +.Sh EXIT STATUS +.Ex -std +.Sh EXAMPLES +Preprocess file with arguments: +.Pp +.Dl $ pp file.upphtml a b +.Pp +.Sh SEE ALSO +.Xr sh 1 diff --git a/share/s.uppcss b/share/s.uppcss new file mode 100644 index 0000000..6511972 --- /dev/null +++ b/share/s.uppcss @@ -0,0 +1,119 @@ +html, body{ + font-family: sans-serif; + color: #ffbb55; + max-width: 750px; + margin-left: auto; + margin-right: auto; + padding: 5px; + background: #111; + } + +h1{ + font-style: italic; + font-size: 4em; + text-align: center; + } + +.untertitel { + text-align: center; +} + +p{ + max-width: 600px; +} + +/*hyperlinks*/ +/* unvisited link */ +a:link { + color: #ff7700; +} +/* visited link */ +a:visited { + color: #ff7700; +} +/* mouse over link */ +a:hover { + color: #111; + background: #f93; +} +/* selected link */ +a:active { + color: #111; +} + +/* collapse section*/ +details { + border: 1px solid #041716; + border-radius: 2px; + padding: 0.5em 0.5em 0; +} + +summary { + #font-weight: bold; + margin: -0.5em -0.5em 0; + padding: 0.5em; +} + +details[open] { + padding: 0.5em; +} + +details[open] summary { + border-bottom: 1px solid #041716; + margin-bottom: 0.5em; +} + +.topnav { + overflow: hidden; + background-color: #ffbb55; + border-radius: 0.25em; +} + +.topnav a { + float: left; + color: #111; + text-align: center; + padding: 14px 16px; + text-decoration: none; + font-size: 17px; +} + +.topnav a:hover { + background-color: #f93; + color: #111; +} + +#.topnav a.active { +# background-color: white; +# color: navy; +#} + +/* frame around text */ +.main { + border: 6px double; + padding: 1em; +} + +hr { + border-color: #ffbb55; +} + +/* tables */ + +table { + padding: 10px; +} + +table.center { + margin-left: auto; + margin-right: auto; +} + +th { + padding-bottom: 20px; + padding-right: 20px; + padding-left: 20px; + border-bottom: 1px solid; +} + + diff --git a/share/sitemap.uppxml b/share/sitemap.uppxml new file mode 100644 index 0000000..478d6b4 --- /dev/null +++ b/share/sitemap.uppxml @@ -0,0 +1,21 @@ +<?xml version='1.0' encoding='UTF-8'?> +<urlset xmlns='http://www.sitemaps.org/schemas/sitemap/0.9'> +#! +for f in *.html +do +#! +<url> +#! +loc=$1/$(basename "${f}") +#! +<loc>${loc}</loc> +#! +lastmod=$(lmt -f '%Y-%m-%dT%H:%M:%SZ' "${f}" | cut -d' ' -f1) +#! +<lastmod>${lastmod}</lastmod> +<priority>1.0</priority> +</url> +#! +done +#! +</urlset> diff --git a/todo.txt b/todo.txt new file mode 100644 index 0000000..6bac75b --- /dev/null +++ b/todo.txt @@ -0,0 +1 @@ +- fix RSS |