jorgenhorstink

The past couple of weeks I've been reading a lot of great articles online, viewed a couple of inspiring TED talks and other video's, and I used that information to build the landing page.

Tomorrow I'm going to try to recap which articles I read, which video's I watched, and I'll write about it in a blogpost.

Good point about the carrousel. I might want to track some events to see if people actually use it. But if it is a long form, doesn't that hurt the experience? On massive long page?

You are actually able to click on the screenshots, but I guess we could make that more clear? Thanks for the feedback! Much appreciated!

I still don't get it why I've seen so few Node.js applications using Application Service layers, Domain Models and Repositories, and instead clog their MVC containers with calls to whatever datastore directly, with no Domain Model at all.

If the entire industry would stop testing and developing for ancient browsers, I'm quite sure people will upgrade their browsers within a couple of months (I understand this is not possible from a business perspective). Companies that still rely on ActiveX components or other proprietary stuff, won't upgrade IE soon anyway, but they might install a browser like Firefox or Google Chrome for daily browsing.

I don't think people would like to create brand icons manually. If I get a lot of e-mails from john.doe@ah.nl, why not running a separate Node.js instance trying to locate the favicon (and using it to display the logo) by trying known locations, or parsing the HTML; http://ah.nl/favicon.ico

The name of the brand might be easy to fetch by doing a WHOIS lookup. Just a thought...

I'm sure it takes a lot of time and dedication to developing the plugin, and I enjoyed reading the article, but this is not what I was expecting to see.

What would be useful to me though is a list of the top X e-mail contacts I received e-mail from and sent e-mail to the last Y days. I regularly have contact with several people from the same company/brand, and I always are using the search bar on top like: "John Doe something I remembered from the specific e-mail I'm looking for".

So basically I'm not that interested in mails I received from a brand, but I'm more interested in e-mails I received from a specific person.

Gamification would be awesome candy: statistics and graphs on how fast I'm responding to e-mails I receive, etc.

Most banks also have mobile applications for smartphones making money transfer even easier. I'm able to transfer money to people I've already sent money to, by just using an iPhone app, and a personal pin code. When I loose my phone, I can just block the app, just like what I'd do when I loose my plastic (credit) bank card.

In Holland we also use iDEAL [1], a nation-wide system for online shopping. It works a little bit like OAuth; I provide the webshop the bank I use, the webshop requests a money transfer, the bank creates a unique transaction, the webshop sends me to the bank, bank requests credentials and processes payment, and sends me back to the webshop proving details about the transaction. This system sounds much more secure to me than the credit card paradigm; only using a credit card number, an expiration date and a 'security code'.

I just don't understand why the USA is still using a method so susceptible to fraud.

[1] http://en.wikipedia.org/wiki/IDEAL

  <?php
  class AuthController extends Controller {
    public function __construct(Request $request) {
      $this->service = AuthService::getInstance();
    }
    // reflection calls a Module + Action attribute to {module}Controller
    public function login(Request $request) {
      if ($request->getRequestMethod() === WebRequest::POST) {

        if ($this->service->login($request->getAttribute('username'), $request->getAttribute('response')) {
          die('{ "success" : true }');
        } else {
          die('{ "success" : false }');
        }
      }
    }
  }
  class AuthService { // Application Service -> it just defines a clear API, not a Domain Driven Design service
    public function __construct(Session $session) {
      $this->session = $session;
    }

    public function login($username, $response) {
      try {
        $user = User::getRepository()->getByUsername($username);

        return $user->isValidChallengeResponse($this->session->getAttribute('challenge', 'auth'), $response);

      } catch (UserDoesNotExistException $e) { }
      return false;
    }
  }
  class User {
    protected static $repository;
    public static function setRepository(IUserRepository $repository) {
      self::$repository = $repository;
    }
    public function getRepository() {
      return self::$repository;
    }

    // yeah yeah, it is arguably if this belongs as a Domain method of the user…
    public function isValidChallengeResponse($challenge, $response) {
      // and yes, this is very weak challenge response…
      return md5($challenge . $this->getPassword()) === $response;
    }
  }
  ?>

You have little to loose. You have a no now, and might be able to upgrade it to a yes :)

I'd love to see an API model based on events and callback URL's.

pseudo, but you'll get the idea:

http://api.facebook.com/event/on-friend-connect?callback=htt...

IMHO, WebServices should communicate in an evented fashion. If I want to draw an umbrella on myserver if it is going to rain in The Netherlands, I don't want to ask the weather server every X minutes: is it going to rain? is it going to rain? is it going to rain?

No, I want:

http://api.weeronline.nl/event/on-weather-change?location=Ut...

pubhubsubbub solves this issue for RSS feeds, but pubhubsubbub is way too narrow to me. I hope evented API's will become the next big thing, enabling developers to create a whole new bunch of awesome products.

If you've any comments, remarks, suggestions, criticism, I'd love to hear it!