I’m just confused why this has annoyed users just NOW since the button has always existed. It was just a down-pointing chevron before it got changed to a new icon so it’s not like it suddenly popped up and took space away
I’m just confused why this has annoyed users just NOW since the button has always existed. It was just a down-pointing chevron before it got changed to a new icon so it’s not like it suddenly popped up and took space away
Just a reminder that Boox does not release the kernel source code and is thus violating GPL2
They incorrectly assumed that when Fairphone was working on the A14 feature update that they halted any and all security updates for existing versions which is not true.
Just in case somebody only reads the title and wants to ready their pitchforks:
And to reiterate a couple important points we’ve communicated in our previous updates published in March and May:
- The webRequest API is not on a deprecation path in Firefox
- Mozilla has no plans to deprecate MV2
Agreed! On a Lenovo Yoga Slim 7 X, I also had a big, big boost of battery life. It’s really great how far it came in comparison to a few months ago!
That’s the solution if you immediately tried to login and it didn’t work.
Twitch login has in general very misleading error messages. The exact same message with unsupported browser also appears if you take too long to login
In the article, it specifically mentions “Business users” and I can torally agree on that. Not many people use iMessage here in the EU or Switzerland anyway and for business I would say practically zero. I have seen bussiness use Threema, Wire, Telegram, Slack or Google Meet.
And heck, if businesses here have customer live chat with messenger, it’s either WhatsApp or Facebook Messenger.
I personally never had to use iMessage after the rise of WhatsApp - neither privately nor in bussiness.
Linux can be run on an Nintendo 64. Mainline Kernel support has been added in v5.12
At least with Firefox Quantum (v57) they have tried to continuously bring in optimizations to bump the performance. In the meantime there has been lots of work with WebRender, a newer and more robust Javascript Engine and better CSS engine which made it get faster every update. Being quite fast and snappy isn’t just a placebo since Firefox has lately started to get better Speedometer scores than Chrome
To be fair, they supported two different git backends, one of them being go-git which was the one corrupting repositories. However, it was never enabled by default, you specifically had to build Forgejo with a specific tag to instead use that as the backend. If you just built normally or pulled ready-made containers or bins then it was always the default git backend.