Main

Not too long ago I decided to change my blog domain name to something more neutral, fun and web performance related. All cool ideas I had were taken so settled for “badbadserver.com”, a semi-obscure error message from Google’s almost-defunct Orkut. To be completely honest, I was never too satisfied with the new name, but managed to live with it. Today, while reading another cryptic error message, this new idea came up, “overloaded.io”. I just love it! Now I’m just waiting for the registration to complete so I can start moving domains again!

Recently I started revisiting the way my data was spread across different cloud services. Up until now, I’ve been using Google Bookmarks to keep all my bookmarks, lots and lots of them, using mainly tags to keep organized. A few years ago when I decided to move from Delicious, it felt like an obvious choice. A few hiccups along the way, but so far, it worked really well. I even created a Chrome extension to help bookmarking and searching bookmarks from the omnibar. A few things annoyed me, like presenting tags the same way as folders, all listed on the left sidebar, creating a loooong page with only links on the side.

Lately I also started bookmarking a few links on Evernote, specially references to technical articles and so on. In the spirit of simplifying, I decided to consolidate everything in the same place, Evernote. This meant I would have to migrate my 3k+ bookmarks from Google to Evernote, trying to preserve all tags and possibly creation dates.

Google Bookmarks doesn’t provide a huge list of exporting options, only one HTML format, with links grouped by tag. The interesting thing about the format is that bookmarks are duplicated if they have more than one tag. One annoying thing I would have to deal with.

Looked around for services or scripts that could help migrating, but not much luck. Most guides only suggested importing the HTML file directly to Evernote, creating one singe note, and that’s not what I wanted. Looked a little bit further and found a Python script on GitHub. Very simplistic. The script would parse the file and write the output in an Evernote format, or ENEX, a simple XML file with Evernote tags.

Tried it and it worked, at least it ran and created a new file. Tried to import it on Evernote and no luck. It failed giving no clue about what was wrong. I decided to play with the file a little bit and found the problem, a few spaces and empty lines in the wrong place. Fixed the script and import worked, sort of…

Remember I mentioned about duplicate entries on the exported file. The script did not account for that, so all entries with more than one tag were duplicated. That would not work. Since the script was almost done, I just decided to fork it and fix this small things. Included a check for duplicated bookmarks. While I was at it, I also minified the output and included created dates to the exported fields.

Recently I came up with a script to quickly print the memory utilization of specific processes on Linux. It’s very simple, but proven to be very handy while I was moving and tuning my VPSs. It quickly showed me that Apache was taking pretty much all my memory and motivated the migration to nginx.

It’s currently set to get the Resident Set Size (RSS), but you can easily change it to use Virtual Memory (VSZ). Just change ‘rss’ to ‘vsz’ in the ps commands. Also, you can add more processes to the script. Just add a new line and change the process name.

During the past couple years, questions have been queueing up on my comment inbox and not getting answered for different reasons. I believe the authors already found found the answers they were looking for or just don’t care about them anymore after a few months.

Having a lot of comments in my inbox is not really productive, so I’m archiving all questions older than 1 month. Later I plan to go through them again and use a few interesting questions as topics for new blog posts.

To avoid situations like that in the future, I’m establishing a new personal SLA. All questions and comments submitted to the blog should be answered within 3 days. So if you don’t hear back from me in 3 days, shout out!

If you submitted a question a while ago and did not get an answer, I apologize. If you’re still looking for some input, please submit it again. If you found your answer somewhere else and would like to share it, let me know. I’m always open to guest posts!