"Which comes first, Facebook Page or Blog Creation?" This question bothers me. There are Facebook pages that I "like" in which it doesn't have a website but I'm sure that almost websites now has Facebook pages. As my personal view, having a 10k-100k likes in Facebook without a site is somehow a missed amount of opportunity and a potential penny. Not being greedy but at least you paid your effort in running your page. Anyway, just to answer the question I created a blog first then Facebook page coz I don't post too much in my Facebook page. I know it's lame! :P On the serious note... Primarily, the main function of social networking sites/media for me is to make your post (video, images, etc.) viral. It's like having a free ad service in every "like" and "retweet" as we call it. It helps you gain huge traffic. Just an advice regarding which path you'll take... If you begin with Facebook page... Share ...
Placing Adsense in the right "place" is important for it increases your revenue(maybe or maybe not). Using Blogger platform, you can place Adsense below the post title or just after your posts. Why not put it in the middle? It will be great like this site: http://screenrant.com/hobbit-3-peter-jackson/ . And I would like to share what I have found, here how to do it. With this method you can place your Ad with your own preference, either in the middle, near middle or bottom, anywhere! Here's how to do it! 1. Find the <data:post.body/> (tick the Expand Widget Templates) then replace that tag with the code below: <div expr:id='"aim1" + data:post.id'></div> <div style="clear:both; margin:10px 0"> <!-- Your AdSense code here --> </div> <div expr:id='"aim2" + data:post.id'> <data:post.body/> </div> <script type="text/javascript"> ...
Super-Related Post: GEODJANGO + GEOSERVER + OPENLAYERS COMBO! The scenario is we have a python script that runs on a given interval that automatically loads shapefile into PostgreSQL with PostGIS database.This shapefile is from a simulation done by a computer and it is updated on a timely basis. Near-real Time module of the app performs INTERSECT query to generate statistics. This involves two tables on the database. Every query took more than 5 minutes which is unacceptable. No matter how I try to change(optimize) my query, it's still SLOOOOOOOOOOOOOOOOOOOOOOW! So, instead of directly performing INTERSECT query between two tables every time the user take request. I have this instead: I created a stats table where the results are inserted and stored on it. After loading the shapefile into the database, a PostgreSQl function will be called and perform the INTERSECT query then insert the new result to the stats table. The database server will just perform select quer...