VSCode Extension Identifier

[azu]

"Is this an official extension?" I heard a comment

• https://x.com/oukayuka/status/1908322402423259469

probably because that person, 3w36zj6.textlint, is not familiar with Identifier.

• https://marketplace.visualstudio.com/items?itemName=3w36zj6.textlint

prettier has a similar problem. However, it has been Publisher Verified( #2 ), so it seems to be converged now.

• https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode

However, Biome use machine account.

• https://marketplace.visualstudio.com/items?itemName=biomejs.biome

If there are no problems with the VSCode Extension conventions, vscode-textlint may also be worthwhile to publish using machine users.
(probably, we need to create GitHub Account for textlint. I will be managed in 1password.)

Perhaps, this may be the last chance as it is difficult to make changes after the blog is published,

@3w36zj6 Do you think about it?

There are several untested issues.

1. can we change the migration destination for VSCode extensions?

Current: taichi.vscode-textlint -> 3w36zj6.textlint
New: taichi.vscode-textlint {new-user}.textlint

2. I don't know the practice of creating a machine user for VSCode.

[azu]

If we do it, we need to do the following:

1. create a GitHub account
2. share the account with 1Password
3. create a VSCode Extension account (via GitHub login)
4. publish or migrate?
5. ask @taichi to change the migrate destination (need to ask if this can be done)

4 may be unnecessary if the Identifier can change the Identifier of 3w36zj6.textlint (a mechanism like Transfer).

[3w36zj6]

I understood the situation at hand.

After conducting some research, I've found precedents for transitioning publishers to organizations, such as the migration from PeterJausovec.vscode-docker to ms-azuretools.vscode-docker. This might be possible by contacting the Visual Studio Code Marketplace support team.

If transfers between different marketplace publishers are indeed possible, azu could create a textlint publisher at https://marketplace.visualstudio.com/manage/createpublisher and then transfer the extension to this new publisher.

Another option would be to publish a new extension (e.g., textlint.textlint-vscode) and request deprecation of the original extension. Although this approach might cause temporary confusion, it could be better in the long term. Just keep in mind that the Marketplace requires globally unique identifiers, so you would need to consider names other than vscode-textlint or textlint. (I'm uncertain what happens if you completely remove an extension rather than deprecating it.)

A quick and straightforward solution would be to prominently display a notice in the extension's README with links to trusted resources (e.g., textlint.github.io, github.com/textlint, x.com/azu_re). This is something that can be implemented immediately while you consider the longer-term options.

[azu]

Thanks for the research 👍

If transfers between different marketplace publishers are indeed possible, azu could create a textlint publisher at https://marketplace.visualstudio.com/manage/createpublisher and then transfer the extension to this new publisher.

It seems like this would be a good thing to do.
I will see if I can create a textlint publisher.
(I hope it doesn't have the same 6 month limit as "Publisher Verified"...)

[azu]

FYI: website is moving to textlint.org

• Move to textlint.org textlint#1482

[azu]

I've created textlint publisher
https://marketplace.visualstudio.com/manage/publishers/textlint

@3w36zj6 Can you tell me your "User Id"?
If this value is secret, send it to 📧 azuciao@gmail.com

[azu]

OK. I've invited.

[azu]

After that, We need to contact microsoft support.

I feel there are several points.

1. in the first place, can we transfer 3w36zj6.textlint to textlint publisher?
2. if 1. what will happen to taichi.vscode-textlint which has 3w36zj6.textlint as a migration target?

Alternatively, taichi.vscode-textlint itself could be transferred to the textlint publisher.

[3w36zj6]

It appears that transferring extension ownership is technically possible¹.

I believe we need to request this through vsmarketplace@microsoft.com. When making the request, we should also ask them to change the migration target settings for taichi.vscode-textlint at the same time.

Similarly, it seems possible to remove the deprecation from taichi.vscode-textlint and change its publisher as well.

Footnotes

1. https://github.com/microsoft/vscode/issues/3670#issuecomment-191767639 ↩

[azu]

1. Publish new textlint extension(textlint.vscode-textlint?) under textlint organization.
2. Deprecate 3w36zj6.textlint and migrate to textlint.textlint-vscode
3. Change taichi.vscode-textlint's migration to textlint.textlint-vscode

I feel this is the softest way to land the case.
In this case, perhaps no contact with support is necessary.
It is possible with the cooperation of @3w36zj6 (3w36zj6.textlint) and @taichi (taichi.vscode-textlint).

[3w36zj6]

I think it's fine.

[3w36zj6]

I received a response to our email: #17 (comment)

My message:

Hi, VS Marketplace Support Team,

Thank you for your message.

The taichi.vscode-textlint was originally a personal project, but due to maintenance and development continuity issues, it was transferred to community maintenance under the textlint organization. Here is the discussion about this transfer: https://github.com/orgs/textlint/discussions/2

Additionally, the deprecated extension request was made with the original author's permission as documented here: microsoft/vscode-discussions#1 (comment)

We are also in the process of preparing for verified publisher status: #2

Based on your guidance, we plan to immediately add a notice in a prominent location in the extension's README indicating that the extension has been transferred to community maintenance.

Regarding the similarities in icon and description, these might be difficult to change since the purpose of the extension (integrating textlint with VSCode) remains the same.

Thank you for your consideration.

Best regards,

Their response:

Thank you for your response and sharing details. We understand your concern; however, this issue arises due to impersonation. Kindly ensure that any exact matches are replaced with the original.

Regards,
VS Marketplace Support Team

It appears that VS Marketplace only allows one extension with similar icons, names, and descriptions to exist in the marketplace.

To prevent receiving similar warnings from the VS Marketplace team, we may need to remove both taichi.vscode-textlint and 3w36zj6.textlint extensions when publishing under the textlint publisher.

cc: @azu @taichi

[azu]

I would like to avoid deletion as much as possible. (as this would be a breaking change).
If we can get away with deprecated markings, I think that would be best.

VSCode Team are accepting feedback on deprecation and migration on the next page.
This place may have a better understanding of open source.

• Deprecated extensions microsoft/vscode-discussions#1

[3w36zj6]

When applying for migration from taichi.vscode-textlint to 3w36zj6.textlint, it feels strange to receive warnings about similarity to an extension that is already marked as deprecated, given that this is being done with permission from both a member of the VS Marketplace support team and the original author.

Since they have stated that they may make the extension private if we don't respond by the deadline, I will check with the VS Marketplace support team about what options are available to us going forward.