Rob Brackett

I want to clarify that I am avoiding the “abstract data model” terminology here because, while not inaccurate, I think it definitely implies something more substantial and specific to most...

I keep thinking back to a document that looks like this as an illustration of how thin or broad the model is here: ``` Hi there! This is a plaintext...

Checking back in here. @jbenet @whyrusleeping @Stebalien @daviddias @aboodman @lanzafame is this a good formulation? https://github.com/ipld/ipld/issues/39#issuecomment-395870317

Relatedly, is there a reason why using it is not recommended? https://github.com/stellar/bridge-server/blob/master/readme_bridge.md#security

> Access should be configured at the proxy/load balancer level rather than by using api_key param Ok, so this is really a concern that the option to do it will...

> The rest of that config file is snake cased. Just to be clear, the one in the config file is properly snake cased. It’s the one that is received...

Probably also when receiving a payment that the compliance server doesn't accept/have a record for: https://github.com/stellar/bridge-server/blob/master/src/github.com/stellar/gateway/listener/payment_listener.go#L181-L187

Ah. I _had_ run `gb generate`, but saw that it failed and so assumed it hadn’t generated the bindata. I’m not sure _when_ I did that, so it’s entirely possible...

When I filed this I hadn’t realized this was also a problem for the compliance server, so I want to note that the migration that shipped in v0.0.12 for compliance...

@nullstyle do you know if there are any plans to change the general behavior w/r/t this? At current, it looks like _either_ you implement `ask_user` and that is the source...