search

js-org / js.org

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

JS.ORG CLEANUP #7929

Closed js-org-cleanup closed 1 year ago

js-org-cleanup commented 1 year 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/7929) with the response format detailed at the top to keep the requested subdomain.**
MattIPv4 commented 1 year ago

👀 Looking at why automatic contact failed...

indus commented 1 year ago

@MattIPv4 It looks also looks like there are some false positives like: https://imgops.js.org or https://angular2in1.js.org Should I check the ones with no 404 error manually or do you want to tweak the bot?

MattIPv4 commented 1 year ago

Both of those show an SSL warning for me, so it seems right that the bot has flagged them

indus commented 1 year ago

I think it is good to contact the requester about this. But would you remove them in case the there is no response from the requester? I mean no response is propably a bad signal... ;-)Am 14.01.2023 22:11 schrieb Matt Cowley @.***>: Both of those show an SSL warning for me, so it seems right that the bot has flagged them

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

MattIPv4 commented 1 year ago

Manually marking these as fixed:

MattIPv4 commented 1 year ago

Yah, the script will remove them if we don't mark them as working (we could do that even with the SSL errors, they'll just get flagged again at the next cleanup).

cloudtom commented 1 year ago

I am responsible for t.js.org. ->https://l-js.mydevapp.tfuture.eu.org/ It has reasonable content but not working.

Because the server has automatic redirection to https turned on and the //noCF tag I added didn't work, the Cloudflare is still working on this subdomain and crawling content via http, then maximum redirect reached errors happened.

Could you please help me check the reason why the //noCF tag is not working successfully? Or could you help me to manually turn off Cloudflare on this subdomain I think it will work as long as Cloudflare is turned off. Thank you!

indus commented 1 year ago

@cloudtom It looks like I made a mistake back then (#4705) and didn't disable the Cloudflare proxy. I just fixed this... I wonder why this hasn't failed in last years cleanup 🤔 Nevertheless you may want to make it work now from the server/host side?!

cloudtom commented 1 year ago

@cloudtom It looks like I made a mistake back then (#4705) and didn't disable the Cloudflare proxy. I just fixed this... I wonder why this hasn't failed in last years cleanup 🤔 Nevertheless you may want to make it work now from the server/host side?!

It dosen't work right now. I think there may have been other issues. Please give me some time to figure out.

cloudtom commented 1 year ago

https://l-js.mydevapp.tfuture.eu.org/

Is the Cloudflare proxy disabled successfully? On my side, it looks like that subdomain still points to Cloudflare's IP.

indus commented 1 year ago

@cloudtom https://geopeeker.com/fetch/?url=t.js.org (I haven't disabled it again - while affirming I would have - again - sorry).

cloudtom commented 1 year ago

@cloudtom https://geopeeker.com/fetch/?url=t.js.org (I haven't disabled it again - while affirming I would have - again - sorry).

It's working now. Thank you!

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

I noticed this sentence above, could you please tick the domain for me? Thanks.

dogancelik commented 1 year ago

I fixed the HTTPS issue for imgops.js.org. Can you check again please?

MattIPv4 commented 1 year ago

👍 LGTM for both t.js.org and imgops.js.org, ty y'all

pythoniaweb commented 1 year ago

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

indus commented 1 year ago

@pythoniaweb I think you subdomain was not in question?! Or I just can't find it in the list above 🤔

pythoniaweb commented 1 year ago

@indus sorry i think its global cleanup

indus commented 1 year ago

@MattIPv4 Thanks for managing the cleanup again.