How can I get data usage programmatically on my WP8? I found class DataUsage with properties BytesReceived and BytesSent. But on MSDN I found the following:
Remarks Windows Phone 8
This API is not implemented and will throw an exception if called.
Perhaps, somebody knows how can I get the traffic usage (for cellular/Wifi connection)?
Unfortunately, there's no API to get the overall traffic usage of the phone. Or at least, none available to third-party developers (there's probably some kind of internal API since Data Sense is able to display that information).
Related
We have a web application that occasionally receives web request that we detect as attempts to inject SQL code, from Google virtual servers (Compute Engine).
I was asked to find a way to identify who is responsible for said machines, so that we can take the corresponding legal actions on our part, or at least, confirm that Google shut down those servers.
What I need is to find a way to communicate with Google, by email or chat, but I haven't found information about it.
EDIT 1:
I have tried to communicate with Google to indicate the information I am looking for, but the only contact available in my case is with the billing department, which could not confirm that they will give me that information if I buy a technical assistance package. On the other hand, I understand that this package is to review requirements of the applications that you own, but in my case I am looking for legal information.
What was recommended to me was to enter the corresponding application in
https://support.google.com/code/contact/cloud_platform_report?hl=en
but I have not received a response for weeks.
I am disappointed in Google, especially because of the importance of computer security.
I will keep searching information.
You can find all information concerning Tech support, phone support and Chat support in your Google Cloud console. Also, this doc shows different supports based on your support role or package.
We are providing websites/CMS solutions for more than 2500 customers. Almost all websites have google-map module. So since google changed its map usage policy, from one day to another all those webs had an error on their map modules. We need to come up with some quick (and dirty) solution. We decided to use multiple api-keys, and devide domains between them - alphabetic. And we registered all those 2500+ domains under these keys - manually. One by one.
The solution worked until last week. Now we somehow reached some kind of limit, as we cannot register any new domains/referrers under one of those api-keys. The actual count of domains/referrer of this given api-key: 1537. The saving process yields an error with tracking code (which is every time I try different).
Is there really some kind of limit? Does anyone experienced the same problems. Does some time-economic solution exists?
Thanks for any help or suggestions. Peace!
There is indeed a limit of (at time of writing) about 1,000 referer restrictions per API key. You can create about 100 keys per project, so you can authenticate 100,000 domains with a single project. To proceed further, you can create multiple projects (note that multiple projects can be combined under the same billing account, so you would still receive a single bill).
As a short term fix, you can temporarily remove all restrictions on the key, so that apps relying on that key are functional again. Then you can take the time to release a new key sharding pattern that follows these guidelines.
I just created a feature request so that the situation can be improved, for this use case ("star" it, to be notified of updates).
Google has recently released an alpha version of API that allows manage API keys programmatically.
The best way to handle thousands of authorized domains is to use an API to programmatically manage your API Keys and their restrictions, and we have recently launched a new service that allows you to do this.
This API is still in Alpha. If you are interested in becoming a Trusted Tester for this service, you can use the following form to sign up, please read the instructions carefully:
https://forms.gle/qx2SMcarWCAsbWVp7
Please note that this API is not part of the Google Maps Platform. After you fill out the form, you will be contacted by the API Keys API team with instructions on how to get started, and how to receive support.
API Keys API is currently free of charge. However, please note that use of Cloud Endpoints may be subject to charges at high traffic volume. You can check the pricing sheet here:
https://cloud.google.com/endpoints/pricing-and-quotas
source: https://issuetracker.google.com/issues/35829646#comment12
Hope this helps!
I am following the video from the google keynote (https://www.youtube.com/watch?v=3nYyApSiSLQ). I also have the same beacon in the demo (iBKS 105) and managed to provision it to serve UID. By using Google's Beacon Tools, I am able to detect and register the beacon in Google Beacon Dashboard and add in my attachments and URLs.
However, the moment I am done with the procedure, I am not able to see any nearby messages/notifications on my device. The guy who presented the demo did it with ease and I am wondering where I went wrong. What a I missing? I have done pretty much what the guy told in his keynote.
I have tried serving for Eddystone URL and successfully broadcasted the URL. I would really like to get the UID to work also.
I'm the guy in the video who did it with ease.
App-free solutions work with -UID, -EID, -TLM, -URL. On Android, you don't need an app to make your beacons useful.
If you do have an app, be sure to use Nearby Messages so that you get the most efficient possible scanning. (Also, no bluetooth permission required -- only location.)
The TLM frame will provide things like low battery alerts on the dashboard. You don't need an app to see these; the battery level is reported to the service with any Nearby request (including for Nearby Notifications).
Choose an interleaving ratio of -UID to -TLM of about 10:1, depending on how much traffic you're expecting your beacon to get. (If it's in a busy place, and you only want updates once/wk, you can go much less frequently than 10:1 with your -TLM frame.)
There was a question about iOS. There's a Nearby Messages Cocoapod that you can use with your iOS app just here. There's currently no equivalent to Nearby Notifications on iOS.
HTH!
It seems that we can not get sensor data in the web workers. I wonder the reason behind it. The use case is that I am thinking about getting geolocation data in the worker thread and only send the processed version to the main thread.
For GPS, this post says it is not supported in the worker thread (no reason is given). And I double checked it, navigator.geolocation is not supported in web workers. For accelerator and gyroscope, we have DeviceOrientationEvent and DeviceMotionEvent. But we need to use them through the window object, which is not available to the worker thread. The same situation applies to ambient light event.
So my questions are:
Why navigator.geolocation is not supported in web workers? I don't see any reason to prevent it in the worker thread. I think there should be no thread safety or security problems.
Does navigator.geolocation belong to navigator? This looks like a silly question. But I cannot find a good explanation online quickly... Web workers have access to the navigator object. And I am confused why navigation.geolocation is not supported.
Why don't we have raw sensor readings from accelerator and gyroscope? I understand that the abstracted event is useful. But there are cases we want to use the raw data for processing. I find that PhoneGap provides ways to access raw sensor data, e.g., through navigator.accelerometer. But my understanding is that such API does not belong to the standardized HTML specification.
What are the related design decisions to decide whether general sensor reading should be supported in the worker thread or not? General sensor reading support in HTML is currently shelved according to W3C Device APIs Working Group. Seeing current sensor support (gps, accelerator, gyro), I think we will get abstracted DOM events. And it is likely to have raw sensor data readings through the navigator object.
OK. After reading some Chromium code, I have the answer to my own question 2 now. I still have no answer to the other 3 questions...
Answer to question 2: Does navigator.geolocation belong to navigator?
navigator.geolocation belongs to navigator in the main thread only, but doesn't belong to navigator in the worker thread.
The main reason is that even though the navigator in worker thread looks exactly the same as the one in main thread, those two navigators have independent implementations on the C++ side. That is why navigator.geolocation is not supported in the worker thread.
The related code is in Navigator.idl and WorkerNavigator.idl in Chromium code. You can see that they are two independent interfaces in the .idl files. And they have independent implementations on the C++ side of the binding. Navigator is an attribute of DOMWindow, while WorkerNavigator is an attribute of WorkerGlobalScope.
However, on the JavaScript side, they have the same name: navigator. Well, I understand that the two navigators are in two different scopes, so there is no name conflict. But when I use the APIs in JavaScript, I expect similar behavior on both main and worker threads if they have the same name. That's how the ambiguity happens.
is it possible to access, invoke and see the results of operations in chrome://net-internals/ WITH and from the extension code that I am trying to write/build?
Not directly.
The closest analog is the WebRequest API, which gives you access to various bits and pieces of the network requests going back and forth between Chrome and the server. That doesn't, however, give you access to some of the even lower-level details that you see in net-internals.
What exactly would you like extensions to have access to? I'd suggest formulating a clear use-case, and filing a feature request: http://new.crbug.com/ as your best bet.