Introducing “MacBlogPinger”. You can now download a “MegaPinger” style application for the mac. This will allow you to upload bulk urls for them to be pinged automatically to many blog ping services.

Screenshot of the application:

Use these and save to rpclist.txt (make sure to remove the empty lines):

http://1470.net/api/ping

http://a2b.cc/setloc/bp.a2b

http://api.feedster.com/ping

http://api.moreover.com/RPC2

http://api.moreover.com/ping

http://api.mw.net.tw/RPC2

http://api.my.yahoo.com/RPC2

http://api.my.yahoo.com/rss/ping

http://bblog.com/ping.php

http://bitacoras.net/ping

http://blog.goo.ne.jp/XMLRPC

http://blog.with2.net/ping.php

http://blogbot.dk/io/xml-rpc.php

http://blogdb.jp/xmlrpc

http://blogdigger.com/RPC2

http://blogmatcher.com/u.php

http://blogoole.com/ping

http://blogoon.net/ping

http://blogpeople.net/servlet/weblogUpdates

http://blogsdominicanos.com/ping

http://blogsearch.google.ae/ping/RPC2

http://blogsearch.google.at/ping/RPC2

http://blogsearch.google.be/ping/RPC2

http://blogsearch.google.bg/ping/RPC2

http://blogsearch.google.ca/ping/RPC2

http://blogsearch.google.ch/ping/RPC2

http://blogsearch.google.cl/ping/RPC2

http://blogsearch.google.co.cr/ping/RPC2

http://blogsearch.google.co.hu/ping/RPC2

http://blogsearch.google.co.id/ping/RPC2

http://blogsearch.google.co.il/ping/RPC2

http://blogsearch.google.co.in/ping/RPC2

http://blogsearch.google.co.it/ping/RPC2

http://blogsearch.google.co.jp/ping/RPC2

http://blogsearch.google.co.ma/ping/RPC2

http://blogsearch.google.co.nz/ping/RPC2

http://blogsearch.google.co.th/ping/RPC2

http://blogsearch.google.co.uk/ping/RPC2

http://blogsearch.google.co.uk/pingRPC2

http://blogsearch.google.co.ve/ping/RPC2

http://blogsearch.google.co.za/ping/RPC2

http://blogsearch.google.com.ar/ping/RPC2

http://blogsearch.google.com.au/ping/RPC2

http://blogsearch.google.com.br/ping/RPC2

http://blogsearch.google.com.co/ping/RPC2

http://blogsearch.google.com.do/ping/RPC2

http://blogsearch.google.com.mx/ping/RPC2

http://blogsearch.google.com.my/ping/RPC2

http://blogsearch.google.com.pe/ping/RPC2

http://blogsearch.google.com.sa/ping/RPC2

http://blogsearch.google.com.sg/ping/RPC2

http://blogsearch.google.com.tr/ping/RPC2

http://blogsearch.google.com.tw/ping/RPC2

http://blogsearch.google.com.ua/ping/RPC2

http://blogsearch.google.com.uy/ping/RPC2

http://blogsearch.google.com.vn/ping/RPC2

http://blogsearch.google.com/ping/RPC2

http://blogsearch.google.de/ping/RPC2

http://blogsearch.google.es/ping/RPC2

http://blogsearch.google.fi/ping/RPC2

http://blogsearch.google.fr/ping/RPC2

http://blogsearch.google.gr/ping/RPC2

http://blogsearch.google.hr/ping/RPC2

http://blogsearch.google.ie/ping/RPC2

http://blogsearch.google.in/ping/RPC2

http://blogsearch.google.it/ping/RPC2

http://blogsearch.google.jp/ping/RPC2

http://blogsearch.google.lt/ping/RPC2

http://blogsearch.google.nl/ping/RPC2

http://blogsearch.google.pl/ping/RPC2

http://blogsearch.google.pt/ping/RPC2

http://blogsearch.google.ro/ping/RPC2

http://blogsearch.google.ru/ping/RPC2

http://blogsearch.google.se/ping/RPC2

http://blogsearch.google.sk/ping/RPC2

