, ,

Advertisers used by banned sellers in Flippa auctions

In a previous post, I listed the top Flippa advertisers, gained through the node.js web scraper. Which advertisers are mentioned most often in auctions by banned sellers? As you can see, there is a big drop in the “unknown” category, and a big increase in banned accounts associated with Infolinks and CJ. After visual inspection, […]

ExtJS TreePanel Example

Problem You want to display a file manager style tree grid. Solution Use the Ext.chart.Chart, and set several properties under the “series” property to render a pie chart.   Discussion The official ExtJS documentation shows how to build a tree grid from an array, which I don’t find terribly helpful. More realistic applications require JSON […]

,

Diagnosing Connection Leaks in Node.js and Postgres

In building a website scraper with Chrome and Node.js, I made mistakes that led to connection leaks. In this application, the scraper runs in a browser and connects to a node.js server, which saves data off to a database. Once you know what the issues look like, they are easy to see, but otherwise often difficult […]

Advertisers referenced in Flippa auctions

The following data show revenue generating partners most commonly mentioned in Flippa auctions. This data is from approximately 76,000 auctions representing over 58,000 domains – note that in many cases more than one advertiser is mentioned per site. This is a broad section of revenue generation strategies, from CPC, CPA, affiliate sales, link sales, etc. […]

Adding Adzerk Units to Blogspot blogs

This applies to adding any html/js widget to blogspot, but in this case, we’re adding adzerk. Select “Layout” on the left hand side of blogger. Click images to enlarge. Select to add a new widget: Select the HTML/JS widget: Paste in the html code. Adzerk tells you to put this in the head block, but […]

How to fix “Error: NAMESPACE_ERR: DOM Exception 14” in Chrome

The only references I’ve found online are to an old bug in Chrome. Error: NAMESPACE_ERR: DOM Exception 14 I generated this with the following xpath expression generated by Firebug: id(‘content’)/x:div[2]/x:div[3]/x:div[1]/x:h2[2] This causes this javascript line to fail: document.evaluate(“id(‘content’)/x:div[2]/x:div[3]/x:div[1]/x:h2[2]”, document, null, XPathResult.ANY_TYPE, null) The fix is very simple: remove the namespaces – the “x:”, like so: […]

,

Fix to error installing “forever” for nodejs

After doing “npm install forever” in a VirtualBox instance you may get an error like the following. This is caused by running the install from a folder shared with the host machine. Certain file operations fail when crossing the machine/file system boundary in VirtualBox. npm ERR! error rolling back forever@0.8.5 Error: UNKNOWN, unlink ‘/vagrant/node_modules/forever/node_modules/winston/docs/winston/transports.html’ npm […]