Lots of discussion in the OAuth mailing group about the implications for OAuth/OIDC. The thread starts here: https://mailarchive.ietf.org/arch/msg/oauth/FFkUlOiz7I4K03pq...

> How to review this as an IETF RFC?

Suggest joining the OAuth mailing list and responding there, or creating a PR against the repo (but I'd first read the discussion on the mailing list thread to avoid duplication).

> Btw the Tailwind newsletter/email that goes out is genuinely useful as well, so I recommend signing up for that if you use Tailwind CSS at all.

What is the signup link? I googled a bit but couldn't find it.

I think it's https://tailwindcss.com/blog

I'm not a heavy claude code user, but opencode is pretty cool. Would love to hear your experience on the differences.

Yeah, the tiered pricing changes for M2M[0] in 2024 didn't make much sense to me. I guess I don't understand their COGS, though.

0: https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-co...

I dunno.

I asked a similar question here: https://news.ycombinator.com/item?id=46472532 on the post where I learned about this list.

My company just released a JWT library for java that supports Ed25519[0]. Any idea how I can submit that to the ianix list?

0: https://github.com/FusionAuth/fusionauth-jwt

Yeah, that one sentence was weird. The rest of it was, I thought, interesting. The idea that genAI is so much better in the attack scenario than in the defense scenario. The fact that Claude has been weaponized. That vendors are, as always, chasing buzzwords. Seemed useful to me.

I have a friend who works at Mastra[0].

Got part way through their tutorial, seemed okay. Haven't used it in prod, though.

0: https://mastra.ai/

Yes, this is so powerful.

One of my favorite moves is to ask a question that I feel has an obvious answer and then say "what am I missing?" Sometimes I am right, other times I am missing something.

Either way I'm modelling:

- that it's okay to ask questions to which the answer seems obvious

- that it is totally fine not to know everything

Mine is "I'm going to ask the stupid obvious question here", then ask the question.

Some good insights here.

> I'm starting to wonder if we'll need to track prompts with commits, like we track commit messages today. Or design systems assuming the debugger never wrote any of the code.

As we start to truly build software systems with a foundation of genAI, there is no question in my mind that the SDLC will change. I'm not sure how you do either of these suggestions, but they seem like a good start.