It is opt-in by default for non-commercial licenses:
> For companies: Admins can enable data sharing at a company-wide level. To support early adopters, we’re offering a limited number of free All Products Pack subscriptions to organizations willing to participate while we explore this program. For companies that are not willing to opt in to the program, nothing changes, and as always, admins are in control.
> For individuals on non-commercial licenses: Data sharing is enabled by default, but you can turn it off anytime in the settings.
> For individuals using commercial licenses, free trials, free community licenses, or EAP builds: Nothing changes. You can still opt in via the settings if you are willing to share data with JetBrains (and your admins, if any, allow it).
And the detail of what is collected:
> We’re now adding the option to allow the collection of detailed code‑related data pertaining to IDE activity, such as edit history, terminal usage, and your interactions with AI features. This may include code snippets, prompt text, and AI responses.
I thought I'd share with the HN crowd. I generally keep up with this kind of thing, but I hadn't seen anyone else mention that you can enable it on the stable channel.
Thanks! I'll compare with Route53 mentioned above and decide the way forward. I was quite happy with Gandi's similar no bullshit approach for the past few years until the abrupt mailbox change last year.
I'm the author of this post. If perhaps you're wondering why I didn't just transfer the domain to Cloudflare, it's because they do not support the South African TLD, unfortunately.
Thanks for the detailed response. It looks like I've still got a lot to learn - I've just lately been playing with LXC to get more familiarised with containers. I've previously looked at Helm apps and they seemed to be very similar to Puppet manifests.
From what you said it seems like the approach is to have immutable containers for each application, set up via Dockerfiles, which somehow also simplifies the upgrade process? Does that mean you just deploy a new version/container of an application linked to the same underlying database (for example) when you need to run an upgrade?
So if you had a fleet of ten containers running the same application in a load balanced config, I'm guessing you'd need to upgrade all of them at once (with downtime) rather than upgrading them one by one (because then the database would be inconsistent)? I'm assuming that since the containers are immutable the data is stored elsewhere.
As someone with limited experience with containers, how does K8s allow you to move away from things like Puppet for configuration management? Does it offer some substitute that alleviates the need for something like Puppet or Ansible?
Thank you for posting. I see it briefly mentions the practice for the remembrance (although I don't know if it's specific to this initiative or whether it is more widespread):
> On November 28, 2020, light a candle in your window, as a memory of every bright soul tortured during the Holodomor of 1932-1933 – the genocide of the Ukrainian nation.
> We want everyone to be remembered – starved, unborn, numbered, and UNCOUNTED
Thanks for mentioning QMK [0], it's not something I've heard of before, and it seems like a huge step up from standard keyboard firmware. As far as I can tell only a small number of manufacturers officially support it, but at least one person seems to have made some progress getting a standard cooler master keyboard to run it [1].
As someone who uses Vim daily, I quite like this idea. I would customise it to mimic the original Vim bindings a bit more closely where possible though, to e.g. keep Ctrl-D as page down.
I'm not sure if this would be possible, but it would be fun to have customisable per-application bindings (based on the active window, probably) in addition to the set of global bindings. I can also think of minor cases where motions would be useful, like 3x alt-tab (i.e. 3gt) to switch to a specific application.
I wonder at what point the depth of the mode-ness will become too much, if you were running this, for example, with a vi-mode bash readline.
> For companies: Admins can enable data sharing at a company-wide level. To support early adopters, we’re offering a limited number of free All Products Pack subscriptions to organizations willing to participate while we explore this program. For companies that are not willing to opt in to the program, nothing changes, and as always, admins are in control. > For individuals on non-commercial licenses: Data sharing is enabled by default, but you can turn it off anytime in the settings. > For individuals using commercial licenses, free trials, free community licenses, or EAP builds: Nothing changes. You can still opt in via the settings if you are willing to share data with JetBrains (and your admins, if any, allow it).
And the detail of what is collected:
> We’re now adding the option to allow the collection of detailed code‑related data pertaining to IDE activity, such as edit history, terminal usage, and your interactions with AI features. This may include code snippets, prompt text, and AI responses.