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

Add additional information #2

Closed
wants to merge 3 commits into from

Conversation

@Andre601
Copy link
Contributor

commented Aug 10, 2019

Changes

+ Info about subdomain to non-botlist related sites (or free site plans)
+ Info about having good documentation of APIs if available.
+ Info about clones to not be allowed

~ General formatting, having "Your bot list..." at the start of the list instead of
  having it in each list-point.

Any additional changes are appreciated, but discuss it first please.

Andre601 added some commits Aug 10, 2019



Your bot list...
1. must have a respectable TLD.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

Could we just make this point that it must have its own custom domain with a respectable (paid) TLD?

That covers the glitch (etc) subdomain point and the tk point?

This comment has been minimized.

Copy link
@Andre601

Andre601 Aug 10, 2019

Author Contributor

Not everyone is aware that a .tk is not seen as a "respectable" domain.
That paid part could clear it up but I still think mentioning the .tk part should stay.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

There are many other free TLDs alike to tk. I don’t believe we should list tk as then users may cite that other free TLDs aren’t listed as a defence for using them.

1. must have a respectable TLD.
- .tk TLDs are not allowed.
- No subdomains used from non-botlists/free hosting (e.g. Glitch.me)
2. can **NOT** be hosted on glitch.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

See change to master.

This comment has been minimized.

Copy link
@Andre601

Andre601 Aug 10, 2019

Author Contributor

The PR was made right AFTER the master branch was updated...

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

Please rebase or merge master in to resolve the conflicts.

This comment has been minimized.

Copy link
@Andre601

Andre601 Aug 10, 2019

Author Contributor

I don't have experience with doing that through github and honestly won't load it on my PC (Desktop) to do this with git.

4. must be usable. No broken links/buttons.
- It should work on all commonly used browsers (Chrome, Opera and yes even Edge)
5. must have consistent uptime.
- Minor downtime due to fixes or maintenance are ok.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

I don’t think this is needed.

5. must have consistent uptime.
- Minor downtime due to fixes or maintenance are ok.
6. should have an easy to understand API-Documentation, if an API is available.
7. can **NOT** be a clone of an already existing (open source) bot list.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

Incorrect. Let’s start a new issue or PR to discuss this further. Remove from this one :)

This comment has been minimized.

Copy link
@Andre601

Andre601 Aug 10, 2019

Author Contributor

What is incorrect?
Having a (one on one) clone is imo not a good way to make a bot list since you basically only mirror the original.

This comment has been minimized.

Copy link
@MattIPv4

MattIPv4 Aug 10, 2019

Member

Create a separate issue or PR to discuss this further and remove it from here. We allow clones in some situations.

@Andre601

This comment has been minimized.

Copy link
Contributor Author

commented Aug 10, 2019

Complains were given and PR is no longer up to date with master branch.

@Andre601 Andre601 closed this Aug 10, 2019

@Andre601 Andre601 deleted the Andre601:patch-1 branch Aug 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.