On 12/13/2017 03:16 PM, Aaron Wolf wrote: > On 12/13/2017 11:28 AM, Bryan Richter wrote: > > <snip> > > Two comments: > >> Buffers can't exist in a system that has no account balances. The >> volatility gets pushed to the question of "Does the patron have >> enough money in their actual bank account." > > > I want it to go through a User Story / consent / design process, > but sometime we'll discuss this. There's no technical requirement > of a buffer, it's a UX and system-design question. It relates to > whether signing up for crowdmatching should actually serve to invite > and match further new patrons. It may be unnecessary or early > optimization. Anyway, it can be dropped from this topic now.
Oof, now I understand! The definition of "buffer" has changed from
*How many more months can I afford my current pledges?*
to
*How many more patrons can join before I get dropped?*
Let's definitely talk about that a lot later -- I already see
problems.
> <snip>
>
> That sounds like what David said too when I talked to him about
> this. He had a moment last weekend to at least look at things and
> think about Snowdrift code stuff. This could be a good place to hand
> off a little coding task(s) to him if you can delineate clearly. He
> understands the issues pretty well and may be able to help or at
> least discuss the implementation…
Great!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
