database.json

{
  "db": {
    "dev-area": {
      "version": "v.2",
      "note": ""
    },
    "bot-config": {
      "prefix": "b!",
      "security-timeout": 0.3
    },
    "language": {
      "d_a1": "The bot is up and running!",
      "d_a2": "The bot is down but still running.",
      "d_a3": "requested this command.",
      "d_a4": "Blacklisted User Joined!"
    },
    "security": {
      "join-kick": {
        "id": {
          "name": "",
          "reason": ""
        }
      },
      "join-ban": {
        "id": {
          "name": "",
          "reason": ""
        }
      }
    },
    "dialogs": {
      "topics": [
        "What's everyone's favorite video game right now?",
        "Do any of you have any pets?",
        "Who's excited for the weekend?",
        "What's everyone's favorite movie?",
        "Do any of you have any hobbies?",
        "What's your favorite type of music?",
        "Do you have any favorite books or authors?",
        "What's everyone's favorite food?",
        "Do any of you have any cool travel stories?",
        "What's your favorite type of weather?",
        "Who's a fan of any sports teams?",
        "Do any of you have any cool DIY projects going on?",
        "What's your favorite type of cuisine?",
        "Do any of you have any favorite TV shows?",
        "What's everyone's favorite type of drink?",
        "Who's a fan of any podcasts or audiobooks?",
        "Do any of you have any upcoming events or plans?",
        "What's your favorite type of nature activity?",
        "Do any of you have any favorite online communities or forums?",
        "Who's a fan of any video game streamers or content creators?",
        "Do any of you have any favorite fashion styles or brands?",
        "What's your favorite type of exercise or physical activity?",
        "Do any of you have any favorite comedians or comedy shows?",
        "Who's a fan of any comic books or graphic novels?",
        "Do any of you have any favorite beauty or skincare products?",
        "What's your favorite type of art or artist?"
      ],
      "8-ball": [
        "Yes",
        "No",
        "Maybe?",
        "Maybe yes?",
        "Maybe no?",
        "Hell nawhh",
        "Hell yes!"
      ]
    },
    "status-code": {
      "100": "Response 100 - Continue [Information Response]\n - This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished.",
      "101": "Response 101 - Switching Protocol [Information Response]\n - This code is sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to.",
      "102": "Response 102 - Processing (WebDAV) [Information Response]\n - This code indicates that the server has received and is processing the request, but no response is available yet.",
      "103": "Response 103 - Early Hints [Information Response]\n - This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.",
      "200": "Response 200 - OK [Successful Response]\n - The request has succeeded. The meaning of the success depends on the HTTP method:\n\n > GET: The resource has been fetched and is transmitted in the message body.\n > HEAD: The representation headers are included in the response without any message body.\n > PUT or POST: The resource describing the result of the action is transmitted in the message body.\n > TRACE: The message body contains the request message as received by the server.",
      "201": "Response 201 - Created [Successful Response]\n - The request has succeeded and a new resource has been created as a result. This is typically the response sent after POST requests, or some PUT requests.",
      "202": "Response 202 - Accepted [Successful Response]\n - The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.",
      "203": "Response 203 - Non Authoritative Information [Successful Response]\n - This response code means the returned meta information is not exactly the same as is available from the origin server, but is collected from a local or a third party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the '200 OK' response is preferred to this status.",
      "204": "Response 204 - No Content [Successful Response]\n - There is no content to send for this request, but the headers may be useful. The useragent may update its cached headers for this resource with the new ones.",
      "205": "Response 205 - Reset Content [Successful Response]\n - Tells the useragent to reset the document which sent this request.",
      "206": "Response 206 - Partial Content [Successful Response]\n - This response code is used when the Range header is sent from the client to request only part of a resource.",
      "207": "Response 207 - Multi Status (WebDAV) [Successful Response]\n - Conveys information about multiple resources, for situations where multiple status codes might be appropriate.",
      "208": "Response 208 - Already Reported (WebDAV) [Successful Response]\n - Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.",
      "226": "Response 226 - IM Used (HTTP Delta encoding) [Successful Response]\n - The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance manipulations applied to the current instance.",
      "300": "Response 300 - Multiple Choice [Redirection Message]\n - The request has more than one possible response. The useragent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)",
      "301": "Response 301 - Moved Permanently [Redirection Message]\n - The URL of the requested resource has been changed permanently. The new URL is given in the response.",
      "302": "Response 302 - Found [Redirection Message]\n - This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.",
      "303": "Response 303 - See Other [Redirection Message]\n - The server sent this response to direct the client to get the requested resource at another URI with a GET request.",
      "304": "Response 304 - Not Modified [Redirection Message]\n - This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.",
      "305": "Response 305 - Use Proxy [Redirection Message]\n - Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding inband configuration of a proxy.",
      "306": "Response 306 - unused [Redirection Message]\n - This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.",
      "307": "Response 307 - Temporary Redirect [Redirection Message]\n - The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.",
      "308": "Response 308 - Permanent Redirect [Redirection Message]\n - This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.",
      "400": "Response 400 - Bad Request [Client Error Response]\n - The server could not understand the request due to invalid syntax.",
      "401": "Response 401 - Unauthorized [Client Error Response]\n - Although the HTTP standard specifies 'unauthorized', semantically this response means 'unauthenticated'. That is, the client must authenticate itself to get the requested response.",
      "402": "Response 402 - Payment Required [Client Error Response]\n - This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.",
      "403": "Response 403 - Forbidden [Client Error Response]\n - The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server.",
      "404": "Response 404 - Not Found [Client Error Response]\n - The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web.",
      "405": "Response 405 - Method Not Allowed [Client Error Response]\n - The request method is known by the server but is not supported by the target resource. For example, an API may forbid DELETE/ing a resource.",
      "406": "Response 406 - Not Acceptable [Client Error Response]\n - This response is sent when the web server, after performing server_driven content negotiation, doesn't find any content that conforms to the criteria given by the user agent.",
      "407": "Response 407 - Proxy Authentication Required [Client Error Response]\n - This is similar to 401 but authentication is needed to be done by a proxy.",
      "408": "Response 408 - Request Timeout [Client Error Response]\n - This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP preconnection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.",
      "409": "Response 409 - Conflict [Client Error Response]\n - This response is sent when a request conflicts with the current state of the server.",
      "410": "Response 410 - Gone [Client Error Response]\n - This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for 'limited time, promotional services'. APIs should not feel compelled to indicate resources that have been deleted with this status code.",
      "411": "Response 411 - Length Required [Client Error Response]\n - Server rejected the request because the Content Length header field is not defined and the server requires it.",
      "412": "Response 412 - Precondition Failed [Client Error Response]\n - The client has indicated preconditions in its headers which the server does not meet.",
      "413": "Response 413 - Payload Too Large [Client Response Error]\n - Request entity is larger than limits defined by server; the server might close the connection or return an Retry After header field.",
      "414": "Response 414 - URI Too Long [Client Response Error]\n - The URI requested by the client is longer than the server is willing to interpret.",
      "415": "Response 415 - Unsupported Media Type [Client Error Response]\n - The media format of the requested data is not supported by the server, so the server is rejecting the request.",
      "416": "Response 416 - Range Not Satisfiable [Client Error Response]\n - The range specified by the Range header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.",
      "417": "Response 417 - Expectation Failed [Client Response Error]\n - This response code means the expectation indicated by the Expect request header field can't be met by the server.",
      "418": "Response 418 - I'm a teapot [Client Error Response]\n - The server refuses the attempt to brew coffee with a teapot.",
      "421": "Response 421 - Misdirected Request [Client Error Response]\n - The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.",
      "422": "Response 422 - Unprocessable Entity (WebDAV) [Client Error Response]\n - The request was well formed but was unable to be followed due to semantic errors.",
      "423": "Response 423 - Locked (WebDAV) [Client Error Response]\n - The resource that is being accessed is locked.",
      "424": "Response 424 - Failed Dependency (WebDAV) [Client Error Response]\n - The request failed due to failure of a previous request.",
      "425": "Response 425 - Too Early [Client Error Response]\n - Indicates that the server is unwilling to risk processing a request that might be replayed.",
      "426": "Response 426 - Upgrade Required [Client Error Response]\n - The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).",
      "428": "Response 428 - Precondition Required [Client Error Response]\n - The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.",
      "429": "Response 429 - Too Many Requests [Client Error Response]\\n - The user has sent too many requests in a given amount of time ('rate limiting').",
      "431": "Response 431 - Request Header Fields Too Large [Client Error Response]\n - The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.",
      "451": "Response 451 - Unavailable For Legal Reasons [Client Response Error]\n - The useragent requested a resource that cannot legally be provided, such as a web page censored by a government.",
      "500": "Response 500 - Internal Server Error [Server Error Response]\n - The server has encountered a situation it doesn't know how to handle.",
      "501": "Response 501 - Not Implemented [Server Error Response]\n - The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.",
      "502": "Response 502 - Bad Gateway [Server Error Response]\n - This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.",
      "503": "Response 503 - Service Unavailable [Server Error Response]\n - The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching related headers that are sent along with this response, as these temporary condition responses should usually not be cached.",
      "504": "Response 504 - Gateway Timeout [Server Error Response]\n - This error response is given when the server is acting as a gateway and cannot get a response in time.",
      "505": "Response 505 - HTTP Version Not Supported [Server Error Response]\n - The HTTP version used in the request is not supported by the server.",
      "506": "Response 506 - Variant Also Negotiates [Server Error Response]\n - The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.",
      "507": "Response 507 - Insufficient Storage (WebDAV) [Server Error Response]\n - The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.",
      "508": "Response 508 - Loop Detected (WebDAV) [Server Error Response]\n - The server detected an infinite loop while processing the request.",
      "510": "Response 510 - Not Extended [Server Error Response]\n - Further extensions to the request are required for the server to fulfill it.",
      "511": "Response 511 - Network Authentication Required [Server Error Response]\n - The 511 status code indicates that the client needs to authenticate to gain network access.",
      "invalid-code": "Invalid Code - The code given is invalid. - In some cases, a response code may come from a server that is not on the list of response codes. This means that the response code is possibly custom to the server's software and is not included on the list of response codes because it is a nonstandard response code.",
      "attribution": "Original Source Website Code Author: Mozilla Foundation (https://foundation.mozilla.org/en/)\nOriginal Source Website Code Link: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#information_responses\nLicense: https://creativecommons.org/licenses/by-sa/4.0/legalcode.txt\n\nDisclaimer: This project is not in affiliation with the Mozilla Foundation."
    }
  }
}