#Xfinity #abancommercials #commercial Watch this video, give it a 👍❤️ (like), and follow me for more commercials
https://abancommercials.com/xfinity/-aposminions-monsters-online-magic-apos-commercial/296808/

Get Your Otamatones Here:Kirby (Deluxe):https://hamee.com/products/otamatone-deluxe-musical-toy-kirby-from-maywa-denki?ref=moshibassGudetama (Deluxe):https:/...
@lisp_1
Re: Receiving spam that appears to have scanned a received text:
It's certainly not a "browser" issue since no "browser" was involved (just the stock Texting app I've been using for years.)
It's an Android phone, so if Google is now scanning people's texts for Spamming purposes, I think I/we would of heard about it long before now.
Only thing new (within the past "year") is my cellular provider, #Xfinity. 🤔
WELL *THAT'S* DISTURBING! 😵
My father's Gastroenterologist texted me a confirmation for an appointment I made for Dad over the phone early this morning, and hours later, I received a SPAM TEXT from "DigestiveHealth". 🤨
Are my texts being scanned/read by advertisers to solicit me???
WTF #Xfinity? 🤬
Comcast Xfinity is participating in the California Broadband Lifeline Program, which I qualify for. I tried to do the application online via the Xfinity site (which is what you have to do).
It took four attempts because it only worked with one browser. I tried three before I hit on a browser that worked. The issue was a missing check box that stated I agreed with the privacy policy.
What sheer fuckery that you can only use one browser to submit the info. Firefox, Brave, and Vivaldi did not work. I had to use Chromium. Maybe it's different for people not on Linux? IDK but I'm annoyed regardless.
#Enshittification #Tech #Comcast #Xfinity #Poverty #Capitalism
Okay, I admit it. My problem with Xfinity yesterday was *most likely* entirely on my side.
(Let me explain the "most likely" bit. I did tests before calling them. I found that port forwarding to two *different* internal servers did not work. So I put the blame on them. I found what the problem was with one server, but I never found what was the problem with the other. When everything was said and done, the other server worked again, even though AFAICT nothing happened to this server.)
The culprit was that my Nextcould instance had gone bonkers for whatever reason. It had not properly restarted its Docker containers and thus was not answering.
What did I learn, other than the above?
I learned that dealing with Xfinity's AI or with Xfinity's CSRs amount to pretty much the same. They are going to ask you to perform impossible tasks.
Does this mean that the AI is as intelligent as the CSRs... or that the CSRs are as dumb as the AI? 🤷
I had the opportunity to talk with Xfinity (Comcast) support this morning.
I was treated to an upsell. Sure, it costs nothing for the first year, but then what does it cost? It is an upsell pure and simple. She said "you can cancel any time." I replied "You can cancel it now."
I was also treated to technical nonsense. The problem (which I still cannot say has been fixed) has to do with bridging and port forwarding. She asked for the name of my Wi-Fi network, which has nothing to do with these issues.
She should have realized she was talking to someone who knows something about networking when I sent her a traceroute output.
Screenshot of the upsell below.
And they wonder why they are so hated...