http://blogsearch.google.tw/ping/RPC2

http://blogsearch.google.us/ping/RPC2

http://blogshares.com/rpc.php

http://blogsnow.com/ping

http://blogstreet.com/xrbin/xmlrpc.cgi

http://bulkfeeds.net/rpc

http://catapings.com/ping.php

http://coreblog.org/ping/

http://effbot.org/rpc/ping.cgi

http://feedsky.com/api/RPC2

http://fgiasson.com/pings/ping.php

http://focuslook.com/ping

http://holycowdude.com/rpc/ping

http://imblogs.net/ping

http://j-ranking.com/ping.cgi

http://lasermemory.com/lsrpc

http://mod-pubsub.org/ping.php

http://newsisfree.com/RPCCloud

http://newsisfree.com/xmlrpctest.php

http://ping.amagle.com

http://ping.bitacoras.com

http://ping.blo.gs/

http://ping.blogg.de

http://ping.blogmura.jp/rpc/

http://ping.blogoon.net/

http://ping.blogs.yandex.ru/RPC2

http://ping.cocolog-nifty.com/xmlrpc

http://ping.exblog.jp/xmlrpc

http://ping.fakapster.com/rpc

http://ping.fc2.com/

http://ping.feedburner.com

http://ping.gpost.info/xmlrpc

http://ping.kutsulog.net/

http://ping.myblog.jp

http://ping.namaan.net/rpc

http://ping.rootblog.com/rpc.php

http://ping.speenee.com/xmlrpc

http://ping.syndic8.com/xmlrpc.php

http://ping.weblogalot.com/rpc.php

http://ping.weblogs.se

http://ping.wordblog.de

http://pinger.blogflux.com/rpc

http://pinger.onejavastreet.com

http://pingoat.com/goat/RPC2

http://pingqueue.com/rpc

http://queerfilter.com/ping

http://r.hatena.ne.jp/rpc

http://rcs.datashed.net/RPC2

http://rpc.blogbuzzmachine.com/RPC2

http://rpc.blogrolling.com/pinger/

http://rpc.britblog.com

http://rpc.icerocket.com:10080

http://rpc.newsgator.com

http://rpc.pingomatic.com/

http://rpc.reader.livedoor.com/ping

http://rpc.tailrank.com/feedburner/RPC2

http://rpc.technorati.com/rpc/ping

http://rpc.weblogs.com/RPC2

http://rpc.wpkeys.com

http://rssfeeds.com/suggest_wizzard.php

http://rssfwd.com/xmlrpc/api

http://serenebach.net/rep.cgi

http://services.newsgator.com/ngws/xmlrpcping.aspx

http://snipsnap.org/RPC2

http://thingamablog.sourceforge.net/ping.php

http://topicexchange.com/RPC2

http://trackback.bakeinu.jp/bakeping.php

http://wasalive.com/ping

http://weblogalot.com/ping

http://weblogues.com/RPC

http://xianguo.com/xmlrpc/ping.php

http://xmlrpc.blogg.de

http://xping.pubsub.com/ping/

http://zhuaxia.com/rpc/server.php

http://blogupdate.org/sverige/ping/

http://blo.gs/ping.php

http://blogping.unidatum.com/RPC2/

http://mod-pubsub.org/kn_apps/blogchatt

http://www.lasermemory.com/lsrpc/

http://ping.amagle.com/

http://ping.blogg.de/

http://ping.bloggers.jp/rpc/

http://ping.feeds.yahoo.com/RPC2/

http://pingoat.com/

http://pingqueue.com/rpc/

http://ping.weblogs.se/

http://rpc.britblog.com/

http://rcs.datashed.net/RPC2/

http://rpc.icerocket.com:10080/

http://rpc.newsgator.com/

http://rpc.pingomatic.com

http://rpc.wpkeys.com/

http://zing.zingfast.com

If you want to use proxy then please make sure all proxies are working, “MacBlogPinger” will not distinguish broken proxies at this stage.

The format of the proxylist.txt file should look like (no newlines):

127.0.0.1:3128

192.168.1.1:8080

