machineid VS keygen-api

Why would you want to scroll horizontally? Or are you referring to the code samples? It's only a code "sample" (i.e. non-working just to show off the platform), so fingerprint would likely come from something like https://github.com/denisbrodbeck/machineid. Full examples are available in the Go SDK docs [^0].

[^0]: https://github.com/keygen-sh/keygen-go

As a Gopher, I've always used and recommended machineid. But there was no equivalent in Python, even though the question comes up all the time. So I wrote a quick semi-port of the machineid package.

I don't have an Elixir background, but I absolutely utilize pattern matching in my Ruby code bases:

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/keygen-api/blob/master/app/migr...

- https://github.com/keygen-sh/keygen-api/blob/36cd61db143cc1c...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

I love it. I want even more pattern matching too, like with defp: https://bugs.ruby-lang.org/issues/19764.

Honestly, I don't have many resources to provide. I read a lot of policy tests via GitHub search (e.g. path:spec/policies/*/*.rb), but couldn't find anything that looked like what I wanted. I wrote the DSL as-needed in order to fully test my app's authz while migrating from Pundit to ActionPolicy.

It's not the prettiest when you actually look beneath the covers [0], but it does what I wanted -- provides a way to write exhaustive authz tests. Without the DSL, I probably wouldn't have written. The PR for said migration was massive [1], and was a precursor to going open source [2].

[0]: https://github.com/keygen-sh/keygen-api/blob/master/spec/sup...

[1]: https://github.com/keygen-sh/keygen-api/pull/647

[2]: https://github.com/keygen-sh/keygen-api/issues/644

Yes, I can see why you might make this argument. [1]

[1] https://github.com/keygen-sh/keygen-api/blob/master/LICENSE....

And not at all set on WorkOS. It just looked like the easiest way to set up SSO last time I researched the topic. Feel free to comment on the issue with any recommendations.

Since when can you run heroku pg:upgrade to switch database tiers? I was following an upgrade sequence I put together over the years [^0], but I guess Heroku automated this at some point? What would be really funny is if this had been possible all long...

[^0]: https://github.com/keygen-sh/keygen-api/blob/master/.notes/d...

Maybe use keygen-sh?

I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do.

[^0]: https://keygen.sh

- org-2.php.pkg.github.com/package

I wonder if that had any impact on their decision.

[0]: https://github.com/keygen-sh/keygen-api/issues/490