Thanks for your reply Victor,
I did a comparison of the user totals from the 'getPayments' data at the
end of the json reports file
with the totals paid in the 12 transaction files, so those very tiny
(<0.0001 BTC) amounts were
already disregarded; I assumed they weren't paid so it's great if you can
have a method of accumulating them.
That user name I saw with the bad bitcoin address was 'tshedy', mostly
editing Lesotho / South Africa,
probably that was the one you already knew about.
Here are those 11 larger payments that didn't seem to make it to the
transactions. (I identified the users
from the differences of totals due/paid, but went back and found there were
individual Worldwide/region
payments expected that matched the difference I had found in each case.)
{"month":"2016-09","region":"","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"hsc666","changes":"79","btcaddress":"1N972ZDrMq5U8sQPPZ3MQCBycDZZNLRytT","rank":3,"weight":18,"btc":0.0012972464710253},
{"osmid":"avm","changes":"37","btcaddress":"1NVnyBRvXQUuzSkv6vJTyQrX9W7jiXSG1P","rank":6,"weight":15,"btc":0.0010810387258544},
{"osmid":"Cd_spb","changes":"19","btcaddress":"1GeHJooiZgMzg4EHMsV9J2LtLEarDkhs7j","rank":8,"weight":13,"btc":0.0009369002290738},
{"osmid":"OverQuantum","changes":"7","btcaddress":"1Ec68EVLoKKPfnVf7rAgorHiAZQbxM7GK3","rank":16,"weight":5,"btc":0.00036034624195146}
]}}
{"month":"2016-09","region":"france_bretagne_europe","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"Le Grand
Blond","changes":"9","btcaddress":"1JjeJbP2ggoR1hhLeGhW8xN3brVx8k5FSP","rank":3,"weight":5,"btc":0.00043402777777778}
]}}
{"month":"2016-09","region":"us_north-carolina_northamerica","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"Sparks","changes":"34","btcaddress":"14PBjqAbVcHEssrtheSMzHq2LQXTpvGAMT","rank":2,"weight":6,"btc":0.00042613636363636}
]}}
{"month":"2016-09","region":"germany_mecklenburg-vorpommern_europe","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"holzheizer","changes":"70","btcaddress":"15tCX1WGDg1ZdsDoCaU2udo8FkDXz9hhGx","rank":1,"weight":7,"btc":0.00042067307692308}
]}}
{"month":"2016-09","region":"switzerland_europe","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"Cebderby","changes":"13","btcaddress":"1C2soFEn17DE8HrKxhQSFr5omJVC8dzw8J","rank":3,"weight":5,"btc":0.00034722222222222}
]}}
{"month":"2016-09","region":"australia-oceania","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"mueschel","changes":"7","btcaddress":"1Pds3UyHBfFnUgfPRtynQF8y65Hup4vJ8K","rank":4,"weight":4,"btc":0.00025}
]}}
{"month":"2016-09","region":"hungary_europe","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"aceman444","changes":"6","btcaddress":"1LHy9D8ZJ7LdDwCgcFpKsNtHmoT5eQqSPp","rank":5,"weight":3,"btc":0.0001953125}
]}}
{"month":"2016-09","region":"poland_warmian-masurian_europe","name":"getRecipients","report":{"month":"2016-09","rows":[
{"osmid":"Percherie","changes":"10","btcaddress":"37WQgombjxYjPboitiU77Dc71PVrDFxE3v","rank":4,"weight":4,"btc":0.00014204545454545}
]}}
Ignoring payments from/to your own '1GRg...' btcaddress, the grand total
from the getPayments data I found as 0.380099,
from the transactions 0.372471, making a difference of 0.007628. The user
with the bad btcaddress was due 0.001734, the sum of
the above 11 payments is 0.005891, making 0.007625 which corresponds apart
from the accumulation of roundoff/truncation differences.
Just an idea: as there were 12 transactions, and 11 missing above, it's
maybe possible that they were meant to be the first or last included
in each transaction, and 'fell down the cracks' between them? Maybe not,
but it's the first thing I'd look for.
Best regards, 'Cebderby'
On Wednesday, 19 October 2016 16:42:31 UTC+1, V S wrote:
>
> Hi,
>
> 1. Download page is fixed and now returns proper json to downoad (error
> was related that this is not an html page).
> 2. You are right, we don't pay to invalid address (I believe we contacted
> the person to change it) and we can't pay small payments cause the payment
> system doesn't allow.
> We made a decision to keep "unpaid" payment for the next month, that's why
> we always round up the number of BTC we've got from subscriptions. We might
> need to properly document or change the automatic payment algorithm, so the
> sum from all regions will be added to the world region.
> Anyway if you find something we missed not a small payment, please let us
> know so we could double check how did it happen.
>
>
> 3. We have a strong cache algorithms behind it, cause the page is too
> heavy to load (we update information every 5 minutes). And also for detail
> investigation it is advised to use JSON file and UI to use to check details
> of 1-10 items. We keep it sorted in order to search information quicker on
> UI.
>
> Best Regards,
> Victor
>
>
> вторник, 18 октября 2016 г., 18:35:22 UTC+2 пользователь Cebderby написал:
>>
>> A few notes on the current OSM Live implementation, triggered by
>> receiving slightly less for the 2016-09 payments than I expected. I
>> worked out that I was missing one specific region payment, but couldn't
>> tell if it was just me. So I've had a look at the available reports and
>> bitcoin transactions:
>>
>> 1. On the OSM Live site (Recipients section, viewing some September
>> data) 'Download all json reports for 2016-09' link shows truncated
>> content (in the browser). But you can save the full contents to a file
>> with a right-click-Save-Link-As... or similar according to your browser.
>> Turns out a user registered and made a few changes, with a user name
>> starting with a '<' which has confused things. Looks like it would be
>> useful if they were helped to change that name...
>>
>> 2. By comparing the totals paid and expected to be paid per bitcoin
>> address, it seems that there's:
>> - One user who has supplied a bad bitcoin address, and,
>> - 11 individual payments of either specific region or worldwide
>> payments that have not been paid, to 11 different users. (And it seems to
>> be real as I'm one). Of course we're talking about small amounts of money
>> but this should be avoided with what must be a highly automated process. 3
>> of the users had just a single Worldwide payment due, no regions, the other
>> 8 have had one or more other Worldwide or region payments made and are
>> missing a single one. Seems there are 4 Worldwide ones, 1 each for France
>> Bretagne, US N Carolina, Germany Meck.-Vorp., Switz, Australia, Hungary and
>> Poland Warm.-Masur. I do have the osm user names / btc addresses which I
>> can email / post if needed. No idea if this happened in previous months
>> (and it's pretty tedious to find out, so hopefully the root cause can be
>> found and/or the data checked).
>>
>> 3. I've a suspicion that on the website Recipients section, when you
>> change the selection of data to be viewed, it probably sorts the existing
>> data into an order (e.g. descending number of changes?) before throwing
>> that data away and loading what you've asked for. If so, it would make
>> navigating away from the initial Worldwide view to the first other region
>> much faster, and less load on the server?
>>
>> regards, 'Cebderby'
>>
>
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.