Jan Lehnardt

icon indicating a website link http://neighbourhood.ie icon indicating an email [email protected]

icon company Neighbourhoodie Software icon location Berlin, Germany icon location Makes @couchdb & #offlinefirst. Made @jsconfeu @greenkeeperio @hoodiehq. CEO at @neighbourh00die. Dissatisfied with the status-quo.

Results 211 comments of Jan Lehnardt

Security: Make databases private by default

@thigg are you planning to submit a PR here?

Performance regression on CouchDB v3 while using custom reduce function

I’ve attempted a quick demo that caches the transpilation inside the JS process, this would still do one transpile per couchjs process, but should still be a lot better. @konrad-ohms...

Performance regression on CouchDB v3 while using custom reduce function

@konrad-ohms thank you for confirming this, we’ll see about getting this into 3.x ✌️

Performance regression on CouchDB v3 while using custom reduce function

@konrad-ohms would you be able to once more test this PR: https://github.com/apache/couchdb/pull/3728 — it uses SHA-256 over crc32, and thus is production ready, we just wanna make sure this still...

Performance regression on CouchDB v3 while using custom reduce function

Thanks for the update! We expected a reduction in performance, but this is quite a jump. Maybe we can think about making this configurable, most folks only ever run trusted...

feat: add same_site = none_secure option

I’d be happy to bike shed this to make it its own config variable `cookie_secure = bool` and folks who want both can set both, this was the least effort...

feat: add same_site = none_secure option

This might still be useful for scenarios where folks are behind proxies where they can’t add the Secure flag to the `Set-Cookie` header dynamically, and if they don’t want to...

Query Server Protocol v2

> With the discussion to move ChakraCore into the system, do we really want to bother with continuing to support a query server protocol at all? I'm not so sure....

Make #4094 an opt-in config until we can swap it to opt-out in the next major release

what about auth proxies? the token is a part of our documented public API

Make #4094 an opt-in config until we can swap it to opt-out in the next major release

that would be an option, but you’d want admins to disable the sha1 check completely still, so I’m not sure we can get around a config option