bits.2013

README.md

bits.2013

This is a Gist for stuffing my quick notes and thoughts in here, also serving as development tracker for bits.

Moved

Now bits has moved to WordPress.

Development of bits

Key points:

• README.md isn't very important since it isn't a note, but it may be used for some indexing or linking to other years.

• Each note is a comment, currently group year's notes in one Gist. No need to title each note, too much effort for reference when comment link is enough.

  Originally, I thought of using pattern like YYYYnnn, year with 3-digit number. But it's really not necessary. Not even me would actually refer to the notes.

• Must have proper formatting capability, like Markdown.

  Although these are just notes, but I would prefer formatting them well. Not tweets, nor blog posts.

• Must be able to scroll down a single page to view multiple rendered notes.

  I wished to have each note their own page, but couldn't really find any easy solution to meet my needs, so settling down in Gist comments works best for now.

• Okay to lose these notes, they may not be worth reading again.

• Okay not to have proper search function since each note is a comment.

• Okay not to have separate comment thread for each note.

• Okay not to have commit history for notes.

Ideas:

• The first note is a bit long due to the emerge log, it might be a good idea to have another Gist to store those log stuff, like bits.2013.bits.

• keyword' bookmark for comment form

  Unfortunately, the form doesn't have ID.

CSS position: sticky looks interesting, but Firefox don't have that in 24 ESR, until 26. Chrome 32:stable doesn't have it, either. might be removed from WebKit or something. Probably not mature enough.

It looks like my handcrafted worm bin is a failure, I am going to super-downsize the box before I murder more worms.

USDA National Nutrient Database for Standard Reference

• Release 26 data files
• some SQLite converter
• GNUtrition

Pitbull feat. Ke$ha - Timber via ASUS ROG while waiting the resume of Game 2 of Elfi and Jaedong, they are under DDoS attack.

nspr is holding autoconf-2.13:

$ eix -I1c autoconf
[I] sys-devel/autoconf (2.13(2.1)@10/18/2009 2.69(2.5)@08/10/2013): Used to create autoconfiguration files

$ equery d =sys-devel/autoconf-2.13
 * These packages depend on sys-devel/autoconf-2.13:
app-editors/vim-7.3.762 (sys-devel/autoconf)
app-editors/vim-core-7.3.762 (sys-devel/autoconf)
dev-libs/nspr-4.10.2 (=sys-devel/autoconf-2.1*)
net-misc/openssh-5.9_p1-r4 (sys-devel/autoconf)
sys-apps/attr-2.4.46-r2 (sys-devel/autoconf)

$ eix -I nspr
[I] dev-libs/nspr
     Available versions:  4.10 ~4.10.1 4.10.2 {debug}
     Installed versions:  4.10.2(10:45:15 PM 12/02/2013)(-debug)
     Homepage:            http://www.mozilla.org/projects/nspr/
     Description:         Netscape Portable Runtime

Trying to make Bokashi composting starter, read about using rice to ferment and use newspaper to soak up the mixture once fermented.

I just put equal part by volume of rice, demerara sugar, potato starch, and flour, with probably three or four times of water. Covered with napkin and placed on a DC adapter, just like making sourdough starter, only I put more stuff. Probably not ideal, just playing around, I might end up with a smelly jar or disgusting mixture.

Whatever the result would be, I would pour the entire jar into my failed compost pile. Just like that, more smelly perhaps?

---

2013-12-09T12:30:20Z: the box is brewing, bubbles coming up from bottom especially after slight shaking.

Since the new python-exec package, I symlink'd for pip for Python 3.3:

/home/livibetter/.local/bin/pip-python3.3 -> /usr/lib/python-exec/python3.3/pip

There is another way:

EPYTHON=python3.3 pip

test post

Oh yeah, it's back.

My mushroom bed is having green mold, thinking about applying salt (or salted water) or just digging the infected area.

There was an error occurred when I tried to add comment #67, Gist threw the following error:

The change you wanted was rejected.

Maybe you tried to change something you didn't have access to.

I emailed GitHub Support, then the error was gone. During the downtime, I searched for alternative options. Tumblr supports Markdown but it doesn't have comment system. Then I saw WordPress supports Markdown on both posts and comments. Needless to say, I was tempted and now bits is on WordPress.

The End