I ended up with two meteor developer accounts due to fiddling around with little understanding when I was just getting started. How do I delete one of the accounts now? I know this is a simple question, but I have searched the command line help, docs and manual with no success.
Go to http://meteor.com/contact
Select "Meteor Account Support"
Fill out the required fields and write a message asking to delete your account.
Wait several days, you may get further instructions to verify you own the account.
There are certain conditions where an account cannot be deleted:
have published packages
have app deployments
active login tokens
In my case, what I really wanted to do was convert an account to an organization, and for this the steps are similar:
Go to http://meteor.com/contact
Select "Meteor Account Support"
Fill out the required fields and write a message asking to convert your account to an organization
Mention the old account name you want converted
Mention the name of the new account that will own this organization
Wait several days for a response
At this point you will be asked to move the email address from the old account to the new account and verify it.
Add a new email address to the old account, verify it and make it the primary email address
Delete the original email address from the old account
Add that email address to your new account and verify it
Go back or reply to the email and let them know you did this.
Some magic will happen and hopefully the name of the old account will appear as an organization in your new account.
I found this issue that recommends emailing contact#meteor.com. (no longer used)
Some people suggested tweeting at some of the people of Meteor to hurry things along as well.
Related
In my Firebase web app, I offer 3 different authentication methods – phone, email/password, and Google.
When new users go through the FirebaseUI sign-in flow, sometimes they don't remember which method they signed up with originally and use a different method (which creates a new user). For example, they created an account originally using their phone number, but when they return later (unauthenticated, perhaps on a new device), they see "Sign in with Google" and try that option – which creates a brand new user/account.
They are then confused why their account state is blank/new.
Is there a way to define a sign-in flow as such, so that if a user does not exist, it should not create a duplicate account (or at least offer an option to link to an existing user)?
I'm using the FirebaseUI for simplicity and hoping there's a flag or something I can set in the config that will achieve this.
For example, they created an account originally using their phone number, but when they return later (unauthenticated, perhaps on a new device), they see "Sign in with Google" and try that option – which creates a brand new user/account.
That's normal behavior since you don't have any information that it is the same user. To solve this, you should collect the email address of the user first time he/she signs up with the phone number. In this way, you can check the second time, whether the user has already an account in your app by searching for the existence of the email, as explained in my answers from the following posts. That's for the Realtime Database:
Checking if a particular value exists in the Firebase database
And that's for Firestore:
Firestore query - checking if username already exists
Is there a way to define a sign-in flow as such, so that if a user does not exist, it should not create a duplicate account (or at least offer an option to link to an existing user)?
Yes, by getting specific data to recognize the user. You either get the email address, as explained above or you get the phone number if it tries to sign in the first time with Google.
I have upgraded a Firebase app to the new version, so I see my Firebase at console.firebase.google.com.
The console shows me a message Wow, you have a lot of users! Because you have over 500 users, they aren't automatically displayed. The only way to see any user details at all seems to be to search for a complete email address and that only works for users with a password.
I don't know how I came to have so many users, it's a development system and I am not aware of more than a dozen userIds. Regardless, I would like to delete them all.
I get the same message in a production system which also has less than 500 known users, so I must have some that are not real - I want to be able to view some details and delete them one by one.
The Docs don't provide a solution for either requirement. Any suggestions please?
This question is not related to ASP.NET specifically, but more web applications in general.
I am building a web application wherein I am registering a user. As of now I am taking in very basic credentials like First Name, Last Name, etc of the user. In this website I am giving some information for free for any user who has just registered so that the user finds my website authentic and that it is not a fake website. After that, to get more information, the user has to pay.
The information my site provides will get obsolete after sometime. So, when a new user registers, he/she will get the new information that gets updated; but the old users have to pay to get the same new information.
My problem here is once the information gets obsolete the same person can re-register with a different set of credentials and get the new information. I want to avoid this from happening.
So my question here is this: what information should I request from the user, or extract from the user, to check that the same user is not re-registering? Or any other way to make this possible.
I am thinking of getting the IP address of the machine from which the person is registering and use it to check. But the user can use a different machine to re-register.
I am completely lost here and not getting the solution. I even checked on the Internet but could not find an answer.
Please let me know if you need any further information from my side.
You will not find a technical way to prevent users from registering multiple times. They can simply use another device, IP, another email account and different credentials.
What you can do is asking them to send you hard to fake "offline" information, like a credit card number or a photo of the ID. Some users may still be able to register multiple times this way, but probably not indefinitly. You will however lose many possible clients this way who are unwilling to provide such information for a test account, so this is likely not the solution you want.
My advice would be one of the following two:
Limit the information/service you give out to free users, so that even if they register again they will gain something when they pay.
Try to bind them to their account in a way where they would lose something if they threw it away. This may for example be providing user rewards for activity (real or virtual) or increasing their experience based on their history. Take SO for example: If you registered again, you would lose all your reputation. The users will think twice if this is worth the new content.
After reading all of the above, i think a good solution could be to let the user identify himself through facebook or linkedin. Few people will have a second account.
I think you cannot put any users like that because every thing can be duplicate
There are some ways for which the user must have payment mode or identity details like passport or it is windows application you can have finger scanner it will be definitely Unique..
You can do this (with limitations) with the use of cookies. Setting a cookie on the users device will allow you to determine who the visitor is and that they have already registered.
The limitations are that cookies can be deleted or blocked and are only valid for that specific user agent - the user could use a different device or a different browser on the same device. A lot of people don't really know about cookies though and how to delete them.
By tying this technique with a requirement to provide a valid email address you can make it a hassle for somebody to register more than once as they will have to create a new email account and then delete their cookies.
Whether this will stop enough people depends on your site and your requirements - if you're giving money away then this technique is not nearly good enough. If you just want to discourage the practice of multiple accounts it may be enough.
Your only way out is to have SOMETHING the existing user gets as a "gift?" or added value to maintain just one account. If you can identify items of value to your subscribers and offer to "give" it to them provided their account "attains" one or more status, then you'll get some control. Take stackoverflow.com for example, I don't need a second account.
Identifying by facebook or linkedin is a good option, but if you are giving such services. which are very beneficial for the users, so they dont mind on creating multiple accounts on even facebook or linked in.
So what i think is to set some reward type stuff with each user, and increase the services as they get increment in rewards.once they are good in rewards and are capable to use multiple services, this increases the probability that they will not create another account.
Since the developer site update the other day, I have lost access to the sandbox.
I was literally using it an hour before the update.
I tried to retrieve my password, but my account is no longer found.
I tried to set up a new account, and it's telling me that I need to have a US registered business in order to sign up.
So, my question is, what does the rest of the world do when they need to test their site?
Am I missing something?
Thanks
Simon
Ok, Got it. PayPay support have said to create a dummy account. In other words, lie about having an American business. Once you've done that, go to applications, then sandbox accounts, and import the data using your old sandbox credentials!
I have the same problem. It appears to be even worse than stated. They appear to have 'integrated' the Sandbox login with PayPal account logins. So you have to have a live PayPal account. In other words developers must also be CFOs in their organizations, or else must be using PayPal as a means of exchange themselves, otherwise they don't exist.
Truly incredible.
Not to mention having cut off arbitrary numbers of existing developers in mid-stream.
Is there a way in the Drupal interface to exclude a specific user from workflow status without having to eliminate his account and make a new one?
Looking over his account, he does not have any of the roles to receive status but he does.
Alternatively, I'd rather be able to somehow search for his actual email in the entire system and make sure he is not listed anywhere. Is that even possible in Drupal?
Thanks
I had to just remove his extra account. He had an older account as a admin buried deep in the users.