🇬🇧/🇨🇦 living in 🇪🇸
I appreciate the concerns about nuance on social media, fair enough. I'll keep an eye out for more detailed discussion, definitely interested to hear more about concerns here.
I appreciate the concerns about nuance on social media, fair enough. I'll keep an eye out for more detailed discussion, definitely interested to hear more about concerns here.
If a maintainer's GH account is cracked though it is indeed game over. Passkey-only 2FA for GH _mostly_ helps there, I think? Still not perfect.
If a maintainer's GH account is cracked though it is indeed game over. Passkey-only 2FA for GH _mostly_ helps there, I think? Still not perfect.
As a publisher, it seems _mostly_ safer - more independent of my machine, lower risk of mistakes (e.g. including a file full of secrets, publishing the wrong content), much lower risk of phishing. Doesn't eliminate all risks, but improves things quite a bit.
As a publisher, it seems _mostly_ safer - more independent of my machine, lower risk of mistakes (e.g. including a file full of secrets, publishing the wrong content), much lower risk of phishing. Doesn't eliminate all risks, but improves things quite a bit.
Can also be limited to specific branches or tag patterns.
Can also be limited to specific branches or tag patterns.
Anybody I know going to DevFest? TBC but I'm likely to be there on Friday.
Anybody I know going to DevFest? TBC but I'm likely to be there on Friday.
Hopefully this is hit-me-with-a-wrench-security equivalent, I think?
Hopefully this is hit-me-with-a-wrench-security equivalent, I think?
Login anywhere with a yubikey tap for BW, 2fa with another yubikey tap, done.
Login anywhere with a yubikey tap for BW, 2fa with another yubikey tap, done.
Classes had their issues, but at least they behaved the same way as all the rest of my codebase.
Classes had their issues, but at least they behaved the same way as all the rest of my codebase.