Everett Pompeii

It would be great to have these as part of the interview metadata. I can add this to my backlog. Do you all know where I could get a copy...

I started looking into this. Flask_User version 1.0, which is [still in Alpha](https://flask-user.readthedocs.io/en/latest/introduction.html#flask-user-v1-0), has the [concept of roles](https://flask-user.readthedocs.io/en/latest/data_models.html#optional-role-and-userroles-data-models) built in. It's incompatible with 0.6 though, so we should probably wait...

Thanks! I was conflating having roles with roles+permissions. Is having the concept of permissions in the data model something that you think would be worth having at this point?

I agree that it would definitely be great feature to have in Flask-User, and it would be preferable to have it added upstream. I'll drop a line on their GitHub...

That makes sense from a performance perspective. I guess this is more of a general question, but when there is more than one application server, the load balancer picks an...

The pull request for the documentation change is [wasm-pack Issue #899](https://github.com/rustwasm/wasm-pack/pull/899).

This seems like a great start towards the goal of having a single backend! As to your first undesirable trait though, could we create a more intelligent default backend based...

I have a fully functioning revisions table with these attributes. Let me know if you would like to take it for spin. There's also some additinal complexity in how a...

@NeilMcKechnie doing so accomplishes two things: 1) It allows for "track changes" or a wiki-like history for listings edits 2) A request -> review -> approve (or reject) workflow The...

Yeah, that would be best! One option is to create an `mdbook` preprocessor that auto-generates the markdown list based on a given file path. Or I could add a check...