cmackenzie1

3 ms·

1. 1.▲
   Epoch Countdown(epochcountdown.org)

   3 points by cmackenzie1 1y ago|0 comments
2. 2.▲
   by cmackenzie1 2y ago

   If the library wasn't open for extension, an enum could work. With the currently model, users can write their own plugins, bring their own storage provider, or even write an email consumer that reacts to events from the EventBus - all
3. 3.▲
   by cmackenzie1 2y ago

   If you are looking to add another provider, one can do so here: https://github.com/cmackenzie1/torii-rs/tree/main/torii-auth... If you want change the plugin logic completely, you can implement the Plugi
4. 4.▲
   by cmackenzie1 2y ago

   I’ve gone back and forth on using TypeId or named plugins using a string. Mainly switched to the named variant to support each oauth provider lookup by name. If you have any suggestions for making it better, let me know!
5. 5.▲
   by cmackenzie1 2y ago

   JavaScript definitely has a few such OpenAuthJS, Better-Auth, and Next-Auth. PHP Laravel, Ruby on Rails, Python Django, Elixir Phoenix all have some ways of doing this, but are usually baked into the framework. Others usually end up as a st
6. 6.▲
   Show HN: Torii – a framework agnostic authentication library for Rust(github.com)

   80 points by cmackenzie1 2y ago|38 comments
7. 7.▲
   Collection of Tech New Grad Roles for 2020 Start(github.com)

   1 points by cmackenzie1 7y ago|0 comments