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.
- 0 Posts
- 8 Comments
TimeWalker@lemmy.foxden.partyto Firefox@lemmy.ml•Firefox adds option to remove 'List All Tabs' button after user backlash41·7 months agoI’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
TimeWalker@lemmy.foxden.partyto Firefox@lemmy.ml•Manifest V3 updates landed in Firefox 127140·11 months agoJust 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
TimeWalker@lemmy.foxden.partyto Linux@lemmy.ml•Massive battery life improvements on AMD over the past year291·1 year agoAgreed! 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
TimeWalker@lemmy.foxden.partyto Linux@lemmy.ml•Craziest/most "exotic" devices able to run Linux?English621·2 years agoLinux can be run on an Nintendo 64. Mainline Kernel support has been added in v5.12
TimeWalker@lemmy.foxden.partyto Firefox@lemmy.ml•Mozilla opposes Web Integrity API proposalEnglish2·2 years agoAt 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
It’s by design as mentioned in this bug report.
There is a hidden config to cap the over magnification on shake
[Effect-shakecursor] OverMagnification=0