Only matters because the purpose of discussion at this point is to, somehow eventually, influence a Core change where it is the reference implementation powering an overwhelming share of the network.
As long as BIP's are defacto suggestion box slips for Core, the problem is unsolvable, or at least reflects state politics as we know them. Core is a politburo #966918.
A blog post would be a sufficient medium otherwise, assuming, that blog is of a developer with a competing implementation with meaningful network share.
On theme for this month, think the first Continental Congress after being censored from British Parliament... it only mattered once they took up arms (autonomous excercise of power).
A possible goal of a centralized alt-BIPs repo could be to unify alternate implementations, being analogous to the Continental Congress, but then who are the 13 alt implementations it could unify to effect the network? Do BTCD maintainers even show up? Seems Knots has even less friends than John Adams did at first.
Only matters because the purpose of discussion at this point is to, somehow eventually, influence a Core change where it is the reference implementation powering an overwhelming share of the network.
As long as BIP's are defacto suggestion box slips for Core, the problem is unsolvable, or at least reflects state politics as we know them. Core is a politburo #966918.
A blog post would be a sufficient medium otherwise, assuming, that blog is of a developer with a competing implementation with meaningful network share.
On theme for this month, think the first Continental Congress after being censored from British Parliament... it only mattered once they took up arms (autonomous excercise of power).
A possible goal of a centralized alt-BIPs repo could be to unify alternate implementations, being analogous to the Continental Congress, but then who are the 13 alt implementations it could unify to effect the network? Do BTCD maintainers even show up? Seems Knots has even less friends than John Adams did at first.