Initial commit of new site

Author: DarkArc

.gitignore

@@ -0,0 +1,72 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Typescript v1 declaration files
+typings/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# dotenv environment variables file
+.env
+
+# gatsby files
+.cache/
+public
+
+# Mac files
+.DS_Store
+
+# Yarn
+yarn-error.log
+.pnp/
+.pnp.js
+# Yarn Integrity file
+.yarn-integrity
+
+# Gallery Photos
+content/gallery-photos/

.prettierrc

@@ -0,0 +1,7 @@
+{
+  "endOfLine": "lf",
+  "semi": false,
+  "singleQuote": false,
+  "tabWidth": 2,
+  "trailingComma": "es5"
+}

content/assets/images/photo-of-me.jpg

@@ -0,0 +1,11 @@
+---
+title: "Let's talk about Venom"
+date: 2015-08-24 1:16:00
+---
+Over the years that I've managed my Minecraft server, I've found myself in a great deal of frustration, and wasting a **ton** of time with file upload. This frustration spurred the creation of [Venom](/projects/venom/).
+
+Prior to tonight, Venom was simply known as Skelril Deployment. The script deploy.py, however, even in its current form is capable of doing far more than just deploying our server updates though. Venom is currently capable of finding files in a directory based on their most recent revision as determined per a regex expression to match their name. It also has the ability to remap a directory to a remote directory, effectively ensuring that all files in folder x are in folder y on the remote server.
+
+However, this isn't good enough. This fits my original use case quite well, however, I think there's a lot of room for improvement in this department. We currently have very complicated and powerful tools that manage our compilers, however, what is there for deployment? What exists which you can say <bla> my_project and then have it upload all relevant files to the remote server?
+
+I find it absurd that in 2015, I still have to go to FileZilla, and browse to all the directories/files I need, and then upload them manually. My goal with Venom is resolve this issue. This will be one of many projects over the next few months, so this may take some time, but I have high hopes that I will be able to make deploy.py aka Venom, into something incredibly useful. In the short term though, I hope to make Venom as huge time saver for Minecraft server owners.

content/blog-posts/let-us-talk-about-venom/index.md

@@ -0,0 +1,17 @@
+---
+title: "Linux, Changing Tides"
+date: 2016-03-19 06:00:00
+---
+In the fall, I wrote quite a bit about my Linux travels, this post is a continuation of that discussion. Over the past few months, I've had what you could call a change of heart.
+
+Minor things inside of KDE, started to really get on my nerves. KDE Plasma has quite a bit of power, but I started to realize, I really don't need that power. I also came to realize, I really hate the traditional "desktop metaphor", it's just not efficient. Thus, I decided to take a leap, and go back to GNOME. At first, it was a pretty big change, I worked with GNOME fairly extensively when it first came out, but in the years since, GNOME has become a much more polished desktop shell.
+
+I'm also quite happy to say, GNOME has far fewer stability issues when compared to KDE, I've had it crash on me only on rare occasions, and even then, most of the time, when it does, it immediately realizes that it has crashed, and recreates the GNOME Shell.
+
+The window management metaphor used by GNOME, I also much prefer, as it's incredibly visual, and intuitive. Using GNOME, it is incredibly easy to find what you're looking for, it's not a tiny icon, with a bit of text next to it, you see the entire window. The GNOME activity overview is also a very polished, well done feature, without any trouble, you can effortlessly create additional virtual desktops, and manage your windows.
+
+GNOME also for me, has a lot of "little" things that just work well, and get out of your way. For instance, the GNOME keyring managing SSH keys, is incredibly convenient. The animations in GNOME, are also subtile, but effect, they really give the desktop a professional feel, where as the animations within KDE tend to feel a bit overbearing, or are simply absent.  
+
+I've also given the Ubuntu family another chance, and switched to Ubuntu GNOME. The reason for this primarily stems in the packaging of some proprietary software that I use. I decided that it just didn't make sense to continue to fight the Debian ecosystem. The PPA system makes it fairly easy to get the few things that I need to be more "bleeding-edge", and I'm not as invested in having the latest, and greatest everything, just for the sake of having it anymore. I still think OpenSUSE is in an incredible distribution, but for my uses, especially as I prepare to leave academia, I am sated with Ubuntu GNOME.
+
+At the end of the day, if you get the feeling that you might want to break away from the traditional desktop metaphor, and try something different, I would highly recommend GNOME for its visual approach. If you're feeling like trying a non-debian based distribution, I would encourage you to give it a go, but at the same time, be aware that you may have a struggle getting certain packages.

content/blog-posts/linux-changing-tides/index.md

