Elvis Stansvik

> This example was working fine for us, except we had to add > > ``` > 'overwritehost' => 'cloud.example.com', > 'overwriteprotocol' => 'https', > ``` > > to our...

> > This example was working fine for us, except we had to add > > ``` > > 'overwritehost' => 'cloud.example.com', > > 'overwriteprotocol' => 'https', > > ```...

> > Is anyone running this example successfully with Nextcloud 18, Collabora 4.2? > > Yes: https://github.com/bentolor/docker-nextcloud-collabora-postgresql-letsencrypt Thanks @bentolor, I will study the differences between our configs.

> > > Is anyone running this example successfully with Nextcloud 18, Collabora 4.2? > > > > > > Yes: https://github.com/bentolor/docker-nextcloud-collabora-postgresql-letsencrypt > > Thanks @bentolor, I will study the...

Could this be merged? It would be sad if it was just left here. We've been successfully running our instance off of this example (or well, what it looked like...

I'm here with another use case for this: We plot drill core scanning results for geological analysis/interpretation. In this field vertical plotting with the (down-hole direction going downward) is a...

I agree with all of this. This is what I think, off hand, would be most intuitive: - The callee _must_ ignore the `INTERRUPT`. - The dealer _may_ send the...

@oberstet It reminds me a little of temporal logic, and perhaps CSP that I learned about in logic class back in school, and quickly forgot about :P But I'm sure...

Point 3: > Clients must not send advanced message types or attributes that they did previously announce during session establishment. should be > Clients must not send advanced message types...

In point 6 and 7, there's a difference in phrasing: "must not send message types" and "must not send advanced feature attributes". Should the former be "must not send advanced...