Futurama in 3D, Animation, Computer Animation, Illustration by Alexey Zakharov

Futurama in 3D is absolutely stunning

Futurama in 3D, Animation, Computer Animation, Illustration by Alexey Zakharov

Whoa. Artist Alexy Zakharov re-imagined the world of Futurama in 3D and transformed the cartoon into a complete stunner. It makes me want to watch a movie version of Futurama set in this world right now. Hell, it makes me want to cryogenically freeze myself so I can live in this world when I wake up.

Using 3ds Max, Nuke, Photoshop and After Effects, Zakharov was able to create a ‘test shot’ to see what his Futurama would look like. It’s so awesome. Here it is in full:

Inbox launches as an open-source email platform

Inbox app - email platform

Email is a painfully out-of-date technology, but it’s not going anywhere. A new startup, Inbox, is launching its “next-generation email platform” as an alternative to aging protocols like IMAP and SMTP.

Before you email junkies get too excited, this is a platform play, so there’s no user-facing app just yet. The core of Inbox’s efforts is an Inbox Sync Engine for developers that adds a modern API on top of mail providers, including Gmail, Yahoo and Outlook.com.

The engine itself is open source, but Inbox is planning to release a hosted SaaS version of its platform later this year. In the meantime, developers can get started on building apps and clients with their own installations.

The Inbox team is comprised mostly of MIT alumni. CEO Michael Grinich worked as an engineer at Dropbox and a designer at Nest, while co-founder Christine Spang previously worked on the Linux kernel at Ksplice. The firm’s seed investors include Fuel Capital, SV Angel, CrunchFund, Data Collective, and Betaworks.

Inbox emerges just weeks after Gmail announced its own API. However, Inbox touts its own service as a better option because it is open source, supports multiple providers and is built by an “email company” rather than an “advertising company.” Zing.

We’re always on the lookout for a killer solution to the email problem, so we’re eager to see what developers come up with on the Inbox platform later this year.

 Inbox Source – TNW

Error codes, HTTP codes

HTTP CODES – a glance

Informational 1xx

  • 100 Continue
  • 101 Switching Protocols

Successful 2xx

  • 200 OK
  • 201 Created
  • 202 Accepted
  • 203 Non-Authoritative Information
  • 204 No Content
  • 205 Reset Content
  • 206 Partial Content

Redirection 3xx

  • 300 Multiple Choices
  • 301 Moved Permanently
  • 302 Moved Temporarily
  • 303 See Other
  • 304 Not Modified
  • 305 Use Proxy

Client Error 4xx

  • 400 Bad Request
  • 401 Unauthorized
  • 402 Payment Required
  • 403 Forbidden
  • 404 Not Found
  • 405 Method Not Allowed
  • 406 Not Acceptable
  • 407 Proxy Authentication Required
  • 408 Request Timeout
  • 409 Conflict
  • 410 Gone
  • 411 Length Required
  • 412 Precondition Failed
  • 413 Request Entity Too Large
  • 414 Request-URI Too Long
  • 415 Unsupported Media Type

Server Error 5xx

  • 500 Internal Server Error
  • 501 Not Implemented
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout
  • 505 HTTP Version Not Supported