Live data from Hacker News

Show HN: Kite, copilot for programmers, available for Python

kite.com

251–257 of 257 posts

Re: Show HN: Kite, copilot for programmers, available for Python

#251

Earlier quoted context omitted.

It's not so much the upload, but the fact that it will always be unclear (and dynamic) what this service will do with a particular LOC. You might store sensitive documents in Google Drive, but it is unlikely you will type something sensitive into Google Search. Because it is a smart autocomplete feature, there will always be lack of clarity of when they delete your files, if at all. Github and PaaS do not have any di…

> It is also worthy to note that this is a live tool. With other services, one has a chance to clean their code before upload. With this, even playing around with an API with embedded keys in your code has already put you at risk. Wow that is a really good point.

Kite address this below, they said they're working on adding:

"Fine-grained privacy controls modeled after the .gitignore file format means that you can selectively and precisely decide which files and folders Kite indexes"

Re: Show HN: Kite, copilot for programmers, available for Python

#254

Since this program uploads code to the cloud, it would be worthy to clarify if it cleans out strings before upload or not. Because if it does not, it is a serious concern as it puts secret keys in code in awful risk. They also run a background process that needs to be manually killed to be able to uninstall. It feels like a quarantine. This is an editor plugin, is there really no simpler way to provide uninstall capa…

1. On MacOS X it's quite impossible to kill the helper and engine processes, so you can remove Kite.app. Something is restarting them automatically, which is really frustrating. 2. It's completely unacceptable to upload code to the cloud.

So you don't use GitHub.

Re: Show HN: Kite, copilot for programmers, available for Python

#255

Earlier quoted context omitted.

Totally legit concern. when we started working on this we realized if we wanted to index tens of thousands of libraries, we wouldn't be able to ship the entire index along with the client. Hence the cloud-based architecture. We've thought a lot about privacy and written up our thoughts here: kite.com/security. The short answer is: we don't index anything on your computer that you don't explicitly ask us to, and our p…

I'm sorry but the true intention is to have recurring revenue and not have licensing issues with open-source software you're leveraging on your backend. It's fine to be a capitalist, and I'm looking forward to using and paying for kite once my language of choice is supported, but come on, just be honest that you need a source of income to create this amazing product and this model is the one that fits the bill best.…

This.

This reason applies to a lot of todays web apps. with the emphasis of recurring revenue.

Re: Show HN: Kite, copilot for programmers, available for Python

#256

Earlier quoted context omitted.

My largest concern is how frequently is my code sent to the cloud? Sometimes when building integrations, I hard code private keys just to get things working and then pull them out into config files that aren't checked into source control. Not knowing where that key might have gone would bother me.

One of the big things we've worked on over the past few months is giving users fine grained control of which files are indexed by kite: - Kite only indexes directories that you have explicitly enabled - You can create a .kiteignore file (same semantics as .gitignore) to exclude specific files / patterns.

[deleted]

Re: Show HN: Kite, copilot for programmers, available for Python

#257
post #8

Earlier quoted context omitted.

Does Kite still send all your code to Kite servers as you type? I remember that being an issue the last time someone talked about Kite on HN. I'm find with an editor or sidekick that can search stack overflow or duckduckgo or google quickly with a hotkey-- maybe keep snippets you can tag and easily reference-- but sending all my code as I type to a web service is something I'm not willing to do and something most com…

(Copied from above.) Totally legit concern. when we started working on this we realized if we wanted to index tens of thousands of libraries, we wouldn't be able to ship the entire index along with the client. Hence the cloud-based architecture. We've thought a lot about privacy and written up our thoughts here: kite.com/security. The short answer is: we don't index anything on your computer that you don't explicitly…

I think this answer (which you used in few places here) does not address concerns people raised all over:

1) kite is useless (or at least substantially less useful) if you explicitly disable files/directories.

Example: Customer says: This fridge I bought, poisons my good. Company: If you don't put your food into fridge its not poisoned. Yeah, but it also not frozen afterwards, which was the reason for the fridge! And no files/directories/lines/whatever policy does solve that problem. Partially because of 2)

2) Human errors will kill this. Just google for number of problems around security tokens, sshkeys and other thing commited to github by mistake.

The only solution is LOCAL index only.

Post reply on HN