Well, well.... (눈_눈)
Received a response from Vimeo requesting that I Factory Reset my Roku Tv.
My Response? "Absolutely, I will NOT factory reset my Roku Device."
In the spirit of openness and transparency, I submit the following-
Repeatedly I have pointed the finger back to the ASP Roku TV app and with the evidence on my end which supports it as the not just probable, but "likely" cause of the problem. Vimeo's response has been and continues to be a complete disregard of what I've presented just like what I've "said" hasn't even been heard.
(One of the tells that would let anyone know they are in a conversation/situation with someone who is using rules from the "Bad Debater's Handbook" isn't r e a l l y participating in good faith...) (_Oo)
The "Factory Reset" is an an example of Vimeo "doubling down" in their approach to the situation here. That approach is loosley, "No problem on OUR end. The problem is on YOUR side." YOU do this/that and jump thru ALL the hoops we present. (YOU do ALL the work fOaR us.)
And Factory resetting my Roku TV is fairly quick/easy just by making a few selections on the right screens. But it is a LOT of work afterwards. I mean this isn't like my Dell computer(s) where I can reset it back to the first OS install and then bring it back to the last/most current and preferred setup by loading a backup. Roku doesn't DO things that way. (⥀.⥀)
Right now I'd bet $100 that even if I DID the factory reset I'd have to report back later, "Nope. That didn't fix the issue." And the next response from Vimeo would be something akin to, "Well, WE have tried just about all WE could do and it looks like WE are running out of options here." Sorta like, "We've fought the good fight my lads but we should be prepared fOaR defeat."
Which IMHO, is exactly where Vimeo intended for this issue to end up from the beginning in this customer service "Flow Chart."
1. Deny the problem is on Vimeo's side of the issue.
2. Assert/insist that it's the user's software/hardware.
3. Keep in communication but STAY the course of reversing the blame (Flip-the-script) until the user accepts this or simply gives up and/or goes away.
Well, well... (Ծ‸ Ծ)
Neil, we're gonna have to go j u s t a little deeper down the rabbit hole to understand what Imma gonna do NEXT. (ʘ‿ʘ)
Remember John? Mr. Correia? Brilliant and effective man who has read and recommends the book, "How to Win Friends & Influence People" by Carnegie? Give him a ring and see if he's read or applied the book "Winning Through Intimidation" by Ringer. Cuz iffin' John has, he would recognize the gameplay/strategy Vimeo is using here as a textbook case of the second of three types of ways the "crook/thief" employs to get something they haven't worked for, haven't earned, and don't deserve. They try to get the "victim" to just "understand-and-accept" the fact they're not getting what they should as well as "accept" the thief isn't a bad guy.
SOooo, we go back to the beginning and the first mis-step in the troubleshooting process with Vimeo. Remember that the app worked fine fOaR MONTHs and then started misbehaving?
My working theory is that at some point, Vimeo pushed an update of the app for some practical or cosmetic appearance issue but somehow gOoFeD it somewhere in the code that makes it compatible with the Roku app version installed on my TV. TBH, I did discover that my Roku TV updated it's own system version in Jan 2024.
Regardless, Neil, anyone not living under a rock knows of instances where Microsoft WEEndows pushed updates that caused certain computer brands to BRICK. Also had customers/users tearing their hair out due to malfunctions and incompatibilities until MS released the patches that fixed(?) the problems the updates caused.
Also plenty of examples of independent apps/programs out there that somehow missed this "moving target" of keeping up-to-date with the OS updates and putting out their own updated program versions with buggy/broken tools. (_Oo)
Sound familiar to the current Vimeo/ASP app situation? I think so. Only instead of going back to examine their own app/version, find the problem, and issue a patch (updated app with a new version number...)? They're demonstrating they'll do anything and everything BUT that. Including trying to marginilize/trivialize my situation as the majority of app users being satisfied with me being "the only one with this problem."
All deception and misrepresentation on their part, Neil. (╯°□°)╯︵ ┻━┻
Imma putting this next part forward cuz we're both experienced (and hopefully WISE/ETHICAL) tech dudes.
In this "dynamic" between VIMEO (caps intended foar the COMPANY), I am only a "user/customer" (NO caps at all...). Telling them what do do is likely to be treated like "the tail telling the DOG how to wag". But that's exactly what NEEDS to be done here from a technical/troubleshooting perspective.
While I (customer/user) have had to jump thru hoops and provide screenshots as the evidence showing imma participating in-good-faith, there is a conspicuous absense of any evidence showing VIMEO's actions or efforts in this "team game-play", don'tcha think? (⊙.☉)7
Imma thinkin' it's practical, reasonable, and sensible that if they're developing the ASP app fOaR Roku TVs? They surely have a COPY of the app I keep finding/installing from the Roku Streaming Store.
Also they, as the developers, should have the ability to acquire (or already HAVE...) the particular System/OS installed on my Roku TV. I mean they requested I provide it and that info WAS provided to them weeks ago.
Mebbe they don't have a physical RCA 55 inch TV in a closet somewheres but I would hope/expect they own/use a decent computer with the correct EMULATOR software. How could they possibly develop/debugg apps for their customer/users without these "tools" to ensure proper performance as well as customer satisfaction? To do so without these tools? IMHO that would be reckless AND irresponsible. щ(゚Д゚щ)
SOooo, Neil. In the mostest calm and reasonable way, imma gonna request politely that they (VIMEO) actually do what they should have done in the beginning- Load the ASP app (the version on my TV..) into a TV Like mine (or an emulator would suffice noicely...) and most importantly, take SCREENSHOTS for the standard "proof of doing their own homework".
Likely the first/fresh install will behave properly and show the thumbnails. But if they wait 24 hours for the next "MUST-SEE" content from any of the ASP Content Creator Team to be uploaded/presented??? ¯\_(⊙︿⊙)_/¯
Dunno...We'll have to see what THEY experience, right? If it's their app being goofy then same missing thumbnails. If not? We continue brainstorming together from there.
BUT, Imma going back to the "winning thru intimidation" framework they've latched onto like a monkey trying to grab a banana inside a mason jar but can't pull it out cuz their fist is too big to pass through the jar opening. ( ఠ ͟ʖ ఠ)
Predictions, Neil?
1. My request doesn't even get a reply or if they DO reply, once again they'll act as if it wasn't even made.
2. Some repeat of the ongoing "Intimidation" strategy where they attempt to explain indignantly they don't NEED to show proof of their homework and double/triple down on the "its MY problem" to force the issue down the greased rails of their "Flow Chart" to destination Farked.
3. FAKERY/FRAUD. I mean screenshots where they rise to the occasion presented here and show the app performing exactly as the concept says it should. Y'know, Neil. Like the Vimeo team gets together and decides to go all "CHALLENGE ACCEPTED" and compose/present the fake shots just to bring the team together as a project demonstrating their solidarity against this upstart customer/user. Battlecry- "FOAR THE LOLS!!!!"
Place yer bets, Neil. (⊙﹏⊙)