@@ -0,0 +1,27 @@
+---
+title: "My Linux Travels"
+date: 2015-09-05 03:10:35
+---
+I've used many distributions over the years. However, I've never really taken the time to discuss what lead me to my current distribution -- OpenSUSE. So I wanted to take some time, and share what I've learned in my travels.
+
+I originally started playing around with OpenSUSE and Kubuntu/Ubuntu/etc ~2009-2010 on an old computer originally meant to run Windows 98. I quickly discovered the hardware was, less than adequate to do... well just about anything. I didn't do much with Linux at this point besides play around with it, basically clicking buttons, and seeing what would happen. Then around 2012, I decided that I had, had enough of Windows, and I decided to get Fedora -- I believe it was Fedora 18 if my memory serves me correctly -- and use it as my primary operation system.
+
+I choose Fedora because I really liked the fact that it's *almost* a bleeding edge distribution. I also thought GNOME 3 looked *really* cool, and to many of my friends protest, I wasn't afraid to share my optimism. Now, you may be thinking, well that was a while ago, wasn't GNOME 3... still kind of new? Yup! It had a ton of very strange problems, and dealings with things which just hadn't been well thought out. One of my biggest complaints with GNOME 3, is/was the way it handles applications which try and stick around in the notifications area. I was, and still am, a heavy user of both Spotify, and Mumble. These applications, at least historically, have made heavy use of the notifications area. GNOME 3 would just awkwardly place them in the activities overview like any other notification, this made for a very awkward experience. My other complaint about GNOME 3, was, and still is, the file manager. "Files" as it's now called, simply can't compete with KDE's Dolphin. I could write an entire blog entry about how annoyingly oversimplified, but yet complicated, the GNOME team has made "Files" -- maybe another time. However, all that aside, what really put a nail in the coffin of GNOME 3 was the little things -- like adding a new entry to the list of applications, which at least at the time, completely lacked a GUI. There were, and from what I've seen still are a number of cases where GNOME makes you really work just to do what -- in my opinion anyways -- should be a simple task.
+
+So, from Fedora GNOME, I went to Fedora KDE. Fedora KDE, was pretty nice actually. My biggest complaint with Fedora KDE was the speed at which I was receiving software updates for KDE software. I really hated how long it took to get the latest builds of KDE onto Fedora. So, why did I eventually leave Fedora? Well, did I mention, I like to play games? Did I also mention this computer had an AMD graphics card? Anyone who's every tried to use AMD proprietary drivers on Fedora almost certainly knows what I'm talking about already. These drivers would frequently be behind in compatibility with the latest Linux Kernel, and xserver, causing frequent problems. Rest assured, I became quite good at reinstalling/reconfiguring the Linux graphics stack.
+
+I had to take another break from Linux when I went off to college for a while. However, once I got my new -- Intel/nvidia powered -- laptop, and with my previous frustrations about Fedora, I decided to try Arch Linux, or rather Manjaro Linux -- my hope being this would provide an excellent buffer on the latest bleeding edge packages. It did **exactly** that, and I was very happy with it for quite some time. I could find almost any package I wanted, the AUR was simply amazing, the proprietary graphics support was superb, and everything was awesome. I still had to fix my computer from time to time, but that wasn't a big deal to me. Then... sketchy things started happening. The Manjaro SSL certificate was allowed to expire for instance. This made me very, disconcerted with their ability to manage a distribution. I also became weary of the occasional system fixes, and didn't trust myself to pick all the software I needed to make a 100% solid, stable, and secure Arch Linux system, so I broke up with my dearly beloved Arch Linux.
+
+So, from here, I decided to go back to Fedora KDE -- I know what you're thinking. I was hoping the RPM fusion support for nvidia would be better than for AMD, and it was! However, the RPM fusion support for bumblebee/nvidia optimus enabled devices, was non-existant. Thus, I had to find some random repository that an individual was maintaining specifically for nvidia optimus enabled laptops/bumblebee/primus/etc. This worked well enough, however, graphics updates weren't as frequent nor as trust worthy, as I would have liked them to be. Fedora also stopped packaging Mumble, so I had to have a self compiled version of Mumble, and honestly, I feel Fedora treats their KDE spin a bit like an awkward step child. It's there, and it's given some love, I'm sure those whom work on it, work very hard. However, regardless of the effort exerted, it doesn't get the polish that GNOME does in Fedora.
+
+I then decided to try a Debian based distribution again, something I hadn't done in quite some time at this point. I wanted to bring myself into "one ecosystem" -- Debian -- to simplify my life. I have several other people I know, running Linux Mint. However, Linux Mint moved far to slowly for me. So, I actually decided to go with Debian testing, and work off of that. My first attempt was to start with only the command line interface, and then compile my own Qt and KDE Plamsa 5.4/Applications 15.08 desktop environment. The idea being, this would allow me to have an "unstable"/bleeding edge desktop environment, while still having a stable, but rolling release base to work off of. I ran into various problems along the way, and after getting a Breeze style cursor to appear on top of a black screen, I decided it wasn't worth pursing any further.
+
+This brings me to my second attempt at Debian. I decided to start from a command line interface, and work my way up by installing their Plasma 5.3.x packages. I made a lot of progress, and got things mostly working. However, this as well was very painful, and I got the feeling that all my work would be for little gain. There was also a major problem in that, the KDE packages for Debian -- at least at the time -- had a rather significant issue where KWin5, and several other core KDE components could not co-exists. You essentially had to either choose KWin or Plasma. I use KDE for KWin almost as much as I use it for Plasma -- I love KWin -- so this wasn't really an option for me.
+
+Thus, I decided to try OpenSUSE again. I hadn't paid much attention to the distribution over the years. I had never really been a fan of YaST. However, in my attempt to simply my life, I accepted that a desktop environment independent configuration utility might actually be quite nice to have. At this point, I was also at the point of... well what do I have to lose? So, I tried OpenSUSE! I have to say, I was not expecting to be impressed, however, I am.
+
+OpenSUSE has matured a lot since I last tried it. One big thing for me, being in Fedora so frequently over the past few years, was that it has official support for proprietary graphics drivers, including nvidia optimus enabled systems -- this takes a bit of work to get working, but it's not too bad. Another thing I really like, is their web based software search. Once I figured out how to use it, I had a system running KDE Plasma 5.4 with mostly Applications 15.08 running in little time at all. They also have a Mumble package -- yippie! The only thing I'm missing at this point, is a Spotify package, as unfortunately, they are only packaging in deb format at the moment. I'm still hoping this will change before too much longer.
+
+Now, all that said, I don't want to mislead you, there are a number of issues with OpenSUSE as well, primarily, with the bleeding edge packages. I imagine much of this will be resolved in the coming months with little intervention on my part. However, I'm currently not using KMail, as the integration with KWallet5 is not there -- KDE PIM 5 was not included in the stable version of the bleeding edge packages. Additionally, Yakuake, unfortunately isn't Yakuake5, and isn't working, as it can't find a compatible Konsole. There is also a rather strange issue with dependencies, where both the new plasma sound applet, and KMix want to be installed at the same time. This becomes evident when you use zypper dup, as one of the package groups includes KMix by default, so if you do a distribution upgrade with dup, you have to make sure to remove KMix after the upgrade, otherwise, your sound will be a bit awkward to control -- seeing as how there are two volume applets open and all.
+
+I think I'll be sticking with OpenSUSE for a while, and seeing how things turn out. So far, I think it's a keeper, it gives me that stable base I desire, while still allowing me to have my bleeding edge desktop environment, which I crave, and minus the initial setup cost, it seems to be rather low maintenance. If this proves to be as stable as I would like, I may start pushing my Linux Mint users to move to OpenSUSE, that way I really have simplified my life -- perhaps I'll write a bit about that some other time. Anyways, with OpenSUSE 42 sharing upstream SUSE packages, and having a variety of core improvements, I only see OpenSUSE becoming a better distribution in the future.

content/blog-posts/my-linux-travels/index.md

@@ -0,0 +1,11 @@
+---
+title: "My New Blog"
+date: 2015-08-19 17:45:35
+---
+It's been a very long time since I had a blog. [My old blog](https://xllog.wordpress.com/) hasn't been used in years actually (August 25th, 2011), almost 4 years ago to the day. However, I decided it was time to make a new blog, one which is actually nice, and maybe just *maybe* be useful to somebody somewhere.
+
+So, without further a due, I intro my new blog, and personal site, haxing.ninja. I'm not sure what I'll be writing about, maybe just work on the Minecraft sever project [Skelril](/projects/skelril/), or maybe some work on something of [sk89q](http://sk89q.com)'s, we'll see.
+
+Regardless, hopefully it will be something a bit more intriguing than my ramblings about [RuneScape](http://runescape.com).
+
+There's still a lot of work to be done as far as this blog site goes as well. The project pages need a lot of work, and the about page is still blank. To be completely honest with you, most of this was just taken from my work on the new Skelril website, which is currently at [beta.skelril.com](http://beta.skelril.com) if you're interested in looking at it.