feat: flame on

9 files changed, 284 insertions, 114 deletions

diff --git a/content-org/blog.org b/content-org/blog.org
index c48539b..f878e37 100644
--- a/content-org/blog.org
+++ b/content-org/blog.org
@@ -8,7 +8,7 @@
 #+HUGO_SECTION: blog
 
 
-* 2024  [80/82]                                                       :@blog:
+* 2024  [82/84]                                                       :@blog:
 :PROPERTIES:
 :EXPORT_HUGO_SECTION: blog/2024
 :EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :image_dir "blog/images" :image_max_width 600
@@ -69,37 +69,169 @@ Love you, Drew!
 
 https://www.youtube.com/watch?v=7OsWuFo2jp4
 
-** Microsoft GitHub on Open Source 
-
-Me, like many others, were lured into (non-MS) GitHub years ago.
+** Microsoft GitHub and Open Source 
+I, like many others, were lured into (non-MS) GitHub years ago.
 It was nicer than the entire competition - it worked better, it looked better, it was where *all* the Open Source lived.
 Well, not all.
 But it was standard for any new project to begin with creating a GitHub repository.
 
-But is stil a good idea?
+But is still a good idea?
 I don't think so.
 In fact, I think that Microsoft GitHub is the single worse place for Open Source to live.
 
