An absolute gem! I find hard it to believe that such thing is possible in year 2022! And that no tester has ever caught such enormously stupid thing:
The good question is who to blame? Firefox testers, Twitter QA or both? But, the truth is that such thing is possible only in Firefox. Any other (normal) browser works exactly as expected and shows "0 Following".
OK, after years of refusing, I finally decided to register an Instagram account. No, no fukin self-promotion, but rather to "save" company name for a future-use project, before someone takes it for me.
I went to that dully website, filled all those tiny (at my large screen) forms, provided some verification code to tell these morons that I am not a robot (like they're) and... then I hit the wall with the "Open Proxy" sign on it.
For as long as we have computers and keyboards with Enter that long we're using this particular key to confirm selection from any list. Any kind of list. No matter what content or items such list has, we can sure that we can use cursor keys to navigate such list and we can hit Enter to confirm our selection.
This is so terribly obvious that it couldn't be more obvious. List = Enter to select something. Amen. Well... not for Microsoft.
Ever dreamed about any support that solves your issues in a matter of seconds? No problemo... register to Strava paid service and... here you go:
Of course you understand that these issues are not actually solved. It's just that a sport service that claims to have 85 million users is using so buggy user support platform that it closes issues in the moment they're created.
Question: How to contact Strava then? Answer: You can't.
Question: What am I paying for then? Answer: Screw you!
There's some magical limit on number of segments that a single user can create. Hell only know why there's such limit and why total number of segments is limited per... 16 hours not per full day or 24 hours.
But the best part is a notification to let you know that you've passed the threshold:
You see it after you created a segment (and failed to do so)!
In other words, you can click-out your segment as a complete moron only to hit the wall that you failed to create it due to limits enforced on you by Strava.
Strava engineers are too stupid (or too ignorant) to warn you that creating new segment is pointless before you start creating it.
Of course it completely doesn't matter whether you are paying to Strava or not. This stupid limitation is enforced equally for both free users and paid subscribers.
For recording sport activities Strava is just great. Full of features with great community and cheap paid subscription.
The problem is that everything works only when... everything works. If anything starts malfunctioning, is missing or isn't working as you expected then you are totally screwed. Because this is yet another company that has a support beyond any critics or imagination. That totally doesn't give a shit on their customers!
We have XXI century for 21 years so far and we have (in Europe) GDPR for three years. Privacy is key concern for everyone using Internet today, but not in Google.
Because Google hires a complete ignorants and morons at deciding level, which completely doesn't understand the meaning of the word "privacy", you are forced to use your real name in every Google Service.
It may happen in a really remote area (with a really poor Internet coverage) that Google Find My Device service won't be able to locate your device. In such situation you will be forced into... agreeing Find My Device service's T&Cs... again.
And then... over and over again... each time you hit "Refresh":
A real idiot must be responsible for writing this part of code.
Who else, if not a complete moron, could figure out such idiotic thing like displaying T&Cs, if there is no connection to the device?
Who else, if not a complete moron, could failed to catch such thing at QA stage?
TeamViewer is phasing out their Google Chrome extension. To speed up this process, their are false-blocking their free license users with following message:
There are three stupid fuckups in action here.
First is that their moron developers aren't even able to display correct value of until when a lock will be in force.
Second that timeout mentioned in this message usually happens about 15-30 seconds after actually establishing connection.
And third fuckup is that when you turn off Chrome extension and immediately run full-featured client, you'll see that your account isn't actually blocked, because you have full, uninterrupted in anyway access to the other machines or users.
Turning off TeamViewer client and switching back to Chrome extension reveals that... you're again blocked.