19.xhtml 4.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. <?php
  2. /**
  3. * <https://y.st./>
  4. * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
  5. *
  6. * This program is free software: you can redistribute it and/or modify
  7. * it under the terms of the GNU General Public License as published by
  8. * the Free Software Foundation, either version 3 of the License, or
  9. * (at your option) any later version.
  10. *
  11. * This program is distributed in the hope that it will be useful,
  12. * but WITHOUT ANY WARRANTY; without even the implied warranty of
  13. * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  14. * GNU General Public License for more details.
  15. *
  16. * You should have received a copy of the GNU General Public License
  17. * along with this program. If not, see <https://www.gnu.org./licenses/>.
  18. **/
  19. $xhtml = array(
  20. 'title' => 'Don&apos;t choose Cricket Wireless if you are within T-Mobile&apos;s coverage area',
  21. 'body' => <<<END
  22. <p>
  23. I contacted Cricket support again, and they said that the order had not been canceled, but had been shipped and was on its way.
  24. To track the order, all I had to do was call $a[UPS] with my order number.
  25. I asked if I really needed the order number, not the tracking number, as the tracking number had not been sent.
  26. He said to try with the order number.
  27. I also explained that because the device had not arrived, I was completely unable to place any calls to anyone.
  28. After explaining this, I tried going to the $a[UPS] website and entering the order number there, but upon submitting it, I was presented with a 403 page.
  29. Presumably, $a[UPS] does not like serving $a[Tor] users.
  30. After telling the support representative about the 403 page, he looked at my account again.
  31. This time, he said that the order had in fact been canceled after all.
  32. Really? Is their system so screwy that from different pages of their interface they get contradicting information? Anyway, he told me I needed to go to an in-person Cricket store and have them fix the account.
  33. I was not happy with this answer.
  34. Not only would it mean paying an extra \$25 $a[USD] for no good reason, it would also likely mean flashing $a[ID] that I don&apos;t have.
  35. </p>
  36. <p>
  37. I tried fixing up the bike so I could get to the Cricket store and back faster.
  38. It didn&apos;t work out so well.
  39. The new inner tube fit and inflated properly, but it now seems that my wheel itself is a bit bent, leaving the tire scraping against the frame of the bicycle.
  40. With my bike still out of commission, I headed to the Cricket store on foot.
  41. The representative at the Cricket Store was of no help though.
  42. I explained the situation, and he explained that the Web support people have way more access to accounts than he does.
  43. He would not be able to fix my locked-up Cricket account, but at least he knew that right away and didn&apos;t waste my time trying to prod a system that he had no real access to.
  44. Simultaneously disappointed and relieved, as he wasn&apos;t able to help but did not try to card me, I headed back home.
  45. </p>
  46. <p>
  47. Once home, I contacted Cricket Web support again, who did not seem to understand the fact that the Cricket website would not allow me to place the order again due to the already-in-use user name.
  48. The representative kept insisting that I place the order again, no mater how many times I explained why the website would not allow me to.
  49. I talked him into transferring me to his supervisor, who claimed that my card issuer had marked the transaction as fraud.
  50. He also said that my user name would be unavailable for sixty days.
  51. </p>
  52. <p>
  53. My Discover account showed the transaction as having gone through though.
  54. If Discover had thought it was fraud, would they really have sent the money to Cricket anyway? I got in touch with a representative at Discover support to see what was really going on.
  55. According to him, Discover had not marked the transaction as fraud, or even suspected that it might have been fraud.
  56. From the sounds of it, the transaction was also only pending, meaning that the interface that Discover presents to me is slightly inaccurate.
  57. In any case, the issue is not on Discover&apos;s end.
  58. I would have hassled Cricket support some more, but I would have been late for my last day of work if I had done so.
  59. </p>
  60. <p>
  61. Today was my final day of work before my departure.
  62. Hopefully I can find a new job in Coos Bay fairly quickly.
  63. </p>
  64. <p>
  65. At work, I came up with a better idea than waiting for my user name to free up, assuming Cricket support even knows what they are talking about when they said that it <strong>*would*</strong> free up at all.
  66. Instead of trying to use my usual user name, I would use the user name field as a second password, another random jumble of characters that no one would guess.
  67. I placed a new order using a random user name just before going to bed.
  68. Hopefully the order will actually go through this time.
  69. </p>
  70. <p>
  71. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  72. </p>
  73. END
  74. );