simplecto

Command line bros, assemble!

PS1 is the settings that give you the cool prompts on the command line.

I've gone searching for a directory of PS1's where I can browse, save, and try out different command prompts.

Do i need to make this? Or is my google-fu, perplexity-fu, and gpt-fu just not where it needs to be?

Or do I need to make one?

I've created oauth2_capture (https://github.com/heysamtexas/django-oauth2-capture/), a Django package that makes it easy to capture, store, and refresh OAuth2 tokens from multiple providers.

The package currently supports Twitter/X, LinkedIn, GitHub, Reddit, Pinterest, and Facebook, with more providers planned. It handles the entire OAuth2 flow, from authorization to token storage and automatic refreshing.

Key technical features:

  * PKCE support for providers that require it
  * Token refresh with retry logic for rate limiting (429 responses)
  * Clean Django models and admin integration
  * Proper token expiration handling

I built this because I kept reimplementing OAuth2 flows in different projects and wanted a reusable solution. The package is designed to be easily extended to support additional providers.

I'd love feedback from the community on the API design, code quality, or additional features that would be useful.

Yes, Allauth does a great job of oauth and user signups/management. This is not that.

When to use oauth2_capture

Choose oauth2_capture when your application needs to:

  * Post to social media platforms on behalf of users
  * Access provider APIs (GitHub, LinkedIn, etc.) using user permissions
  * Perform actions that require fresh OAuth tokens with specific scopes
  * Maintain long-term API access with automatic token refreshing
  * When to use django-allauth

Choose django-allauth when you primarily need:

  * Social authentication for user login
  * User registration and management
  * Email verification workflows
  * Account linking between social providers

Can they be used together?

Absolutely! You can use django-allauth for user authentication and oauth2_capture for API interactions. They solve different problems and complement each other well.

Simply put: django-allauth manages users, oauth2_capture manages tokens.

It is incredibly sad that companies and executive leadership teams are more devout to cloud and long-term contracts than their people. This is a function of poor procurement and short-term IT strategy, sure. More on that later.

Every day we see the hits come in. 15% here, 20% RIF there, it is relentless. Eventually these places get down to a skeleton crew.

I wonder, though, when many of these companies who push terabytes or petabytes across cloud and SaaS services -- will they begin to take a serious and sober look at an on-prem strategy?

In the last 18 months I've been part of a few projects to support teams in their efforts to do the forensics, hunt idle resources, waste, duplication, and not just trim the fat but really innovate back into on-prem.

Fixed costs with lots of overhead to grow.

Imagine that -- having petabytes of storage ready to go with a much bandwidth as a 10gig line can push all at relatively fixed costs?

Its possible because is it not 2013 anymore. All those APIs and automations you enjoy in cloud are available in one form or another on-prem.

But you still need the bare-metal expertise that seems to belong to older Millennials and the grizzled Gen-Xers (remember those salty bastards?). They are out there, hiding in the cool isles of the data-centers racking and stacking all those nvidia GPUs right now.

Think about it -- its time to re-evaluate the value of all this surplus SaaS and cloud convenience. We are way past the time of being intellectually lazy and hand-wavy "cloud is just better" conversations.