Tech

🔔 Prelude: I sometimes wonder if adding a license to my campus homework is too serious. Nevertheless, I still will add it. 🖋️ Main License Version Include License Include Source Code Trademark Status Change Commercial Use Distribution Modification Patent Right Private Use License Transfer No Liability No Trademark Apache License 2.0 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes FreeBSD License Yes Yes Yes Yes Yes Yes Yes 2-Clause BSD License Yes Yes Yes Yes Yes Yes Yes GNU General Public License(GPL) 2.0 Yes Yes Yes Yes Yes Yes Yes No Yes GNU Lesser General Public License 2.1 Yes Yes Yes Yes Yes Yes Yes No Yes GNU General Public License 3.0 Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes GNU Lesser General Public License 3.0 Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes MIT License Yes Yes Yes Yes Yes Yes Yes Yes Mozilla Public License(MPL) 2.0 Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Eclipse Public License 1.0 Yes Yes Yes Yes Yes Yes Yes Yes No Yes Affero General Public License 3.0 Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes General Copyright Yes Yes Yes Yes No No Yes No In short? Completely Open Source -> MIT License, BSD License Open Source, But Must Credit the Original Author -> Apache License 2.0 Open Source, Must Use the Same License (Copyleft) -> GPL Allows Commercial Use -> MIT License, BSD License, Apache License 2.0, GPL Allows Closed Source (Can Be Integrated into Proprietary Software) -> MIT License, BSD License, Apache License 2.0 Does Not Allow Closed Source (Must Remain Open Source) -> GPL

🔔 Prelude: Hi! This is my first post, which is also a template post. Actually, this blog is built by Notion and Nextjs. I directly write my posts on Notion. So convenient! You can check my references to have a see! Main This is my main block. View 1 This is my citation. And view. Summary This is my main summary. Sometimes I don’t make a summary. 📎 References This is my references. https://github.com/tangly1024/NotionNext

This site runs on Hugo with the PaperMod theme, bilingual content, and Algolia for search. None of those choices were difficult. Wiring them together produced four bugs that were, so this post is mostly about those. Why Hugo The decision came down to Hugo against Hexo. Two requirements settled it: content organised by directory, and a tolerable path for Org-mode files. Hugo maps content/ directly onto URL structure. A file at content/tech/foo.md becomes /tech/foo/ and the tech directory becomes a section with its own list page. No plugin, no configuration. Hexo can be pushed into the same shape with permalink rules and a category plugin, but it is a workaround rather than the design. ...