December 4, 2007
The OAuth protocol enables websites or applications (Consumers) to access Protected Resources from a web service (Service Provider) via an API, without requiring Users to disclose their Service Provider credentials to the Consumers. More generally, OAuth creates a freely-implementable and generic methodology for API authentication.
An example use case is allowing printing service printer.example.com (the Consumer), to access private photos stored on photos.example.net (the Service Provider) without requiring Users to provide their photos.example.net credentials to printer.example.com.
OAuth does not require a specific user interface or interaction pattern, nor does it specify how Service Providers authenticate Users, making the protocol ideally suited for cases where authentication credentials are unavailable to the Consumer, such as with OpenID.
OAuth aims to unify the experience and implementation of delegated web service authentication into a single, community-driven protocol. OAuth builds on existing protocols and best practices that have been independently implemented by various websites. An open standard, supported by large and small providers alike, promotes a consistent and trusted experience for both application developers and the users of those applications.
1.
Authors
2.
Notation and Conventions
3.
Definitions
4.
Documentation and Registration
4.1.
Request URLs
4.2.
Service Providers
4.3.
Consumers
5.
Parameters
5.1.
Parameter Encoding
5.2.
Consumer Request Parameters
5.3.
Service Provider Response Parameters
5.4.
OAuth HTTP Authorization Scheme
6.
Authenticating with OAuth
6.1.
Obtaining an Unauthorized Request Token
6.2.
Obtaining User Authorization
6.3.
Obtaining an Access Token
7.
Accessing Protected Resources
8.
Nonce and Timestamp
9.
Signing Requests
9.1.
Signature Base String
9.2.
HMAC-SHA1
9.3.
RSA-SHA1
9.4.
PLAINTEXT
10.
HTTP Response Codes
Appendix A.
Appendix A - Protocol Example
Appendix A.1.
Documentation and Registration
Appendix A.2.
Obtaining a Request Token
Appendix A.3.
Requesting User Authorization
Appendix A.4.
Obtaining an Access Token
Appendix A.5.
Accessing Protected Resources
Appendix B.
Security Considerations
Appendix B.1.
Credentials and Token Exchange
Appendix B.2.
PLAINTEXT Signature Method
Appendix B.3.
Confidentiality of Requests
Appendix B.4.
Spoofing by Counterfeit Servers
Appendix B.5.
Proxying and Caching of Authenticated Content
Appendix B.6.
Plaintext Storage of Credentials
Appendix B.7.
Secrecy of the Consumer Secret
Appendix B.8.
Phishing Attacks
Appendix B.9.
Scoping of Access Requests
Appendix B.10.
Entropy of Secrets
Appendix B.11.
Denial of Service / Resource Exhaustion Attacks
Appendix B.12.
Cryptographic Attacks
Appendix B.13.
Signature Base String Compatibility
11.
References
§
Author’s Address
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119] (Bradner, B., “Key words for use in RFCs to Indicate Requirement Levels,” .). Domain name examples use [RFC2606] (Eastlake, D. and A. Panitz, “Reserved Top Level DNS Names,” .).
- Service Provider:
- A web application that allows access via OAuth.
- User:
- An individual who has an account with the Service Provider.
- Consumer:
- A website or application that uses OAuth to access the Service Provider on behalf of the User.
- Protected Resource(s):
- Data controlled by the Service Provider, which the Consumer can access through authentication.
- Consumer Developer:
- An individual or organization that implements a Consumer.
- Consumer Key:
- A value used by the Consumer to identify itself to the Service Provider.
- Consumer Secret:
- A secret used by the Consumer to establish ownership of the Consumer Key.
- Request Token:
- A value used by the Consumer to obtain authorization from the User, and exchanged for an Access Token.
- Access Token:
- A value used by the Consumer to gain access to the Protected Resources on behalf of the User, instead of using the User’s Service Provider credentials.
- Token Secret:
- A secret used by the Consumer to establish ownership of a given Token.
- OAuth Protocol Parameters:
- Parameters with names beginning with oauth_.
OAuth includes a Consumer Key and matching Consumer Secret that together authenticate the Consumer (as opposed to the User) to the Service Provider. Consumer-specific identification allows the Service Provider to vary access levels to Consumers (such as un-throttled access to resources).
Service Providers SHOULD NOT rely on the Consumer Secret as a method to verify the Consumer identity, unless the Consumer Secret is known to be inaccessible to anyone other than the Consumer and the Service Provider. The Consumer Secret MAY be an empty string (for example when no Consumer verification is needed, or when verification is achieved through other means such as RSA).
OAuth defines three request URLs:
- Request Token URL:
- The URL used to obtain an unauthorized Request Token, described in Section 6.1 (Obtaining an Unauthorized Request Token).
- User Authorization URL:
- The URL used to obtain User authorization for Consumer access, described in Section 6.2 (Obtaining User Authorization).
- Access Token URL:
- The URL used to exchange the User-authorized Request Token for an Access Token, described in Section 6.3 (Obtaining an Access Token).
The three URLs MUST include scheme, authority, and path, and MAY include query and fragment as defined by [RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI): Generic Syntax,” .) section 3. The request URL query MUST NOT contain any OAuth Protocol Parameters. For example:
http://sp.example.com/authorize
The Service Provider’s responsibility is to enable Consumer Developers to establish a Consumer Key and Consumer Secret. The process and requirements for provisioning these are entirely up to the Service Providers.
The Service Provider’s documentation includes:
The Consumer Developer MUST establish a Consumer Key and a Consumer Secret with the Service Provider. The Consumer Developer MAY also be required to provide additional information to the Service Provider upon registration.
OAuth Protocol Parameter names and values are case sensitive. Each OAuth Protocol Parameters MUST NOT appear more than once per request, and are REQUIRED unless otherwise noted.
All parameter names and values are escaped using the [RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI): Generic Syntax,” .) percent-encoding (%xx) mechanism. Characters not in the unreserved character set ([RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI): Generic Syntax,” .) section 2.3) MUST be encoded. Characters in the unreserved character set MUST NOT be encoded. Hexadecimal characters in encodings MUST be upper case. Text names and values MUST be encoded as UTF-8 octets before percent-encoding them per [RFC3629] (Yergeau, F., “UTF-8, a transformation format of Unicode and ISO 10646,” .).
unreserved = ALPHA, DIGIT, '-', '.', '_', '~'
OAuth Protocol Parameters are sent from the Consumer to the Service Provider in one of three methods, in order of decreasing preference:
In addition to these defined methods, future extensions may describe alternate methods for sending the OAuth Protocol Parameters. The methods for sending other request parameters are left undefined, but SHOULD NOT use the OAuth HTTP Authorization Scheme (OAuth HTTP Authorization Scheme) header.
Response parameters are sent by the Service Provider to return Tokens and other information to the Consumer in the HTTP response body. The parameter names and values are first encoded as per Parameter Encoding (Parameter Encoding), and concatenated with the ‘&’ character (ASCII code 38) as defined in [RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI): Generic Syntax,” .) Section 2.1. For example:
oauth_token=ab3cd9j4ks73hf7g&oauth_token_secret=xyz4992k83j47x0b
This section defines an [RFC2617] (Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” .) extension to support OAuth. It uses the standard HTTP Authorization and WWW-Authenticate headers to pass OAuth Protocol Parameters.
It is RECOMMENDED that Service Providers accept the HTTP Authorization header. Consumers SHOULD be able to send OAuth Protocol Parameters in the OAuth Authorization header.
The extension auth-scheme (as defined by [RFC2617] (Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” .)) is OAuth and is case-insensitive.
The OAuth Protocol Parameters are sent in the Authorization header the following way:
For example:
Authorization: OAuth realm="http://sp.example.com/", oauth_consumer_key="0685bd9184jfhq22", oauth_token="ad180jjd733klru7", oauth_signature_method="HMAC-SHA1", oauth_signature="wOJIO9A2W5mFwDgiDvZbTSMK%2FPY%3D", oauth_timestamp="137131200", oauth_nonce="4572616e48616d6d65724c61686176", oauth_version="1.0"
Service Providers MAY indicate their support for the extension by returning the OAuth HTTP WWW-Authenticate header upon Consumer requests for Protected Resources. As per [RFC2617] (Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” .) such a response MAY include additional HTTP WWW-Authenticate headers:
For example:
WWW-Authenticate: OAuth realm="http://sp.example.com/"
The realm parameter defines a protection realm per [RFC2617] (Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” .), section 1.2.
OAuth authentication is the process in which Users grant access to their Protected Resources without sharing their credentials with the Consumer. OAuth uses Tokens generated by the Service Provider instead of the User’s credentials in Protected Resources requests. The process uses two Token types:
- Request Token:
- Used by the Consumer to ask the User to authorize access to the Protected Resources. The User-authorized Request Token is exchanged for an Access Token, MUST only be used once, and MUST NOT be used for any other purpose. It is RECOMMENDED that Request Tokens have a limited lifetime.
- Access Token:
- Used by the Consumer to access the Protected Resources on behalf of the User. Access Tokens MAY limit access to certain Protected Resources, and MAY have a limited lifetime. Service Providers SHOULD allow Users to revoke Access Tokens. Only the Access Token SHALL be used to access the Protect Resources.
OAuth Authentication is done in three steps:
The Consumer obtains an unauthorized Request Token by asking the Service Provider to issue a Token. The Request Token’s sole purpose is to receive User approval and can only be used to obtain an Access Token. The Request Token process goes as follows:
To obtain a Request Token, the Consumer sends an HTTP request to the Service Provider’s Request Token URL. The Service Provider documentation specifies the HTTP method for this request, and HTTP POST is RECOMMENDED. The request MUST be signed and contains the following parameters:
- oauth_consumer_key:
- The Consumer Key.
- oauth_signature_method:
- The signature method the Consumer used to sign the request.
- oauth_signature:
- The signature as defined in Signing Requests (Signing Requests).
- oauth_timestamp:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_nonce:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_version:
- OPTIONAL. If present, value MUST be 1.0 . Service Providers MUST assume the protocol version to be 1.0 if this parameter is not present. Service Providers’ response to non-1.0 value is left undefined.
- Additional parameters:
- Any additional parameters, as defined by the Service Provider.
The Service Provider verifies the signature and Consumer Key. If successful, it generates a Request Token and Token Secret and returns them to the Consumer in the HTTP response body as defined in Service Provider Response Parameters (Service Provider Response Parameters). The Service Provider MUST ensure the Request Token cannot be exchanged for an Access Token until the User successfully grants access in Obtaining User Authorization (Obtaining User Authorization).
The response contains the following parameters:
- oauth_token:
- The Request Token.
- oauth_token_secret:
- The Token Secret.
- Additional parameters:
- Any additional parameters, as defined by the Service Provider.
If the request fails verification or is rejected for other reasons, the Service Provider SHOULD respond with the appropriate response code as defined in HTTP Response Codes (HTTP Response Codes). The Service Provider MAY include some further details about why the request was rejected in the HTTP response body as defined in Service Provider Response Parameters (Service Provider Response Parameters).
The Consumer cannot use the Request Token until it has been authorized by the User. Obtaining User authorization includes the following steps:
In order for the Consumer to be able to exchange the Request Token for an Access Token, the Consumer MUST obtain approval from the User by directing the User to the Service Provider. The Consumer constructs an HTTP GET request to the Service Provider’s User Authorization URL with the following parameter:
- oauth_token:
- OPTIONAL. The Request Token obtained in the previous step. The Service Provider MAY declare this parameter as REQUIRED, or accept requests to the User Authorization URL without it, in which case it will prompt the User to enter it manually.
- oauth_callback:
- OPTIONAL. The Consumer MAY specify a URL the Service Provider will use to redirect the User back to the Consumer when Obtaining User Authorization (Obtaining User Authorization) is complete.
- Additional parameters:
- Any additional parameters, as defined by the Service Provider.
Once the request URL has been constructed the Consumer redirects the User to the URL via the User’s web browser. If the Consumer is incapable of automatic HTTP redirection, the Consumer SHALL notify the User how to manually go to the constructed request URL.
Note: If a Service Provider knows a Consumer to be running on a mobile device or set-top box, the Service Provider SHOULD ensure that the User Authorization URL and Request Token are suitable for manual entry.
The Service Provider verifies the User’s identity and asks for consent as detailed. OAuth does not specify how the Service Provider authenticates the User. However, it does define a set of REQUIRED steps:
When displaying any identifying information about the Consumer to the User based on the Consumer Key, the Service Provider MUST inform the User if it is unable to assure the Consumer’s true identity. The method in which the Service Provider informs the User and the quality of the identity assurance is beyond the scope of this specification.
After the User authenticates with the Service Provider and grants permission for Consumer access, the Consumer MUST be notified that the Request Token has been authorized and ready to be exchanged for an Access Token. If the User denies access, the Consumer MAY be notified that the Request Token has been revoked.
If the Consumer provided a callback URL in oauth_callback (as described in Consumer Directs the User to the Service Provider (Consumer Directs the User to the Service Provider)), the Service Provider constructs an HTTP GET request URL, and redirects the User’s web browser to that URL with the following parameters:
- oauth_token:
- The Request Token the User authorized or denied.
The callback URL MAY include Consumer provided query parameters. The Service Provider MUST retain them unmodified and append the oauth_token parameter to the existing query.
If no callback URL was provided, the Service Provider instructs the User to manually inform the Consumer that authorization has completed.
The Consumer exchanges the Request Token for an Access Token capable of accessing the Protected Resources. Obtaining an Access Token includes the following steps:
The Request Token and Token Secret MUST be exchanged for an Access Token and Token Secret.
To request an Access Token, the Consumer makes an HTTP request to the Service Provider’s Access Token URL. The Service Provider documentation specifies the HTTP method for this request, and HTTP POST is RECOMMENDED. The request MUST be signed per Signing Requests (Signing Requests), and contains the following parameters:
- oauth_consumer_key:
- The Consumer Key.
- oauth_token:
- The Request Token obtained previously.
- oauth_signature_method:
- The signature method the Consumer used to sign the request.
- oauth_signature:
- The signature as defined in Signing Requests (Signing Requests).
- oauth_timestamp:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_nonce:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_version:
- OPTIONAL. If present, value MUST be 1.0 . Service Providers MUST assume the protocol version to be 1.0 if this parameter is not present. Service Providers’ response to non-1.0 value is left undefined.
No additional Service Provider specific parameters are allowed when requesting an Access Token to ensure all Token related information is present prior to seeking User approval.
The Service Provider MUST ensure that:
If successful, the Service Provider generates an Access Token and Token Secret and returns them in the HTTP response body as defined in Service Provider Response Parameters (Service Provider Response Parameters). The Access Token and Token Secret are stored by the Consumer and used when signing Protected Resources requests. The response contains the following parameters:
- oauth_token:
- The Access Token.
- oauth_token_secret:
- The Token Secret.
- Additional parameters:
- Any additional parameters, as defined by the Service Provider.
If the request fails verification or is rejected for other reasons, the Service Provider SHOULD respond with the appropriate response code as defined in HTTP Response Codes (HTTP Response Codes). The Service Provider MAY include some further details about why the request was rejected in the HTTP response body as defined in Service Provider Response Parameters (Service Provider Response Parameters).
After successfully receiving the Access Token and Token Secret, the Consumer is able to access the Protected Resources on behalf of the User. The request MUST be signed per Signing Requests (Signing Requests), and contains the following parameters:
- oauth_consumer_key:
- The Consumer Key.
- oauth_token:
- The Access Token.
- oauth_signature_method:
- The signature method the Consumer used to sign the request.
- oauth_signature:
- The signature as defined in Signing Requests (Signing Requests).
- oauth_timestamp:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_nonce:
- As defined in Nonce and Timestamp (Nonce and Timestamp).
- oauth_version:
- OPTIONAL. If present, value MUST be 1.0. Service Providers MUST assume the protocol version to be 1.0 if this parameter is not present. Service Providers’ response to non-1.0 value is left undefined.
- Additional parameters:
- Any additional parameters, as defined by the Service Provider.
Unless otherwise specified by the Service Provider, the timestamp is expressed in the number of seconds since January 1, 1970 00:00:00 GMT. The timestamp value MUST be a positive integer and MUST be equal or greater than the timestamp used in previous requests.
The Consumer SHALL then generate a Nonce value that is unique for all requests with that timestamp. A nonce is a random string, uniquely generated for each request. The nonce allows the Service Provider to verify that a request has never been made before and helps prevent replay attacks when requests are made over a non-secure channel (such as HTTP).
All Token requests and Protected Resources requests MUST be signed by the Consumer and verified by the Service Provider. The purpose of signing requests is to prevent unauthorized parties from using the Consumer Key and Tokens when making Token requests or Protected Resources requests. The signature process encodes the Consumer Secret and Token Secret into a verifiable value which is included with the request.
OAuth does not mandate a particular signature method, as each implementation can have its own unique requirements. The protocol defines three signature methods: HMAC-SHA1, RSA-SHA1, and PLAINTEXT, but Service Providers are free to implement and document their own methods. Recommending any particular method is beyond the scope of this specification.
The Consumer declares a signature method in the oauth_signature_method parameter, generates a signature, and stores it in the oauth_signature parameter. The Service Provider verifies the signature as specified in each method. When verifying a Consumer signature, the Service Provider SHOULD check the request nonce to ensure it has not been used in a previous Consumer request.
The signature process MUST NOT change the request parameter names or values, with the exception of the oauth_signature parameter.
The Signature Base String is a consistent reproducible concatenation of the request elements into a single string. The string is used as an input in hashing or signing algorithms. The HMAC-SHA1 signature method provides both a standard and an example of using the Signature Base String with a signing algorithm to generate signatures. All the request parameters MUST be encoded as described in Parameter Encoding (Parameter Encoding) prior to constructing the Signature Base String.
The request parameters are collected, sorted and concatenated into a normalized string:
The oauth_signature parameter MUST be excluded.
The parameters are normalized into a single string as follows:
a=1, c=hi%20there, f=25, f=50, f=a, z=p, z=t
a=1&c=hi%20there&f=25&f=50&f=a&z=p&z=t
The Signature Base String includes the request absolute URL, tying the signature to a specific endpoint. The URL used in the Signature Base String MUST include the scheme, authority, and path, and MUST exclude the query and fragment as defined by [RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI): Generic Syntax,” .) section 3.
If the absolute request URL is not available to the Service Provider (it is always available to the Consumer), it can be constructed by combining the scheme being used, the HTTP Host header, and the relative HTTP request URL. If the Host header is not available, the Service Provider SHOULD use the host name communicated to the Consumer in the documentation or other means.
The Service Provider SHOULD document the form of URL used in the Signature Base String to avoid ambiguity due to URL normalization. Unless specified, URL scheme and authority MUST be lowercase and include the port number; http default port 80 and https default port 443 MUST be excluded.
For example, the request:
HTTP://Example.com:80/resource?id=123
Is included in the Signature Base String as:
http://example.com/resource
The following items MUST be concatenated in order into a single string. Each item is encoded (Parameter Encoding) and separated by an ‘&’ character (ASCII code 38), even if empty.
See Signature Base String example in Appendix A.5.1 (Generating Signature Base String).
The HMAC-SHA1 signature method uses the HMAC-SHA1 signature algorithm as defined in [RFC2104] (Krawczyk, H., Bellare, M., and R. Canetti, “HMAC: Keyed-Hashing for Message Authentication,” .) where the Signature Base String is the text and the key is the concatenated values (each first encoded per Parameter Encoding (Parameter Encoding)) of the Consumer Secret and Token Secret, separated by an ‘&’ character (ASCII code 38) even if empty.
oauth_signature is set to the calculated digest octet string, first base64-encoded per [RFC2045] (Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies,” .) section 6.8, then URL-encoded per Parameter Encoding (Parameter Encoding).
The Service Provider verifies the request by generating a new request signature octet string, and comparing it to the signature provided by the Consumer, first URL-decoded per Parameter Encoding (Parameter Encoding), then base64-decoded per [RFC2045] (Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies,” .) section 6.8. The signature is generated using the request parameters as provided by the Consumer, and the Consumer Secret and Token Secret as stored by the Service Provider.
The RSA-SHA1 signature method uses the RSASSA-PKCS1-v1_5 signature algorithm as defined in [RFC3447] (Jonsson, J. and B. Kaliski, “Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography; Specifications Version 2.1,” .) section 8.2 (more simply known as PKCS#1), using SHA-1 as the hash function for EMSA-PKCS1-v1_5. It is assumed that the Consumer has provided its RSA public key in a verified way to the Service Provider, in a manner which is beyond the scope of this specification.
The Signature Base String is signed using the Consumer’s RSA private key per [RFC3447] (Jonsson, J. and B. Kaliski, “Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography; Specifications Version 2.1,” .) section 8.2.1, where K is the Consumer’s RSA private key, M the Signature Base String, and S is the result signature octet string:
S = RSASSA-PKCS1-V1_5-SIGN (K, M)
oauth_signature is set to S, first base64-encoded per [RFC2045] (Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies,” .) section 6.8, then URL-encoded per Parameter Encoding (Parameter Encoding).
The Service Provider verifies the signature per [RFC3447] (Jonsson, J. and B. Kaliski, “Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography; Specifications Version 2.1,” .) section 8.2.2, where (n, e) is the Consumer’s RSA public key, M is the Signature Base String, and S is the octet string representation of the oauth_signature value:
RSASSA-PKCS1-V1_5-VERIFY ((n, e), M, S)
The PLAINTEXT method does not provide any security protection and SHOULD only be used over a secure channel such as HTTPS. It does not use the Signature Base String.
oauth_signature is set to the concatenated encoded values of the Consumer Secret and Token Secret, separated by a ‘&’ character (ASCII code 38), even if either secret is empty. The result MUST be encoded again.
These examples show the value of oauth_signature for Consumer Secret djr9rjt0jd78jf88 and 3 different Token Secrets:
- jjd999tj88uiths3:
- oauth_signature=djr9rjt0jd78jf88%26jjd999tj88uiths3
- jjd99$tj88uiths3:
- oauth_signature=djr9rjt0jd78jf88%26jjd99%2524tj88uiths3
- Empty:
- oauth_signature=djr9rjt0jd78jf88%26
The Service Provider verifies the request by breaking the signature value into the Consumer Secret and Token Secret, and ensures they match the secrets stored locally.
This section applies only to the Request Token and Access Token requests. In general, the Service Provider SHOULD use the response codes defined in [RFC2616] (Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol – HTTP/1.1,” .) Section 10. When the Service Provider rejects a Consumer request, it SHOULD respond with HTTP 400 Bad Request or HTTP 401 Unauthorized.
In this example, the Service Provider photos.example.net is a photo sharing website, and the Consumer printer.example.com is a photo printing website. Jane, the User, would like printer.example.com to print the private photo vacation.jpg stored at photos.example.net.
When Jane signs-into photos.example.net using her username and password, she can access the photo by going to the URL http://photos.example.net/photo?file=vacation.jpg. Other Users cannot access that photo, and Jane does not want to share her username and password with printer.example.com.
The requests in this example use the URL query method when sending parameters. This is done to simplify the example and should not be taken as an endorsement of one method over the others.
The Service Provider documentation explains how to register for a Consumer Key and Consumer Secret, and declares the following URLs:
- Request Token URL:
- https://photos.example.net/request_token, using HTTP POST
- User Authorization URL:
- http://photos.example.net/authorize, using HTTP GET
- Access Token URL:
- https://photos.example.net/access_token, using HTTP POST
- Photo (Protected Resource) URL:
- http://photos.example.net/photo with required parameter file and optional parameter size
The Service Provider declares support for the HMAC-SHA1 signature method for all requests, and PLAINTEXT only for secure (HTTPS) requests.
The Consumer printer.example.com already established a Consumer Key and Consumer Secret with photos.example.net and advertizes its printing services for photos stored on photos.example.net. The Consumer registration is:
- Consumer Key:
- dpf43f3p2l4k3l03
- Consumer Secret:
- kd94hf93k423kf44
After Jane informs printer.example.com that she would like to print her vacation photo stored at photos.example.net, the printer website tries to access the photo and receives HTTP 401 Unauthorized indicating it is private. The Service Provider includes the following header with the response:
WWW-Authenticate: OAuth realm="http://photos.example.net/"
The Consumer sends the following HTTP POST request to the Service Provider:
https://photos.example.net/request_token?oauth_consumer_key=dpf43f3p2l4k3l03&oauth_signature_method=PLAINTEXT&oauth_signature=kd94hf93k423kf44%26&oauth_timestamp=1191242090&oauth_nonce=hsu94j3884jdopsl&oauth_version=1.0
The Service Provider checks the signature and replies with an unauthorized Request Token in the body of the HTTP response:
oauth_token=hh5s93j4hdidpola&oauth_token_secret=hdhd0244k9j7ao03
The Consumer redirects Jane’s browser to the Service Provider User Authorization URL to obtain Jane’s approval for accessing her private photos.
http://photos.example.net/authorize?oauth_token=hh5s93j4hdidpola&oauth_callback=http%3A%2F%2Fprinter.example.com%2Frequest_token_ready
The Service Provider asks Jane to sign-in using her username and password and, if successful, asks her if she approves granting printer.example.com access to her private photos. If Jane approves the request, the Service Provider redirects her back to the Consumer’s callback URL:
http://printer.example.com/request_token_ready?oauth_token=hh5s93j4hdidpola
Now that the Consumer knows Jane approved the Request Token, it asks the Service Provider to exchange it for an Access Token:
https://photos.example.net/access_token?oauth_consumer_key=dpf43f3p2l4k3l03&oauth_token=hh5s93j4hdidpola&oauth_signature_method=PLAINTEXT&oauth_signature=kd94hf93k423kf44%26hdhd0244k9j7ao03&oauth_timestamp=1191242092&oauth_nonce=dji430splmx33448&oauth_version=1.0
The Service Provider checks the signature and replies with an Access Token in the body of the HTTP response:
oauth_token=nnch734d00sl2jdk&oauth_token_secret=pfkkdhi9sl3r4s00
The Consumer is now ready to request the private photo. Since the photo URL is not secure (HTTP), it must use HMAC-SHA1.
To generate the signature, it first needs to generate the Signature Base String. The request contains the following parameters (oauth_signature excluded) which are ordered and concatenated into a normalized string:
- oauth_consumer_key:
- dpf43f3p2l4k3l03
- oauth_token:
- nnch734d00sl2jdk
- oauth_signature_method:
- HMAC-SHA1
- oauth_timestamp:
-<PHONE_NUMBER>
- oauth_nonce:
- kllo9940pd9333jh
- oauth_version:
- 1.0
- file:
- vacation.jpg
- size:
- original
The following inputs are used to generate the Signature Base String:
The Signature Base String is:
GET&http%3A%2F%2Fphotos.example.net%2Fphotos&file%3Dvacation.jpg%26oauth_consumer_key%3Ddpf43f3p2l4k3l03%26oauth_nonce%3Dkllo9940pd9333jh%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1191242096%26oauth_token%3Dnnch734d00sl2jdk%26oauth_version%3D1.0%26size%3Doriginal
HMAC-SHA1 produces the following digest value as a base64-encoded string (using the Signature Base String as text and kd94hf93k423kf44&pfkkdhi9sl3r4s00 as key):
tR3+Ty81lMeYAr/Fid0kMTYa/WM=
All together, the Consumer request for the photo is:
http://photos.example.net/photos?file=vacation.jpg&size=original Authorization: OAuth realm="http://photos.example.net/", oauth_consumer_key="dpf43f3p2l4k3l03", oauth_token="nnch734d00sl2jdk", oauth_signature_method="HMAC-SHA1", oauth_signature="tR3%2BTy81lMeYAr%2FFid0kMTYa%2FWM%3D", oauth_timestamp="1191242096", oauth_nonce="kllo9940pd9333jh", oauth_version="1.0"
And if using query parameters:
http://photos.example.net/photos?file=vacation.jpg&size=original&oauth_consumer_key=dpf43f3p2l4k3l03&oauth_token=nnch734d00sl2jdk&oauth_signature_method=HMAC-SHA1&oauth_signature=tR3%2BTy81lMeYAr%2FFid0kMTYa%2FWM%3D&oauth_timestamp=1191242096&oauth_nonce=kllo9940pd9333jh&oauth_version=1.0
photos.example.net checks the signature and responds with the requested photo.
The OAuth specification does not describe any mechanism for protecting Tokens and secrets from eavesdroppers when they are transmitted from the Service Provider to the Consumer in Section 6.1.2 (Service Provider Issues an Unauthorized Request Token) and Section 6.3.2 (Service Provider Grants an Access Token). Service Providers should ensure that these transmissions are protected using transport-layer mechanisms such as TLS or SSL.
When used with PLAINTEXT signatures, the OAuth protocol makes no attempts to protect User credentials from eavesdroppers or man-in-the-middle attacks. The PLAINTEXT signature algorithm is only intended to be used in conjunction with a transport-layer security mechanism such as TLS or SSL which does provide such protection. If transport-layer protection is unavailable, the PLAINTEXT signature method should not be used.
While OAuth provides a mechanism for verifying the integrity of requests, it provides no guarantee of request confidentiality. Unless further precautions are taken, eavesdroppers will have full access to request content. Service Providers should carefully consider the kinds of data likely to be sent as part of such requests, and should employ transport-layer security mechanisms to protect sensitive resources.
OAuth makes no attempt to verify the authenticity of the Service Provider. A hostile party could take advantage of this by intercepting the Consumer’s requests and returning misleading or otherwise incorrect responses. Service providers should consider such attacks when developing services based on OAuth, and should require transport-layer security for any requests where the authenticity of the Service Provider or of request responses is an issue.
The HTTP Authorization scheme (OAuth HTTP Authorization Scheme) is optional. However, [RFC2616] (Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol – HTTP/1.1,” .) relies on the Authorization and WWW-Authenticate headers to distinguish authenticated content so that it can be protected. Proxies and caches, in particular, may fail to adequately protect requests not using these headers.
For example, private authenticated content may be stored in (and thus retrievable from) publicly-accessible caches. Service Providers not using the HTTP Authorization scheme (OAuth HTTP Authorization Scheme) should take care to use other mechanisms, such as the Cache-Control header, to ensure that authenticated content is protected.
The Consumer Secret and Token Secret function the same way passwords do in traditional authentication systems. In order to compute the signatures used in the non-PLAINTEXT methods, the Service Provider must have access to these secrets in plaintext form. This is in contrast, for example, to modern operating systems, which store only a one-way hash of user credentials.
If an attacker were to gain access to these secrets - or worse, to the Service Provider’s database of all such secrets - he or she would be able to perform any action on behalf of any User. Accordingly, it is critical that Service Providers protect these secrets from unauthorized access.
In many applications, the Consumer application will be under the control of potentially untrusted parties. For example, if the Consumer is a freely available desktop application, an attacker may be able to download a copy for analysis. In such cases, attackers will be able to recover the Consumer Secret used to authenticate the Consumer to the Service Provider.
Accordingly, Service Providers should not use the Consumer Secret alone to verify the identity of the Consumer. Where possible, other factors such as IP address should be used as well.
Wide deployment of OAuth and similar protocols may cause Users to become inured to the practice of being redirected to websites where they are asked to enter their passwords. If Users are not careful to verify the authenticity of these websites before entering their credentials, it will be possible for attackers to exploit this practice to steal Users’ passwords.
Service Providers should attempt to educate Users about the risks phishing attacks pose, and should provide mechanisms that make it easy for Users to confirm the authenticity of their sites.
By itself, OAuth does not provide any method for scoping the access rights granted to a Consumer. A Consumer either has access to Protected Resources or it doesn’t. Many applications will, however, require greater granularity of access rights. For example, Service Providers may wish to make it possible to grant access to some Protected Resources but not others, or to grant only limited access (such as read-only access) to those Protected Resources.
When implementing OAuth, Service Providers should consider the types of access Users may wish to grant Consumers, and should provide mechanisms to do so. Service Providers should also take care to ensure that Users understand the access they are granting, as well as any risks that may be involved.
Unless a transport-layer security protocol is used, eavesdroppers will have full access to OAuth requests and signatures, and will thus be able to mount offline brute-force attacks to recover the Consumer’s credentials used. Service Providers should be careful to assign Token Secrets and Consumer Secrets which are long enough - and random enough - to resist such attacks for at least the length of time that the secrets are valid.
For example, if Token Secrets are valid for two weeks, Service Providers should ensure that it is not possible to mount a brute force attack that recovers the Token Secret in less than two weeks. Of course, Service Providers are urged to err on the side of caution, and use the longest secrets reasonable.
It is equally important that the pseudo-random number generator (PRNG) used to generate these secrets be of sufficiently high quality. Many PRNG implementations generate number sequences that may appear to be random, but which nevertheless exhibit patterns or other weaknesses which make cryptanalysis or brute force attacks easier. Implementors should be careful to use cryptographically secure PRNGs to avoid these problems.
The OAuth protocol has a number of features which may make resource exhaustion attacks against Service Providers possible. For example, if a Service Provider includes a nontrivial amount of entropy in Token Secrets as recommended above, then an attacker may be able to exhaust the Service Provider’s entropy pool very quickly by repeatedly obtaining Request Tokens from the Service Provider.
Similarly, OAuth requires Service Providers to track used nonces. If an attacker is able to use many nonces quickly, the resources required to track them may exhaust available capacity. And again, OAuth can require Service Providers to perform potentially expensive computations in order to verify the signature on incoming requests. An attacker may exploit this to perform a denial of service attack by sending a large number of invalid requests to the Service Provider.
Resource Exhaustion attacks are by no means specific to OAuth. However, OAuth implementors should be careful to consider the additional avenues of attack that OAuth exposes, and design their implementations accordingly. For example, entropy starvation typically results in either a complete denial of service while the system waits for new entropy or else in weak (easily guessable) secrets. When implementing OAuth, Service Providers should consider which of these presents a more serious risk for their application and design accordingly.
SHA-1, the hash algorithm used in HMAC-SHA1 signatures, has been shown (De Canniere, C. and C. Rechberger, “Finding SHA-1 Characteristics: General Results and Applications,” .) [SHA1] to have a number of cryptographic weaknesses that significantly reduce its resistance to collision attacks. Practically speaking, these weaknesses are difficult to exploit, and by themselves do not pose a significant risk to users of OAuth. They may, however, make more efficient attacks possible, and NIST has announced (National Institute of Standards and Technolog, NIST., “NIST Brief Comments on Recent Cryptanalytic Attacks on Secure Hashing Functions and the Continued Security Provided by SHA-1,” .) [NIST] that it will phase out use of SHA-1 by 2010. Service Providers should take this into account when considering whether SHA-1 provides an adequate level of security for their applications.
The Signature Base String has been designed to support the signature methods defined in this specification. When designing additional signature methods, the Signature Base String should be evaluated to ensure compatibility with the algorithms used.
The Signature Base String cannot guarantee the order in which parameters are sent. If parameter ordering is important and affects the result of a request, the Signature Base String will not protect against request manipulation.
| OAuth Core Workgroup | |
| Email: |<EMAIL_ADDRESS>|


NEWS.md
rtablulate
family of functions do not support the row_*_data_args
arguments anymore. Instead, the col_wise_args
argument is introduced.order_rrows
, sort_rrows
, order_rtables
, and sort_rtables
are introduced.rtables
from being unlisted with unlist.rtables
Viewer
now also accepts objects of class shiny.tag
(defined in package htmltools
)as.html
accepts class.table
, class.tr
, class.th
, and class.td
as an argumentsprintf_format
for formatting rcells (thanks to Doug Kelkhoff for the suggestion)"(N=xx)"
and ">999.9"
format labelsrtabulate
has now an argument col_N
and the function col_N()
Version 0.1.0
is a major re-design with lots of internal refactoring and the following API changes:
Redesign: rtable
has now header
argument instead of col.names
. A header
can be created with rheader
and is a collection of rrow
s. If header
is set to c("A", "B")
then rtable
will create the rheader
with a single rrow
and by setting row.name
to NULL
.
header
and header<-
function added
renamed get_rcell_formats
to list_rcell_format_labels
If rcell
format is NULL
then the cell content will be converted to a string with paste(as.character(x), collapse = ', ')
accessor [i,]
works now to subset a table.
rbind
method for rtables
row.names<-.rtable
method
rtabulate
added for creating tables
indented_row.names
function added


Across: 1. Priest’s band (6) 4. Jug in front of singer may be mine (7) 9. Kitchen appliance reported in Northants (9) 10. In seconds write final dispatches (5) 11. Sloth is problematical for composer (5) 12. Boy’s cat observed one, we hear (3 6) 13. Restricted small child in cap (7) 15. Record places business in Norfolk town (6) 17. Removed seed out of it (6) 19. Room cleaner accepts honour (7) 22. Harry and I pop out and see The Madness Of King George (9) 24. In sex, celibates may not do very well! (5) 26. Succeed when surrounded by Eliot’s siblings (5) 27. Unpleasant to be at home with Freud? (9) 28. Flyer left Krays in disarray at weekend (7) 29. Looked intently at top journalist (6) Down: 1. Bag carried by girls at Chelsea parties (7) 2. Wore out left part of spur (5) 3. Pretty as North Wales town (9) 4. Almost built bonfire in the centre of structure (7) 5. Opera in Ascot? (5) 6. Darling, search the cells for bees! (9) 7. String of beads is in a sorry mess! (6) 8. Began right away, it is said (6) 14.  Account of condition of guys at Turks Head (9) 18. Make a mistake about Richard Crane (7) 19. Revolutionary freedom movement captured by luck (6) 20. Connected to Edward Lear in a strange way (7) 21. Floods pass round Lawrence (6) 23. Presenter is given a plant (5) 25. Free Charles King! (5)


28 February 1997
Disease Outbreak Reported
The weekly number of dengue fever cases has increased steadily on the island of Rarotonga since the beginning of January 1997. Up to 15 February 1997, 123 cases had been confirmed of which 39 had been hospitalized - none of them severely ill. Only dengue virus type 2 has been isolated in this outbreak. WHO has sent an expert to assess current control measures.


Dad, 36, killed himself after 'ex-wife stopped him from seeing their kids'
Jamie Bull's mental health issues had "spiralled" and he had an argument with his ex-wife on the day he hanged himself at his home near Barrow-in-Furness, Cumbria, an inquest heard
by Barnaby KellawayA dad killed himself after his ex-wife prevented him from seeing their two children leading to his mental health problems to "spiral", an inquest heard.
Tragic Jamie Bull, 36, hanged himself at his home near Barrow-in-Furness, Cumbria, on March 5 this year.
Just a few months earlier his ex-wife had stopped him from seeing their kids, the hearing was told.
His girlfriend, Stephanie Clayton, told the court "it was the number one reason he was feeling the way he was".
Mr Bull's brother, Chris, told Friday's hearing at Barrow Town Hall the ex-wife had "fought against him having access to his children".
Chris said his brother was "good at hiding" his mental health issues.
Miss Clayton claimed in the court that Mr Bull's ex used his mental health issues "against him" to prevent him seeing their kids.
She said: "Child access only became an issue once his ex-wife found out about our relationship.
"He only had very limited access. It hurt him a lot. He was devastated.
"He left her because he was unhappy. He stayed for the children but when he did leave it was used against him time and time again.
"His ex wasn't willing to communicate or reach any kind of compromise."
Miss Clayton said Mr Bull was meant to have his children on Christmas Day but that his ex prevented that from happening.
The inquest heard Mr Bull had an argument with his partner on the day of his death.
His family became concerned for his welfare and went to his flat in Walney to check on him.
Mr Bull's dad, Jim Bull, and stepmum, Nicola Bull, discovered his body.
Jim desperately tried to resuscitate his son, but he was pronounced dead by paramedics a short time later.
The grieving family were highly critical of an incident in October 2018 when Mr Bull was detained by police under the Mental Health Act.
His stepmum Nicola told the inquest said: "We sat with him in the A&E waiting area with two police officers, from 8am until 6pm."
The inquest heard there had been no mental health beds available and so Mr Bull had to wait in A&E until a doctor arrived.
North Cumbria Integrated Care NHS Foundation Trust, which was responsible for acute mental health services when Mr Bull was detained in October 2018, carried out an investigation after his death which highlighted a number of lessons to be learned.
A spokeswoman said: "We express our sincere condolences to the family and friends of Mr Bull at this difficult time.
"The Trust is not able to comment on this case at this time."
Samaritans (116 123) operates a 24-hour service available every day of the year. If you prefer to write down how you’re feeling, or if you’re worried about being overheard on the phone, you can email Samaritans at<EMAIL_ADDRESS>.


| Name | Specialty | City | Delete |
|---|---|---|---|
{{doctor["First Name"] | capitalcase}} {{doctor["Last Name/Organization Name"] | capitalcase }} |
{{doctor["Provider Type"]}} |
{{doctor["City"]}}, {{doctor["State Code"]}} |
Delete |


Repeats are pretty straight forward. They just repeat whatever code you have in them a certain amount of time. Available Variables within repeat 1. Repeat Index. ## Syntax
repeat(<#Integer#>) {
•Actions•
}
or
repeat(<#Variable#>) {
•Actions•
}
repeat(3) {
wait(Repeat index)
}
or
repeat(seconds) {
wait(Repeat index)
}


Home
About
Archive
About Me
My Linkedin
Linkedin
Yearly Goals
change a better job
buy house , car
get married
Help With Something Else:
google map
bing
help for coder
my music id@163


Movie Ticket Prices
What movie do you want to see?
NEW Release of A Horror Movie
Second-Run of Some Boring RomCom
When do you wanna watch?
Matinee
Evening Movies Are The Best!
Mind if we ask your age?
Show Me The Price
Ticket Prices:


--- layout: minimal title: "Hi there!" permalink: /about/index.html description: "About bazylSoft" ---
We are small startup company located in Wroclaw Poland.
Currently we are working on software which will make tournament management process as easy as it should be.


Traditional
Ming Mang is a two player game played on a 17x17 square board, with the following setup:
|
Ming Mang is played on Tibet. There is some questions about the term, Ming Mang can also means board games in general, or even another variant of Go, Tibet Go. If you have more info about this, please contact me.
| An example
If it's White's turn, he can capture two black stones by sliding to cell [1]. However, if it's Black's turn, he may safely slide to cell [1], avoiding the dangerous White move. |
Ming Mang is easily scaled to any square board. A faster game can be played with an Othello 8x8 board and material. Check a modern variant of this game, made by Schmittberger. He notices a flaw on this game rules, since it's easy to create impregnable little structures where a player cannot be stalemated, check the next example!
| Avoiding
stalemates, and avoiding it! The black structure is impregnable, the corner stone just slides along both cells [1] and White cannot do a thing about it! One way to solve this, is to include a push rule, like in Abalone. If so, White would move stone f4 to cell [2] and then push left to eliminate the structure. |


Hot body
jump start!
Flat
abs
lean
legs
firm
butt!
>HAPPY
>CONFIDENT
>ENERGIZED
Feel amazing
every day!
36 Smart
& speedy
ways to look
gorgeous
THE
WALKING
DEAD'S
LAUREN
COHAN
Steal her
killer
sculpting
secrets
3
BEST
MEALS
FOR
WEIGHT
LOSS
SEX, the
way you
want it
Jan | Feb 2016
shape.com


TERMS & CONDITIONS
www.wunderfit.com (the "Site") is owned and operated by Inner Treasures LLP. ("we" or "us" or Inner Treasures), a company incorporated under the laws of India and having its office at 519, I Floor, 4th Cross, 5th Main, 2nd Block, R.T. Nagar, Bangalore 560 032 India.
www.wunderfit.com is a business/commercial site and can be accessed only by a valid account holder. Your access and use of the site is subject to the following terms and conditions ("Website Terms and Conditions") and all applicable laws. By accessing and browsing this site, you accept, without limitation or qualification, the Website Terms and Conditions. If you do not agree with any of the below Terms and Conditions, please do not use this site.
We reserve the right, in our sole discretion, to modify, alter or otherwise update these Website Terms and Conditions at any time and you agree to be bound by such modifications, alterations or updates. Updated versions will be posted on the Inner Treasures Website and are effective immediately. When using the Inner Treasures Website, you should regularly verify whether the Website Terms of Use have been updated or amended. The Inner Treasures Website provides information on Inner Treasures, the Inner Treasures Business and Wunderfit products and services.
INTENDED AUDIENCE Unless otherwise specified, this site is intended for two categories of people i.e. Inner Treasures Consultants Preferred Customers
Each category in turn is bound by an additional agreement i.e. a Inner Treasure Consultant is bound by the "Consultant agreement"; and a Preferred Customer is bound by the " Preferred Customer agreement", for any purchases of goods or services, the Inner Treasures Refund Policy applies. These agreements find mention on the relevant portions of the website that relate to each of these categories. If you fall within any of these categories, it is your responsibility to familiarise yourself with the appropriate agreement and to comply with its terms.
This website (operated by us from our office located in Bangalore, India) is intended as a service to the above-mentioned categories of people located in India. Therefore, any person who accesses this website from outside India shall do so at his/her own risk and is responsible for compliance with the laws of his/her respective jurisdiction.
The products, information, services and other content provided on and through this site, including without limitation any products, information, services and other content provided on any Linked Site, are provided for informational purposes only to facilitate discussions regarding use options.
The information provided on this site and Linked Sites, including without limitation information relating to products and benefits is often provided in summary or aggregate form.
INTELLECTUAL PROPERTY RIGHTS
Copyrights:
All material on this Site ("Material"), including but not limited to text, images, illustrations, etc are protected by copyrights which are owned and controlled by us or by other parties that have licensed their material to us.
Material from the site may not be copied, reproduced, republished, uploaded, posted, transmitted, or distributed in any way.
We grant you a limited license to access and make personal use of this site and not to download (other than page caching) or modify it, or any portion of it, except with the written consent of Inner Treasures. This license does not include any resale or commercial use of this site or its contents; any collection and use of any product listings, descriptions, or prices; any derivative use of this site or its contents; any downloading or copying of account information for the benefit of another merchant; or any use of data mining, robots, or similar data gathering and extraction tools.
You may not frame or utilise framing techniques to enclose any trademark, logo, or other proprietary information (including images, text, page layout, or form) of Inner Treasures without express written consent. You may not use any meta tags or any other "hidden text" utilising Inner Treasures name or trademarks without the express written consent of Inner Treasures. Any unauthorised use terminates the permission or license granted by Inner Treasures.
You are grated a limited, revocable and nonexclusive right to create a hyperlink to the home page of Inner Treasures so long as the link does not portray Inner Treasures, its affiliates, or their products or services in a false, misleading, derogatory, or otherwise offensive matter. You may not use any Inner Treasures logo or other proprietary graphic or trademark as part of the link without express written permission.
Trademarks:
The trademarks, logos and service marks ("Marks") displayed on the Site are our property and the property of other parties. Users are prohibited from using any Marks without our written permission or third parties, which may own the Marks. We also own "trade-dress" rights to the look and feel of our website, which cannot be replicated, without our permission.
SUBMISSIONS OF INFORMATION/IDEAS Any information or material submitted by you to the Inner Treasures website (whether through e-mail or otherwise) will be deemed non-proprietary and non-confidential and may be used by Inner Treasures without restriction. Notwithstanding the foregoing, all personal data (e.g., name, address and telephone number) provided to Inner Treasures will be handled in accordance with Inner Treasures Privacy Policy.
Inner Treasures is always improving its products and services and developing new features. If you have ideas regarding improvements or additions to the Inner Treasures, we would like to hear them. However, please note that under no circumstances shall any disclosure of any idea, related materials to Inner Treasures be subject to any obligation of confidentiality or expectation of compensation.
By submitting the idea and/or any related material to Inner Treasures, you are waiving any/all rights that you may have in the idea or any related materials and are representing and warranting to Inner Treasures that the idea and/or related materials are wholly original with you and that no one else has any rights in the idea and/or materials and that Inner Treasures is free to implement that idea and to use the materials if it so desires as provided or as modified by Inner Treasures, without obtaining permission or license from any third party.
LINKED SITES We may provide links and pointers to Internet sites maintained by others ("Third Party Sites"). We are not responsible for the contents of or any products or services offered in such Third-Party Sites.
RESTRICTING OR BLOCKING ACCESS TO THE INNER TREASURES WEBSITE FOR VIOLATIONS OF THE WEBSITE TERMS OF USE. In case of a violation of these Website Terms of Use, particularly in case of use of the Inner Treasures Website or individual elements of the Inner Treasures Website for other than its intended use, access to the Inner Treasures Website may be restricted or blocked.
Inner Treasures generally reserves the right to partially or entirely alter, block, or discontinue the Inner Treasures Website or its content at any time and for any reason.
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY This site is provided by Inner Treasures on an "as is and "as available" basis. Inner Treasures makes no representations or warranties of any kind, express or implied, as to the operation of this site or the information, content, materials, or products included on this site.  To the full extent permissible by applicable law, Inner Treasures disclaims all warranties, express or implied, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Inner Treasures does not warrant that this site, its servers, or e-mail sent from Inner Treasures are free of viruses or other harmful components. Inner Treasures will not be liable for any damages of any kind arising from the use of this site, including, but not limited to direct, indirect, incidental, punitive, and consequential damages.
LIMITATION OF REMEDY If you are damaged or injured by any of the Material contained in the Site, or you are dissatisfied with the Site or Material for any reason, then your sole and exclusive remedy is to discontinue accessing and using the Site.
JURISDICTIONAL ISSUES This agreement shall be governed by, construed and enforced solely in accordance with the laws of the India and the courts at Bangalore shall have exclusive jurisdiction in this regard. This is the entire agreement between the parties relating to the matters contained herein.
TERMINATIONThis agreement will terminate immediately without notice from us if in our sole discretion you fail to comply with any term or provision of this Agreement. Upon termination, you must destroy all materials obtained from this Site and all copies thereof, whether made under the terms of this Agreement or otherwise. In the event of termination, the disclaimers of warranties and limitations of liabilities, damages and remedies set forth in this Agreement shall survive.
OTHER If any provision of this agreement shall be unlawful, void, or for any reason unenforceable then that provision shall be deemed severable from this agreement and shall not affect the validity and enforceability of any remaining provisions. We may at any time revise these Terms and Conditions by updating this posting. You are bound by any such revisions and should therefore periodically visit this page to review the then current Terms and Conditions to which you are bound.


About Home Workuts
Home Workouts provides daily workout routines for all your main muscle groups. In just a few minutes a day, you can build muscles and keep fitness at home without having to go to the gym. No equipment or coach needed, all exercises can be performed with just your body weight.
Sessions
Morning
6:00 AM - 11:00 PM
Evening
4:00 PM - 9:00 PM
Copyright © 2020 Your Company
| Design: Nihon Syed


Frequently asked questions
What should I be looking for or concerned about?
Check out the National Cancer Institute’s guide to moles.
Does this app tell me if I have melanoma?
This app is designed for self-tracking to help you monitor the size, shape, and color of your moles. This app does not make any claim to detect, diagnose, or treat any skin condition. Any data stored within the app is for personal use only. We encourage you to share your photos and measurements with a licensed professional and refer to their professional opinion.


public class PathAnimation extends ControlAnimation
| Modifier and Type | Class and Description |
|---|---|
static interface |
PathAnimation.SetPosition |
ControlAnimation.AnimationFinished
| Modifier and Type | Field and Description |
|---|---|
PathAnimation.SetPosition |
setpos |
c, delayAfterFinish, executedTime, releaseScreenShot, totalTime, useOffscreen
| Modifier and Type | Method and Description |
|---|---|
protected void |
animate() |
static PathAnimation |
create(Control c,
int direction,
ControlAnimation.AnimationFinished animFinish,
int totalTime)
Creates a path animation, moving the control in a direction.
|
static PathAnimation |
create(Control c,
int toX,
int toY,
ControlAnimation.AnimationFinished animFinish,
int totalTime)
Creates a path animation, moving the control to the given x and y positions.
|
static PathAnimation |
create(Control c,
int fromX,
int fromY,
int toX,
int toY,
ControlAnimation.AnimationFinished animFinish,
int totalTime)
Creates a path animation, moving the control from a position to another.
|
void |
stop(boolean abort) |
computeSpeed, setAnimationFinishedAction, start, then, updateListenerTriggered, with
public PathAnimation.SetPosition setpos
protected void animate()
animate
in class ControlAnimation
public void stop(boolean abort)
stop
in class ControlAnimation
public static PathAnimation create(Control c, int toX, int toY, ControlAnimation.AnimationFinished animFinish, int totalTime)
c
- The control to be movedtoX
- The destination X coordinatetoY
- The destination Y coordinateanimFinish
- An interface method to be called when the animation finished, or null if none.totalTime
- The total time in millis that the animation will take, or -1 to use the default value (800ms).public static PathAnimation create(Control c, int fromX, int fromY, int toX, int toY, ControlAnimation.AnimationFinished animFinish, int totalTime)
c
- The control to be movedfromX
- The origin X coordinatefromY
- The origin Y coordinatetoX
- The destination X coordinatetoY
- The destination Y coordinateanimFinish
- An interface method to be called when the animation finished, or null if none.totalTime
- The total time in millis that the animation will take, or -1 to use the default value (800ms).public static PathAnimation create(Control c, int direction, ControlAnimation.AnimationFinished animFinish, int totalTime)
c
- The control to be moveddirection
- One of BOTTOM, -BOTTOM, TOP, -TOP, LEFT, -LEFT, RIGHT, -RIGHT. Any other value will return null.animFinish
- An interface method to be called when the animation finished, or null if none.totalTime
- The total time in millis that the animation will take, or -1 to use the default value (800ms).


Enumerable is a powerful module that gives you ways of working with arrays and hashes.It lets you do something to each or all of the items in an object. A lot of times in programing, you would have an object with large amount of data, and you would need enumerable to deal with them in order to not waste time repeating the same process again and again.
As you may have known,
Does that remind you of the method #each? Yes, all enumerable methods including
Example:
Your health concious sibling left a list of grocery items on the desk for your mother to buy later:
fruits = ['apple', 'banana', 'blueberry', 'peach']
You dont want any of these items on the list but you are really craving for PIES!! So you make your version of her list and secretly swtiches the two:
fruitpies = fruits.map {|fruit| fruit + "pie"}
print fruitpies #=> ["applepie", "bananapie", "blueberrypie", "peachpie"]
Now that looks much better! You are welcome =)


