Atom io packages/themes readme display no images

[the-j0k3r]

Description

Atom io packages/themes readme display no images

report going unnoticed by devs, and no community members can submit a fix since theres no source code;
See related atom/atom#22904

Steps to Reproduce

1. Navigate to any atom package page, e.g. https://atom.io/packages/terminus or https://atom.io/packages/x-terminal,
2. look at readme see no images
3. Open repo directly and see images.

Expected behavior:

That images are displayed on https://atom.io/packages/#package-name the same way they display on projects readmes.

Actual behavior:

No images display. of any extension, source e.g. cdn or raw or any other distributions methods.

Reproduces how often:

100%

Versions

Additional Information

Screenshot of https://atom.io/packages/terminus

Screenshot of readme in actual repo.

[IneptusMechanicus]

It appears that the image CDN/Service they've setup for atom.io which is i.github-camo.com does not work. Any attempts to access this domain returns a DNS error

[in-tension]

Why has this not been addressed? It comes up all the time (especially browsing themes because they are inherently visual in nature). Displaying an image is a pretty basic thing so it shouldn't be that hard to fix. It makes atom look pretty schlocky which in general isn't really true.

[IneptusMechanicus]

I feel like it's fair to say that brand-wise Atom has been abandoned for VS Code. The stupid thing is that alternate methods of embedding images other than following the markdown conventions also appears to be parsed by either apm or the site backend to be copied on to the CDN

[the-j0k3r]

@in-tension @IneptusMechanicus

First this isn't exactly a bug that affects functionality, its cosmetic and users can clik on the repo button to see the readme in the github repo with all images, so hardly a critical issue.

Plus there is only one person from GitHub doing merges for Atom, and afaik he does not have access to the private repo for the atom.io site only GitHub staff do, and since its not a critical issue I doubt it will be fixed soon or maybe ever.

On the minus side, Atom has now closed the discussions, Im now getting a 404 error on https://github.com/atom/atom/discussions

So whatever is happening seems bad news all around, not surprising, MS usual tactics of absorbing a company and smothering competing products is not new.

In any case, if it bothers you, complain to GitHub support, making noise in threads no one follows or maintains will get no attention.