Woah, that's very generous of you. I have a question tho. I have a dual screen setup. What is in your opinion the best DX to develop for both mobile and desktop at the same time? My current approach is having an editor + docs + devtool on one screen, the website on the other with full screen. When I need to check how it looks on mobile I turn on the mobile mode thingy but I always felt it is kinda jank

xz is a bit silly too. Someone maintain it alone and look what almost happened. He got peer pressured to almost hands the project to malicious actor (which probably also by social engineering)

V1.2.3 is not unique to semver tho. So it could really be anything like linux 7.1.2. To be fair, linux does predate semver by a long time. But the point is that not every software with #.#.# needs to be semver. And I think better-auth, from the issue linked, has stated that they don't yet follow semver somewhere in their docs.

Damn, what's the movie name again? With Tom Cruise cloned and all?

Edit: It was oblivion

Naah, I don't really demand anything if the author breaks something on update. I just asked if the breaking changes are intentional and if there's a workaround. Failing that, I revert and look for other libraries or roll my own. To me Open Source is always about making something you love without any obligation. Not even to follow semver.

I wonder if XSS, CSRF and other client side attacks are still common

So in other words, it is just his pleasure

*Badum, tsss

Honestly, the wave of system integrator and people making SFF build to compete with steam machine already puts steam at the advantage. They already released SteamOS for every other desktop, that means system integrator and pre built can also make SFF with console like experience

Bloody great write up. Thank you so much for sharing this and thanks to the author for writing it.

I guess maybe because the site is still a work in progress? I'll give the dev the benefit of the doubt because all of the things that they try to tackle are not exactly web development. Here if you want yo read the docs.

https://gitlab.com/kyber/kyber/-/wikis/home

All of this wouldn't be needed if people care to actually use os keychain like kdewallet.

Sure reviewing changes is easy. But the problem is that it is still a review. You need to have an understanding of what exactly is being done and to account for any oddities that may or may not be because of the quirks of upstream. That's why I mentioned that AUR trust models should be made like pacman for most helper. We trust the maintainer of Arch so why can't we trust other people too? Take PPA, the trust model is exactly that. You trust the maintainer. At the very least make it an option that you can choose on first run