this post was submitted on 27 Jun 2023
20 points (100.0% liked)
.NET
1431 readers
9 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would imagine all that was detailed in the license.
That's not a licence thing, it's a privacy & security thing. Whos APIs are they using? What are their agreements with them? What leaks, what doesn't? Where is our code & context being sent to....etc
There is a lot more there that should be announced with it. Otherwise it's a hard no from security focused orgs unless they have this posted, in detail, somewhere, and it's favorable.
Edit: Looks like they just post who the providers are, and it's OpenAI. So that's gonna be a no unless we can bring our own APIs, since we have Azure GPT-3.5 & 4 access that meets opsec standards.