As Guid are unique (if correctly generated) you can reuse existing IDs. Be careful, though, because a malicious client can send any ID of course, not just a random one. So a client can easily provoke a collision among his own Guids. If all benevolent clients generate their Guid randomly, a malicious client cannot cause a collision with them. In that sense, a Guid is like a 128-bit password, which is exceptionally strong.
On the other hand, the way you generate those Guids is not using a cryptographically secure random number generator. So I guess you should make the server provide a secure Guid to you by issuing an AJAX call to it.
Since your algorithm is based on pseudo-random numbers generated by Math.random, and since the random number generator is seeded from the current time, it does seem that there is a risk of collisions.
Sometimes tenant administrators may want to change the number for outbound and/or inbound calls based on the patterns they created to ensure interoperability with Session Border Controllers (SBCs). This article describes how you can specify a Number Translation Rules policy to translate numbers to an alternate format.
To assign, configure, and list number manipulation rules on SBCs, use the New-CSOnlinePSTNGateway and Set-CSOnlinePSTNGateway cmdlets together with the InboundTeamsNumberTranslationRules, InboundPSTNNumberTranslationRules, OutboundTeamsNumberTranslationRules, and OutboundPSTNNumberTranslationRules parameters.
The maximum total number of translation rules is 400, maximum translation parameter name length is 100 symbols, maximum translation parameter pattern length is 1024 symbols, and maximum translation parameter translation length is 256 symbols.
In this scenario, a dial plan translates the number before sending it to the Direct Routing interface. When Alice enters 425 555 0100 in the Teams client, the number is translated to +14255550100 by the country/region dial plan. The resulting numbers are a cumulative normalization of the dial plan rules and Teams translation rules. The Teams translation rules remove the "+1" that was added by the dial plan.
Alice calls Bob using a four-digit number. Alice uses 0100 to reach Bob from Calls or by using a contact.SBC is configured to use non-E.164 four-digit numbers for Teams users and ten-digit numbers for PSTN users. The dial plan isn't applied in this scenario.
We recommend that you create separate projects for experiments, testing, andproduction. After you create a project, record the project number orID.You must provide the project number (or ID) when you make calls to theCloud Translation API.
Cloud Translation has a quota management system to help you and Google manageusage of the service. By default, the number of characters that you can send perday is unlimited. If you have a set budget, we recommend monitoring your dailyusage and adjusting quotas according to your planned spend.
If you plan to use the Cloud Translation API, you need to set up authentication.Any client application that uses the API must be authenticated and grantedaccess to the requested resources. For more information, see Authenticate toCloud Translation.
Client libraries are available for several popular languages. We recommend thatyou use these client libraries to make calls to Cloud Translation because theymake it easier to access the APIs. If a client library doesn't meet yourneeds or isn't available for your language, build your own custom code. Formore information, see Using your own clientcode.
For example, when you use a client library, it can determine your credentialsimplicitly through the GOOGLE_APPLICATION_CREDENTIALS environment variable.You don't need to explicitly specify your credentials in code. For moreinformation, see Client LibrariesExplained in the Cloud APIsdocumentation.
Caution: The Java client library does not support Android.If you are using Maven, addthe following to your pom.xml file. For more information aboutBOMs, see The Google Cloud Platform Libraries BOM.
I've managed to strike a deal with my local DHL and now use them to ship all of my orders worldwide. DHL requires the receiver's email address and phone number for every package that I send through them.
I haven't needed to try it but I've read some people in the forums mention using a personalisation option to request the phone number. Here's how to set that up: -gb/articles/360000344528-How-to-Offer-Personalised-Listings
If people are using older versions of the app then they might not be shown the personalisation box however it should be seen by a majority of buyers and if you make it mandatory then it might help reduce the number of people you need to contact directly.
As others have mentioned, for privacy reasons it may be necessary to disclose upfront in your listings, FAQs, etc that you will provide the buyer's email address and/or phone number to DHL for use during the shipment in case they need to contact the buyer regarding delivery.
You will need to use the personalization box to request buyers leave their phone numbers. Regardless you may still have problems getting phone numbers. You will need to demonstrate to them in the listing or FAQ that the phone number is for use only by the service you are using. Many buyers are reluctant to leave phone numbers.
Sorry but why is it invasive? I have a claim with UPS right now and I have spent $150 in shipping it twice $75 each time. Plus had to make the item twice because the first time it broke because UPS throws our stuff around and doesn't care at all that I spent 20 hours each time making it for my customer and made a meager $250. Now I don't have the ladies phone number for UPS to inspect the damage. So, I lose out on another 20 hours of work and another UPS delivery at $75. Yeah - I need people to give out their phone numbers or they can continue to buy crap from China. Luckily for me, I Googled her and found her phone number. I guess my bad for being a great business and getting her replacement to her promptly - because I am quite sure that if I asked for her phone number before she received her replacement she wouldn't be ignoring me now!
As a customer I would not feel comfortable giving away my phone number and email address to just anyone. You could probably use your business number and your business email. It might really discourage customers from buying from your shop. If you do decide to use their phone number and email address please disclose that in the listing before they decide to buy (or you might get some really unhappy customers).
That doesn't mean you have to use it. I wouldn't want a seller putting my email address and my phone number on the shipping label for the whole world to see. That would give me a bad taste in my mouth.
I'm about as paranoid as it gets when it comes to giving out personal info to *just anyone*. I objected to giving my BANKING INFO including SSN to Etsy when they forced me onto their payments platform. And since you are a US seller, you also gave them this information. Were you as concerned about that? Your address, phone number and email address are basically public information anyways -- thanks to hackers. Welcome to 2019. Equifax hack, anyone?
@zsjewelry I personally do not believe any delivery company needs a phone number. They have the address, and they have ONE job to do. Until recently they were all able to deliver without having a phone number. No one gets my personal information just because they say they need it.
IMHO, people are way too protective of information that isn't really private (phone numbers and email addresses, sadly, are not highly personal anymore thanks to corporations buying and selling them like they're commodities and hackers doxxing all of us every time a business suffers a data breach).
DHL is a legitimate courier (albeit not the best) that offers speedy, relatively low-cost international shipping. It's why my husband gets most of his stuff from Japan these days via DHL. Amazon Japan uses DHL. They're fine. They want your phone number so they can deliver your package in a timely manner. I'm really not sure what's so wrong about that.
@SprocketsInside and @lltrivwz - thank you for your concerns regarding privacy, I fully understand them. I do agree, the email address after all, is slightly less important than the phone number when it comes to delivery. But regarding the phone number, DHL will not allow me to send anything without the means to contact the buyer to let them know that their order has arrived.
After all, I guess the best way to go about this might just be for me to remember to convo each buyer to ask them for their phone number and explain that it is for delivery reasons. Might make buyers less reluctant by asking them myself than by having them fill it out under a personnalisation option...
@CraftyCornishMaids I've noticed on the Royal Mail website that they say it is advisable to have a buyer's telephone number (especially for international mail) but it is definitely not mandatory. I'm not sure why they would advise this if they wouldn't use it.
They don't use it, I've asked the postie, he doesn't have access to any phone numbers, and they don't do anything at the depot either. People either respond to the card, or the item is returned or if no return address, it's auctioned off
@CraftyCornishMaids I wonder whether their advice to use a telephone number means that, at some point in the future, they plan to make it mandatory for overseas mail at least. Perhaps one overseas country once asked for the information and somebody thought it would be a good idea to mention it on the website to cover Royal Mail?
I have a holiday home which is remote and hard to find, almost every delivery driver calls me to ask directions, if they had no number for me I'd miss out on my delivery and that would put my work behind.
dd2b598166