HN user

pstatho

47 karma
Posts0
Comments20
View on HN
No posts found.

Just tried it out and looks pretty good, nice work!

My business account is on Office 365 and the emails that come in from the system go into my Junk folder. I took a quick look at the headers and didn't notice anything obvious. Perhaps the body is to short and with the link it looks suspicious??

Other than that, I got 2 email notifications that the email is available and then another 2 emails with the success after the signature.

IMO you should lean towards whatever makes you feel productive. There is nothing more self-motivating than being able to build something even if it's just for yourself. No matter what technology you use, you will come up against hurdles, so how does the documentation and community help out? These are much more important than licensing.

As for licensing MS technology, I highly recommend the Bizspark program. You can register a company for $50 at Registres des Entreprises and that's all you need. You will get free licenses for 3 years that you get to keep plus a whole bunch of Azure discounts. BTW, the licensing of Windows and VS are pretty much negligible in any business. SQL server on the other hand is cost prohibitive, but that is where you can use PostgreSQL.

MS is slowly changing, adopting more and more open source, github, mono. I think they are transforming their business from selling licenses to subscriptions (like Office).

I don't know the financial deal that is in place, but I don't see how it impacts the affiliation.

From my perspective the accounts are not shared, so you needed to register there to create an account. We don't share databases. Also, it is not our company and operates completely independent from us. This is what I meant by not affiliated. Hope that clears it up.

The 3rd party sells their service, which is web-based chat application, to any company. Think of it as a company that offers hosted forums (SaaS model), but chats instead of forums. It allowed Youporn to offer a chat service to users, without us having to develop and maintain it. Again this decision was done before we took over.

Using chat.youporn.com is not that different than using ypchat.com, personally I would have preferred the latter for obvious reasons.

No I wasn't, our company had no involvement with YouPorn at that time.

We spoke to the owners about the issue and they are really some of the nicest people we've met. They really did not have malicious intentions.

That issue brought the privacy flaw to the forefront, and certainly the adult industry pushes those limits. We always strive to respect industry best practices regarding privacy, especially around cookie handling. We constantly review privacy policies around the world.

Hashing algorithms are not standardize across our network of sites yet. We use various methodology depending on what allows us to move fast and secure. You would be surprised to see the amount of moving parts there are.

We are currently in very close discussions with the 3rd party. In our official statement we purposely did not name them, we don't want to throw them under the bus. Of course we are reviewing all obligations.

We do deal with multiple security firms, and we regularly do security audits (both white and black box audits). We also deal with PCI, because we have paying sites as well, like Brazzers.

We can talk about the industry in general another time, but obviously we believe all types of sites can co-exist.

I'm CTO for Manwin Canada and ultimately responsible for YouPorn.

It's unfortunate that people are associating chat.youporn.com to the actual YouPorn.com site, but they are not affiliated at all. It was operated by a completely separate entity, which we've obviously closed as soon as we discovered it. The accounts on chat.youporn.com are different than the accounts on YouPorn. Though as was mentioned, it is probably that some have re-used the same username password combination that is highly unrecommended for all you folks out there (if you read Hacker News, you already know that).

As for password policies, I've been enforcing hashing of passwords ever since joining, though as we inherit a lot of old code and sites we correct issues such as that as we come across them.

I'll be around for a while, if anyone wants to ask questions.

Gotta agree that 500 req/s for a scale on demand service. I'm building my service on the Azure platform, though nothing has been officially announced, it doesn't look like they'll have similar limits.

Great job! I've only looked at the video though. Your user experience looks quite intuitive which is important. I would continue to work on that. For example, those that say to use Flash for video, well you can detect what the browsers capabilities are.

Don't worry too much about the Silverlight installation. If the product is good, that won't be a barrier.

I also believe RIA apps are much better than AJAX based apps.