4 ms·

Edgefolio (https://edgefolio.com/ https://edgefolio.com/) – London, U.K. Lead Designer – Full Time Edgefolio is a new platform for the hedge fund industry tha

Edgefolio (https://edgefolio.com/ https://edgefolio.com/) – London, U.K. Lead Designer – Full Time Edgefolio is a new platform for the hedge fund industry that connects investors and funds in a transparent, compliant and scalable way. We are looking for a lead designer to join our team in London and shape the next generation of our webapps that deal with: - visualising complex data and - social interactions between stakeholders. Our ideal candidate is an experienced web designer who’s confident owning all aspects of design at Edgefolio, from product to UI to visual design. Experience with (or a basic understanding of) the following is a definite plus: - financial data visualization - the requirements for front-end development - responsive design for different contexts. Edgefolio is a seed funded company and part of this year’s Seedcamp accelerator program. If you're interested in joining us, please send us whatever you'd like share (portfolio site, dribbble, github, ...) to hn@edgefolio.com. (Unfortunately we are not in a position to help with visas, so we mostly need a great designer who is already eligible to work in the UK.)

boothead 12y ago
I'm getting an ssl error on you site from my iPad.
- sarciszewski 12y ago
  This is what I get: SHA1: 0A:82:48:79:58:9F:0C:1E:13:B8:D9:AB:69:3E:11:8F:CB:FE:D3:EC MD5: 10:EE:4F:E5:43:DD:81:F2:3F:E6:4B:B9:4D:9C:53:31 Serial: 6A:B2:9B:5B:0B:0E:92:22:E5:3A:07:D1:0A:D3:81:B5 Your browser is probably blocking it because it doesn't have use SHA-256.
  - icebraining 12y ago
    It seems like they're sending different certs to different clients - the Qualys SSL test reported it as expired on the 17th of Feb.
    - hnarayanan 12y ago
      This seems to have stemmed from Qualys caching an earlier certificate that has since been updated. Independently, the original problem seems to have been our usage of Xdomain (a JavaScript alternative to CORS) to support older IEs used by some of our customers. The way it was being used seemed to conflict with Chrome on iOS. I've pushed a fix to our staging servers and this will manifest in production once it has been better tested. Thanks everyone for pointing this out!
      - sarciszewski 12y ago
        Any time :)
- hnarayanan 12y ago
  Thank you for pointing this out, I will investigate this now.

boothead 12y ago

I'm getting an ssl error on you site from my iPad.

sarciszewski 12y ago
This is what I get: SHA1: 0A:82:48:79:58:9F:0C:1E:13:B8:D9:AB:69:3E:11:8F:CB:FE:D3:EC MD5: 10:EE:4F:E5:43:DD:81:F2:3F:E6:4B:B9:4D:9C:53:31 Serial: 6A:B2:9B:5B:0B:0E:92:22:E5:3A:07:D1:0A:D3:81:B5 Your browser is probably blocking it because it doesn't have use SHA-256.
- icebraining 12y ago
  It seems like they're sending different certs to different clients - the Qualys SSL test reported it as expired on the 17th of Feb.
  - hnarayanan 12y ago
    This seems to have stemmed from Qualys caching an earlier certificate that has since been updated. Independently, the original problem seems to have been our usage of Xdomain (a JavaScript alternative to CORS) to support older IEs used by some of our customers. The way it was being used seemed to conflict with Chrome on iOS. I've pushed a fix to our staging servers and this will manifest in production once it has been better tested. Thanks everyone for pointing this out!
    - sarciszewski 12y ago
      Any time :)
hnarayanan 12y ago
Thank you for pointing this out, I will investigate this now.