it be better to fix it upstream after the fact, since its not available for all browsers.

Someone is probably working on the vscode store instead

Well yeah obviously it'd be better if they just fixed the issue at the source... the extension is very simple though and should be compatible with Firefox and other browsers that use similar web extensions APIs. Just haven't formally submitted it to Firefox's extension store.

I get it, but whats the point I ask, I'm interested as developer (because I have published atom packages) not as a user, and most users wont come here or look at your extension.

So I'de like my users to see what those images are.

Now extension is edge cases, I cant tell people who use our packages to go and download your extension, I rather just redirect them to the real readme.

Im sure their atom io site has a source code repo somewhere and its opensource, so a contrib is most likely to be the best way, i.e. fix it for all not just a hand full.

Sorry not for me. This should be a contribution to their source code as a fix.

I've looked and it doesn't seem like their site is open source 😕

@the-j0k3r @mauricioszabo we will take a look into the situation

any news in this? is riducolus you want that users switch to vscode?

People sure have bigger priorities, not only in real live but professionally, also likely someone with access to the relevant system is required.

In the grand scheme of things images on readme's aren't a crucial portions to the normal functioning of the system, which still works and people can always visit the projects repo.

Its annoying but not worth the bother.

@the-j0k3r The trouble is, someone already made the code for them. There's a Chrome extension that solves this issue. There are two issues to solve this: the one you opened, and the one that I opened here: #22929

I pointed on my issue how to solve the problem, down to the very JS that solves the issue - it's 9 JS lines of code, but on their repository could be even less, because the issue is just to swap the properties data-canonical-src to src. On September, @sadick254 commented that "it was on their radar, and it'll be solved as soon as they can" - it sure is a looong time to swap 2 attributes, right?

I can only see two options: one, they lost the source code or the deploy instructions for the atom.io/packages somehow, or they simply don't care and actually want to see Atom being discontinued. I honestly bet on the second choice

@mauricioszabo

None of the people you mention have access to the server side to change anything, none work for GitHub/Microsoft.

Its the same as asking you to go change the 2 lines yourself.

As for the extension, asking someone to install some extension, its the same as asking people to click on the repo link on the atom.io to go read the readme github repo page, the later its faster actually and no extensions necessary and works on all browsers, as not everyone uses Chrome. FYI I wouldn't install an extension that for the sake of what amounts to saving ppl one click to open a new tab and see pretty images.

Im not defending anyone mind, these are the facts.

Microsoft you know as well as I do, its wheels within wheels, too many Chiefs and not enough Indians.

Send them a letter snail mail type complain, Open a petition online and ask people to sign it (you need 100K signatures for it to be heard)

Now, Ill go back to my real life problems, I have much bigger problems that cant be solved by posting on GitHub.

@afmarchetti Do whatever you like, freedom is as one can do, I'll continue using Atom and then when it no longer works, I will use the community edition if it comes to be https://github.com/atom-community/atom

If it doesn't come to be, I will find another editor other than VScode (its closed source nonsense), which by then I wont even be running Windows at all and no more MS products for me. Plenty choices out there, even replacements for GitHub.

Good luck.