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.

Reply via email to