WinForms.Net
Scrappy notes because I'm primarily a web developer
- Managed code access to later Windows apis (file dialogs etc):
- Krypton controls- free winforms controls
- Icons:
- FamFamFam icons - nice, free (used in the FF WebDeveloper toolbar, flags used in Wikipedia)
- PInvoke - free with attribution
- My SortableBindingList<T> (for Windows.Forms)
Events
Note the order: Enter - GotFocus - TextChanged - Leave - Validating - Validated - LostFocus
TextBox can be ReadOnly (gets focus), !Enabled (no focus).
Validation levels:
- TextBox properties- simple properties like MaxLength, CharacterCasing, AllowTabs
- Key Events- KeyPress (and for ctl/alt KeyDown/Up) in combo with KeyChar:
if (Char.IsDigit(e.KeyChar) == true) e.Handled=false
form1.KeyPreview= true for form-level keys - Validating Event- CausesValidation of next control must be true (false for help providers)
- Form level- on a button_Click
- MessageBox.Show or myErrorProvider.SetError(textBox1, "message") (use string.Empty to clear the errorProvider)
Exception Handling
You should at least log all unhandled exceptions, and preferably show a MessageBox saying sorry before Application.Exit().
In Asp.Net it's simple to trap unhandled exceptions in Application_Error in global.asax or in CustomErrors in web.config.
In Winforms and console apps, you can use the AppDomain.UnhandledException event:
AppDomain.CurrentDomain.UnhandledException +=
(o, eventArgs) =>
{
Console.WriteLine("Application errrored!");
Log.LogException(eventArgs.ExceptionObject as Exception);
Environment.Exit(0);
};
In Winforms you also have a Application.ThreadException (check the UnhandledExceptionMode as by default you'll swallow the exception and continue). It only traps exceptions on the main UI thread, so you probably need the AppDomain event too.
You can use Application.Exit() or Environment.Exit(0) to close (and stop the default .Net unhandled exception dialog).
GDI+
Is also used with the PrintPage event of the PrintDocument component
Graphics object is available from a form1.CreateGraphics factory method (anything Control-derived), from PaintEventArgs(or PrintPageEventArgs).Graphics, or the static Graphics.FromImage(img)
Draw* for lines (with a Pen), Fill* for filled shapes (with a Brush).
Pen myPen = new Pen(myBrush)
Coordinates: Point, Size, Rectangle (a Size with a Point as origin).
g.DrawString(str, new Font("Arial", 36, FontStyle.Regular), myPen, 0, 0);
Dispose all Pens/Brushes/Graphics objects (enclose them in using)
GraphicsPaths- is for complex shapes- use AddString etc, StartFigure/CloseFigure
- Resize- In form_Resize, call form1.Invalidate()
- Resize- form.ResizeRedraw= true
Making thumbnail (best quality)
private static void ResizeImage(string origPath, string smallPath)
{
using (var orig = Image.FromFile(origPath))
{
const int newWidth = 150;
const int newHeight = 200;
var small = new Bitmap(newWidth, newHeight);
using (var g = Graphics.FromImage(small))
{
g.InterpolationMode = InterpolationMode.HighQualityBicubic;
g.FillRectangle(Brushes.White, 0, 0, newWidth, newHeight);
g.DrawImage(orig, 0, 0, newWidth, newHeight);
}
small.Save(smallPath, ImageFormat.Jpeg);
}
}
Compress a jpeg
private static void CompressImage(string origPath, string compressedPath)
{
using (var orig = Image.FromFile(origPath))
{
//look up jpeg mime type
ImageCodecInfo codec = ImageCodecInfo.GetImageEncoders().First(
e => e.FormatID == ImageFormat.Jpeg.Guid);
var encoderPars = new EncoderParameters();
//quality must be a LONG from 1 to 100 - not an INT
encoderPars.Param[0] =
new EncoderParameter(System.Drawing.Imaging.Encoder.Quality, 60L);
orig.Save(compressedPath, codec, encoderPars);
}
}
Overlaying images
private static void OverlayImage(string origPath, string overlayPath, string newPath)
{
using (Image background = Image.FromFile(origPath))
{
using (var g = Graphics.FromImage(background))
{
using (var overlay = new Bitmap(overlayPath))
{
g.DrawImage(overlay, new Point(780, 0));
}
}
background.Save(newPath, ImageFormat.Jpeg);
}
}
DPI problems: if the image isn't default 96dpi, bitmap.SetResolution(overlay.HorizontalResolution, overlay.VerticalResolution);
Authoring Controls
- Inherit from existing control.
You can override OnPaint (not for TextBox)- assign Region for round buttons etc.
VS: add reference + Project-Add Inherited Control - Composite (user) controls inherit from UserControl. Use tb.Modifiers = public
VS: Project -Add User Control - Custom controls inherit from Control
Override OnPaint (PaintEventArgs.Graphics
In #ctor,SetStyle(ControlStyles.ResizeRedraw, true)
so resizing redraws (or manually Refresh())
or in _SizeChanged callInvalidate()
VS: New Project =Windows Control Library
Add toolbox icons- [ToolboxBitmap(typeof(Button))]. Or pass the path, or simply put add YourClassName.bmp as an embedded resource (bmp filename== classname) and it does it magically.
You can also use LicenseManager.Validate.
Help
- Form and controls have a HelpRequested event (when F1 pressed)
- You can show "?" button in the titlebar ("What's This"): form1.HelpButton= true AND false for Maximise/Minimise.
In 2.0, forms have a HelpButtonClicked event for this. - There's a static Help class (with ShowHelp(control, "file://c:\myhelp.chm") and ShowHelpIndex()) and a HelpProvider.
- A HelpProvider has a HelpNamespace (file or URL). You can just SetHelpString(ctl,str) for tooltip-like ("pop-up") help with no namespace (the What's This titlebar button calls this) or use SetHelpKeyword (ie "topic"= topic.htm).
- There's also an AccessibleName, for accessibility tools (and Tooltips!)
Settings
WinForms 2.0 designer - properties - Application Settings/ PropertyBindings creates the Settings class and binds for you. (msdn)
For C# (not VB) you need:
private void Form1_FormClosing(object sender, FormClosingEventArgs e)
{
Properties.Settings.Default.Save();
}
Tooltips on TreeView treenodes
Option 1: treeview1.ShowNodeToolTips = true and set the treeNode's ToolTipText
Option 2: Add a Windows.Forms.ToolTip, and handle the treeview's MouseMove event. You can use the treeNode's ToolTipText directly, or cast the Tag. You need to remember the last node or tooltip to avoid unpleasant repeat flashing as the cursor moves.
private string lastNode; //remember tooltips to avoid flashing
private void DatabaseScripterTreeView_MouseMove(object sender, MouseEventArgs e)
{
// Get the node at the current mouse pointer location.
TreeNode theNode = GetNodeAt(e.X, e.Y);
// if mouse not over a node, or it has no tag, no tooltip
if (theNode == null || string.IsNullOrEmpty(theNode.ToolTipText))
{
toolTip1.Active = false;
lastNode = null;
return;
}
//check still on same node - otherwise fires repeatedly
if (theNode.ToolTipText == lastNode) return;
lastNode = theNode.ToolTipText;
//show the tooltip
var tag = theNode.ToolTipText;
if (!toolTip1.Active) toolTip1.Active = true;
toolTip1.SetToolTip(this, tag);
}
CrossThread Pattern
For the dreaded cross-thread exception. You can either define a delegate or use an Action/ Func (or new MethodInvoker- anonymous delegates don't work).
void Model_Changed(object sender, EventArgs e)
{
//model changed by background worker or UI
UpdateUI();
}
/// <summary>
/// Updates the UI in a threadsafe way
/// </summary>
private void UpdateUI()
{
if (InvokeRequired)
{
//call myself on the windows thread
Invoke(new Action(UpdateUI));
}
else
{
txtName.Text = "Hello";
}
}


A channel to discuss trading. For useful links and more info click the pinned messages to the right.
100 messages
Before 05-Dec-19 12:00 AM
dukeleto04-Sep-19 12:58 PM
I hope an actually legit company comes along to actually use all our awesome tech
meatspoon04-Sep-19 12:59 PM
Another way of saying that is “no legit company is using our tech.” Ouch.
Markus04-Sep-19 01:03 PM
The part about NN mining big blocks well im not very surprised. If a system will allow u to do something like mining easier than others then obviously ppl will try to do their very best to exploit anything what would bring them more money
jl777c04-Sep-19 01:06 PM
if we didnt create a hunting pool, then i estimated 10+ NN would end up hunting instead of steady mining and that is not good
Alexfrog04-Sep-19 01:06 PM
yeah, the big block mining 'exploit' doesnt surprise me and i dont blame some people for using it, its good that it got changed
jl777c04-Sep-19 01:06 PM
with the hunting pool, it makes no sense for any NN to be a dedicated hunter as it is negative expected ROI
because the team donates 90% of hunted funds to the rest of the NN
grewalsatinder04-Sep-19 01:06 PM
>If a system will allow u to do something like mining easier than others
gigapool was not a notary node miner, who was getting all big blocks.
Alexfrog04-Sep-19 01:07 PM
im just sad that it caused enough drama to make dwy leave. hopefully people can start getting along and being productive again soon.
Markus04-Sep-19 01:07 PM
Would it not be possible to change it so if a NN mines a block with lets say larger than 500 kmd then it auto split reward to all NN
jl777c04-Sep-19 01:08 PM
its possible, but we just did a hardfork
grewalsatinder04-Sep-19 01:08 PM
productivity will be back as soon as this dead subject dead again.
1
Alexfrog04-Sep-19 01:09 PM
markus i think the solution already in place is bettr than that, it splits the rewards
jl777c04-Sep-19 01:09 PM
it takes literally a couple months to get all the nodes updated and doing annual hardfork seems the practical, unless it is some sort of horrible attack. which this isnt
also, the hunting pool is now setup to encourage teamwork. the better all the notaries do (best performing vs worst performing) the higher the payout
Markus04-Sep-19 01:10 PM
Alexfrog04-Sep-19 01:10 PM
sorry for brinigng up the issue grewal, NNs dealt with this already but us in the public just heard of it now lol
jl777c04-Sep-19 01:10 PM
so we turned an otherwise messy situation into the best outcome that we could come up with. now it rewards financially all the NN for helping each other do better
1
grewalsatinder04-Sep-19 01:10 PM
It was a headache catching up with that convo
Markus04-Sep-19 01:11 PM
Ye indeed, im sorry too for talking about this we dont need negativity
jl777c04-Sep-19 01:11 PM
we didnt make any public announcing of this as it is an internal NN matter and also it just got put in place in the last month
i never forbade people from talking about it
it is not my fault nobody mentioned it before today
some people feel that my decision that 75% of blocks should get 75% of revenues is very controversial, but i felt it wasnt really any big issue that i needed to immediately make some sort of public announcement about
all the data is being publicly displayed on the notary stats websites, for anybody who wanted to follow such matters
also, i found that nothing you can do will make some people stop posting, the best seems to just ignore it and this was a very stressful topic especially consiering the timing. i didnt really feel motivated to go out of my way to explain it all over again
Markus04-Sep-19 01:14 PM
How did u come up with 75%? Just trying to understand the thinking of the decision, was there any other options to consider?
jl777c04-Sep-19 01:14 PM
i prefered to come up with some new tech, like nspv
75% is what the NN are currently mining via the easy mining
it has been that way for over a year
Markus04-Sep-19 01:15 PM
Lets say KMD price goes to 100$ one day, will NN still mine 75% or will it get adjusted?
jl777c04-Sep-19 01:15 PM
based on the consensus code, the NN could actually be mining 95%, but we are intentionally mining less so the external miners could get 25%
but one of the external miners started sniping and NN ended up with significantly less than 75%
Alexfrog04-Sep-19 01:16 PM
lol, so THATS how it started, an external miner caught on
jl777c04-Sep-19 01:16 PM
at higher KMD prices, we can indeed change the 75% down but not less than 50%
Markus04-Sep-19 01:17 PM
Alright
jl777c04-Sep-19 01:17 PM
yes, until the external miner started sniping, there was peace in the land
once that happened, it destablised things, so we responded with the hunting pool
Alexfrog04-Sep-19 01:17 PM
NNs were just peacefully exploiting the loophope all to themselves, until one day...
jl777c04-Sep-19 01:17 PM
no
NN were intentionally mining only 75% instead of 95% that they could
Alexfrog04-Sep-19 01:18 PM
ah
jl777c04-Sep-19 01:18 PM
and randomly NN would get big blocks
and statisically if you get 75% of blocks, you expect 75% of total
starting end of last year, it stated being significantly less
we then identified a specific miner that was sniping the big blocks
once we found that out, we solved why 75% of blocks wasnt getting anywhere near the 75% of total
so we worked on a solution and now are able to get much close to 75%
THAT is the apparent controversy
Alexfrog04-Sep-19 01:23 PM
well, keep creating tech. maybe the market will eventually care, and not just dump everything for the original shitcoin that cant scale and has almost full blocks
Deleted User04-Sep-19 01:37 PM
the thing is yeah, people can say it s just anger. This is not just anger. A decentralized organisation can t keep doing centralised stuff. I m ok being seen as a bad person again. But the thing is that all of this should have been public far sooner. The point of that is that wether people admit or not, to be healthy and improve itself, an ecosystem need multiple type of people and minds. Revealing issues is key to improvement, but it s the ability to address them and fix before we come to a situation where after monthes nothing has been done.
yes it s pretty hard to admit things, but it s the path to reconsider own choices, and find ways to improve, neglecting it is neglecting the fact that it was done to improve the system. Agility is key, and being too slow is not good. This space goes very fast, so the ability to fix is also a key to success
When I told James I wanted to break pride and ivory tower, that meant being able to consider different opinions that may or may not help to move forward, and again, improve
Can t prove anything without some facts. Unfortunately after monthes of saying stuff people didn t understand, this was the only way to get credibility. This must just evolve
like KomodoWorld said, things must just change for the good of the ecosystem
Lumbi04-Sep-19 01:47 PM
Maybe a KNIP channel could be created to hash out proposals...? It seems this situation has been mostly defused except for some ruffled feathers and shattered nerves?
1
dukeleto04-Sep-19 01:48 PM
KIP
Komodo Improvement Proposals, they are called KIPs
we don't have any official ones yet, but they are coming
Lumbi04-Sep-19 01:49 PM
N is for Notary
dukeleto04-Sep-19 01:49 PM
BIPs, ZIPs, KIPs
Last message from Dwy was him saying he would sue me
do we have any big ZEC bag holders in here? What are y'all thinking?
Deleted User04-Sep-19 02:02 PM
@dukeleto you need to understand that disagreeing with you is possible, after last messages and tests I announced publicly, you jumped on conclusion about evilness, without taking the time to just try to understand
polycryptoblog04-Sep-19 02:03 PM
Not big, but zooko needs to get his head out of his butt
dukeleto04-Sep-19 02:05 PM
@polycryptoblog so many people hoping for a ZEC/BTC bounce, but man, there is a lot more room to go down
from what I hear, many A9++ owners have not gotten their machines, or are nowhere close to breaking even
That means massive sell pressure still exists
grewalsatinder04-Sep-19 02:06 PM
holding 0 ZEC soon after you last time raised their issues.
dukeleto04-Sep-19 02:07 PM
I believed in ZEC and held it a long time, but finally saw that my wishes and reality were not the same
polycryptoblog04-Sep-19 02:07 PM
That is correct machines still not here
dukeleto04-Sep-19 02:18 PM
@polycryptoblog really sorry to hear that. I see a lot of A9's for sale on the cheap, so some A9++'s must be getting delivered
polycryptoblog04-Sep-19 02:19 PM
I was in the first preorder so they have to be coming soon , probably just getting the big guys filled first
dukeleto04-Sep-19 02:22 PM
@polycryptoblog it should be interesting to see what ZEC/BTC price is once most A9++'s are delivered
Tek04-Sep-19 02:26 PM
zec has a high inflation what do you expect
polycryptoblog04-Sep-19 02:33 PM
I hope it falls the way of the X3 and A900/2000 Basically they stop producing them , so it is the best miner left standing
dukeleto04-Sep-19 02:41 PM
@Tek the inflation has been constant for almost 4 years, lol
we talking about other forces at play, mining forces
ASIC miners decide the price of ZEC and all equihash coins
Tek04-Sep-19 02:53 PM
@dukeleto yeah well, if thereis a coin with 30pct inflation no one is going to keep it considering there are coins with a lot less
dukeleto04-Sep-19 02:57 PM
@Tek hence why miners decide the price.
Tek04-Sep-19 04:31 PM
@tolken i don't know man I don't want to feel these kmd feels anymore
tolken04-Sep-19 04:36 PM
Hah.
tolken04-Sep-19 04:44 PM
Still waiting on that pre sept 5th Binance kmd dump.
I mean airdrop
Andersen04-Sep-19 04:50 PM
In line with general market flows, our OTC desk saw more altcoin sell flows compared to buy flows. Surprisingly, the buy/sell ratio was not as lopsided as one might expect with the current market conditions


Standards are the backbone of the Proximal Tool. We suggest using the Common Core Standards, but give people the ability to create any standard they would like too.
Resources are anything from Videos and books to questions. You can utilize resources by creating activities and linking them together. They are a way of illustrating your point or providing additional information.


HEAD
This Tag gives the browser all the control information of a Web Page.
All the
Global Settings are defined here.
The scripting functions are also defined here.
This is also a Container Tag and thus has to be closed. Text Written in the
HEAD Tag, except of what is written in the
TITLE Tag
is not displayed on the Browser Window.
Syntax
<HTML>
<HEAD>
...
...
...
</HEAD>
...
...
</HTML>
Home
About


1st Counter: {{ stCounter }}
2nd Counter: {{ ndCounter }}
1st Result Method: {{ resultMethod() }}
1st Result Computed: {{ resultComputed }}


CS 634 / Data Mining / Supervised Learning / Naive Bayes Classification
Bijaya Kumar Pradhan | Project Option 3 ( Amazon EC2 Cloud )
Census Income Data Set from UCI Machine Learning Library/ Weka Machine Learning Library
Testing dataset : Required. You can upload your testing data as a .csv ( with header row) or .arff ( as required by Weka) file
If you upload a .csv file, the file will be transformed to .arff format by the application to be used by the Prediction program. Please download sample test file below.
Training dataset : Optional because the application is already initialized with default Training dataset as available from UCI ML Library Census Income Data. You can upload your training data as a .csv or .arff ( as required by Weka) file. Requires Retraining and Evaluation if new training data is uploaded for prediction to be effective, and it will be applicable for all users.
If you upload a .csv file, the file will be transformed to .arff format by the application to be used by the Prediction program In either case, a .CSV file is preferred and easier.
Train / Evaluate:
This one will create in memory model from scratch from 'training data' set ( on default availabe "training data" set i.e it will be retrained or if you have uploaded a new "training dataset", it will use the uploaded one ) and evaluate the trained model
Analyze Your Test Data!:
When you click this one, your uploaded "test data" will be run against the existing trained model ( in memory, prepared during application initilization or recently retrained) of Census Income data.
| Item Id | Item Description | Predicted Class | Accurate Prediction? | Probability Distribution |
|---|
| Training Evaluation Summary |
|---|


Module : math
Module Overview
This module provides functions to perform fixed-precision integer arithmetic and fixed-precision decimal arithmetic. It includes functions to get the absolute, cosine, sine, root, tangent, and more for a given value.
For information on the operation, which you can perform with this module, see the below Function. For examples on the usage of the operation, see Math Api.
| Detail |
Record type to hold the details of an error. |
| absFloat |
Calculates the absolute value of a float value. |
| absInt |
Calculates the absolute value of an int value. |
| acos |
Calculates the arc cosine of a value; the returned angle is in the range 0. |
| asin |
Calculates the arc sine of a value. |
| atan |
Calculates the arc tangent of a value. |
| atan2 |
Calculates the angle theta from the conversion of rectangular coordinates (a, b) to polar coordinates (r, theta). |
| cbrt |
Calculates the cube root of a float value. |
| ceil |
Calculates the smallest (closest to negative infinity) double value that is greater than or equal to the argument and is equal to a mathematical integer. |
| copySign |
Calculates the first floating-point argument with the sign of the second floating-point argument. |
| cos |
Calculates the trigonometric cosine of an angle. |
| cosh |
Calculates the hyperbolic cosine of a float value. |
| exp |
Calculates Euler's number, that is 'e' raised to the power of exponent. |
| expm1 |
Calculates (e to the power of x) -1. |
| floor |
Calculates the largest (closest to positive infinity) float value that is less than or equal to the argument and is equal to a mathematical integer. |
| floorDiv |
Calculates the largest (closest to positive infinity) int value that is less than or equal to the algebraic quotient. |
| floorMod |
Calculates the floor modulus of the long arguments. |
| getExponent |
Calculates the unbiased exponent used in the representation of a float. |
| hypot |
Calculates sqrt(a squared +b squared) without intermediate overflow or underflow. |
| log |
Calculates the natural logarithm (base e) of a float value. |
| log10 |
Calculates the base 10 logarithm of a float value. |
| log1p |
Calculates the natural logarithm of the sum of the argument and 1. |
| negateExact |
Calculates the negation of the argument. |
| nextAfter |
Calculates the floating-point number adjacent to the first argument in the direction of the second argument. |
| nextDown |
Calculates the adjacent floating-point value closer to negative infinity. |
| nextUp |
Calculates the adjacent floating-point value closer to positive infinity. |
| pow |
Calculates the value of the 'a' raised to the power of 'b'. |
| random |
Selects a random number between 0. |
| randomInRange |
Selects a random number between the given start(inclusive) and end(exclusive) values. |
| remainder |
Computes the remainder operation on two arguments as prescribed by the IEEE 754 standard. |
| rint |
Calculates the double value that is closest in value to the argument and is equal to a mathematical integer. |
| round |
Calculates the closest int to the argument, with ties rounding to positive infinity. |
| scalb |
Calculates a × (2 to the power of b) rounded as if performed by a single correctly rounded floating-point multiply to a member of the float value set. |
| signum |
Calculates the signum function of the argument. |
| sin |
Calculates the trigonometric sine of an angle. |
| sinh |
Calculates the hyperbolic sine of a float value. |
| sqrt |
Calculates rounded positive square root of the given value. |
| tan |
Calculates the trigonometric tangent of an angle. |
| tanh |
Calculates the hyperbolic tangent of a double value. |
| toDegrees |
Converts an angle measured in radians to an approximately equivalent angle measured in degrees. |
| toRadians |
Converts an angle measured in degrees to an approximately equivalent angle measured in radians. |
| ulp |
Returns the size of an ulp of the argument. |
| ARITHMETIC_ERROR |
Represents the reason string for the |
| PI |
Ratio of the circumference of a circle to its diameter. |
| E |
Base of the natural logarithms. |
| Error |
Represents an error occurred in the |


{% extends "app/layout.html" %} {% block content %}
If there were words that felt honest I would use them. But sadly I have never been too creative nor honest to depict my minds world onto paper. So here I find myself struggling to explore what is on in my mind. What has been on for a while now. Jana has broken up with me two weeks ago, it really didn't come as a surprise but considering all the numbness I feel, I am devastated. Having been a hyperemotional wreckage for pretty much all my life, I am not yet sure about whether this apathy is indeed an achievement or another symbol of emotional decay. Ultimately it was another fight that ended it, one of those were I was not even sure who I was fighting with. She wouldn't budge, having set her character as static and unchangeable since her last breakup, making out even the slightest compromise as a major sacrifice on her side. That was her fault, that I know. But coming from that I thought I could accept it, I really hoped for a rational way to overcome this.  I wanted her because I wanted her to feel like compromising isn't something inherently bad. I loved her for trying to repair her 'something' that might not even constitute a flaw. I wanted her to be at ease with someone, to be at ease with herself, to live without comprise but to never forget who enables you to do that. I wanted her to be grateful for being with me, for the time I spend yearning for her approval and love, that I never got. Demands I uttered might have accelerated her distancing but we were inevitably doomed to fail. Accepting that she just didn't love me the way I wanted to be seen by her, not being understood or just in the end being okay with the fact that she indeed understood me, saw me for who I really am and didn't like it, will be so hard. I am afraid, to suffocate what I love, exploring every inch and flaw. Loving my self is hard enough, apparently I will not be able to love someone the way I want to.
{% endblock %}


NaN
(Not-a-Number) is the only value not equal to itself when comparing with any of the comparison operators. NaN
is often the result of meaningless math computations, so two NaN
values make no sense to be considered equal.
isNaN()
and Number.isNaN()
const isNaN = x => x !== x


Facebook Libra coin don't need KYC. They have so much more data on the 2 billion people. Not just name, id, address, phone number. They know your family, friends, real-time/historic location, what you like... They know you more than yourself. And now your wallet too. Best ...