Viewing profile — dmitriv
dmitriv
HN member- Joined
- Sat, May 02, 2026, 11:58 PM UTC
- HN karma
- 221
- Public activity
- 31 items
- HN profile
- View on Hacker News ↗
About dmitriv
No profile information was provided.
Recent public activity
-
comment
Comment #48017220
FYI - we have posted update on the subject with more details, links and analysis here: https://github.com/microsoft/vscode/issues/314311 Hopefully this answers some more of the que…
-
comment
Comment #47995237
The fact that non-AI changes are attributed to Copilot is a bug. The intent was to allow customers to add attribution of AI-generated code. As with any bug, it was not intetional.
-
comment
Comment #47995199
Thank you so much for explaining the exact reason I did it! I am reading all pings from GitHub on VS Code and this was just turning into a stream of spam that wasn't adding much ne…
-
comment
Comment #47995183
I did both, didn't I? :-)
-
comment
Comment #47995148
Correct.
-
comment
Comment #47995141
I really did create a new account to respond :)
-
comment
Comment #47995136
I think this is a good point - perhaps there should be some commit-time UI which would let the user make the choice. Thanks for the suggestion!
-
comment
Comment #47995126
First comment does not sound constructive - are you interested in my opinion on (n)vim? I am not a legal, so can't comment on legal things. However, I have already responded elsewh…
-
comment
Comment #47994560
Agreed, fixed disableAiFeatures in my PR: https://github.com/microsoft/vscode/pull/313931 Will work on making it better later.
-
comment
Comment #47994546
The change was about helping teams ensure AI-generated code is attributed in commits - nothing to do with copyrights and the like. If you don't have to take my word for it - query …
-
comment
Comment #47994500
Sorry about that, it's being reverted: https://github.com/microsoft/vscode/pull/313931
-
comment
Comment #47994485
Switched back to opt-in here: https://github.com/microsoft/vscode/pull/313931
-
comment
Comment #47994483
That's ok :-)
-
comment
Comment #47994482
Thanks. Done here: https://github.com/microsoft/vscode/pull/313931
-
comment
Comment #47994479
It would be tricky, yes, since it depends on core editor functionality which is not exposed through the API.
-
comment
Comment #47994475
I don't refuse - what would you like to ask?
-
comment
Comment #47994474
Correct, this was the ask.
-
comment
Comment #47994461
Good feedback, there needs to be a more explicit opt-in into this for teams that want it. FWIW nobody's performance here will improve from having this metric :-)
-
comment
Comment #47994442
It is the middle of the night and I am responding. Anything specific you'd like me to respond to?
-
comment
Comment #47994431
Agreed on both points. Having it shown before going into the commit would let the developer decide whether they want it. #2 is fixed in my PR.
-
comment
Comment #47994202
I am reverting it because there are bug in the feature and it obviously does not work as expected. Any feedback is important, HN or not.
-
comment
Comment #47994193
Fair point. We did catch it internally in testing (as we use VS Code for all our work, so some folks did stumble on it), but I think we underestimated the impact and should do a be…
-
comment
Comment #47994183
Here you go: https://github.com/microsoft/vscode/pull/313931
-
comment
Comment #47994146
There are customers who would like to see attribution on changes where AI contributed (companies, users, etc). True, that's not everyone, but you can query our repo for the issues …
-
comment
Comment #47994112
Thanks for the PR, I'll work on getting this in.