Reformat and fixup old blog posts
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 46 KiB |
Before Width: | Height: | Size: 34 KiB |
|
@ -11,7 +11,7 @@ Hello there, everyone! This is a celebratory post as today we are celebrating th
|
||||||
|
|
||||||
This news comes with the arrival of our Swift, C and C# tutorials. We hope that our popularity continues to grow. But, for now, let's celebrate and rejoice! We're going up in the world.
|
This news comes with the arrival of our Swift, C and C# tutorials. We hope that our popularity continues to grow. But, for now, let's celebrate and rejoice! We're going up in the world.
|
||||||
|
|
||||||
[![](images/Celebration-300x300.png)](http://www.ethanjmarshall.co.uk/wp-content/uploads/2018/06/Celebration.png)
|
![Celebrate](celebration.png)
|
||||||
|
|
||||||
We hope you continue to visit and enjoy our content here on ethanjmarshall.co.uk. Please share you messages below if you want to show your support. Thanks!
|
We hope you continue to visit and enjoy our content here on ethanjmarshall.co.uk. Please share you messages below if you want to show your support. Thanks!
|
||||||
|
|
||||||
|
|
Before Width: | Height: | Size: 84 KiB |
Before Width: | Height: | Size: 279 KiB |
|
@ -3,7 +3,6 @@ title: "Don't be like me with GPG"
|
||||||
date: "2020-12-19"
|
date: "2020-12-19"
|
||||||
categories:
|
categories:
|
||||||
- Old Blog
|
- Old Blog
|
||||||
coverImage: "key-2114459_640.png"
|
|
||||||
---
|
---
|
||||||
|
|
||||||
Ah, public key cryptography; where would we be without you? I mean, probably somewhere at least, but nowhere near where we are technically today.
|
Ah, public key cryptography; where would we be without you? I mean, probably somewhere at least, but nowhere near where we are technically today.
|
||||||
|
|
BIN
content/blog/old/2020/me-and-my-dad/dad.jpg
Normal file
After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 70 KiB |
|
@ -1,11 +1,12 @@
|
||||||
---
|
---
|
||||||
title: "Me and My Dad: Positive Memories"
|
title: "Me and My Dad"
|
||||||
date: "2020-12-19"
|
date: "2020-12-19"
|
||||||
categories:
|
categories:
|
||||||
- Old Blog
|
- Old Blog
|
||||||
coverImage: "Dad.jpg"
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
![My Dad](dad.jpg)
|
||||||
|
|
||||||
It is a pretty special thing to be able to think back on your time with a person and to have no negative memories of them whatsoever come to mind. In fact, some would say that this is an impossible feat; something which cannot possibly be done by any functioning person.
|
It is a pretty special thing to be able to think back on your time with a person and to have no negative memories of them whatsoever come to mind. In fact, some would say that this is an impossible feat; something which cannot possibly be done by any functioning person.
|
||||||
|
|
||||||
My dad was living proof that this is not the case.
|
My dad was living proof that this is not the case.
|
||||||
|
|
Before Width: | Height: | Size: 94 KiB |
Before Width: | Height: | Size: 58 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 76 KiB |
Before Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 96 KiB |
Before Width: | Height: | Size: 668 KiB |
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
@ -5,6 +5,8 @@ categories:
|
||||||
- Old Blog
|
- Old Blog
|
||||||
---
|
---
|
||||||
|
|
||||||
|
![CPP in a nutshell](cpp-nutshell.png)
|
||||||
|
|
||||||
C++ is not exactly known for its elegant syntax or concise expressiveness. It is a pretty common joke to hear in the programming world that "C++ is the only language where the error message may actually be longer than the program that caused it". Now, be that as it may, I think its more accurate to say that "C++ is the only language where the symbol name will be longer than the program that uses it". Take the following example:
|
C++ is not exactly known for its elegant syntax or concise expressiveness. It is a pretty common joke to hear in the programming world that "C++ is the only language where the error message may actually be longer than the program that caused it". Now, be that as it may, I think its more accurate to say that "C++ is the only language where the symbol name will be longer than the program that uses it". Take the following example:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
Before Width: | Height: | Size: 49 KiB |
Before Width: | Height: | Size: 130 KiB |
Before Width: | Height: | Size: 129 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 1.7 MiB |
|
@ -5,6 +5,8 @@ categories:
|
||||||
- Old Blog
|
- Old Blog
|
||||||
---
|
---
|
||||||
|
|
||||||
|
![Maple Leaf Rag](mlr.jpg)
|
||||||
|
|
||||||
It is very rare in the world of music that you come across something which you believe to be totally perfect. A piece which is so wonderfully intricate and yet to perfectly easy to listen to that you daren't change a single note, as that may upset the balance and ruin it. At least, for me, it was particularly rare until I re-discovered the undisputed king of ragtime: Scott Joplin.
|
It is very rare in the world of music that you come across something which you believe to be totally perfect. A piece which is so wonderfully intricate and yet to perfectly easy to listen to that you daren't change a single note, as that may upset the balance and ruin it. At least, for me, it was particularly rare until I re-discovered the undisputed king of ragtime: Scott Joplin.
|
||||||
|
|
||||||
Scott Joplin's music is not only iconic, but it has lasted hundreds of years. The Maple Leaf Rag (one of his more famous pieces) was first published in 1899, and yet it is still one of the best known pieces of ragtime ever written.
|
Scott Joplin's music is not only iconic, but it has lasted hundreds of years. The Maple Leaf Rag (one of his more famous pieces) was first published in 1899, and yet it is still one of the best known pieces of ragtime ever written.
|
||||||
|
|
BIN
content/blog/old/2021/scott-joplin-genius/mlr.jpg
Normal file
After Width: | Height: | Size: 127 KiB |
Before Width: | Height: | Size: 406 KiB |
Before Width: | Height: | Size: 200 KiB |
Before Width: | Height: | Size: 160 KiB |
Before Width: | Height: | Size: 290 KiB |
|
@ -3,7 +3,6 @@ title: "Public Emails for Paranoid UNIX Users"
|
||||||
date: "2022-03-13"
|
date: "2022-03-13"
|
||||||
categories:
|
categories:
|
||||||
- Old Blog
|
- Old Blog
|
||||||
coverImage: "more-spam-1.png"
|
|
||||||
---
|
---
|
||||||
|
|
||||||
I have been dealing with spam on my public email address for quite some time now, and it finally got to the peak of my patience with the the following email, sent to my email not so long ago:
|
I have been dealing with spam on my public email address for quite some time now, and it finally got to the peak of my patience with the the following email, sent to my email not so long ago:
|
||||||
|
@ -48,7 +47,7 @@ However, these obfuscated mailing addresses gave me an idea. How were the spamme
|
||||||
|
|
||||||
Now, I have heard from the AUR maintainers that some spammers are starting to realise of this common obfuscation method and attempt to decode it properly. So, I added an extra layer of obfuscation - the sed layer. At the end of the email pipeline, you will see something which looks like this:
|
Now, I have heard from the AUR maintainers that some spammers are starting to realise of this common obfuscation method and attempt to decode it properly. So, I added an extra layer of obfuscation - the sed layer. At the end of the email pipeline, you will see something which looks like this:
|
||||||
|
|
||||||
```
|
```bash
|
||||||
| sed 's/com.au/co.uk/'
|
| sed 's/com.au/co.uk/'
|
||||||
```
|
```
|
||||||
|
|
||||||
|
@ -56,7 +55,7 @@ All this is doing is substituting the fake domain registrar ".com.au" for the re
|
||||||
|
|
||||||
This process also helps to eliminate non-UNIX users from being able to email me. As mentioned in the contact page, people who claim that they use WSL occasionally still slip through the net. This is a problem I need to solve, and I do have an idea, From personal experience, I know that neither WSL 1 nor 2 implement direct packet access. So, simple programs like **ping(8)** will completely fail. So, I could just add:
|
This process also helps to eliminate non-UNIX users from being able to email me. As mentioned in the contact page, people who claim that they use WSL occasionally still slip through the net. This is a problem I need to solve, and I do have an idea, From personal experience, I know that neither WSL 1 nor 2 implement direct packet access. So, simple programs like **ping(8)** will completely fail. So, I could just add:
|
||||||
|
|
||||||
```
|
```bash
|
||||||
ping -c1 ethanjmarshall.co.uk >/dev/null 2>&1 && ( <rest of pipeline> )
|
ping -c1 ethanjmarshall.co.uk >/dev/null 2>&1 && ( <rest of pipeline> )
|
||||||
```
|
```
|
||||||
|
|
||||||
|
@ -68,7 +67,7 @@ In any case, this simple method has reduced my volume of spam by at least two th
|
||||||
|
|
||||||
_Check your compliance with Based_™_ UNIX-ism with the following simple script:_
|
_Check your compliance with Based_™_ UNIX-ism with the following simple script:_
|
||||||
|
|
||||||
```
|
```bash
|
||||||
#!/bin/sh
|
#!/bin/sh
|
||||||
asdfg() {
|
asdfg() {
|
||||||
return "this should cause an error"
|
return "this should cause an error"
|
||||||
|
|
Before Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 283 KiB |
|
@ -4,14 +4,14 @@
|
||||||
{{ .Content }}
|
{{ .Content }}
|
||||||
</header>
|
</header>
|
||||||
|
|
||||||
{{ range .Pages }}
|
{{ range where .Pages "Kind" "page" }}
|
||||||
<article class="post">
|
<article class="post">
|
||||||
<header class="post__header">
|
<header class="post__header">
|
||||||
<h1><a href="{{ .Permalink }}">{{ .Title | markdownify }}</a> -- {{ .Date.Format "2 January 2006" }}</h1>
|
<h1><a href="{{ .Permalink }}">{{ .Title | markdownify }}</a> -- {{ .Date.Format "2 January 2006" }}</h1>
|
||||||
</header>
|
</header>
|
||||||
|
|
||||||
<section class="post__summary">
|
<section class="post__summary">
|
||||||
{{ .Summary }}
|
{{ .Description }}
|
||||||
</section>
|
</section>
|
||||||
</article>
|
</article>
|
||||||
{{ end }}
|
{{ end }}
|
||||||
|
|