From a01dea7cc38f706617a72203e34b6bc9b3003137 Mon Sep 17 00:00:00 2001 From: randogoth Date: Tue, 16 May 2023 23:39:09 +0300 Subject: [PATCH] remove output --- .gitignore | 3 + example/output/micron/archives.mu | 48 ------ example/output/micron/author/node-nomad.mu | 50 ------- example/output/micron/authors.mu | 6 - example/output/micron/categories.mu | 5 - example/output/micron/category/misc.mu | 49 ------- .../output/micron/concepts-and-terminology.mu | 67 --------- example/output/micron/index.mu | 48 ------ example/output/micron/introduction.mu | 23 --- example/output/micron/markup.mu | 137 ------------------ example/output/micron/tags.mu | 4 - 11 files changed, 3 insertions(+), 437 deletions(-) delete mode 100644 example/output/micron/archives.mu delete mode 100644 example/output/micron/author/node-nomad.mu delete mode 100644 example/output/micron/authors.mu delete mode 100644 example/output/micron/categories.mu delete mode 100644 example/output/micron/category/misc.mu delete mode 100644 example/output/micron/concepts-and-terminology.mu delete mode 100644 example/output/micron/index.mu delete mode 100644 example/output/micron/introduction.mu delete mode 100644 example/output/micron/markup.mu delete mode 100644 example/output/micron/tags.mu diff --git a/.gitignore b/.gitignore index 68bc17f..2c54b39 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,6 @@ +# Pelican +example/output/ + # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] diff --git a/example/output/micron/archives.mu b/example/output/micron/archives.mu deleted file mode 100644 index 002eba3..0000000 --- a/example/output/micron/archives.mu +++ /dev/null @@ -1,48 +0,0 @@ -`# lang: en ->Micron Blog - - - -+[Tue 16 May 2023] ->>>>`[`!Concepts and Terminology`!`/concepts-and-terminology.html] ->>>>> Concepts and Terminology - -The following section will briefly introduce various concepts and terms used in the program. - ->> Peer - -A `*peer`* refers to another Nomad Network client, which will generally be operated by another person. But since Nomad Network is a general LXMF client, it could also be any other LXMF … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Introduction`!`/introduction.html] ->>>>>> Communicate Freely. - -The intention with this program is to provide a tool to that allows you to build private and resilient communications platforms that are in complete control and ownership of the people that use them. - -Nomad Network is build on LXMF and Reticulum, which together provides the cryptographic mesh … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Markup`!`/markup.html] ->>>>> Outputting Formatted Text - -- - -`!Hello!`! This is output from `*micron`* -Micron generates formatted text for your terminal - -- - -Nomad Network supports a simple and functional markup language called `*micron`*. If you are familiar with `*markdown`* or `*HTML`*, you will feel right at home writing pages with micron. - -With micron you can easily … - -- - - - diff --git a/example/output/micron/author/node-nomad.mu b/example/output/micron/author/node-nomad.mu deleted file mode 100644 index f78fb3a..0000000 --- a/example/output/micron/author/node-nomad.mu +++ /dev/null @@ -1,50 +0,0 @@ -`# lang: en ->Micron Blog - ->>Articles by Node Nomad - - - -+[Tue 16 May 2023] ->>>>`[`!Concepts and Terminology`!`/concepts-and-terminology.html] ->>>>> Concepts and Terminology - -The following section will briefly introduce various concepts and terms used in the program. - ->> Peer - -A `*peer`* refers to another Nomad Network client, which will generally be operated by another person. But since Nomad Network is a general LXMF client, it could also be any other LXMF … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Introduction`!`/introduction.html] ->>>>>> Communicate Freely. - -The intention with this program is to provide a tool to that allows you to build private and resilient communications platforms that are in complete control and ownership of the people that use them. - -Nomad Network is build on LXMF and Reticulum, which together provides the cryptographic mesh … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Markup`!`/markup.html] ->>>>> Outputting Formatted Text - -- - -`!Hello!`! This is output from `*micron`* -Micron generates formatted text for your terminal - -- - -Nomad Network supports a simple and functional markup language called `*micron`*. If you are familiar with `*markdown`* or `*HTML`*, you will feel right at home writing pages with micron. - -With micron you can easily … - -- - - - diff --git a/example/output/micron/authors.mu b/example/output/micron/authors.mu deleted file mode 100644 index 87281be..0000000 --- a/example/output/micron/authors.mu +++ /dev/null @@ -1,6 +0,0 @@ -`# lang: en ->Micron Blog - ->Authors on Micron Blog+ `[Node Nomad`/author/node-nomad.html] (3) - - diff --git a/example/output/micron/categories.mu b/example/output/micron/categories.mu deleted file mode 100644 index 1e28f4e..0000000 --- a/example/output/micron/categories.mu +++ /dev/null @@ -1,5 +0,0 @@ -`# lang: en ->Micron Blog - -+ `[misc`/category/misc.html] - diff --git a/example/output/micron/category/misc.mu b/example/output/micron/category/misc.mu deleted file mode 100644 index d28ef25..0000000 --- a/example/output/micron/category/misc.mu +++ /dev/null @@ -1,49 +0,0 @@ -`# lang: en ->Micron Blog - ->>misc - - -+[Tue 16 May 2023] ->>>>`[`!Concepts and Terminology`!`/concepts-and-terminology.html] ->>>>> Concepts and Terminology - -The following section will briefly introduce various concepts and terms used in the program. - ->> Peer - -A `*peer`* refers to another Nomad Network client, which will generally be operated by another person. But since Nomad Network is a general LXMF client, it could also be any other LXMF … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Introduction`!`/introduction.html] ->>>>>> Communicate Freely. - -The intention with this program is to provide a tool to that allows you to build private and resilient communications platforms that are in complete control and ownership of the people that use them. - -Nomad Network is build on LXMF and Reticulum, which together provides the cryptographic mesh … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Markup`!`/markup.html] ->>>>> Outputting Formatted Text - -- - -`!Hello!`! This is output from `*micron`* -Micron generates formatted text for your terminal - -- - -Nomad Network supports a simple and functional markup language called `*micron`*. If you are familiar with `*markdown`* or `*HTML`*, you will feel right at home writing pages with micron. - -With micron you can easily … - -- - - - diff --git a/example/output/micron/concepts-and-terminology.mu b/example/output/micron/concepts-and-terminology.mu deleted file mode 100644 index 9a9d0cd..0000000 --- a/example/output/micron/concepts-and-terminology.mu +++ /dev/null @@ -1,67 +0,0 @@ -`# lang: en ->Micron Blog - - ->Concepts and Terminology - - -Tue 16 May 2023 - -by Node Nomad - -> Concepts and Terminology - -The following section will briefly introduce various concepts and terms used in the program. - ->> Peer - -A `*peer`* refers to another Nomad Network client, which will generally be operated by another person. But since Nomad Network is a general LXMF client, it could also be any other LXMF client, program, automated system or machine that can communicate over LXMF. - -All peers (and nodes) are identified by their `*address`* (which is, technically speaking, a Reticulum destination hash). An address consist of 32 hexadecimal characters (16 bytes), and looks like this: - -`=<e9eafceea9e3664a5c55611c5e8c420a# `= - -Anyone can choose whatever display name they want, but addresses are always unique, and generated from the unique cryptographic keys of the peer. This is an important point to understand. Since there is not anyone controlling naming or address spaces in Nomad Network, you can easily come across another user with the same display name as you. - -Your addresses will always be unique though, and you must always verify that the address you are communicating with is matching the address of the peer you expect to be in the other end. - -To make this easier, Nomad Network allows you to mark peers and nodes as either `*trusted`*, `*unknown`* or `*untrusted`*. In this way, you can mark the peers and nodes that you know to be legitimate, and easily spot peers with similar names as unrelated. - ->> Announces - -An `*announce`* can be sent by any peer or node on the network, which will notify other peers of its existence, and contains the cryptographic keys that allows other peers to communicate with it. - -In the `![ Network ]`! section of the program, you can monitor announces on the network, initiate conversations with announced peers, and announce your own peer on the network. You can also connect to nodes on the network and browse information shared by them. - ->> Conversations - -Nomad Network uses the term `*conversation`* to signify both direct peer-to-peer messaging threads, and also discussion threads with an arbitrary number of participants that might change over time. - -Both things like discussion forums and chat threads can be encapsulated as conversations in Nomad Network. The user interface will indicate the different characteristics a conversation can take, and also what form of transport encryption was used for messages within. - -In the `![ Conversations ]`! part of the program you can view and interact with all currently active conversations. You can also edit nickname and trust settings for peers belonging to these conversations here. To edit settings for a peer, select it in the conversation list, and press `!Ctrl-E`!. - -By default, Nomad Network will attempt to deliver messages to a peer directly. This happens by first establishing an encrypted link directly to the peer, and then delivering the message over it. - -If the desired peer is not available because it has disconnected from the network, this method will obviously fail. In this case, Nomad Network will attempt to deliver the message to a node, which will store and forward it over the network, for later retrieval by the destination peer. The message is encrypted before being transmitted to the network, and is only readable by the intended recipient. - -For propagated delivery to work, one or more nodes must be available on the network. If one or more trusted nodes are available, Nomad Network will automatically select the most suitable node to send the message via, but you can also manually specify what node to use. - -To select a node manually, go to the `![ Network ]`! part of the program, choose the desired node in the `*Known Nodes`* list, and select the `!< Info # ** button. In the **Node Info`! dialog, you can specify the selected node as the default propagation node. - -By default, Nomad Network will check in with propagation nodes, and download any available messages every 6 hours. You can change this interval, or disable automatic syncronisation completely, by editing the configuration file. - -You can always initiate a sync manually, by pressing `!Ctrl-R`! in the `![ Conversations ]`! part of the program, which will open the syncronisation window. - ->> Node - -A Nomad Network `*node`* is an instance of the Nomad Network program that has been configured to host information for other peers and help propagate messages and information on the network. - -Nodes can host pages (similar to webpages) written in a markup-language called `*micron`*, as well as make files and other resources available for download for peers on the network. Nodes also form a distributed message store for offline users, and allows messages to be exchanged between peers that are not online at the same time. - -If no nodes exist on a network, all peers will still be able to communicate directly peer-to-peer, but both endpoints of a conversation will need to be available at the same time to converse. When nodes exist on the network, messages will be held and syncronised between nodes for deferred delivery if the destination peer is unavailable. Nodes will automatically discover and peer with each other, and handle syncronisation of message stores. - -To learn how to host your own node, read the `*Hosting a Node`* section of this guide. - - - diff --git a/example/output/micron/index.mu b/example/output/micron/index.mu deleted file mode 100644 index 002eba3..0000000 --- a/example/output/micron/index.mu +++ /dev/null @@ -1,48 +0,0 @@ -`# lang: en ->Micron Blog - - - -+[Tue 16 May 2023] ->>>>`[`!Concepts and Terminology`!`/concepts-and-terminology.html] ->>>>> Concepts and Terminology - -The following section will briefly introduce various concepts and terms used in the program. - ->> Peer - -A `*peer`* refers to another Nomad Network client, which will generally be operated by another person. But since Nomad Network is a general LXMF client, it could also be any other LXMF … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Introduction`!`/introduction.html] ->>>>>> Communicate Freely. - -The intention with this program is to provide a tool to that allows you to build private and resilient communications platforms that are in complete control and ownership of the people that use them. - -Nomad Network is build on LXMF and Reticulum, which together provides the cryptographic mesh … - -- - - -+[Tue 16 May 2023] ->>>>`[`!Markup`!`/markup.html] ->>>>> Outputting Formatted Text - -- - -`!Hello!`! This is output from `*micron`* -Micron generates formatted text for your terminal - -- - -Nomad Network supports a simple and functional markup language called `*micron`*. If you are familiar with `*markdown`* or `*HTML`*, you will feel right at home writing pages with micron. - -With micron you can easily … - -- - - - diff --git a/example/output/micron/introduction.mu b/example/output/micron/introduction.mu deleted file mode 100644 index e0276e3..0000000 --- a/example/output/micron/introduction.mu +++ /dev/null @@ -1,23 +0,0 @@ -`# lang: en ->Micron Blog - - ->Introduction - - -Tue 16 May 2023 - -by Node Nomad - ->> Communicate Freely. - -The intention with this program is to provide a tool to that allows you to build private and resilient communications platforms that are in complete control and ownership of the people that use them. - -Nomad Network is build on LXMF and Reticulum, which together provides the cryptographic mesh functionality and peer-to-peer message routing that Nomad Network relies on. This foundation also makes it possible to use the program over a very wide variety of communication mediums, from packet radio to fiber. - -Nomad Network does not need any connections to the public internet to work. In fact, it doesn't even need an IP or Ethernet network. You can use it entirely over packet radio, LoRa or even serial lines. But if you wish, you can bridge islanded Reticulum networks over the Internet or private ethernet networks, or you can build networks running completely over the Internet. The choice is yours. - -The current version of the program should be considered a beta release. The program works well, but there will most probably be bugs and possibly sub-optimal performance in some scenarios. On the other hand, this is the best time to have an influence on the direction of the development of Nomad Network. To do so, join the discussion on the Nomad Network project on GitHub. - - - diff --git a/example/output/micron/markup.mu b/example/output/micron/markup.mu deleted file mode 100644 index e643448..0000000 --- a/example/output/micron/markup.mu +++ /dev/null @@ -1,137 +0,0 @@ -`# lang: en ->Micron Blog - - ->Markup - - -Tue 16 May 2023 - -by Node Nomad - -> Outputting Formatted Text - -- - -`!Hello!`! This is output from `*micron`* -Micron generates formatted text for your terminal - -- - -Nomad Network supports a simple and functional markup language called `*micron`*. If you are familiar with `*markdown`* or `*HTML`*, you will feel right at home writing pages with micron. - -With micron you can easily create structured documents and pages with formatting, colors, glyphs and icons, ideal for display in terminals. - -##Recommendations and Requirements - -While micron can output formatted text to even the most basic terminal, there's a few capabilities your terminal `*must`* support to display micron output correctly, and some that, while not strictly necessary, make the experience a lot better. - -Formatting such as `_underline`_, `!bold`! or `*italics`* will be displayed if your terminal supports it. - -If you are having trouble getting micron output to display correctly, try using `*gnome-terminal`* or `*alacritty`*, which should work with all formatting options out of the box. Most other terminals will work fine as well, but you might have to change some settings to get certain formatting to display correctly. - -###Encoding - -All micron sources are intepreted as UTF-8, and micron assumes it can output UTF-8 characters to the terminal. If your terminal does not support UTF-8, output will be faulty. - -###Colors - -Shading and coloring text and backgrounds is integral to micron output, and while micron will attempt to gracefully degrade output even to 1-bit terminals, you will get the best output with terminals supporting at least 256 colors. True-color support is recommended. - -###Terminal Font - -While any unicode capable font can be used with micron, it's highly recommended to use a `*"Nerd Font"`* (see https://www.nerdfonts.com/), which will add a lot of extra glyphs and icons to your output. - -If you want to make a break, horizontal dividers can be inserted. They can be plain, like the one below this text, or you can style them with unicode characters and glyphs, like the wavy divider in the beginning of this document. - -- - -Text can be `_underlined`_, `!bold`! or `*italic`*. - -###Sections and Headings - -You can define an arbitrary number of sections and sub sections, each with their own named headings. Text inside sections will be automatically indented. - -- - -If you place a divider inside a section, it will adhere to the section indents. - ->>> - -If no heading text is defined, the section will appear as a sub-section without a header. This can be useful for creating indented blocks of text, like this one. - -> Micron tags - -Tags are used to format text with micron. Some tags can appear anywhere in text, and some must appear at the beginning of a line. If you need to write text that contains a sequence that would be interpreted as a tag, you can escape it with the character \. - -##Formatting - -Text can be formatted as `!bold`! by using the `=**`= tag, `_underline`_ by using the `=_`= tag and `*italic`* by using the `=*`= tag. - -##Sections - -To create sections and subsections, use the # tag. This tag must be placed at the beginning of a line. To specify a sub-section of any level, use any number of # tags. If text is placed after a # tag, it will be used as a heading. - -Here is an example of sections: - -`= -# High Level Stuff -This is a section. It contains this text. - -## Another Level -This is a sub section. - -### Going deeper -A sub sub section. We could continue, but you get the point. - -#### -Wait! It's worth noting that we can also create sections without headings. They look like this. - -`= - -The above markup produces the following output: - -> High Level Stuff - -This is a section. It contains this text. - ->> Another Level - -This is a sub section. - ->>> Going deeper - -A sub sub section. We could continue, but you get the point. - ->>>>Wait! It's worth noting that we can also create sections without headings. They look like this. - - - -#Links - -Links to pages, files or other resources can be created with the `=[`= tag, which should always be terminated with a closing `=]`=. You can create links with and without labels, it is up to you to control the formatting of links with other tags. Although not strictly necessary, it is good practice to at least format links with underlining. - -Here's a few examples: - -`= -Here is a link without any label: [72914442a3689add83a09a767963f57c:/page/index.mu] - -This is a [labeled link](72914442a3689add83a09a767963f57c:/page/index.mu) to the same page, but it's hard to see if you don't know it -`= - -The above markup produces the following output: - -Here is a link without any label: [72914442a3689add83a09a767963f57c:/page/index.mu] - -This is a `[labeled link`72914442a3689add83a09a767963f57c:/page/index.mu] to the same page, but it's hard to see if you don't know it - -- - -When links like these are displayed in the built-in browser, clicking on them or activating them using the keyboard will cause the browser to load the specified URL. - -#Literals - -To display literal content, for example source-code, or blocks of text that should not be interpreted by micron, you can use literal blocks, specified by the ``` tag. - - - diff --git a/example/output/micron/tags.mu b/example/output/micron/tags.mu deleted file mode 100644 index be5bd8e..0000000 --- a/example/output/micron/tags.mu +++ /dev/null @@ -1,4 +0,0 @@ -`# lang: en ->Micron Blog - -