Akismet has a test mode; we should be able to use it.

The reason for this is mentioned on https://github.com/joshfrench/rakismet:

Rakismet can be configued to tell Akismet that it should operate in test mode - so Akismet will not change its behavior based on any test API calls, meaning they will have no training effect. That means your tests can be somewhat repeatable in the sense that one test won't influence subsequent calls.

This sounds like a reasonable behavior too:

NOTE: When running in Rails, Rakismet will run in test mode when your Rails environment is test or development, unless explictly configured otherwise. Outside of Rails Rakismet defaults to test mode turned off.

It would be great if you could add a tag for 1.0.0 to this repository

I've used this gem for 100K+ spam checks, 10K+ were marked as spam, and exactly 0 were marked as blatant. Is there a problem with Akismet, or this gem, or maybe there's a problem with my code (is there specific content I can send to trigger the blatant flag?).

I noticed that data is being sent over http, not https:

The SDK correctly formats datetimes that are DateTime but not Time

This should probably be updated to account for both since they both have the iso8601 method.

The internet made a mistake on the spelling of "referrer" so we need to make sure we always use "referer" instead.

client.rb:376 needs to be updated to referer: :referer

• Running test phase for ruby20 ...
  Loaded suite ClientTest
  Started
  ...F

  Failure:
  test_comment_check_with_invalid_api_key_raises(ClientTest)
  /var/tmp/portage/dev-ruby/akismet-1.0.1/work/ruby20/akismet-1.0.1/test/client_test.rb:39:in `test_comment_check_with_invalid_api_key_raises'
  36: end
  37:
  38: def test_comment_check_with_invalid_api_key_raises
  => 39: error = assert_raise( Akismet::Error ) do
  40: @invalid_client.comment_check 'ip', 'ua'
  41: end
  42: assert_equal Akismet::Error::INVALID_API_KEY, error.code

Akismet::Error expected but was
<URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.akismet.com:80 (or bad hostname?)>)>

diff:
? A kismet ::Error

? URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.a .com 80 ( bad hostname?)>)

....F

Failure:
test_submit_ham_with_invalid_api_key_raises(ClientTest)
/var/tmp/portage/dev-ruby/akismet-1.0.1/work/ruby20/akismet-1.0.1/test/client_test.rb:54:in `test_submit_ham_with_invalid_api_key_raises'
51: end
52:
53: def test_submit_ham_with_invalid_api_key_raises
=> 54: error = assert_raise( Akismet::Error ) do
55: @invalid_client.submit_ham 'ip', 'ua'
56: end
57: assert_equal Akismet::Error::INVALID_API_KEY, error.code

Akismet::Error expected but was
<URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.akismet.com:80 (or bad hostname?)>)>

diff:
? A kismet ::Error

? URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.a .com 80 ( bad hostname?)>)

.F

Failure:
test_submit_spam_with_invalid_api_key_raises(ClientTest)
/var/tmp/portage/dev-ruby/akismet-1.0.1/work/ruby20/akismet-1.0.1/test/client_test.rb:65:in `test_submit_spam_with_invalid_api_key_raises'
62: end
63:
64: def test_submit_spam_with_invalid_api_key_raises
=> 65: error = assert_raise( Akismet::Error ) do
66: @invalid_client.submit_spam 'ip', 'ua'
67: end
68: assert_equal Akismet::Error::INVALID_API_KEY, error.code

Akismet::Error expected but was
<URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.akismet.com:80 (or bad hostname?)>)>

diff:
? A kismet ::Error

? URI::InvalidURIError(<the scheme http does not accept registry part: invalid_api_key.rest.a .com 80 ( bad hostname?)>)

..

Finished in 2.922023833 seconds.

13 tests, 22 assertions, 3 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
76.9231% passed