Is there a convenient programatic way to create google plus test users?
I searched through most of the google plus apis provided in their dev resources portal, however did not find a decent way to create test users.
Any advice would be very helpful.
For general use, no there isn't a programmatic way to create test accounts.
However, if you have a Google Apps domain, you could use the Admin SDK to create user accounts within your domain, which would likely suffice for most testing that you might need to do. You'd also need to make sure that Google+ was enabled for the domain. And there are some limitations, such as not being able to use the plus.login scope.
I realize this solution is unlikely to work for most people, but you never know.
Related
I am developing an application that will let users login via Twitch.
We already support Facebook login.
For Facebook, testing was easy as through a developer account I could create 2000 test accounts and signup using them one by one.
For twitch, I could not find anything similar. I am signing up everytime, verifying the email and then testing. Is there an elegant solution to this?
(I hope this won't be marked inappropriate as this is not a programming question)
Thank you.
There are no easy way to approach this,
Although Baba Tools has made a really descent tool for that, which creates temporary emails and verifies them.
I think it's the easiest approach you can get.
There are few others in the market, but babas probably the best.
Twitch does not have any api to create test accounts.
https://discuss.dev.twitch.tv/t/creating-test-users/3803
Like most people, we're pretty impressed with BigQuery. We're willing to put up with it being based on proprietary "Dremel" in exchange for not having to configure a ton of servers in our LAN, on EC2, or anywhere else.
The REST API is excellent, and we're incorporating that into our apps, but we still find ourselves using the BQ Browser interface as well. We'd like to incorporate something like a 'generic SQL window' into our app, without divulging that the backend is BQ or that data is stored in Google at all, for that matter. Does Google provide a way to use their BQ browser tool in a white-label manner?
Note also, that even extending access to the existing browser tool is problematic. It relies on user-accounts existing in one's own domain - something that can't be done, in our case, with a customer's email address. The REST interface solves this with service-level accounts, but that doesn't get you to the SQL window/browser tool.
If the folks at Google are listening (and I know that you are), consider the benefits of white-labeling the browser tool: I think you'd find a lot of software companies integrating it into their suites of products and, then, running circles around any Hadoop/CDH/EMR/Impala/Hive combination.
So, to summarize: How does a software developer import or emulate the BQ browser tool (with all it's autocompletes, query histories, etc..) in their own web-based app?
The initial version of the BigQuery web interface was considered just an 'example' UI that anyone could create themselves. It uses only the public BigQuery API to talk to BigQuery.
There are a couple of Google-internal things we've added since then, such as the current design of 'saved queries', and an auth shortcut so that users don't have to explicitly grant permission to the UI to access BigQuery data. But it is still mostly plain-ol-javascript talking to BigQuery via the REST API the same way anybody else does.
The javascript is obfuscated, however, but my understanding is that this is just for compression purposes so that it downloads more quickly.
The SQL highlighting is done by CodeMirror with special configuration for the BigQuery SQL variant.
I'll talk to the other members of the BigQuery team about open-sourcing the javascript code in the Web UI. It may be difficult to do at this point, but it doesn't hurt to have a conversation about it. I'll bring this up with the team and update this thread. The most likely answer will be "We'll think about it", but hopefully we can also think about it and start working on it too :-)
Let me know if that sounds like it would meet your needs. It might not solve the auth problems you mention, since your users likely won't have BigQuery accounts, but you may be able to solve that by proxying oauth2 access tokens.
I am looking into creating a login for my website. I am currently receiving free hosting from my college (UW Whitewater) server. I have learned HTML, CSS and JavaScript fairly well, but have not used any of these three languages a ton.
I would like to create a login for users to login to see their account information and use a web app that I will be creating in the future, but for now that doesn't matter.
I would like to know an overhead view of what I need to be able to have a login and keep account information for users.
Now I'm guessing I'm gonna need a database, and some kind of PHP or server-side language. Which language will be the best? As for the database is it possible to use an Access database? Also I dont know if UW Whitewater has mySQL that I can use or not? Is that possible? I would like to keep this free... college student here haha. I would also definitely be willing to learn a new language too.
Thanks for any replies in advanced!
If I were you, here's what I would do:
Decide what server-side language you want to use and which database you want to use based on whatever is available at your college. Although it is possible that they support many languages, if you ask the local IT administrators they will probably be able to suggest the best one for you, or they might even have a standard that they mandate.
Once you know which server-side language and database, do a web search on how to create a simple user login page with that language and database. There are tons out there.
If you run into any specific problems with your chosen solution, this would be the place to post them. But your question at the moment is probably a bit too broad.
Is it possible to use Mailchimp API to subscribe emails to the lists of MY USERS' Mailchimp Accounts and not my own?
Basically I have a web app, and users collect emails of various subscribers through this app. I then want them to be able to click a button and subscribe all those emails to their lists.
I've looked at Mailchimp's API - particularly the /lists/subscribe and the /lists/batch-subscribe methods. However so far it appears that these will only work for your own Mailchimp account and not for remote users' accounts.
Can someone please tell me whether what I'm trying to achieve is possible with Mailchimp's API?
You would need to execute the api-calls with your users' api-key, which would mean that you execute the calls with their credentials.
There are three different ways to get their api keys, with different practicality levels.
You guess. They look like guids without dashes, and some information about which datacenter it is associated with. Some easy (and somewhat bad) calculations indicate that there are 2^128 api keys in every datacenter, so this will consume both cpu- and network-resources, and invoke the rage of the Mailchimp. The linked image shows him on a good day. He won't be as pleasant if you choose this alternative. Dont do this.
You ask, in an evil way, for their username/password. This is bad since it will give you to all accounts those credentials works with. This would also give you access to stuff that aren't available using api calls (like payment stuff). This wont work at all if your user is intelligent administrators that are using AlterEgo, the two-factory security alternative. This alternative is less bad than blindly guessing, but still provides too much access, if it works at all.
You ask, in a user-friendly way (with perhaps some quick tutorials), for the user to generate an api-key in mailchimp to provide to you. This is the Good Alternative (tm).
You may choose any implementation as long as you choose number three.
In particular I'm interested in the possibility of getting an App Access Token with no expiration time, exactly as I do with Facebook.
I want to publish on behalf of the user via server, and I found very useful and convenient the Facebook's procedure in which we ask for the user permissions only the first time.
I have been working with this kind of social-networks interaction for merely three weeks, so I will be very happy to hear any type of suggestions or critics.
Google+ does not currently have a public write API. There are selected partners that they work with (such as HootSuite) that provide this feature, but they are making access to it available very slowly. See https://developers.google.com/+/api/pages-signup for further details.
Google+ does have a concept of Moments, which are activities that happen in your app that are reported to Google+ and which the user may later wish to share, or may make available to people in their circles on a limited non-notification basis. This is probably not what you want, but may serve some needs. See https://developers.google.com/+/api/latest/moments for more info and examples how to use it.
Simply, No there is no way to do that in Google+ in current time. In general, apps for Google plus is read only.