Your sitelist.txt file should be the URLs of each you want pinged, for example (without newlines again):

http://www.garyadamshannon.com

http://www.google.com

This product solves the annoying problem we all face, when, at 2am or 11pm at night we decide to flip on the computer and take a quick note or look something up, and, subsequently get blasted with LCD rays stronger than the sun.

f.lux makes the color of your screen adapt automatically depending on the time of day, a product such as this could actually help you sleep better too – if you’re a night owl geek.

It is available for mac, windows and linux systems which says to me it could be a piece of java or an adobe air application. Either way, it is pretty neat and something everyone should have installed.

This is a fairly important question that isn’t covered in great detail, so I will quickly dive into my theories which I have proven through domain testing over the years.

Do Google, or other search engines pull domain age from WHOIS details?

To put it simply, no. Having a history of working for a reputable domain name registrar myself and dealing with fairly low level technical problems; I can say that search engines at best have access to a complete incomplete set of root zone files. These root zone files simply list the domain name and the allocated nameservers. Some TLDs do not even give registrars root zone files.

The UK tld (.co.uk) which is run by Nominet does not provide rootzone files to registrars. In this situation a search engine must rely entirely upon natural discovery of these domains with no assistance from rootzone files (which could have been used for hints).

For a search engine to obtain full whois details they would need to engage in whois scraping. Whilst this is totally possible, it is not something a public company would even be allowed to do without proper disclosure. Even if a search engine were to engage in whois scraping (I am sure they do in black ops), they would be relying on an incomplete snapshot of rootzones and thus they would not have full data integrity.

To make matters even more difficult, some TLDs do not even record creation dates in their whois records (for an example, check any .eu domain).

A search engine cannot rely on incomplete domain sets and incomplete whois sets in order to make critical ranking decisions.

Do Google, or other search engines pull domain age from the oldest or earliest sitemap entry?

Again, no. Relying on a sitemap entry or the publisher for data would lead to plenty of blackhat techniques to game the system by simply changing publish dates.

So how does a search engine measure domain age?

Crawl date. Get your site indexed as soon as possible.

50 pages in and so far so good

I did this by creating a file called open_sesame.php

setCookie("OpenSesame", "1", time()+(3600*24*7), '/');
);
header("Location: /wp-admin");
?>


This simply sets a cookie called OpenSesame and expires it in 7 days time.

So now you need to modify your .htaccess or apacheconfig so with a simple rewriterule:


RewriteEngine on
RewriteCond %{HTTP_COOKIE} !OpenSesame
RewriteRule wp-admin /404.php


This tells apache to look for the cookie OpenSesame; if it exists then let wp-admin be accessed. If it does not exist then make sure wp-admin redirects to a 404 page.

This eliminates people from finding out if your blog has a wp-admin directory and most script kiddies will probably not push much further on your site.

Additionally you could lock it down further by restricting IP addresses, but thats sort of painful if you travel around.

Once this is setup, all you need to do is access open_sesame.php and you’ll be able to login ok!

Programmers are programmers, they like rules. Adopting a trend that is supposed to stop unwanted spammy links sounds great, so it is with greater frequency that I am seeing content management systems and bits of code floating around the net that automatically add ‘rel=”nofollow”‘ to links.

This is bad, why? Because it dilutes the importance of ‘rel=”nofollow”‘.

If a growing percentage of new opensource software released adopts this trend, then we end up in a situation where ‘rel=”nofollow”‘ is no longer useful to search engine spiders.

Nofollow is already dead

It is my belief that ‘rel=”nofollow”‘ is infact already dead, or, at least somewhat partially diminished. It’s importance is being diluted daily by new software and misuse of the tag.

As of right now, nofollow links may not be as highly regarded as “dofollow” links; however the disparity between them both is not as great as most people are lead to believe.

Do I target ‘rel=”nofollow”‘ links and ‘dofollow’ links in my search marketing campaign?

Of-course you should, I would think it is unwise not to. If we end up in a situation where ‘rel=”nofollow”‘ is disregarded entirely, then your “dofollow” links are no longer an advantage point.

Quite a bit of pain, I hope it goes away!