Attack on Life ⚔️

Today, ChatGPT’s advanced voice mode started its gradual rollout. After using it, I found it quite good, so I’m documenting the usage situation in this article.

Limit

• It is currently only open to Plus and Team members and is still being gradually rolled out. It is expected to be fully available this week.

  Advanced Voice is rolling out to all Plus and Team users in the ChatGPT app over the course of the week. While you’ve been patiently waiting, we’ve added Custom Instructions, Memory, five new voices, and improved accents.

  Advanced Voice is not yet available in the EU, the UK, Switzerland, Iceland, Norway, and Liechtenstein.

• If you are a member but are still prompted “currently unavailable,” you can try upgrading the app to the latest version and re-logging in to try to get access. The community has mentioned uninstalling and reinstalling to gain access, so try various strategies. If none work, wait patiently for the gradual rollout to reach you.

Supported Platforms

1. ChatGPT Mac App
2. ChatGPT iOS App
3. ChatGPT Android App

For security reasons, passwordless login is generally implemented using public-private key pairs. Here, I’ll mark down the configuration method.

1. Log into the client machine and create a public-private key pair if you don’t already have one.

   The public and private keys are stored in the ~/.ssh directory.

2. Log into the target server and open the ~/.ssh/authorized_keys file.

   The authorized_keys file records the list of public keys authorized for login.

3. Copy the public key from the client machine into this file and save it.

4. Try SSH login to the target machine again, and you’ll find no password is required.

Sometimes, switching the source of npm packages in a project is necessary due to network or security issues. The general practice is to switch the source in npmrc, but after switching and installing packages, you will find that the install still goes through the old source, primarily when a lock file has already been generated.

Here, we analyze the issue of the registry not working.

Version Information

For verification, I am using the following versions:

• npm v9.5.1

• node v18.16.1

Issue

In projects using redux-logger, redux-logger still exists after packaging in Webpack production mode.

Theoretically, the logger should only be used in the development environment, so it should be removed after packaging. Therefore, with this question in mind, let’s analyze the problem.

Code Details

Recently, I used Monaco editor to implement an SQL editor. To improve the user experience, code auto-completion was necessary. After some research, I found a solution, so I’m marking it down here.

Built-in Autocompletion?

YES, Monaco supports some built-in languages by default, such as JavaScript, TypeScript, CSS, JSON, and HTML. You can achieve code autocompletion for languages with built-in support simply by setting the editor language to JavaScript`.

However, for languages like SQL that do not have built-in support, setting the editor language to SQL only enables syntax highlighting.