Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 on https://nodejs.org/static/images/logos/nodejs-new-pantone-black.svg #7382

Closed
legendecas opened this issue Jan 1, 2025 · 6 comments
Closed
Labels

Comments

@legendecas
Copy link
Member

URL:

https://nodejs.org/static/images/logos/nodejs-new-pantone-black.svg

Browser Name:

Chrome

Browser Version:

131.0.6778.205

Operating System:

macOS

How to reproduce the issue:

Chrome Node.js dedicated DevTools display a Node.js icon on the main page. This icon links to https://nodejs.org/static/images/logos/nodejs-new-pantone-black.svg and it is now 404.

Refs: https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/entrypoints/node_app/NodeConnectionsPanel.ts;l=51;drc=c17be942eda920858d6f98c2a4ff36483cde1782

@legendecas legendecas added the bug label Jan 1, 2025
@AugustinMauroy
Copy link
Member

AugustinMauroy commented Jan 1, 2025

What does this icon look like, as it must have changed its name over time?
https://nodejs.org/en/about/branding

@legendecas
Copy link
Member Author

legendecas commented Jan 1, 2025

Tracing back the change history, it is now https://nodejs.org/static/logos/nodejsStackedDark.svg.

Is there any guarantee that the new icon link will be "permanent"?

@AugustinMauroy
Copy link
Member

Is there any guarantee that the new icon link will be "permanent"?

IDK, we should try. Maybe sync with the foundation

@bmuenzenmeyer
Copy link
Collaborator

no - people should not be hot-linking to our hosted images, IMO

@ovflowd
Copy link
Member

ovflowd commented Jan 3, 2025

no - people should not be hot-linking to our hosted images, IMO

+1, please do not hot link images from the website. We ain't a CDN provider.

@bmuenzenmeyer
Copy link
Collaborator

we had problems with people doing this even within the project, with plenty of examples of READMEs breaking.
The only way to "guarantee" a file will be available "permanently" is to host it yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants