guest271314 (2019-03-07T23:11:31.000Z)
guest271314 at gmail.com (2019-03-07T23:48:53.947Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming ; http://embed.plnkr.co/5CwKsW/; "This account is temporarily suspended network-wide. The suspension period ends on Feb 28 '24 at 16:20."; https://twitter.com/guest271314/status/1102254119161491456). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others; e.g., https://stackoverflow.com/questions/47119426/how-to-set-file-objects-and-length-property-at-filelist-object-where-the-files-a ; https://github.com/guest271314/SpeechSynthesisSSMLParser. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:48:28.510Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming ; http://embed.plnkr.co/5CwKsW/; "This account is temporarily suspended network-wide. The suspension period ends on Feb 28 '24 at 16:20."; https://twitter.com/guest271314/status/1102254119161491456). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others; e.g., https://stackoverflow.com/questions/47119426/how-to-set-file-objects-and-length-property-at-filelist-object-where-the-files-a; https://github.com/guest271314/SpeechSynthesisSSMLParser. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:33:51.781Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming ; http://embed.plnkr.co/5CwKsW/; "This account is temporarily suspended network-wide. The suspension period ends on Feb 28 '24 at 16:20."; https://twitter.com/guest271314/status/1102254119161491456). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others; e.g., https://stackoverflow.com/questions/47119426/how-to-set-file-objects-and-length-property-at-filelist-object-where-the-files-a. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:31:52.080Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming ; http://embed.plnkr.co/5CwKsW/). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others; e.g., https://stackoverflow.com/questions/47119426/how-to-set-file-objects-and-length-property-at-filelist-object-where-the-files-a. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:29:31.298Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming ; http://embed.plnkr.co/5CwKsW/). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:29:02.531Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted user"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming; http://embed.plnkr.co/5CwKsW/). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenge faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:28:21.502Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is (hypocritically) practiced from top-down (CEO; management; moderators; "trusted users"; etc.) at the linked sites (full disclosure for your own edification https://english.meta.stackexchange.com/questions/12046/is-using-colored-girls-as-an-incidental-example-offensive-or-unwelcoming; http://embed.plnkr.co/5CwKsW/). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenged faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:26:00.453Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is practiced from top-down (CEO; management; moderators; "trusted users"; etc.) at the linked sites (full disclosure for your own edification http://embed.plnkr.co/5CwKsW/). That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenged faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:22:50.384Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to **censorship** which unfortunately, is practiced from top-down (CEO; management; moderators; "trusted users"; etc.) at the linked sites. That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenged faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:22:28.798Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to *censorship* which unfortunately, is practiced from top-down (CEO; management; moderators; "trusted users"; etc.) at the linked sites. That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenged faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.
guest271314 at gmail.com (2019-03-07T23:14:22.459Z)
Am not concerned with "down" votes. Do not really care about "up" or "down" votes. Would only object directly to *censorship, *which unfortunately, is practiced from top-down (CEO; management; moderators; "trusted users"; etc.) at the linked sites. That is beyond the scope of this proposal. Nonetheless, have posted questions and answers at those sites, before being censored, thus the links provided. The proposal states the *specification* is **WIP**. Handing leading 0's at decimal portion of number was a challenged faced when initially conceived the proof of concept. Which was solved by the answer at the SO post which fixed the two bugs described at the question at SO. Therefore, there is working code which can convert Number <--> Array, and *spread* a Number [...Math.PI]. The 1.0 is not a proper example, though illustrates the problems with JavaScript number implementation. An appropriate example would be 1.1. That is, a standardized way to represent a decimal as an array. Have already described a "real world" example, at least twice above, citing the original proposal. If you do not see that as a "real world" example, am not interested in trying to convince you, or anyone else of that "real world" example. What will more than likely eventually occur is that your "community" will ban this user after presenting evidence, as am not beholden to you or your views, and have no need to fit into to your "community". Am well-suited to solving own problems. Share when have a notion that what have experimented with may be of interest to others. Just posted the proposal to you here for your consideration. If the proposal is not useful, then disregard and return to your important affairs that you have deemed useful to your time.