I have a fairly basic question regarding the new Box API v2.
I have developed a Firefox extension (FEBE) that performs automatic, scheduled, unattended backups of the user's Firefox profile. These backups can (optionally) be automatically uploaded to the user's Box account. I currently use the v1 API and it has been working fine for several years. I now see the v1 API is being deprecated in December, 2013. Does this mean it will no longer work, or that it is just no longer supported?
If I have to re-write my code (JavaScript) to handle the v2 API, will I still be able to provide the upload capability without any user intervention? FEBE securely stores the user's Box username and password and silently logs in to initiate the upload. From what I've been able to research so far, it seems the OAuth 2 verification process requires an interstitial page to confirm the users credentials. Is this true? If so, that would remove the 'unattended' aspect of the backup.
Also, can anyone recommend a good source of JavaScript code snippets that show examples of the Box v2 API in action (preferably not JQuery, just plain, old-fashion JavaScript)?
Does this mean it will no longer work, or that it is just no longer supported?
Yes, in December 2013 the V1 API will cease to function in its entirety.
…will I still be able to provide the upload capability without any user intervention?
The user will need to go through an initial web flow once to authorize your use of their account. After that, you can perform everything in the background.
There aren't any good sources of sample JS that I'm aware of, hopefully someone else can chime in on that.
Related
can you guys help me please to find any information about it, I'm sure there are good sources in which I could find all answers.
I have a testing project which requires me to login with a Google account into the web site, but the problem is that I cannot do it manually, like enter all data such as pass and mail itself, there are a lot of things preventing test to log in, different security stuff doesn't allow to use it like that.
I have tried to find some info but there are only "how to implement a google auth 2.0 into your web application", I believe that's not what I need.
I need just to log in into google account using some Testing framework, that's all.
Can google script be used to make the list broadcast api for you tube and the stream and basically can you make the broadcast samples using scripts i have made the other samples but it is unclear if scripts can be used to the broadcast. Also it appears that depending on the manor of which i access the scripts app I get different options. For instance if i access the the scripts app using google drive I can share and other stuff that is not available if i access the google drive though api and the regular free account. I wonder if there is a better way to access to get all the services? I think before the scripts service would not work for the broadcast. however it appears it has been updated is that because i have a credit card on file now? i notice i have more options now than before in scripts.
I found the answer yes you can make broadcast api from you tube ver (3) on google scripts as long as you have a credit card on file. That's cool google deserves to get paid. With out your card key elements are missing in scripts and everyplace else. Makeing it difficult if not impossible for hacks like me to get the api back on the internet. But with a credit card on file wow two clicks and its done no coding nada just change out the public api credential. I just wish this would have been told to me months ago. and please everyone forget about java, go, java-script and everything else if you want a web-service or web app from youtube api. Use in this order Python .php google scripts. But i did learn how to become a expert developer its called master card. this is my experience only and i still think its a great thing but if your not a genius use your card you will feel like one.
I built some widgets and uploaded on my local marketplace, is there a way to share that?
And better is it possible to share a Mashup (the widget composition) without giving the
possibility to wiring to the user?
I mean the user should use an application layout without change anything.
You can make public your workspaces/dashboards following the steps documented in the user guide. Only the owner of a workspace will be able to modify it. I think this is what are you searching for.
Another option is to create a packaged mashup using the "Upload to my resources" option in the editor view:
Take a look to the "Advanced" tab, where you can block widgets (make them unremovable), block connections (make wiring connections unremovable) and embed used widgets/operator (by default packaged mashups depends on the user having installed all the required widgets/operators. This way you can distribute the widgets and operators used by the mashup in the same package).
However, take into account that this method is meant for sharing mashup templates, the user will always be able to add additional widgets and create new connections in the wiring view.
Once packaged, mashups/dashboards (and widgets and operators) can be uploaded to a WStore server (e.g. to the Store portal provided on FIWARE Lab) for sharing them with other users. The steps for making this is also described in the WireCloud's user guide.
I have the problem, revisited.
I have set up a working Marketplace instance (v2.3) but am unable to integrate it with Wirecloud. The marketplace is correctly registered but all the requests i am making to this Marketplace are throwing 502 error, even though i am actually able to see some results when querying the Marketplace server through a browser.
Indicatively, i can issue a GET command at http://:8080/FiwareMarketplace/v1/registration/stores/ and get an answer, but Wirecloud's internal APIs return a 502 (Bad Gateway).
Any idea on what might have gone wrong?
PS: This happens for WC v0.6.5. When upgrading to a newer (Beta) version of WC, everything seems to be performing as expected, i.e. the marketplace is correctly inserted and the stores are correctly retrieved and processed.
Is it possible to get a real-time notification (without extensive polling) for changes made to a Google document (document / spreadsheet / presentation)? If so, what is the model structure (if that makes sense)? Any pointers to documentation or samples would help!
The documentation at https://developers.google.com/drive/manage-changes gives an API call that returns instantly and tells you whether there have been any changes since the last one. However, this is useless you want to know almost as soon as a change has been made -- you would have to make back to back API calls every second or sooner and churn a lot of resources. The Drive Real-time API in contrast gives a way to be instantly notified of any changes without extensive and frequent polling. It does this with an HTTP call that "hangs" until there is a change ready (or a timer expires). This is a classic long-poll technique.
My question is whether such a facility exists for Google Documents / Spreadsheets / Presentations. Or is it available only for custom app-specific files other than these standard ones. If it is not available, are there any plans for making them available?
Thanks in advance!
In my knowledge - the answer is "NO". I have tried this before and could only do it with the timed polling. The API is limited to tell you only when you ask, not when something happens.
I thought of a code that is embed into document and does a self broadcast to a specific URL or some listener. My experiments were with Google App Scripts. Detail idea is to create a custom function that gets triggered on the 'Save' event. But I could go no further as there is nothing enough in documentation as per me to achieve this specific goal.
On the timelines for this availability, there are questions in the scripts forum on this, but none replied on these lines.
It looks like it, see https://developers.google.com/drive/v2/reference/changes
it has examples too
edit:
https://developers.google.com/drive/manage-changes
more info about tracking changes
The answer, I'm afraid, is no. There is currently no way for you to be notified by email when a change is made to a Drive text document. This function is available for spreadsheets, but not for text files. If your document is public, you ccan subscribe to its RSS feed to view changes, or use the Tools -> Revision History function in Drive.
There is one downloadable program, googledocsnotifier --information--, which emails you when edits are made and allows you to open the doc that was edited, but it appears that it only works when you are online. You can download it here.
Hope this helps!
Could a chrome extension be made that maintains a bitcoin wallet while also making it easy for web stores to integrate a one-click purchase experience.
Suppose a button on a webpage is clicked. Is it possible for that to trigger a function call to the chrome extension to send bitcoins?
Obviously letting webpages unlimited access to chrome extensions would never have been designed. But is there some way to make this work securely?
Chrome extensions can insert arbitrary code into web pages (content scripts).
Content scripts are JavaScript files that run in the context of web
pages. By using the standard Document Object Model (DOM), they can
read details of the web pages the browser visits, or make changes to
them.
This code can communicate with the original web page via the DOM and with the rest of the extension via message passing.
In theory, this should suffice. But make it secure, please.
Multibit provides an external application solution
Clicking on a "bitcoin:" protocol URI in Chrome (or any other browser) will transfer the URI over to MultiBit (v0.3+), starting the application if necessary. This approach removes the need for private keys to be held (and potentially shared) within the browser.
This is very dangerous because a single security hole in Chrome could allow any website to empty your wallet.
First, any payment have to be confirmed with the wallet password. But, as that password is typed inside Chrome itself, it might be possible for an attacker to read that password.
In fact, there are so many security issues to solve that I think it's better to let the bitcoin client do that job.
What should be done is a way for any software to ask the bitcoin client for a transaction. The first idea that comes to mind is using DBus.
That way, the Chrome extension would only have to transform any bitcoin address by a button which calls a DBus method.
The blockchain.info Bitcoin Wallet provides some support for this
by using navigator.registerProtocolHandler and Bitcoin URI's. Unfortunately it only works in firefox at present.