summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/donate.md2
-rw-r--r--content/theses/metaphysical/hyperlogical/ethics.md1
-rw-r--r--content/theses/metaphysical/hyperlogical/free-will.md5
-rw-r--r--content/theses/metaphysical/hyperlogical/logic.md (renamed from content/theses/metaphysical/hyperlogical/axioms.md)7
-rw-r--r--content/theses/metaphysical/interpersonal/abilities.md1
-rw-r--r--content/theses/metaphysical/interpersonal/self-made-hell.md1
-rw-r--r--content/theses/metaphysical/religious/catholicism.md1
-rw-r--r--content/theses/metaphysical/religious/demonology.md1
-rw-r--r--content/theses/metaphysical/religious/judaism.md1
-rw-r--r--content/theses/research/monitoring.md237
-rw-r--r--content/theses/technological/_index.md5
-rw-r--r--content/theses/technological/licensing/NESL.md115
-rw-r--r--content/theses/technological/licensing/_index.md5
-rw-r--r--content/theses/technological/licensing/nesl_preamble.md31
-rw-r--r--content/theses/technological/licensing/philosophy.md65
-rw-r--r--content/theses/technological/research/_index.md (renamed from content/theses/research/_index.md)0
-rw-r--r--content/theses/technological/research/arc-agi/_index.md (renamed from content/theses/research/arc-agi/_index.md)0
-rw-r--r--content/theses/technological/research/arc-agi/approach.md (renamed from content/theses/research/arc-agi/approach.md)2
-rw-r--r--content/theses/technological/research/arc-agi/introduction.md (renamed from content/theses/research/arc-agi/introduction.md)1
19 files changed, 238 insertions, 243 deletions
diff --git a/content/donate.md b/content/donate.md
index f305abe..d92fc0c 100644
--- a/content/donate.md
+++ b/content/donate.md
@@ -15,4 +15,4 @@ if you found anything in the site useful, and would like to support me, you can
0xfB03A91f345445451F5eb479573d07893b9e6FcB
## BTC:
-bc1q53e6ka96fd6sfrd4k48ft2xhfajp7nn5y72tpq
+bc1qg03xjq9ktpewxde3zg93umumskzmr9605lasys
diff --git a/content/theses/metaphysical/hyperlogical/ethics.md b/content/theses/metaphysical/hyperlogical/ethics.md
index 28d00d4..cf700af 100644
--- a/content/theses/metaphysical/hyperlogical/ethics.md
+++ b/content/theses/metaphysical/hyperlogical/ethics.md
@@ -2,6 +2,7 @@
title: ethical
weights: 3
---
+<h1>On ethics</h1>
having defined free will, i can now discuss about the ethical.
diff --git a/content/theses/metaphysical/hyperlogical/free-will.md b/content/theses/metaphysical/hyperlogical/free-will.md
index 9e31b47..36c6823 100644
--- a/content/theses/metaphysical/hyperlogical/free-will.md
+++ b/content/theses/metaphysical/hyperlogical/free-will.md
@@ -2,8 +2,9 @@
title: free will
weight: 2
---
+<h1>On free will</h1>
-## the existence of free will
+## on the existence of free will
in order to define and then converse on ideas relating to free will, one must first convince themselves on its existence. truthfully, one can simply make a definition, as well as talk about the emergent system much like any other metaphysical structure, but there is merit in being able to argue for its existence.
@@ -20,7 +21,7 @@ obviously such a statement is extremely subjective, but such a statement is true
finally, we can simply make an admission, without any extra argumentation. besides, it is obvious that there is no need for a person to justify or rationalize every aspect of their faith, nor are they obligated to answer to anybody except for themselves. it is therefore possible, and maybe even proper, for someone to define the existence of free will axiomatically, ignoring any other argument for or against it.
-## defining free will
+## on the definition of free will
if we accept the idea of free will existing, we should be able to define it, in order to be able to self reference and call upon to make use of this idea. this also helps in clarifying the meaning, which in everyday speech is muddled, much like most of language, due to the nature of communication (which is a discussion for a later time.).
diff --git a/content/theses/metaphysical/hyperlogical/axioms.md b/content/theses/metaphysical/hyperlogical/logic.md
index f99d24c..be76cfd 100644
--- a/content/theses/metaphysical/hyperlogical/axioms.md
+++ b/content/theses/metaphysical/hyperlogical/logic.md
@@ -1,9 +1,10 @@
---
-title: axioms
+title: logic
weight: 1
---
+<h1>On logic</h1>
-## the nature of logic
+## on the nature of logic
the words "logic" and "knowledge" are often connected in the minds of humans. in the sciences, logic is used religiously, in an attempt to obtain knowledge, in the same way that it is used in religions.
@@ -39,7 +40,7 @@ given then that one can never know the truth *a priori*, and all axiomatic syst
the only way that exists is faith, which is the principal decision one makes before even choosing an axiomatic system, and which occurs due to the fact that, before you can study the system, you need to belive that it is well defined and founded, and also that to some extent it is capable of representing the truth.
-## the failure of logic
+## on the failure of logic
to conclude the discussion on logic, i would like to examine in depth the propagation of knowledge, in order to present the greatest result; the fact that most appeals to logic are themselves a logical fallacy.
diff --git a/content/theses/metaphysical/interpersonal/abilities.md b/content/theses/metaphysical/interpersonal/abilities.md
index fbb8d48..525d6cd 100644
--- a/content/theses/metaphysical/interpersonal/abilities.md
+++ b/content/theses/metaphysical/interpersonal/abilities.md
@@ -2,6 +2,7 @@
title: the abilities of humans
weight: 100
---
+<h1>On the abilities of humans</h1>
## free body
If one is to imagine an individual, possessing free will, alone, one can think of how said individual might operate, and what abilities the individual might have.
diff --git a/content/theses/metaphysical/interpersonal/self-made-hell.md b/content/theses/metaphysical/interpersonal/self-made-hell.md
index 67faa4a..0b9a4e9 100644
--- a/content/theses/metaphysical/interpersonal/self-made-hell.md
+++ b/content/theses/metaphysical/interpersonal/self-made-hell.md
@@ -2,6 +2,7 @@
title: self-made hell
weight: 20
---
+<h1>On self-made hell</h1>
A couple of friends and I know a couple of other people, with whom they used to hang out, that loved to complain about their lives.
diff --git a/content/theses/metaphysical/religious/catholicism.md b/content/theses/metaphysical/religious/catholicism.md
index c2b35c0..02c26ea 100644
--- a/content/theses/metaphysical/religious/catholicism.md
+++ b/content/theses/metaphysical/religious/catholicism.md
@@ -2,6 +2,7 @@
title: catholicism
weight: 350
---
+<h1>On Catholicism</h1>
It is generally affirmed by tradition that, in the Old Testament, the first five Books ---Genesis, Exodus, Levitikon, Numbers, Deuteronomion--- were written by Moses himself, who was granted the authority to do so by God. Following Moses' passing, the rest of the books in the Old Testament were written to describe that acts and words of people chosen by God; the Judges, the Kings, and the Prophets. Finally, in Christianity, the Old Testament is fulfilled in the person of Jesus, the Christ, who established the New Testament.
## authority and tradition
diff --git a/content/theses/metaphysical/religious/demonology.md b/content/theses/metaphysical/religious/demonology.md
index 7ded6cd..534ea3d 100644
--- a/content/theses/metaphysical/religious/demonology.md
+++ b/content/theses/metaphysical/religious/demonology.md
@@ -2,6 +2,7 @@
title: demonology
weight: 150
---
+<h1>On demons</h1>
Satan and the rest of the demons are truly the most tragic beings in existence.
diff --git a/content/theses/metaphysical/religious/judaism.md b/content/theses/metaphysical/religious/judaism.md
index 888c493..3da02dc 100644
--- a/content/theses/metaphysical/religious/judaism.md
+++ b/content/theses/metaphysical/religious/judaism.md
@@ -2,6 +2,7 @@
title: judaism
weight: 300
---
+<h1>On Judaism</h1>
{{% hint info %}}
This page does not presuppose any assumption about the existance of Christ.
diff --git a/content/theses/research/monitoring.md b/content/theses/research/monitoring.md
deleted file mode 100644
index 9d7e2c9..0000000
--- a/content/theses/research/monitoring.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-title: monitoring
-weight: 10
----
-
-The easiest way to set up logging for ai experiments is to use `mlflow`, which is a ready made `python` package.
-
-## installation
-To get started we can add `mlflow` to our project, using reasonable package managers like `poetry` or `uv`
-
-```sh
-$ poetry add mlflow
-```
-
-and then inside our environment we can run
-```sh
-$ mlflow server --host 127.0.0.1
-```
-
-This sets up a web server on `localhost:5000`, which is only accessible via the computer (for local monitoring).
-If you want to make this accessible to other computers (say locally via LAN, or via the internet) use `--host 0.0.0.0`. Just make sure that [you open the proper port in the firewall (by default port 5000)](/self-sufficiency/networking)
-
-{{% hint info %}}
-for example, to serve publicly on port 8889, we run
-```sh
-$ mlflow server --host 127.0.0.1 --port 8889
-```
-{{% /hint %}}
-
-## docker-compose
-In order to use docker and easily handle/manage updates we can create a `docker-compose.yaml`
-```yaml
-services:
- mlflow:
- image: ghcr.io/mlflow/mlflow
- container_name: mlflow
- ports:
- - '5000:5000'
- environment:
- MLFLOW_TRACKING_URI: http://0.0.0.0:5000
- volumes:
- - ./mlflow:/mlflow/mlruns
- restart: always
- command: ["mlflow", "server", "--host", "0.0.0.0", "--port", "5000"]
-```
-This pulls the latest image of `mlflow` from github and sets it to always run so we can access the service from anywhere on port `5000`.
-{{% hint info %}}
-if we want to serve it on port 8889, we need to set `ports: '8889:5000'`
-{{% /hint %}}
-
-## demo
-
-To get a ready-made demo, we will do a basic MNIST setup
-
-```python
-import mlflow
-
-import torch as T
-import torch.nn as nn
-import torch.nn.functional as F
-import torch.optim as optim
-
-from torch.utils.data import DataLoader
-
-from torchvision import datasets
-from torchvision.transforms import ToTensor
-
-train_data = datasets.MNIST(
- root='data',
- train=True,
- transform=ToTensor(),
- download=True
- )
-
-test_data = datasets.MNIST(
- root='data',
- train=False,
- transform=ToTensor(),
- download=True
- )
-
-loaders = {
- 'train': DataLoader(
- train_data,
- batch_size=params['batch_size'],
- shuffle=True,
- num_workers=1
- ),
-
- 'test': DataLoader(
- test_data,
- batch_size=params['batch_size'],
- shuffle=True,
- num_workers=1
- )
-}
-```
-and set up an `ImageClassifier`
-```python
-class ImageClassifier(nn.Module):
-
- def __init__(self):
- super(ImageClassifier, self).__init__()
-
- self.conv1 = nn.Conv2d(1, 10, kernel_size=5)
- self.conv2 = nn.Conv2d(10, 20, kernel_size=5)
- self.conv2_drop = nn.Dropout2d()
- self.fc1 = nn.Linear(320, 50)
- self.fc2 = nn.Linear(50, 10)
-
- def forward(self, x):
- x = self.conv1(x)
- x = F.max_pool2d(x, 2)
- x = F.relu(x)
- x = self.conv2(x)
- x = self.conv2_drop(x)
- x = F.max_pool2d(x, 2)
- x = F.relu(x)
- x = x.view(-1, 320)
- x = self.fc1(x)
- x = F.relu(x)
- x = F.dropout(x, training=self.training)
- x = self.fc2(x)
- return F.softmax(x)
-
-model = ImageClassifier().to(device)
-optimizer = optim.Adam(model.parameters(), lr=params['learning_rate'])
-loss_func = nn.CrossEntropyLoss()
-```
-
-### train/test functions
-Using the [official documentation](https://mlflow.org/docs/latest/tracking/), we can build a tracking experiment
-
-We will need two functions, `train` and `test`:
-```python
-def train(epoch):
- """
- Train the model on a single pass of the dataloader, and send the metrics to mlflow
- """
- model.train()
- for batch_idx, (data, target) in enumerate(loaders['train']):
-
- data, target = data.to(device), target.to(device)
- optimizer.zero_grad()
- output = model(data)
-
- loss = loss_func(output, target)
- loss.backward()
- accuracy = batch_idx/len(loaders['train'].dataset)
-
- optimizer.step()
-
- if batch_idx % 20 == 0:
- print(
- f"Train Epoch: {epoch}, [{
- batch_idx*len(data)
- }/{
- len(loaders['train'].dataset)
- } ({
- 100*batch_idx/len(loaders['train'].dataset):.0f
- }%)]), Loss: {loss}"
- )
-
- loss, current = loss.item(), batch_idx
- step = batch_idx // 20 * (epoch + 1)
- mlflow.log_metric("loss", f"{loss:2f}", step=step)
- mlflow.log_metric("accuracy", f"{accuracy:2f}", step=step)
-
-def test():
- """
- Evaluate the model, and log results with mlflow
- """
- model.eval()
-
- loss = 0
- correct = 0
-
- with T.no_grad():
- for data, target in loaders['test']:
- data, target = data.to(device), target.to(device)
- output = model(data)
- loss += loss_func(output, target).item()
- pred = output.argmax(dim=1,keepdim=True)
- correct += pred.eq(target.view_as(pred)).sum().item()
-
- loss /=len(loaders['test'].dataset)
- accuracy = correct/len(loaders['test'].dataset)
-
- print(
- f"\nTest set: Average Loss: {loss:.4f}, Accuracy: {correct}/{
- len(loaders['test'].dataset)
- } ({
- 100*correct/len(loaders['test'].dataset):.0f
- })\n"
- )
-
- mlflow.log_metric("eval_loss", f"{loss:2f}", step=epoch)
- mlflow.log_metric("eval_accuracy", f"{accuracy:2f}", step=epoch)
-```
-
-### parameter logging
-
-In order to log the hyperparameters so we can reference them during finetuning, we first need to inform the script where our `mlflow` instance is at, and to do this we set
-```python
-mlflow.set_tracking_uri(uri="http://localhost:5000")
-
-mlflow.set_experiment("MNIST mlflow demo")
-```
-{{% hint info %}}
-`set_tracking_uri` points to the `url` we run `mlflow` at. This means that is we run it on `127.0.0.1`, we use `localhost` or `127.0.0.1`. If we set it up as `0.0.0.0`, and the experiment is run outside of the mlflow server (ie another computer), we use the IP that points to that computer; either the LAN IP provided by the router (if we are using a LAN), or the public IP of the server.
-
-`set_experiment` is the name of the experiment inside the mlflow instance, and is used for experiment grouping and comparisons.
-{{% /hint %}}
-
-Now we can define the hyperparameters and log them
-
-```python
-params = {
- "batch_size": batch,
- "learning_rate": lr,
- "num_epochs": epochs
-}
-mlflow.log_params(params)
-```
-
-### the loop
-We are now ready to let the experiment run.
-
-The main training loop needs to run inside the `mlflow` [***context***](https://realpython.com/python-with-statement/)
-
-```python
-with mlflow.start_run():
- for epoch in range(params['num_epochs']):
- train(epoch)
- test()
-```
-and wait.
diff --git a/content/theses/technological/_index.md b/content/theses/technological/_index.md
new file mode 100644
index 0000000..180b379
--- /dev/null
+++ b/content/theses/technological/_index.md
@@ -0,0 +1,5 @@
+---
+title: technological
+weight: 30
+bookCollapseSection: true
+---
diff --git a/content/theses/technological/licensing/NESL.md b/content/theses/technological/licensing/NESL.md
new file mode 100644
index 0000000..ab33cd8
--- /dev/null
+++ b/content/theses/technological/licensing/NESL.md
@@ -0,0 +1,115 @@
+---
+title: nesl
+weight: 20
+---
+{{% hint %}}
+`.txt` found [here](/NESL.txt)
+{{% /hint %}}
+{{% hint %}}
+consider adding a [preamble on your source files](/theses/technological/licensing/nesl_preamble)
+{{% /hint %}}
+
+<h1>Non-Enclosing Software License (NESL)</h1>
+
+<h4>Version 1.0</h4>
+
+## -1. Spirit of the License (Interpretation)
+
+This License exists to prevent the use of software as an instrument of coercion.
+
+In the event of ambiguity or uncertainty in the interpretation of this License, such ambiguity shall be resolved in the manner that most preserves individual autonomy, the ability to act independently, voluntary action, and the absence of involuntary obligation, and least enables coercion, enclosure, or asymmetric control.
+
+This section governs interpretation only and creates no independent rights or obligations.
+
+## 0. Preamble
+
+This License governs the use, modification, and distribution of the Software.
+
+By exercising any rights granted under this License, you accept its terms.
+No party is obligated to exercise any right granted herein.
+
+This License grants permissions only.
+It does not create any duty of use, labor, service, maintenance, support, security response, availability, or continued involvement by any party.
+
+Sublicensing is not permitted by this License. Distribution of the Software is not a grant of a separate sublicense. No distributor may impose additional restrictions or transfer the Software under different terms.
+
+File-level notices are informational only and do not create conditions
+beyond those stated in this License.
+
+## 1. Definitions
+
+- Software: “Software” means the covered work in source or object form, including any portion thereof, and any modification, derivative work, or combination incorporating the covered work.
+
+- Distribute / Distribution: “Distribute” or “Distribution” means any act of conveying the Software, or making its functionality available, to another party, whether or not consideration is exchanged, including but not limited to:
+ - providing copies,
+ - deploying the Software on devices not exclusively controlled by the distributor,
+ - providing access to the Software or its functionality over a network or service,
+ - making the Software available for execution, interaction, or use by third parties.
+
+- Control: “Control” means the ability to determine, restrict, or prevent the conditions under which the Software may be executed, modified, replaced, or continued in use, whether through technical, legal, or contractual means, including control exercised via software, hardware, firmware, boot mechanisms, or execution environments.
+
+- Single Party: “Single Party” means one legal person or any group of legal persons acting in concert or under common control, including but not limited to parents, subsidiaries, affiliates, contractors, or agents, regardless of corporate form or jurisdiction.
+
+- User: “User” means any natural person or legal entity that uses, interacts with, depends upon, or is subject to the behavior of the Software.
+
+## 2. You May Not Take Away Freedoms You Did Not Create
+
+Any Distribution of the Software that results in recipients or Users being unable to exercise the freedoms enumerated below in this Section is prohibited.
+
+In particular, Distribution is prohibited where the distributor or any Single Party retains Control over the Software in a manner that restricts, conditions, or revokes the ability to:
+ 1. use the Software for any purpose,
+ 2. study its operation,
+ 3. modify it,
+ 4. replace it with a modified version,
+ 5. or continue using it independently of the distributor.
+
+Restrictions include, without limitation, technical or legal measures that enforce such Control, including but not limited to digital restrictions management, hardware or firmware enforcement mechanisms, or cryptographic signing requirements controlled by a Single Party.
+
+The freedoms granted by this License include, at minimum, the right to:
+
+- use the Software for any purpose,
+- study how the Software works,
+- modify the Software,
+- distribute the Software and modified versions of the Software.
+
+Any Distributed copy of the Software, modified or unmodified, must include this License in full and remain governed by it.
+
+## 3. No Implied Rights
+
+No contributor, assignee, transferee, or distributor may assert any patent claim owned or controlled by them to restrict, condition, or interfere with the exercise of the permissions and freedoms explicitly granted by this License with respect to the Software.
+
+Except as necessary to give effect to the foregoing limitation, this License grants no rights or licenses under any patent, trademark, or similar intellectual property right.
+
+The Software is provided “as is”, without warranty of any kind, express or implied.
+
+No claim is made that the Software is safe, complete, suitable, or fit for any use.
+Use of the Software is at the sole discretion and risk of the user.
+
+No reliance interest shall be inferred from the use or availability of the Software.
+
+Nothing in this License shall be interpreted to create any implied guarantee, entitlement, or right.
+
+## 4. No Implied Obligations
+
+No author, contributor, or upstream party assumes any obligation by virtue of authorship, contribution, publication, or distribution of the Software.
+
+The creation, release, or distribution of the Software does not constitute an offer of maintenance, support, updates, security review, coordination, or continued availability.
+
+Any labor, service, or ongoing involvement related to the Software exists only by explicit, voluntary agreement.
+Absent such agreement, no duty—whether contractual, moral, customary, or implied—shall be inferred.
+
+Requests for labor, including requests relating to defects or security issues, are requests only and create no obligation.
+
+## 5. License Versions
+
+This Software is licensed under Version 1.0 of the License or, at the option of any recipient, any later version of this License.
+
+Any Distribution of the Software shall preserve this option and shall not restrict the ability of recipients to apply a later version of this License.
+
+Later versions of this License shall be revisions that preserve the fundamental principles stated in Section 0 and the freedoms enumerated in Section 1.
+
+## 6. Non-Expansion and Severability
+
+No interpretation of this License may be used to create obligations, duties, or restrictions not explicitly stated herein.
+
+If any provision of this License is held unenforceable, the remaining provisions shall remain in effect.
diff --git a/content/theses/technological/licensing/_index.md b/content/theses/technological/licensing/_index.md
new file mode 100644
index 0000000..a707997
--- /dev/null
+++ b/content/theses/technological/licensing/_index.md
@@ -0,0 +1,5 @@
+---
+title: licenses
+weight: 10
+bookCollapseSection: true
+---
diff --git a/content/theses/technological/licensing/nesl_preamble.md b/content/theses/technological/licensing/nesl_preamble.md
new file mode 100644
index 0000000..10b6e9e
--- /dev/null
+++ b/content/theses/technological/licensing/nesl_preamble.md
@@ -0,0 +1,31 @@
+---
+title: nesl preamble
+weight: 100
+---
+
+# Long preamble for NESL
+
+This file is part of a project governed by the Non-Enclosing
+Software License (NESL).
+
+You are free to use, study, modify, and distribute this file and
+derivative works under the terms of the NESL v1.0 or any later version.
+
+No distributor or intermediary may impose technical, legal, or
+contractual controls that prevent recipients from exercising these
+freedoms.
+
+No user, distributor, or intermediary may infer, claim, or impose any
+obligation, duty, support, maintenance, or continued involvement from
+the authors, contributors, or upstream parties by virtue of the use or
+distribution of this file.
+
+See the LICENSE file for full terms.
+
+--------
+# Short preamble for NESL
+
+Governed by the Non-Enclosing Software License (NESL),
+Version 1.0 or later.
+
+
diff --git a/content/theses/technological/licensing/philosophy.md b/content/theses/technological/licensing/philosophy.md
new file mode 100644
index 0000000..e006311
--- /dev/null
+++ b/content/theses/technological/licensing/philosophy.md
@@ -0,0 +1,65 @@
+---
+title: philosophy
+weight: 10
+---
+<h1>Personal philosophy on software licensing</h1>
+
+It is well understood that free and open source software (*libre* software) stands for freedom as in "free speech", not as in "free beer". More specifically, free software is defined as any software that guarantees these four freedoms
+
+- The freedom to use the program for any purpose.
+- The freedom to study how the program works, and change it to make it do what you wish.
+- The freedom to redistribute and make copies so you can help your neighbor.
+- The freedom to improve the program, and release your improvements (and modified versions in general) to the public, so that the whole community benefits.
+
+These four freedoms guarantee that the *user* can make a fully informed choice; given they, or someone else, has knowledge of programming, they may study the code, and obtain full knowledge of how the software works.
+
+This, however, means that the code itself must be accessible, which comes with the implicit consequence that somebody well versed in programming might get the code, and use the software as they may, *without* paying. In this sense a consequence of free (*libre*)[^1] software (or rights-preserving software) is also *gratis* software (or zero-cost software).
+
+For the above reason, *libre* software has been massively adopted by programming communities; not only does it liberate the user by ensuring that they may make a choice based on full information, it also provides extra securities; rather than needing to place trust on the developer(s), you can trust the product itself. Security bugs and issues are found more easily, because more people are looking over the code, and the project is, in theory, constantly being audited; the project may organically grow because people take a natural interest in it, and become a communal effort rather than a personal one.
+
+It also is seen as a collectivising movement. Since the implication is that *libre* software has to provide access to the full source code for the four freedoms to be upheld, the implication of the capacity of others to use said code *without providing any financial compensation* means that businesses are typically disincentivised from using or creating *libre* software. Governments and other bad faith actors also typically prefer to make or use proprietary software, since making and using *libre* software would leave their misdeeds exposed.
+
+For this reason a more "lenient" software movement rose to prominence, that of *open source* software, which is also called *permissive*, because it permits the developer more freedoms, at the expense of the freedoms of the user[^2]. Open source software, although it does provide the user some freedoms, mostly cares for the developer experience, and the end-user is secondary[^3].
+
+This in turn allowed corporations to see open-source software in a more friendly light, and reinforced the idea that there is an ideological and political distinction between *open-source* vs *libre* software; open-source is typically seen as corporate-friendly and capitalistic, whilst *libre* software is considered the collectivist/communist/anarchist option. If we look at this from a classical liberal viewpoint however, we might see a different story, and realise that *libre* software is the foundation of a free market of software.
+
+## legal plunder and lawful defence
+In 1850, French economist Frederic Bastiat[^4] wrote a book called The Law[^5], in which he tries to argue that the rule of the Law is to guarantee and preserve the rights of the majority. In his argument, he says that since the government is comprised of people, then the government itself has no more rights than those that people individually have; the rights to life, to liberty, and to property.[^6]
+
+> *"Life, liberty, and property do not exist because men have made laws. On the contrary, it was the fact that life, liberty, and property existed beforehand that caused men to make laws in the first place. What, then, is law? As I have said elsewhere, it is the collective organization of the individual right to lawful defense."*
+
+In this regard, the role of government is exclusively to protect these very rights; anything that the government does that goes beyond the simple task of protecting the rights of the people is a degeneration of the law.
+
+> *"The law has placed the collective force at the disposal of the unscrupulous who wish, without risk, to exploit the person, liberty, and property of others. It has converted plunder into a right, in order to protect plunder. And it has converted lawful defense into a crime, in order to punish lawful defense."*
+
+We see in the above quote the root of the matter; lawful defence, insofar as it is defence that does not remove from the rights of others, is being subverted, in favour of plunder, so that others may exploit the individual, as well as the property of the individual, and in doing so reduce the capacities of the individual to exercise their liberty. In this sense, legal plunder, as Bastiat calls it, is nothing more than the erosion of the rights of the individual for the benefit of another, and because the law ends up perverted by the very people who seek to erode the liberties of others, lawful defence is seen as a detriment, and oftentimes opposing plunder is made illegal.
+
+## copyleft
+It is on this that *libre* software takes a stand, where the open-source movement doesn't; *libre* software acts as an extension of good law; it protects and reinforces the rights of the user. Meanwhile *non-libre* software aims to plunder the user; it deducts from the user's rights.
+
+The way the rights are preserved is through a type of license called *copyleft*, called so because it forces not only the developer to provide the entirety of the project in a way that respects user freedom, but also any other developer who might build upon it and make their own modifications and distributions of the software. In essence it forces, in a viral way, all derived software to be as respectful of the user's rights as the original version. It promotes user freedom at the detriment of the developer.
+
+> *"[...]
+>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:
+>[...]
+>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.
+>[...]"*
+
+## example of non-copyleft abuse
+In order to see why *copyleft* is so important to the preservance of user freedom, and how *libre* software acts as an extension of the righteous purpose of the law, as per classical liberalism, and why *open-source* and proprietary software permits legal plunder, I need to quote a very strong historical example.
+
+> MINIX is an operating system first released in 1987 by Andrew S. Tanenbaum, as an open-source clone of the Unix operating system, specifically targeted at low-power devices. Because it was licensed with an open-source license without a *copyleft* provision, a company, namely Intel, copied the code (ie *forked* in the proper terminology) and developed their own derivative operating system. Due to the lack of any *copyleft* clause that would force Intel to respect user freedom, by allowing the users to study and/or modify their derivative work, nobody, apart from the engineers that maintain it, know exactly what it does and how it works. The issue arises from the fact that this custom version of the MINIX operating system is run on the *Intel ME*, which is a small chip that exists in *every* Intel CPU for the past twenty years, and this operating system has *full* access to everything that happens inside of a computer that includes it. This includes the capability to control the computer; even if the computer is turned off, as long as it is connected to a power source (e.g. an outlet or a battery), it may even turn the computer on *without* user knowledge or consent. This control over the user system, alongside the inability of the user to study the MINIX operating system running inside of Intel ME, is enough of a reason to call it *malware* or *spyware*. It is a piece of code that is running without the user being able to give explicit and informed consent, and most of the time without even the user's knowledge. It is legal plunder.[^7]
+
+It is exactly this form of plunder that *copyleft* in *libre* software prevents, and in doing so creates a unique and interesting dynamic.
+
+## the free market of software
+Exactly because it allows the user the maximal freedom, i.e. the ability to make fully informed consensual decisions concerning the software they wish to use, it forms the foundation of a free market of software; the voluntary exchange of goods and services. In classical liberalism, the term *market* is not restricted to use only in the exchange of goods for currency, but also includes any voluntary exchange of ideas and services, in a non-interventionist, fully decentralized manner. Besides, the concept of a free market does not axiomatically carry a preferred method of transaction; monetary exchanges, cryptocurrencies, barter, donations, everything is appropriate, with the only prerequisite being that an exchange is conducted on a voluntary premise for all participants, which necessitates transparency and full knowledge of the good or service provided; a free market of software *requires copyleft* in order to exist, and *copyleft* cannot function outside of a free market.
+
+[^1]: *free* software is an extemely poor choice of wording in my opinion, because it confuses the notion of freedom, with the notion of zero monetary costs. The distinction is why *libre* software has historically been used to denote free software as in freedom, and why *freeware* has been associated with zero-monetary cost.
+[^2]: Because of this, I tend to call "permissive" licenses "restrictive". They restrict the user's freedoms.
+[^3]: The difference is mainly ethical/moral, however there is open-source software that is *not* libre.
+[^4]: 1801-1850
+[^5]: You can find a free copy [here](https://cdn.mises.org/thelaw.pdf)
+[^6]: I am slowly compiling my own notes on the subject matter; you can find part of my viewpoint [here](https://notes.aethrvmn.gr/metaphysical/interpersonal/abilities)
+[^7]: This specific example is the most egregious one *that we know of*, and has given rise to the term [*cuck license*](https://lukesmith.xyz/articles/why-i-use-the-gpl-and-not-cuck-licenses/) for non *copyleft*, open-source licenses.
diff --git a/content/theses/research/_index.md b/content/theses/technological/research/_index.md
index 7e23064..7e23064 100644
--- a/content/theses/research/_index.md
+++ b/content/theses/technological/research/_index.md
diff --git a/content/theses/research/arc-agi/_index.md b/content/theses/technological/research/arc-agi/_index.md
index 89585e6..89585e6 100644
--- a/content/theses/research/arc-agi/_index.md
+++ b/content/theses/technological/research/arc-agi/_index.md
diff --git a/content/theses/research/arc-agi/approach.md b/content/theses/technological/research/arc-agi/approach.md
index 3745b68..4b034a0 100644
--- a/content/theses/research/arc-agi/approach.md
+++ b/content/theses/technological/research/arc-agi/approach.md
@@ -2,6 +2,8 @@
title: approach
weight: 20
---
+<h1>My Approach</h1>
+
My idea is to use my [`alectors`](https://docs.apotheke.earth/alectors) library to parse the JSON as tokens, as standard LLM approaches do, but because it is a pure RL library, it is a *markov decision process* not a *markov chain*.
## observation space
diff --git a/content/theses/research/arc-agi/introduction.md b/content/theses/technological/research/arc-agi/introduction.md
index ea7e06e..1872a1b 100644
--- a/content/theses/research/arc-agi/introduction.md
+++ b/content/theses/technological/research/arc-agi/introduction.md
@@ -2,6 +2,7 @@
title: introduction
weight: 10
---
+<h1>Introduction to ARC-AGI</h1>
[ARC-AGI-2](https://arcprize.org) is a competition regarding pattern recognition for machine learning algorithms.
Directive (EU) 2019/790, Article 4(3); all rights regarding Text and Data Mining (TDM) are reserved.