For me, TLS errors would happen every so often after we had used all our data allowance and our connection was being shaped to a slow speed. Once the speed returned to normal it was fine. I always thought it was the slow speed but maybe there were bugs in the shaping software.
I previously used my partner's Google account to watch on YouTube and it had built up recommendations based on what I previously watched since I didn't use the subscriptions, but one day it all just disappeared and only showed recommendations from my partner's subscriptions. I'd prefer if they implemented a user driven exploration system rather than attempting to guess what I want but it must be useful to be able to change how it works without modifying the user interface. I eventually gave up and used my own account with now 32 subscriptions and it's better than it was although it shows a lot of videos I've already watched. It throws in a few videos from other channels but it's mostly from the subscriptions.
Exploit details were released a few days ago[1]. Some essential bits were removed, so not any script kiddie can use it, but it's only a matter of time before a full exploit available publicly.
As for how it relates to the app, I don't think it matters much. I'd imagine most people already have bluetooth enabled, so using this app or not won't change their vulnerability status.
GitExtensions includes a terminal and shows the commands it runs and I recently discovered the GitGraph extension in VSCode which allows having a terminal open at the same time. There's more text focused ones like Magit or Tig, I haven't used them personally but from reading the manual of Magit it looks like it can [1] and Tig allows for setting up custom commands [2].
I understand Microsoft needs to continue supporting IE for old websites but my boss a couple days ago used the Microsoft Lifecycle Policy as a reason why we, as website developers, need to support IE11 also. I would like articles saying people shouldn't use IE to also explicity answer the question, "Should website developers support IE?"
To me the answer to that question is another question - "what market share does IE11 still have amongst our target users, how fast is it decreasing, and what's the development effort required to support it?"
I'm just guessing but I think it would be easier to start from a perfect system and progressively work towards an accurate imperfect system rather than the other way of guessing an imperfect system and working back towards an accurate imperfect system.
