growse

23 ms·

421.
by growse 3y ago
The visual approach isn't an issue, it's the requirements to maintain visual separation. Under emergency conditions, you'd expect the separation to be handled by ATC.
422.
by growse 3y ago
I thought we were trying to decentralise?
423.
by growse 3y ago
> They are solving the problems, so why should they not prioritize them? > If that's not to somebody's liking, they are welcome to prioritize and solve the problems themselves. There's two types of problems that develop
424.
by growse 3y ago
> I care only about one thing: solving the problem! Who prioritises the problems?
425.
by growse 3y ago
This tension is why it's a good idea to align everyone's incentives. Bonus the product team on reliability (as well as velocity), and the ops/sre team on feature velocity (as well as reliability), and it'll balance itsel
426.
by growse 3y ago
It seems like you're arguing that the dev teams should spend some of their time managing the product. In other words, it's a 'hat' to be worn occasionally by some team members. Nothing wrong with that, except what typica
427.
by growse 3y ago
> People don't adopt software only because it is open source. It also has to be useful high-quality software. These things are symbiotic. It's a virtue circle. People find it useful, they contribute, other people then find it u
428.
by growse 3y ago
> The elephant in the room here is that software is incredibly expensive. Developing and maintaining a large project requires a large team of high salary software devs. There's plenty of expensive, major open source projects that se
429.
by growse 3y ago
> But Hashicorp's business hasn't turned a profit to date. And they rarely merge external pull requests. When they started out, they had enormous traction in the community because they were open source. People actively contri
430.
by growse 3y ago
> So software makers should give their competitors their software with a liberal free “as in beer” license and then try to compete with them. This is literally what they did when they released their product code under an OSS license. I
431.
by growse 3y ago
Meanwhile, hashcorp gets to profit off the contributions of others, whilst denying everyone else the opportunity to do the same.
432.
by growse 3y ago
There are actually people who reason like this. I remember being struck by this attitude when reading Bloomberg's book - effectively morally eqivocating business competition with stealing food out of their children's mouths.
433.
by growse 3y ago
Everything in life is only for now.
434.
by growse 3y ago
Someone needs to write a reddit "here now" prometheus exporter.
435.
by growse 3y ago
> My point is that I really don't believe that CI systems provide anything so unique that it couldn't be also provided by local software in a developer's laptop. If the question of "how do I build this in my laptop&qu
436.
by growse 3y ago
I don't have an iPhone, so I've no idea how it works. On my android device, I can plug it in or NFC it. Have you tried plugging it in?
437.
by growse 3y ago
This has a very "technically correct" feel to it, which doesn't actually translate into anything useful in the real world. If you think the very existence of HSMs threatens the concept of "ownership over your hardware&qu
438.
by growse 3y ago
This is fine if you treat your CI provider as a "dumb shell runner". But good CI platforms have actually useful features and APIs (e.g. caching) and if you want to use them, a simple Makefile isn't going to work. For projects
439.
by growse 3y ago
I can't look at the secret material in my solo usb key either. That's a feature . Do I have "zero control" over it?
440.
by growse 3y ago
Genuinely curious: what's the use case that's solved by being able to back up a passkey? Why is it not solved by simply registering multiple passkeys for your account context? Is it just friction of having to set it up multiple
441.
by growse 3y ago
Level 1 (I think they're talking FIDO?) is the bare minimum level. If Nitrokey aren't certified, there's plenty of open and proprietary keys not owned by "big tech" that are. https://fidoalliance.org&#x2F
442.
by growse 3y ago
So don't use them. Buy a yubikey and use that instead (or whatever). Passkeys are just webauthn, with more standardised flows around them.
443.
by growse 3y ago
No-one's forcing you to use biometrics. Stick a strong password on your device and now it's guarded by something you know.
444.
by growse 3y ago
Why is #2 important? Passkeys break the 1:1 relationship between credentials and accounts, so just register multiple passkeys. If it can be extracted, it can be stolen. Better to stick your secret material in a HSM that takes the key with i
445.
by growse 3y ago
If this isn't an open admission that it's such a shitty place to work, that they have to withold your pay to trap you there once you work it out for yourself, I don't know what is. Places that provide good working environment
446.
by growse 3y ago
Amazing, thanks. Bookmarking the lot.
447.
by growse 3y ago
Out of interest, would you also say that "images are arrays of bytes"? If not, what's the semantic difference? For me, strings represent text , which is fundamentally linked to language (and all of its weird vagueness and ed
448.
by growse 3y ago
I don't disagree, but you're arguing that the government gives a greater share of its tax receipts to the SEC. This is a question for Congress, not the agency. The usual assertion of "let's spend more money on x" re
449.
by growse 3y ago
Not even necessarily microservers. If you want a common authentication system used by lots of disparate services, token based Auth is a reasonable approach. If you've just got one service endpoint, it doesn't buy you very much. Ju
450.
by growse 3y ago
The access tokens go everywhere , to all services and are much more likely to be accidentally leaked / misappropriated. Refresh tokens are only used when talking (infrequently) to the access token minting service, so the scope of use

More ›