The use of commit-hooks is also very clever (mentioned here in the replies)

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?

Comments URL: https://news.ycombinator.com/item?id=44541738

Points: 5

# Comments: 5

Then those tokens would be saved in the database for your freelancer to use on their customer's behalf.

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'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

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

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.

Comments URL: https://news.ycombinator.com/item?id=43953010

Points: 3

# Comments: 2

One left tech to join his brother in an outdoors adventure company where they rent/sell rafting and camping equipment and run tours.

I know another one who shutdown his zombie startup. Now he just manages his rental properties and runs a newsletter for a "ZeroHedge" type crowd.

No one seems to be getting rich but they seem much more fulfilled.

This is in my requirements.txt

git+https://github.com/richardpenman/whois.git@master#egg=python...

And the meat of the file:

    import whois

    """Get WHOIS information for a domain."""
    try:
        domain_info = whois.whois(domain)
    except whois.parser.PywhoisError as e:
        return Response({"message": "Bad request", "details": str(e)}, status=400)

    if domain_info["domain_name"] is None and domain_info["registrar"] is None:
        return Response({"message": "Bad request", "details": f"{domain} not found or registered"}, status=400)

    return {"result": domain_info}

If this thing takes off and becomes a thing then adding those will be fairly straight forward.

https://news.ycombinator.com/item?id=43173022

Long story short is that I've decided to build an API service that wraps many of the most useful libraries and other services, even those "one-feature" SaaS offerings.

Be gentle, I'm sharing it to poke and critique.

I have some colleagues in F50 companies who asked to have a service like this deployed internally because of a number of bureaucratic reasons.

It is easier to get an internal API approved than it is to add it to the existing compiled/deployed software stacks. (weird, but it is what it is -- mostly about software supply chains)

Anyway, go look at the openapi spec and see that it is mostly just about scraping and format conversions (for now).

Comments URL: https://news.ycombinator.com/item?id=43173022

Points: 3

# Comments: 5

That didn't work for a number of reasons (cooking the books), but also network bandwidth is not fungible. Unlike commodities such as oil or natural gas, bandwidth’s value is highly dependent on specific factors like location, time, and network conditions. This variability makes it difficult to standardize bandwidth as a tradable commodity, complicating efforts to create a seamless trading market.

There are a few in the crypto/DePIN space poking at this problem. I remain highly skeptical.

I've implemented this in our workflows, albeit a bit more naive: when we kick off new processes the user is given the option to "put a human in the loop" -- at which point processing halts and a user/group is paged to review the content in flight, along with all the chains/calls.

The human can tweak the text if needed and the process continues.

It is a land grab like everywhere else.

The crypto people have already shown up, and the solopreneurs are chiming in as well.

Hopefully Bluesky’s algorithm can make the experience significantly different that people stick around.

Instagram launched a recent thing where they allowed people to reset their profile history and clean the slate.