yurukov

SELECT a.timest,a.level, a.isinvalid, (select round(avg(a1.level)) from air_sofia a1 where a1.station=a.station and a1.param=0 and a1.isinvalid=0 and a1.timest>=a.timest - interval 12 hour and a1.timest<a.timest + interval 12 hour) level24,(select count(a2.level) from air_sofia a2 where a2.station=a.station and a2.param=0 and a2.isinvalid=0 and a2.timest>=a.timest - interval 12 hour and a2.timest<a.timest + interval 12 hour) validcount FROM air_sofia a where param=0 and station=1

yurukov

1. Open http://registry.plovdiv.bg/eDogs/default.aspx
2. Select 50 entries per page
3. Copy JS in console and run
4. Back up the downloaded data file
5. Extract all addresses:
  awk -F '\t' '{print $4}' plddogs.tsv | grep -v address | sed 's_,\? \?\(ет\|ап\)\.\? \?[0-9]\+ \?__g;s_ \?№ \?_ _' |sort -u > addr
6. Geotag the addresses:
  php geotag.php addr > addrg
7. Merge geotagged addresses with scaraped data and exclude columns:
  for i in `sed 's_\t_|_g;s_ _\__g' plddogs.tsv | grep -v address`; 

yurukov

I updated my permalink structure from .../Y/m/d/title to .../Y/title. 
Naturaly the share button count was set to 0 due to the new URL. My 
solution was to use the old URL structure for the share buttons only 
for posts before the update. The downside of this is that old posts 
will be shared with the old url structure. Thus when shared, there'll
be another 301. Upside - share count is kept. 

Also, I wanted to optimize the scripts written to the footer by the
share module of jetpack. The registered js file includes all the
scripts for opening the share dialogs in a new window. These are the

yurukov

These are a few commands that could be used to scrape a full group page
from Facebook. One can use the Graph API, but there some users would be
hidden. The JS commands should be run in a browser and scroll through
the page opening up hidden content and comments. I used Chrome. Once
enough content is opened, you should save the page as any other and
analyse it's contents. 

yurukov

yurukov

24102
39493
83017
73780
35746
65543
07257
35064
05009
72693

yurukov

This is a an abstract description of the loopback algorythm that @govalerteu uses to RT tweets from a selection of accounts.

The database keeps a list of all the accounts that are monitored with the timestamp of the last RT and check (run of this algo), the number of all tweets that were RT and the sum of their RT and fav.

For each account on regular intervals:
1. List all the tweets since the last check
2. Exclude all that are newer than 2 hours
3. Exclude all the answers
4. Sort them in 3 categories - tweets in Bulgarian, tweets mentioning Bulgaria and others. Sort these categories by the number of RTs and then by the number of fav.
5. Get the one on the top and check if it has more fav+RT than 2/3 of the average of those RT-ed until now for this account, but not less than 3. If the account hasn't been retweeted for over 4 days and 2 hours, RT the top tweet if it has more than 3 RT+fav.

yurukov

yurukov

yurukov

<?php 
$file = $argv[1];

echo date('H:i:s')."\n";
$image = new Imagick($file); 

echo date('H:i:s')."\n";
$image->cropImage(25000,11900,9440,23160);
$image->writeImage('cut_'.$file);
echo date('H:i:s')."\n";