techtangerine Meditations and Musings on Tech

A Redditor Laments on the Destruction of Reddit

A Reddit user going by the moniker aaaa222 put up an interesting post in r/conspiracy 26 days ago, on how Reddit’s culture of being a geek meritocracy was being undermined by dark forces. He claims that the post disappeared after it gained a lot of traction (and then suddenly reappeared). We are preserving his post here for the day when Reddit will be posthumously remembered as another Digg.

Continuous Ink Systems Come of Age

Continuous Ink Systems have come a far way. But they still aren’t mainstream. And they are unlikely to be, given that no inkjet printer manufacturer is willing to make a printer dedicated to a Continuous Ink System. But the niche continues to grow. Here are some tips for potential Continuous Ink System adoptees, as well existing Continuous Ink System users.

Visualizing WordPress

Newcomers and converts to Wordpress usually find themselves baffled over how Wordpress interlopes with other server-side components such as PHP and MySQL. While its true that understanding Wordpress’ relationship with PHP and MySQL is not neccessary for operating a Wordpress site, there are those of us who want to peek under the hood. The following is an attempt to better visualize Wordpress by blurring the boundary between art and abstraction.

Why WordPress should be served Cached

The biggest strength of Wordpress is its dynamic nature. A browser view of a Wordpress website is like a “skin” which interfaces with dynamic components under the hood. But once a Wordpress website starts growing, this also becomes the biggest weakness of Wordpress. The “skin” becomes overloaded with more and more dynamic components. and a simple pageview becomes acrimonious for the server, as it struggles to deliver a “freshly prepared skin” to the browser for each and every page view. On the user end, the lag becomes noticeable. When it comes to self-hosting Wordpress, Caching is an inevitability.

Subversion for a Casual WordPress User…Promises and Challenges

Subversion offers many promises for casual Wordpress users, such as the ability to update Wordpress using a single shell command. But many underlying challenges also remain. This post examines what makes the lure of Subversion so strong for Wordpress users while thoroughly discussing the challenges the author faced in an experimental deployment of Subversion. Subversion clients are also discussed. The article concludes with a “wish-list” for the ideal theoretical Subversion client.

Why Subversion is not a complete way to update WordPress

While Wordpress offers the functionality of upgrading core files, themes and plugins via the Dashboard, this feature cannot be used with some webhosts who are keen on security. Upgrading via FTP is time-consuming and error prone. FTP is also not very secure. To quote one webhost, “Its 2012, and you shouldn’t be using FTP for anything.” Subversion offers the promise of one-click one-command, lightning-fast, server side upgrades. Is Subversion the way to go or has Subversion yet to grow up for the casual Wordpress user?

HP’s dreaded “Ink System Failure”

There have been numerous cases of an “ink System Failure” message popping up on HP inkjets. To give an extent of the problem, typing in “HP” and “Ink System Failure” throws up 340,000 results in Google. There appears to be no clear solution.

Who killed Encyclopaedia Dramatica?

In April 2011, the url of Encyclopaedia Dramatica began redirecting to OhInternet. In a span of a few days, an important part of the Internet subculture Anonymous had disappeared. And was replaced by a website similar to the dozens of websites that commercialize Internet phenomena. Here’s some investigation of what may have happened.