2017-08-31, 16:57
The values in the slots are more nuanced than that author realizes. To get Alexa to pump out a literal transcribed string at the end depends several things, such as number of values provided and the distribution of the string lengths (by number of words). His suggestion that people simply manually type in 20-30 values can work, but it's very likely to either not work as well, or even not at all.
There really is no "windows way," other than the one caveat I mentioned. All of the other commands are identical on the various platforms. The fact that you got it to work under Windows may simply boil down to you being more comfortable with that platform, or simply executing something in a subtly different way that you didn't realize before.
I understand the howtogeek article provides more detail for things such as creating the initial AWS account, setting up dynamic DNS, etc, but the problem with people using 3rd-party guides for something as complex as this is that if we change how something works, we cannot guarantee that the 3rd-party guide authors will follow suit (and do it correctly).
HowToGeek seems to have been keeping up, but I imagine they won't do that indefinitely. Hence, the "right answer" is for that author to submit a pull request to get the official documentation cleaned up. But I've already indicated why they didn't do that in the first place
FWIW, it's on my TODO list to clean up the official documentation, but obviously new features are far more exciting to work on, and this is something I do for fun, after all.
There really is no "windows way," other than the one caveat I mentioned. All of the other commands are identical on the various platforms. The fact that you got it to work under Windows may simply boil down to you being more comfortable with that platform, or simply executing something in a subtly different way that you didn't realize before.
I understand the howtogeek article provides more detail for things such as creating the initial AWS account, setting up dynamic DNS, etc, but the problem with people using 3rd-party guides for something as complex as this is that if we change how something works, we cannot guarantee that the 3rd-party guide authors will follow suit (and do it correctly).
HowToGeek seems to have been keeping up, but I imagine they won't do that indefinitely. Hence, the "right answer" is for that author to submit a pull request to get the official documentation cleaned up. But I've already indicated why they didn't do that in the first place
FWIW, it's on my TODO list to clean up the official documentation, but obviously new features are far more exciting to work on, and this is something I do for fun, after all.
