Google Hates Blogs?

As of late I’ve been noticing that a lot of blog posts are not appearing in Google. A similar behavior was found by Marco Arment. Sure, my blog isn’t really the most relevant piece of journal in the internet.

Amusingly, I think the crawlers are doing their job. However, what goes on their results is being filtered. For example, all the tags pages (linux, programming, etc) have been thoroughly indexed by Google. Only ONE article I have written made it to the index. It could simply be a rule set to withhold any of the following URI [site]/posts/* where posts already determines the resource is in fact a blog post.

In a related note, I don’t know if I’m crazy but in the past you could actually search blogs. It was one of my favorite features from Google as you could really find a lot of educational material that websites couldn’t provide.

Will this keep me from writing posts? Not really. I’m not popular now, and I will not be popular in the future. Even if I was popular, I don’t think people should write to appear in a search engine. It kills the very notion of why weblogs exists in the first place, pretty sure it’s not for SEO or anything related to search engines.

Site Update – 2015-02-13

I spent this friday cleaning up the theme. I’m overly pleased on all the changes that have been done today. The site should provide useful metadata to crawlers, and of course it’ll be making it easier for results to become revelant. Quite nice, right?

I have yet to write more articles for my blog. Ultimately, I don’t want to just write guides for WINE, or make small posts of little progress. That’s what I’d love to say, sadly my time is limited; even simple cleanup tasks like the one I did today took a few hours to complete. This is simply because initially the theme I’m using was for Movable Type and I ported it to Pelican so yea, it was meant to be messy.

Good news? Nuja is closing in for a release. So if you are a Pelican user, be on the look out!

Pelican Theme: Nuja

It’s been a completely crazy day. Today I finished porting a theme I created for Movable Type called Nuja. I actually worked on it in 2013, but due to life I couldn’t keep updating it. It also amazes me how time passes. I didn’t think this was from 2013, I guess life is going faster than I thought; hopefully for the better.

Nuja is a simple theme, it was created as a tribute to Nujabes. The theme might be released over time; I’m planning to polish it before release of course. I had a bit of trouble working with Pygments, apparently Bootstrap kept overriding CSS elements when it shouldn’t. In the end I just decided to hardcore the solution as I knew I couldn’t do anything about it.

RSync + Pelican: A Short Note About Permissions

Yesterday I spent most of my time dabbling in Pelican’s configuration file. Right now how is set is pretty simple. I just rsync the data to the server, and back up the project on a weekly basis to my personal account in BitBucket. There’s a catch on this, any tool using rsync will upload the data as the user you are uploading it as. This doesn’t sound as a problem at all if you are using a shared hosting! However, I use a VPS from DigitalOcean, so it sort of changes quite a bit.

I’ll be frank, before explaining my solution which is just a simple line. I haven’t configured my nginx completely, and if there’s another way to do this it’s lost on me. Feel free to contact me, my e-mail is in the About Me page!

What I did was simple, edit your Pelican generated Makefile and add this line in the rsync_upload action:

rsync_upload: publish
rsync -e "ssh -p $(SSH_PORT)" -P -rvzc --delete $(OUTPUTDIR)/ $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR) --cvs-exclude
ssh $(SSH_USER)@$(SSH_HOST) "chown -R www-data:www-data $(SSH_TARGET_DIR)"

That’s all you really need to solve the permission problems. There’s another way which is adding rsync to sudoers, but doing so introduces a security risk. The alteration made my way simply re-uses the variables that were previously declared. Once rsync finishes syncing the files, it will make open up ssh and chown the folder.

That’s all, and if you are using vim. Type :make rsync_upload (you must have your virtualenv enabled if you didn’t install it system wide). 🙂

Vim: My Experience as a New User

Many of you have heard of Vim, a lot of people call it the greatest text
editor ever “second to none”. While that claim seems like a bit of a mouthful
and purely driven by the fans there are reasons why Vim is great, as well as
there are reasons for you not to use it.

I started learning Vim this week. Let’s make this clear, Vim is not an IDE,
you can make it look like an IDE but it won’t behave like one. As I searched
through the web for plugins to empower my Vim editor I noticed one thing:
Everyone wants Vim to be an IDE. Oh, the many out there. I don’t mind
them, but it puzzled me as a new user.

Don’t get me wrong, I love Vim. I love all the amazing text editing keymaps
you can do with it. I love how you can use Visual Block and replace whatever
text with the same name in just a matter of 2-3 keys. I love how you can just
ci” and magically delete. I love plugins like YouCompleteMe, how well
NERDTree works even though I’m looking at something like Sauce but bookmarks
do just fine, how AMAZING is python-mode, tagbar is a must, vim-airline, and
oh so many plugins out there that even in 2014 it maintains Vim relevant.

Vim is an investment. As a new user it took me a couple of days to fully get
it to where I wanted it. Just like Emacs if you want to be its user, then
you’ll know that you need to install plenty of plugins for it too.

But see, Vim is a great tool. Let me show you the first screenshot:

My .vimrc is a mess so I’m not going to post it here today but let’s take a
look at semantic completion provided by YouCompleteMe, it also uses omni-
completion. This is just one of my random projects.

Here is a more IDE-like screenshot that shows you tagbar.

It looks great, doesn’t it? As a new user I should have waited a bit before
getting into plugins but at the same time I wanted to do some C++ already. My
reason to choose Vim was because Eclipse just keep crashing over and over
again and it also froze several times. Netbeans didn’t even want to work.

So, I chose Vim because it was THE text editor I needed. The world whispered
in my ears and said “Use vim, use vim! You won’t regret it!” I don’t regret
it. I like it, I haven’t worked on a REAL project with it but I know that
it’ll be a delight to work with.

Now, all my praises for it so far ends here. Let’s go on to why you might not
want to deal with vim.

  • Setting up a project with virtualenv and YouCompleteMe is a pain. No matter how you look at it, you don’t get a predefined workspace like you do in Eclipse or Netbeans. There’s no ROOT PROJECT folder to use. It causes YCM not look up the libraries set with virtualenv. And it’s just awkward hard to make it work. Since YCM looks at your system libraries, what I did was just install the framework I wanted to use to get the semantic support. It’s sad.
  • ctags? Manual generation of something that should be automated? Well, yea it’s like that. Apparently you gotta freshen up your ctags if you want to navigate your source files.
  • No way to jump around headers/sources file. I can’t for the life of me find a way to JUMP at the standard header I just included. In Emacs, this is done oh so easily, it makes me sad.
  • It takes time to deal with buffers/windows/tabs. If you are new like me, chances you are going to be nuts jumping from buffer to buffer, or tab to tab.

Listen, if I were to choose between PyCharm and vim, my answer would be
PyCharm. It removes a lot of the hassle that is introduced by vim. But see,
vim is a text editor and such it cannot be blamed for not working as one.

So where’s the investment exactly? Text editing. No, really. Once you learn
the flow of vim you will be fast to get that source written. At first, you
will feel slow, frustrated because the workflow is really different. I know I
have. Heck, I have started typing while it was in Normal Mode and I’ve screwed
up plenty of files due to that. It happens because we are just new to vim.

Is it worth the pain? That’s for you to choose. I’m sticking with it for a
while because it doesn’t hurt.