what difference it would do to have such a script and have this in ptokax, except the the time involved to change?

I don't know what ptokax is, can you elaborate?

----

On another note - to any active/standby witnesses I'm still seeking additional price feed publishers for the Norns. We've been stuck at 6 for over the last month unfortunately, only 1 more to activate.

Please explain what you consider a "User" in your statistics.

The Google Analytics is very limited, it's implemented using the measurement protocol as you can see here:
https://github.com/BTS-CM/Bitshares-HUG-REST-API/blob/master/hug_script.py#L74
https://developers.google.com/analytics/devguides/collection/protocol/v1/reference

The following shows device breakdown, with a 'mozilla compatible agent' being the highest, there seems to be continuous fetching of some cryptobridge market orders which Google Analytics is interpreting as between 70-100 continuous users. I'd imagine that if someone was implementing a production grade solution that they would run their own private HUG REST API with increased security though.

The intention of the Bitshares HUG REST API is to provide users an open-source high performance interface to the Bitshares network through simple GET requests. It's implemented using python-bitshares, HUG, nGinx and Gunicorn to offer 'unparalleled performance'. It's fairly easy to set up for a private API and doesn't require running a full server (though do respect usage limits).

I'm interested in potentially continuing development of the Bitshares HUG REST API through a Bitshares worker proposal, I've been maintaining it for the last 2 years as a fully open source project.

Would you support such a worker proposal in the future? If so, what would you like to see included? Is anyone running their own private HUG REST API?

Potential scope of worker proposal development:

• Functions which query account details are slow - this needs debugged/investigated
• Some functions are only for 1 asset, like getting price feeds for smartcoins, making more generic than specific functions
• Increase server size to increase gunicorn worker count
• Implement anti-abuse functions - currently there's nothing preventing anyone from consuming more than their fair share of resources, though caching does counter some of this concern
• Improve analytics dashboard - currently limited to what functions are hit and frequency over time
• Static HTML front end pages for some of the functions, the hertz page is fully generated rather than simply populated so it's pretty slow.
• Bitshares github org fork of my repo is behind in commits: https://github.com/bitshares/Bitshares-HUG-REST-API
• Create tests for the functions
• Create user requested functions
• Create a more sophisticated API key mechanism
• Host Bitshares full node server locally to the REST API so as to further reduce latencies
• Host a testnet REST API - currently only production available to save on billing costs.
• Implement basic 'write' functions for private API usage - currently all functions are read-only.
• Fine tune Gunicorn & server configuration
• Stream account history from full node via ZeroMQ into a Google BigQuery table. Implement HUG functions which interact with BigQuery.
• Split the python script down into separate python files for easier maintenance.
• Maintaining inter-worker data stores. Currently a few functions save to disk to get around this limitation, this could be optimized.
• Create example scripts to query the API using different languages

Current Github stats
* 8 stars
* 7 forks
* Forked into the bitshares github org

Last month's public HUG REST API analytics:


Related links:
https://github.com/BTS-CM/Bitshares-HUG-REST-API
https://github.com/bitshares/python-bitshares

RE: ZeroMQ implementation - https://github.com/oxarbitrage/bitshares-core/tree/zeromq/libraries/plugins/zeromq

Could produce a ZeroMQ client which streams to postgresql 👍

Some recent updates to the price feeds and documentation:
https://whaleshares.io/@customminer/norns-updates-improved-price-feed-scripts-and-documentation-changes

Would you be interested in publishing price feeds for 3 new Algorithm Based Assets on the BTS DEX? They're called Verthandi, Skuld and Urthr.

About: https://github.com/BTS-CM/Norns/blob/master/about.md

Here's the price feed script repo: https://github.com/BTS-CM/Norns

Parallel price feed script: https://github.com/BTS-CM/Norns/blob/master/parallel_feed.py (change the min price feed value difference at your discretion).

https://cryptofresh.com/a/VERTHANDI
https://cryptofresh.com/a/URTHR
https://cryptofresh.com/a/SKULD

It would be massively appreciated, thanks 👍

It's already possible to issue an MPA using UIA as backing collateral, you'd need to contact the gateway to see if they're alright, though technically there's nothing they can do to stop you doing this.