jcmfernandes

This is also one of my major complaints at this point. I'm building a developer tool with starklark resting at its core and I had already came across your work.

I wish the starklark team had addressed it at this point.

> No foreign key constraints

Wat?

There are LOTS of them. Anything that allows you to link your Google/Facebook/etc. account to another system, so that system can perform actions on your Google/Facebook/etc. account on your behalf.

Examples: Slack (e.g., notify you of events on your calendar, create a GMeets meeting), services like cal.com, whatsapp (store backups on your Google Drive).

Since OIDC is a layer on top of OAuth 2, it inherits its complexity. OAuth 2.1 (currently draft) will help bring some sanity. GNAP - https://oauth.net/gnap/ - will, one day, tie everything.

Correct. OAuth is for delegated authorization. OpenID Connect for authentication.

Busy market, hard to sell to companies who need to migrate. The main reason for migrations is price (eg. Auth0 being super expensive), which is not a good thing. I'm probably not telling you anything new.

It can go up to 48%. But as in most countries, it's progressive: you pay X% over the first A€, then Y% over the next B€, etc.

Then you have Social Security (mandatory): 11% on the employee and 23,75% on the employer, or 21,4% for independent workers.

Portugal already has tax breaks for the youth (aka IRS Jovem), but the new right-wing government is seeking to extend what the previous left-wing government introduced. That includes loosening requirements and extending the duration of the tax breaks.

Now, while in Portugal people talk about these as measures to retain the Portuguese youth in the country, no political party has framed it as a measure to capture foreign youth. Puzzling to me.

https://github.com/hajimehoshi/ebiten (golang) and https://github.com/gosu/gosu a (ruby) are, IMHO, worth exploring if you want to put some emphasis on coding.

I expected this comment, just not so early in the life of this thread. Moving on... cool stuff!

I'm sorry to hear that. Thanks for the tool and wishing you a speedy recovery!

There's a Portuguese watch company using this same style since 2016: https://isotopewatches.com/products/isotope-gmt-zero-degrees

I love their timepieces.

Do they use zeitwerk?

Thanks for this. Can you share the experience of those who don't use VS Code?

OIDC standardadized Initiating Login from a Third Party: https://openid.net/specs/openid-connect-core-1_0.html#ThirdP...

It works very differently, but it will get the job done in a much safer way.

Here's an interesting blog post on why SAML is insecure by design: https://joonas.fi/2021/08/saml-is-insecure-by-design/

Malleability sucks in this context.

OIDC supports Initiating Login from a Third Party: https://openid.net/specs/openid-connect-core-1_0.html#ThirdP...

Unlike SAML's "take this assertion" IdP-initiated flow, OIDC went for a "start an authentication with this IdP, for this user, and send them back here". Much, much safer.

We are happy WorkOS customers at hopin.com :) their SDKs make integration dead easy and their team is super responsive. Thanks @grinich and all the WorkOS team!