-Funny think is, that only one thing changed - the owner.
-Microsoft, past-Balmmer era, in their "pro-open source" phase (mon! it's not a phase!) bought the single most important place for software.
+Funny thing is, that only one thing changed - the owner.
+Microsoft, in their past-Ballmer era, in their "pro-open source" phase (mom! It's not a phase!) bought the single most important place for software.
 Not only software development, but software in general.
-It is near impossible to use sotware without thouching something that was stored on Microsoft Github.
+It is near impossible to use software without touching something that was stored on Microsoft GitHub.
 
 But, let's face it, Microsoft hasn't changed one bit.
-They may own Thorvald's soul and body but they are still actively against Open Source.
+They may own Torvald's soul and body, but they are still actively against Open Source.
 
 Why do *care* about Open Source?
 It's not a popularity contest, it's a bullet point in CV.
-Open Souce is based on community, as groups of people who have nothing in common, join forces to create something.
+Open Source is based on community, as groups of people who have nothing in common, join forces to create something.
 They may come from different backgrounds, location, believes, and so on.
 The one thing that connect them, is this project they are developing.
+Open Source is built on the idea of free access to the source code and access to modify it, ergo anyone can work on it.
 
 (non-MS) GitHub was great for it.
 You had all the developers out there.
 You could collaborate with the entire world!
 GitHub was a great place to share code.
 
-But Microsoft Github is anythihg but that.
+But Microsoft GitHub is going in the other direction.
+To make any change to a forge-based repository, one needs some kind of authentication.
+It would be dangerous to allow anyone to change the code.
+To participate in GitHub one needs an GitHub account.
+It was always shady, but now one needs to give personal data to Microsoft.
+This alone should be a red flag.
+To help develop an Open-Source project, you need to ask Microsoft to allow that.
+Account can be revoked at any moment, repository can be deleted without prior notice.
+Microsoft GitHub is a mean to, de-facto, own Open-Source ecosystem.
+You can't suggest change or inform maintainers about a problem without this account.
+
+I hate to say it, but for cooperation nothing comes close to [[https://sourcehut.org/][Source Hut]].
+There is only one (AFAIK) big, open forge which allows anyone with an email account to participate.
+You can send patches via email, and the maintainers can process solely using email.
+
+Microsoft GitHub even started making it harder to use for people who don't want to give their data to Redmond by disabling search for visitors.
+When you encounter a bug, you go to the source - it's obvious.
+But now you need to clone it locally.
+It's small annoyance, but it shows the general direction.
+
+Microsoft GitHub is still not near the biggest sin an Open Source can commit when it comes to cooperation (that crown still goes to using Discord), but it's far from being "Open".
+
+
+** DONE FLAME ON: web
+CLOSED: [2024-10-19 Sat 23:38]
+:PROPERTIES:
+:EXPORT_FILE_NAME: flame-on-web
+:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Abstract Another part of me rambling on email
+:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Listening Miles Davis - Kind of Blue
+:END:
+
+Speaking of the [[https://www.ietf.org/rfc/rfc1855.txt][RFC1855]] I've [[/blog/2024/email-again/][yesterday]], the idea of "flame" is a bit lost on us.
+Let me give you a few short snippets from that guide:
+
+1:
+#+begin_quote
+A good rule of thumb:  Be conservative in what you send and
+      liberal in what you receive.  You should not send heated messages
+      (we call these "flames") even if you are provoked.  On the other
+      hand, you shouldn't be surprised if you get flamed and it's
+      prudent not to respond to flames.
+#+end_quote
+
+2:
+#+begin_quote
+Wait overnight to send emotional responses to messages.  If you
+      have really strong feelings about a subject, indicate it via
+      FLAME ON/OFF enclosures.  For example:
+      FLAME ON:  This type of argument is not worth the bandwidth
+                 it takes to send it.  It's illogical and poorly
+                 reasoned.  The rest of the world agrees with me.
+      FLAME OFF
+#+end_quote
+
+3:
+#+begin_quote
+Don't get involved in flame wars.  Neither post nor respond
+      to incendiary material.
+#+end_quote
+
+Image if we, as the global village, followed those rules.
+There would be no Twitter, not social media.
+There would be much less news sites, as those feed on anger.
+The web would great - it would the antithesis of our current social status-quo.
+
+It seems that breaking the first rule one is expected.
+There are subject and names in the Open Source community alone, that have a 90% chance of starting a small flame.
+And this is a very small community!
+There are touchy subjects all around!
+
+Now, the only social media I partake is [[https://mastodon.bsd.cafe/@mms][mastodon]] which is full of nice people.
+But even there I fell into trap of typing something stupid just to get some attention.
+
+So, I for one, am starting to follow RFC1885 in my everyday life.
+No more starting flames, or partaking in them.
+But if still feel the urge, I will use the =FLAME ON=/=FLAME OFF= enclosures as those are so freaking cool.
+
+btw - have you noticed the "wait over night" part?
+It was expected to wait and think of response.
+Magical times /man/, magical.
+
+
+
+** DONE Email, again
+CLOSED: [2024-10-18 Fri 23:28]
+:PROPERTIES:
+:EXPORT_FILE_NAME: email-again
+:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Abstract Another part of me rambling on email
+:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Listening Miles Davis - Kind of Blue
+:END:
+
+One of the things I am seeing up again is my email system.
+I like calling it a system, but basically it's just [[/emacs/notmuch/][a very standard mbsync(1) + notmuch(1)]] combo.
+But this puts me in the vanguard of email fantastic.
+Nothing fancy, just basic stun *which works*.
+I am therefore the only person who loves using email I know in meat-space.
+
+And I think I know there reason why:
+
+#+begin_quote
+
+In the past, the population of people using the Internet had "grown
+   up" with the Internet, were technically minded, and understood the
+   nature of the transport and the protocols.  Today, the community of
+   Internet users includes people who are new to the environment.  These
+   "Newbies" are unfamiliar with the culture and don't need to know
+   about transport and protocols. In order to bring these new users into
+   the Internet culture quickly, this Guide offers a minimum set of
+   behaviors which organizations and individuals may take and adapt for
+   their own use.
+
+   -- [[https://www.ietf.org/rfc/rfc1855.txt][rfc1855]]
+#+end_quote
+
+The above is from RFC definite netiquette guidelines.
+Yup, the thing we heard about since we were in our win-modem age was an official guideline.
+
+It's from 1995 and yet we learn that people are new to the web and may not know how to use it.
+Email is an old protocol, it was created for a much smaller internet, less hostile one.
+It expects users to own their communication - to learn the tools, and the tribe culture.
+Is very much like Usenet in that matter.
+To use it properly, one should study it.
+
+People don't study things anymore.
+They expect instant feed of memes, not a long text.
+There are people who love the long text (present company included, I assume), but we are not the norm.
+An everyday, normal guy doesn't know that nothing comes close to scripting capabilities of email.
+He doesn't care that it's one of the very few things one is capable of owning on the inter-webs.
+For them email is that old thing where notifications and spam live.
+
+Email is an elegant tool for more civilized times, and as that it requires our special attention.
+It needs love, it needs usage.
+No one else will give it, especially not people forced to use terrible clients, like Gmail or Outlook.
 
 
 ** DONE New Mastodon server
@@ -109,6 +241,7 @@ CLOSED: [2024-10-17 Thu 21:16]
 :EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Abstract I had to change server
 :END:
 
+
 There's a lot of hostilty on the web.
 It seems that it's worse than it's ever been.
 The creator of emacs.ch Mastodon server, which I loved to be part of, was subjected to attacks and doxing.
@@ -128,37 +261,21 @@ CLOSED: [2024-10-16 Wed 22:28]
 :EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Listening Steve Kirk -  Thimbleweed Park (Original Soundtrack) 
 :EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :Listening_url https://thimbleweedpark.bandcamp.com/album/thimbleweed-park-original-soundtrack
 :END:
-A very short update: last week I broke my computer.
-FreeBSD did its best, but my sheer stupidity wouldn't listen.
 
-I updated my ZFS, which worked fine.
-It informed me info about potentially needing to update my bootloader, but what the hell.
-I'll have time for it later!
 
-Later was when I forgot about that and rebooted my system.
-"ReBOOTING" is not the correct word, as it was not booting.
-FreeBSD was starting, but it could not find any bootable partition.
-They warned me, but I didn't listen.
+A very short update: last week I broke my computer. FreeBSD did its best, but my sheer stupidity wouldn't listen.
+
+I updated my ZFS, which worked fine. It informed me info about potentially needing to update my bootloader, but what the hell. I'll have time for it later!
 
-After two evenings of trying to fix it (I still think it's possible), I gave up.
-I downloaded  =GhostBSD=, mounted my ZFS datasets (the problem was not with them, but with booting up), created a small =tar= backup which I moved to my NAS.
-Then, making sure I had the backup, I reinstalled the system as fresh.
+Later was when I forgot about that and rebooted my system. "ReBOOTING" is not the correct word, as it was not booting. FreeBSD was starting, but it could not find any bootable partition. They warned me, but I didn't listen.
 
-About that backup, well.
-For one, I had stuff I didn't want to lose, but I had yet to add any external storage, like git server.
-Not a smart move on my side.
-Good thing, that =ZFS= is designed to be moron-resilient.
-The other part is that my =tar= command didn't include ~dotfiles~, and I never bothered to back those as well.
-My =GNUS= state is lost, never to be recovered ever again.
+After two evenings of trying to fix it (I still think it's possible), I gave up. I downloaded GhostBSD, mounted my ZFS datasets (the problem was not with them, but with booting up), created a small tar backup which I moved to my NAS. Then, making sure I had the backup, I reinstalled the system as fresh.
 
-But the upside here is that I am much more experienced local-admin than I was when I first moved to =FreeBSD=.
-Setup when smooth like butter.
-Real butter.
+About that backup, well. For one, I had stuff I didn't want to lose, but I had yet to add any external storage, like git server. Not a smart move on my side. Good thing, that ZFS is designed to be moron-resilient. The other part is that my tar command didn't include dotfiles, and I never bothered to back those as well. My GNUS state is lost, never to be recovered ever again.
 
-I used this occasion to move this site to my server & create the next iteration.
-I'm still evolving, but backwards.
-What you are seeing here is, of course, a work in progress.
+But the upside here is that I am much more experienced local-admin than I was when I first moved to FreeBSD. Setup when smooth like butter. Real butter.
 
+I used this occasion to move this site to my server & create the next iteration. I'm still evolving, but backwards. What you are seeing here is, of course, a work in progress.
 
 ** DONE Yey USA!
 CLOSED: [2024-10-16 Wed 00:10]
diff --git a/content/_index.md b/content/_index.md
deleted file mode 100644
index 0721a0e..0000000
--- a/content/_index.md
+++ /dev/null
@@ -1,48 +0,0 @@
-+++
-title = "Cool Emacs"
-author = ["Michał Sapka"]
-date = 2024-06-15T21:52:00+02:00
-categories = ["emacs"]
-draft = false
-weight = 2001
-image_dir = "emacs"
-image_max_width = 480
-primary_menu = "emacs"
-shortname = "Cool usages of Emacs"
-[menu]
-  [menu.emacs]
-    weight = 2001
-    identifier = "cool-emacs"
-    post = "Emacs usage that is not text editing"
-+++
-
-{{< image forced_width="350" class="right no-border" alt="An Emacs logo in cool glassess doing a skateboard flip" file="cool-macs.png" >}}
-noop
-{{< /image >}}
-
-> _Let me tell you: Emacs is not a text editor._
->
-> -- Emerald McS., PhD
-
-Even though most of what Emacs is known for is _editing text_, it can do so much more.
-It's the most flexible application out there, so when you start to adjust the basics for yourself, you want to use it everywhere.
-Here, I will present _Emacs_ as a general purpose interface.
-
-
-## Cool ways to use Emacs {#cool-ways-to-use-emacs}
-
-{{< menu "cool-emacs-ways" >}}
-Dune
-{{< /menu >}}
-
-
-## Appendix {#appendix}
-
-{{< menu "cool-emacs-appendix" >}}
-Dune
-{{< /menu >}}
-
-
-## Coolmacs {#coolmacs}
-
-The mascot, Coolmacs, was drawn by [Drew](https://drewsh.com/).
diff --git a/content/blog/2024/broken-system.md b/content/blog/2024/broken-system.md
index 8cde9c4..9c93065 100644
--- a/content/blog/2024/broken-system.md
+++ b/content/blog/2024/broken-system.md
@@ -4,7 +4,7 @@ author = ["Michał Sapka"]
 date = 2024-10-16T22:28:00+02:00
 categories = ["blog"]
 draft = false
-weight = 2001
+weight = 2003
 image_dir = "blog/images"
 image_max_width = 600
 Abstract = "I am not a smart person"
@@ -12,33 +12,16 @@ Listening = "Steve Kirk -  Thimbleweed Park (Original Soundtrack)"
 Listening_url = "https://thimbleweedpark.bandcamp.com/album/thimbleweed-park-original-soundtrack"
 +++
 
-A very short update: last week I broke my computer.
-FreeBSD did its best, but my sheer stupidity wouldn't listen.
+A very short update: last week I broke my computer. FreeBSD did its best, but my sheer stupidity wouldn't listen.
 
-I updated my ZFS, which worked fine.
-It informed me info about potentially needing to update my bootloader, but what the hell.
-I'll have time for it later!
+I updated my ZFS, which worked fine. It informed me info about potentially needing to update my bootloader, but what the hell. I'll have time for it later!
 
-Later was when I forgot about that and rebooted my system.
-"ReBOOTING" is not the correct word, as it was not booting.
-FreeBSD was starting, but it could not find any bootable partition.
-They warned me, but I didn't listen.
+Later was when I forgot about that and rebooted my system. "ReBOOTING" is not the correct word, as it was not booting. FreeBSD was starting, but it could not find any bootable partition. They warned me, but I didn't listen.
 
-After two evenings of trying to fix it (I still think it's possible), I gave up.
-I downloaded  `GhostBSD`, mounted my ZFS datasets (the problem was not with them, but with booting up), created a small `tar` backup which I moved to my NAS.
-Then, making sure I had the backup, I reinstalled the system as fresh.
+After two evenings of trying to fix it (I still think it's possible), I gave up. I downloaded GhostBSD, mounted my ZFS datasets (the problem was not with them, but with booting up), created a small tar backup which I moved to my NAS. Then, making sure I had the backup, I reinstalled the system as fresh.
 
-About that backup, well.
-For one, I had stuff I didn't want to lose, but I had yet to add any external storage, like git server.
-Not a smart move on my side.
-Good thing, that `ZFS` is designed to be moron-resilient.
-The other part is that my `tar` command didn't include `dotfiles`, and I never bothered to back those as well.
-My `GNUS` state is lost, never to be recovered ever again.
+About that backup, well. For one, I had stuff I didn't want to lose, but I had yet to add any external storage, like git server. Not a smart move on my side. Good thing, that ZFS is designed to be moron-resilient. The other part is that my tar command didn't include dotfiles, and I never bothered to back those as well. My GNUS state is lost, never to be recovered ever again.
 
-But the upside here is that I am much more experienced local-admin than I was when I first moved to `FreeBSD`.
-Setup when smooth like butter.
-Real butter.
+But the upside here is that I am much more experienced local-admin than I was when I first moved to FreeBSD. Setup when smooth like butter. Real butter.
 
-I used this occasion to move this site to my server &amp; create the next iteration.
-I'm still evolving, but backwards.
-What you are seeing here is, of course, a work in progress.
+I used this occasion to move this site to my server &amp; create the next iteration. I'm still evolving, but backwards. What you are seeing here is, of course, a work in progress.
diff --git a/content/blog/2024/bsd-cafe.md b/content/blog/2024/bsd-cafe.md
index 693ae52..c37d835 100644
--- a/content/blog/2024/bsd-cafe.md
+++ b/content/blog/2024/bsd-cafe.md
@@ -4,7 +4,7 @@ author = ["Michał Sapka"]
 date = 2024-10-17T21:16:00+02:00
 categories = ["blog"]
 draft = false
-weight = 2001
+weight = 2002
 image_dir = "blog/images"
 image_max_width = 600
 Abstract = "I had to change server"
diff --git a/content/blog/2024/email-again.md b/content/blog/2024/email-again.md
new file mode 100644
index 0000000..fda5dbd
--- /dev/null
+++ b/content/blog/2024/email-again.md
@@ -0,0 +1,54 @@
++++
+title = "Email, again"
+author = ["Michał Sapka"]
+date = 2024-10-18T23:28:00+02:00
+categories = ["blog"]
+draft = false
+weight = 2002
+image_dir = "blog/images"
+image_max_width = 600
+Abstract = "Another part of me rambling on email"
+Listening = "Miles Davis - Kind of Blue"
++++
+
+One of the things I am seeing up again is my email system.
+I like calling it a system, but basically it's just [a very standard mbsync(1) + notmuch(1)](/emacs/notmuch/) combo.
+But this puts me in the vanguard of email fantastic.
+Nothing fancy, just basic stun **which works**.
+I am therefore the only person who loves using email I know in meat-space.
+
+And I think I know there reason why:
+
+>
+>
+> In the past, the population of people using the Internet had "grown
+>    up" with the Internet, were technically minded, and understood the
+>    nature of the transport and the protocols.  Today, the community of
+>    Internet users includes people who are new to the environment.  These
+>    "Newbies" are unfamiliar with the culture and don't need to know
+>    about transport and protocols. In order to bring these new users into
+>    the Internet culture quickly, this Guide offers a minimum set of
+>    behaviors which organizations and individuals may take and adapt for
+>    their own use.
+>
+> -- [rfc1855](https://www.ietf.org/rfc/rfc1855.txt)
+
+The above is from RFC definite netiquette guidelines.
+Yup, the thing we heard about since we were in our win-modem age was an official guideline.
+
+It's from 1995 and yet we learn that people are new to the web and may not know how to use it.
+Email is an old protocol, it was created for a much smaller internet, less hostile one.
+It expects users to own their communication - to learn the tools, and the tribe culture.
+Is very much like Usenet in that matter.
+To use it properly, one should study it.
+
+People don't study things anymore.
+They expect instant feed of memes, not a long text.
+There are people who love the long text (present company included, I assume), but we are not the norm.
+An everyday, normal guy doesn't know that nothing comes close to scripting capabilities of email.
+He doesn't care that it's one of the very few things one is capable of owning on the inter-webs.
+For them email is that old thing where notifications and spam live.
+
+Email is an elegant tool for more civilized times, and as that it requires our special attention.
+It needs love, it needs usage.
+No one else will give it, especially not people forced to use terrible clients, like Gmail or Outlook.
diff --git a/content/blog/2024/flame-on-web.md b/content/blog/2024/flame-on-web.md
new file mode 100644
index 0000000..3b50274
--- /dev/null
+++ b/content/blog/2024/flame-on-web.md
@@ -0,0 +1,59 @@
++++
+title = "FLAME ON: web"
+author = ["Michał Sapka"]
+date = 2024-10-19T23:38:00+02:00
+categories = ["blog"]
+draft = false
+weight = 2001
+image_dir = "blog/images"
+image_max_width = 600
+Abstract = "Another part of me rambling on email"
+Listening = "Miles Davis - Kind of Blue"
++++
+
+Speaking of the [RFC1855](https://www.ietf.org/rfc/rfc1855.txt) I've [yesterday](/blog/2024/email-again/), the idea of "flame" is a bit lost on us.
+Let me give you a few short snippets from that guide:
+
+1:
+
+> A good rule of thumb:  Be conservative in what you send and
+>       liberal in what you receive.  You should not send heated messages
+>       (we call these "flames") even if you are provoked.  On the other
+>       hand, you shouldn't be surprised if you get flamed and it's
+>       prudent not to respond to flames.
+
+2:
+
+> Wait overnight to send emotional responses to messages.  If you
+>       have really strong feelings about a subject, indicate it via
+>       FLAME ON/OFF enclosures.  For example:
+>       FLAME ON:  This type of argument is not worth the bandwidth
+>                  it takes to send it.  It's illogical and poorly
+>                  reasoned.  The rest of the world agrees with me.
+>       FLAME OFF
+
+3:
+
+> Don't get involved in flame wars.  Neither post nor respond
+>       to incendiary material.
+
+Image if we, as the global village, followed those rules.
+There would be no Twitter, not social media.
+There would be much less news sites, as those feed on anger.
+The web would great - it would the antithesis of our current social status-quo.
+
+It seems that breaking the first rule one is expected.
+There are subject and names in the Open Source community alone, that have a 90% chance of starting a small flame.
+And this is a very small community!
+There are touchy subjects all around!
+
+Now, the only social media I partake is [mastodon](https://mastodon.bsd.cafe/@mms) which is full of nice people.
+But even there I fell into trap of typing something stupid just to get some attention.
+
+So, I for one, am starting to follow RFC1885 in my everyday life.
+No more starting flames, or partaking in them.
+But if still feel the urge, I will use the `FLAME ON=/=FLAME OFF` enclosures as those are so freaking cool.
+
+btw - have you noticed the "wait over night" part?
+It was expected to wait and think of response.
+Magical times _man_, magical.
diff --git a/content/emacs/notmuch.md b/content/emacs/notmuch.md
index 1f6c0a9..53093e4 100644
--- a/content/emacs/notmuch.md
+++ b/content/emacs/notmuch.md
@@ -6,7 +6,7 @@ categories = ["emacs"]
 draft = false
 weight = 3002
 abstract = "My email based workflow for GitHub Pull Review Requests"
-aliases = ["/2023/notmuch/", "/emacs/notmuch/", "/cool-emacs/read-email-notmuch"]
+aliases = ["/2023/notmuch/",  "/cool-emacs/read-email-notmuch"]
 [menu]
   [menu.cool-emacs-ways]
     weight = 3002
diff --git a/layouts/partials/blog/face-game.html b/layouts/partials/blog/face-game.html
index df54451..714ceff 100644
--- a/layouts/partials/blog/face-game.html
+++ b/layouts/partials/blog/face-game.html
@@ -105,6 +105,7 @@
         let inAnimation = false;
 
         const faceImg = document.getElementById('face');
+        const faceBg = document.getElementById('faceBg');
 
         document.addEventListener('DOMContentLoaded', function() {
             const moneyLink = document.getElementById('moneyLink');
@@ -133,13 +134,13 @@
             updateState();
 
             if(state !== "state3") {
-                document.body.style.background = "#ff0000";
+                faceBg.style.background = "#ff0000";
                 state = "state5";
                 updateFace(getStateFaces().front);
                 
                 setTimeout(
                     () => {
-                        document.body.style.background = null
+                        faceBg.style.background = null
                     }, 10)
                 
                 if(!inAnimation) {
@@ -154,7 +155,7 @@
 
             }
             else {
-                document.body.style.background = "#000";
+                faceBg.style.background = "#000";
             }
 
             console.log(`state: ${state}; health: ${health}`);
diff --git a/themes/24-unification/layouts/_default/baseof.html b/themes/24-unification/layouts/_default/baseof.html
index b780182..c2759dd 100644
--- a/themes/24-unification/layouts/_default/baseof.html
+++ b/themes/24-unification/layouts/_default/baseof.html
@@ -387,7 +387,7 @@
     <nav class="nav">
 
       <div class="nav-box">    
-        <div class="logo">
+        <div class="logo" id="faceBg">
           {{ partial "blog/face-game.html" . }}
         </div>
         
@@ -414,6 +414,10 @@
           </li>
 
           {{- end}}
+
+          <li class="section" id="moneyLink">
+            <a href="https://ko-fi.com/mmspl" target="blank">Buy me a Ko-Fi</a>
+          </li>
         </ol>
         {{- end}}