Benedikt Allendorf

Thank you for the reply! You're right, that makes a difference - but only in the error messages ("no auth" vs. "invalid auth"). I have had a look at HA's...

@richieadler I thought about that, but while the specific technical aspects are solved, there isn’t an answer to the general topic of plans/roadmaps/handling of bugs. @tiangolo talks about the “bus...

You missed the place where it says [ `// prepend base (dev base is guaranteed to have ending slash)`](https://github.com/vitejs/vite/pull/10723/files#diff-f2f744fef86a2c562dd5142240912f7a2d28404fac536740a2424daf628aa609R381) - and it took me forever to find that! ;) Nevertheless,...

Detecting the new monitor isn't a problem: ([newDisplay](https://www.electronjs.org/docs/api/screen#event-display-added) can be used for that. But implementing it would be a bit of a hassle right now (see #744)

I'm just looking for a similar setting and I think it's not about the notification. While in a meeting (especially with screensharing), I do not want to have any Stretchly...

Here is a small PoC of what I've been thinking: https://github.com/hovancik/stretchly/compare/trunk...BenediktAllendorf:stretchly:MeetingDND

Yeah, I can see how additional `if`s and `switch`es are annoying (but only three have been introduced and two of the occurrences are only intermediate steps anyway). Maybe it could...

I tried the extract approach and introduced three new helper methods (I didn't think too hard about the naming): https://github.com/hovancik/stretchly/compare/master...BenediktAllendorf:duplicated_code Those were lines with almost identical code except the one...

Sure, no worries. Changes like this are kind of hard to review and I'm not sure if they are worth it. On the one hand, reducing duplication seems like a...

😓 yeah, got messed up there. It's fixed now (and running locally here).