welcome to bitcoin culture lol

Oh, I wasn't aware that was an option. Let me know how you like it!

i dunno, never thought about it. the social meetup wasn't scratching my itch. i gained a lot of technical during that time so maybe i was just outpacing the other folks at those meetups.

i started my own meetup to discuss only the tech

fwiu their linux fork is way out of date

get yourself a framework

amen

i have undertaken the task of writing and implementing the spec, as requested by the team

> the specs will sort themselves out if they’re needed

they are needed and i am the guy to make it happen

i'm overthinking it, just write the damn code and push out the PR

if they are two codebases with two different maintainers, then it would seem that getting the PR merged is equivalent. you still have two different folks review and approve the implementations, each in a different context. and the spec repo PR also needs to get merged so 2-3 distinct sets of eyes (the spec is maintained by the same person as one of the impl codebases in my case so 2 sets of maintainer eyes for 3 PRs in 3 different contexts.)

it's a serious question! i have never written a (successfully merged) spec before.

seems like the key goal is to disambiguate any possible misunderstanding of the important implementation details while leaving the rest of the decisions up to the implementor. does this require two different individuals to implement it? if an llm is implementing it, are two different prompts sufficient?

asking for maude