> Being an OAuth 'provider' (emphasis) is not open source
Being an OAuth provider is precisely what everyone expects from a self-described "open source authentication service". If Supertokens does not support that out of the box, it should not really be called an open source authentication service.
I understand you want to capitalize from your work, but I feel this is a gross misrepresentation of a project.
> My personal pet (non scientific) theory is that repeated infections over-sensitize the immune system, almost like an allergic reaction or something.
There have been a few variants that have a markedly change in their ability to spread and also their severity. They might be hitting people differently. I mean, if the same person is getting infected multiple times with carrying degrees of severity, something is changing in the infection.
You are oblivious to the point of this approach. Scaling has nothing to do with it. It has everything to do with not imposing useless and detrimental constraints that buys you nothing but problems. You specify interfaces, and keep implementation details from leaking by encapsulating and insulating them. This is terribly basic stuff.
You can do this already without adding any sort of microservice, schemas, duplicate definition files, externally maintained libraries, etc..
It's a basic feature of most languages.
It is NOT an exclusive benefit of a microservice pattern. Stop claiming that, it's one of the most frustrating claims/lies microservice advocates make.
The actual benefit is that you're forcing developer to use interfaces. At a massive cost.
There are much cheaper alternatives. You enforce a Dependeny Injection pattern on your services. Code reviews. Linting tools.
So no, this is not basic stuff.
And worse still, if your team can't properly use interfaces in your languages, how do you expect them to suddenly learn to use them properly in your services?
It'd be great if you minded your tone; this is HN.
I don't know where you're getting implementation details leaking when it's just API definitions being shared - they don't leak implementation details unless they're badly designed, which would affect them either way.
People get work done by knowing what they're doing, which I'm not sure you are able to tell.
There is plenty of literature that explains quite thoroughly the process of software architecture. Basically all major software architecture styles from the past four decades reflect the need to encapsulate and insulate implementation details, including the need to specify a domain model and how it should be specific and exclusive to each project.
Somehow, you are oblivious to basic principles but still feel entitled to insult others based on domain knowledge you clearly lack.
> but I agree, this is not something that i've ever considered when filtering CVs.
As a proficient LaTeX user, this is the stupidest take I ever saw on resume tips. I mean, your skills and experience do not vary with the document system you used to generate your CV. Some hiring managers swear by MS Word templates, other hiring managers ask for Europass, others ask you to fill in a form and request a cover letter. It would be stupid to assess the suitability of any candidate on this sort of bullshit.
> LaTeX for your resume?! If someone sumgly sends me a .TEX (...)
I'm not sure you got it right. You still have a LaTeX doc if you compile it to generate a PDF. LaTeX can have a very unique and peculiar look and feel that pops up to those in the know.
>you're already talking about people which are fainting and suffocating.
No. Many Covid patients have blood oxygen levels so low they should be dead (into the 70s and even lower). But they’re not gasping for air, their hearts aren’t racing, and their brains show no signs of blinking off from lack of oxygen. They did not need vents- their pulse ox levels were misleading.
It makes absolutely no sense at all to fabricate conspiracy theories based on the assumption that everyone in the world was systematically subjected to a procedure which was rejected right from the start.
> Early COVID-19 research found that most patients with optimum levels of vitamin D did not require ICU or breathing assistance and survived the infection.
Some sources point out that only 10-20% cases of covid are admitted to intensive care unit, and 80-90% of cases are mild.
I seriously doubt that up to 90% of the population has "optimum levels of vitamin D".
You can’t reverse an implication like that. “Most patients with X did not require Y” is not the same thing as “most patients who did not require Y had X”.
Being an OAuth provider is precisely what everyone expects from a self-described "open source authentication service". If Supertokens does not support that out of the box, it should not really be called an open source authentication service.
I understand you want to capitalize from your work, but I feel this is a gross misrepresentation of a project.