san_at_weblegit

4 ms·

1.
by san_at_weblegit 8y ago
The fact that there are so many reasons for the failure itself tell why the failures are so frequent. I strongly believe that it should be more than just the development teams which should be attributed for failures. Projects rarely get del
2.
by san_at_weblegit 8y ago
Assuming that you are referring to browsers as client here. One simple reason is that the client side data can always be manipulated so it does not really makes any difference. It might just give a false sense of safety but does not changes
3.
by san_at_weblegit 9y ago
This is indeed an important discussion. I was looking for some similar experience in the top few comments but couldn't find it, so I thought about writing my own. From my experience its about the person in the role, not the role itself
4.
by san_at_weblegit 9y ago
This is a pretty common trend in lots of places. These kind of decisions are driven for things other than computing needs. Maybe to look cool/cloudy/nextgen ...
5.
by san_at_weblegit 9y ago
Tangential answer: It would vary based on sensitivity of your application. JWT is not a bad option if we do not have a requirement of absolute session termination and if implementation does not have any vulnerability. People also use cookie
6.
Cheat sheet for interviews(medium.com)
2 points by san_at_weblegit 9y ago|0 comments
7.
by san_at_weblegit 9y ago
There is no single good answer to this question without taking into account the security consideration of the API in question and the consumers. On a high level all solutions work just fine as long as we understand the tradeoff's invol
8.
by san_at_weblegit 9y ago
The answer would be yes with a rider. It would vary across the use cases and security requirements.
9.
by san_at_weblegit 9y ago
This is a common problem with more and more companies relying on SAML federation. A part of this problem is solved by using SCIM provided your IDP and service supports it. Ironically even though SCIM is a protocol, the implementations vary
10.
Show HN: A simple, scalable, flexible and economical URL Shortener for Web(github.com)
3 points by san_at_weblegit 9y ago|1 comments
11.
by san_at_weblegit 9y ago
1. As an engineer I would definitely not work with a team that comes up with the first reason for rejection (Provided that I have not mentioned that stack on my resume to begin with). 2. The second reason is more of a choice of the given co
12.
Why another email verification service?(medium.com)
1 points by san_at_weblegit 9y ago|0 comments
13.
by san_at_weblegit 9y ago
Hi HN, We are providing a simple to use service to validate the user email addresses at the web doorway for the businesses. We validate the email addresses for more than just the syntax. The goals are three folds, First, give another
14.
Show HN: Validating the email addresses on signup, contact and subscribe forms(weblegit.com)
4 points by san_at_weblegit 9y ago|3 comments