search

js-org / js.org

Dedicated to JavaScript and its awesome community since 2015
https://JS.ORG
5.25k stars 3.49k forks source link

JS.ORG CLEANUP #3554

Closed js-org-cleanup closed 4 years ago

js-org-cleanup commented 4 years ago

JS.ORG CLEANUP

The following js.org subdomains have been detected to no longer be working.

If you are the 'owner' of any of these subdomains and wish to still use them, please leave a comment below in the following format:

I am responsible for `xxx.js.org`.
It now has [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) and is now working.

Subdomains that aren't accounted for after a month and are still down will be removed.

Note to maintainers:

Domains with the checkbox ticked are now working and will not be removed at the end of the cleanup period.

Pending Contact

All domains in this list have not been contacted by the maintainers of js.org yet regarding the domain status.

Contact Made

All domains in this list have had contact made (issue raised on relevant repository etc.) by the js.org maintainers or the cleanup robot.

'Owners' of subdomains that are identifiable through the GitHub pages site that the subdomain points to will be contacted via their repository where possible (repository public & issues enabled) They will receive the following message asking them to reply to this issue to keep their domain:

# JS.ORG CLEANUP

Hello, it seems a `js.org` subdomain that was requested to target this repository no longer works.
The subdomain requested was `xxx.js.org` and had the target of `xxx`.
It produced the following failures when tested as part of the cleanup:
 - [HTTP](http://xxx.js.org): `xxx`
 - [HTTPS](https://xxx.js.org): `xxx`

To keep the `js.org` subdomain you should add a page with [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) within a month so the subdomain passes the validation.
Failure to rectify the issues will result in the requested subdomain being removed from JS.ORGs DNS and the list of active subdomains.

**If you are wanting to keep the `js.org` subdomain and have added [reasonable content](https://github.com/js-org/js.org/wiki/No-Content), YOU MUST reply to the [main cleanup issue](https://github.com/js-org/js.org/issues/3554) with the response format detailed at the top to keep the requested subdomain.**
MattIPv4 commented 4 years ago

webpack-config-plugins was an error with the cnames_active.js file, fixed in https://github.com/js-org/js.org/commit/6a2c84ab4eaea975a6fcd79dc9ee29593072877c

MattIPv4 commented 4 years ago

styled-icons has been updated in https://github.com/js-org/js.org/pull/3550

yuxizhe commented 4 years ago

I am responsible for yu.js.org. It now has reasonable content and is now working.

mirmousaviii commented 4 years ago

I am responsible for mo.js.org. It now has reasonable content and is now working.