Hacker Newsnew | past | comments | ask | show | jobs | submit | ypeter's commentslogin

Are there any advantages of using asdf instead of Pyenv for Python version management (or disadvantages)?


I guess this limitation is on the size of the request body and including that doesn’t make sense for GET requests?


Maybe Cloud Armor calculates en sets it?


Yes, I'm sure, not even camping related ads. I'm a hotel guy.


I do use Signal. But unfortunately I lack convincing power to make everyone else use Signal.

But this is not about alternatives to WhatsApp, imo it's weird that this even happens/is possible.


What do you expect from Facebook? They make their money with advertising, of course they will exploit and capitalize everything that gets send through their channels.


I expect that they don't lie on their public website. This is what WhatsApp says on their own website https://faq.whatsapp.com/general/security-and-privacy/answer... :

  Neither WhatsApp nor Facebook can read your messages or hear your calls with your friends, family, and co-workers on WhatsApp. Whatever you share, it stays between you. That’s because your personal messages are protected by end-to-end encryption. We will never weaken this security and we clearly label each chat so you know our commitment.


Well they also promised to never exchange data between WhatsApp and Facebook when they bought WhatsApp. You simply can't believe any promise Facebook (or any FAANG company for that matter) makes regarding privacy or how they protect your personal data.


> it's weird that this even happens/is possible.

It’s not. This will happen with any chat app that is locked to a single service. Stop using those.


It's weird if even WhatsApp says it's not possible (see my other comment).


Cool, I'm gonna test this out. If it works well it's really useful.


And before this you could implement Cloud KMS in your app to decrypt the encrypted secrets you can store in your repo.


This still seems ridiculous. Why did I need to keep secrets in my repo to begin with? GAE, as far as I can tell, has been the only major PaaS that hasn't offered a solution for this. It's so easy to get wrong...it contradicts one of the biggest rules of version control: keep your secrets out of your repo.


There are a million ways to do it that don't require Google? Your CI system builds the production image, it can get secrets from anywhere.


My CI system arguably shouldn't have access to production secrets any more than my developers' macbooks.


No, Dependabot scans your repo on dependencies that have known vulnerabilities and suggests to update those dependencies.

This new GitHub feature will scan your code on potential vulnerabilities like SQL injection.


Wow, jinx, this is pretty much identical to the answer I just wrote!


Two benefits:

- I already use Helm to install open source software; there are already so many Charts available. So that makes it easy to also use Helm for my own apps (I use it just for templating though)

- Helm templating language is more flexible, but that can also bite you since it can become complex. With Kustomize, changing a single environment variable value in a Deployment is quite some work compared to Helm (I don’t like JSON patching)


> With Kustomize, changing a single environment variable value in a Deployment is quite some work compared to Helm (I don’t like JSON patching)

Config maps, enough said. I have a CD pipeline that writes environment variables to files, Kustomize eats them up and creates a configmap, environment variables in the deployment reference the config map, done.

Kapp as a layer on top of Kustomize is showing some progress. Ultimately Kustomize is like every other resource bundled with k8s, it’s a building block for higher level tooling.


What I do is just not respond until they say what they want from me.

And I also do this when someone just pastes an error message without a question.


Well, that sounds logical. I do the same, too.

1. Current work

2. Today work

3. Review for when work

4. Far future work

Everything in 1 and 2 are lined up for work. Anything without clear action items requires follow-up and clearly signals non-urgency so it's in 3 which is the end of the day. And a 4 is just intentionally forgotten.

If you stick that in your github.com/username/me/README.md then it's documented behaviour.


Same here. I have a “No Hello/Hi/Hey” policy. I just ignore it


Same. Or I reply "nohello.com".


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: