Sven Slootweg

> crossing=uncontrolled is more useful for railway=crossing. That doesn't sound right to me - it is *primarily* used for road crossings in practice, with railway usage being [much less common](https://taginfo.openstreetmap.org/tags/?key=crossing&value=uncontrolled#combinations),...

> * The `crossing=marked`/`unmarked` scheme relies on a separate [`crossing:signals`](https://wiki.openstreetmap.org/wiki/Proposed_features/crossing:signals) key to indicate signalization. The `crossing` and `crossing:signals` keys together can express all four configurations. Aaahhhh, *that* is the missing...

> Good point. I wrote [a new overview article](https://wiki.openstreetmap.org/wiki/Crossings) about the different kinds of crossings and the conflicting crossing classification schemes. I also [explained the `crossing=unclassified` misnomer in more detail](https://wiki.openstreetmap.org/wiki/Tag:crossing%3Duncontrolled#Terminology)...

> I agree about the usefulness of the feature, and nobody is against the idea of supporting drag-and-drop local photos onto iD, we just don't have the developer bandwidth to...

Something to keep in mind is that despite the lofty ideals, the *practical* usefulness of copyleft licenses is... debatable, at best. GPL violations are widespread in practice, and are basically...

@morguldir > And there are umbrella organizations that handle GPL enforcement, e.g. Software Freedom Conservancy. In practice, it is very unlikely that your case will be taken on by such...

Attaching the contents of the Etherpad (in both HTML and Etherpad format) for posterity, due to the EOL of Mozilla's Etherpad instance. [rust-api-guidelines-error-chain.zip](https://github.com/rust-lang-nursery/error-chain/files/2497990/rust-api-guidelines-error-chain.zip)

The problem is caused by `errors`, though I'd say it probably qualifies as a nexe bug. The issue in the following code ([source](https://github.com/bodenr/errors/blob/master/lib/errors.js#L814-L815)): ```js errorCss = fs.readFileSync(__dirname + '/static/error.css', 'utf8');...

To be clear: to make this work without cookies in a browser environment, you have two options: 1. In an SPA, keep around the credentials in a locally scoped variable....

To clarify - `express-session` only delays the `end` of the response itself, not the chunks that are sent... meaning that Chrome will technically obtain the `Location` header _before_ the session...