Simon Frei

I moved this over to the docs, as that's what it targets. There's a lot of things that make sense to document (and might already be documented), like progress updates....

What's the scope of what you'd like to tackle - reorganisation the docs structure or "just" (it's a lot on its own) structuring the FAQs? From what you wrote in...

Partly :) What I am looking for is some middle ground between the super high-level part in the first post (separate docs by those principles) and taking existing content apart...

Right, that's already quite a bit of work in and of itself, however that's at least what I understood Audrius' "skeleton" and Jakobs "sketch" to be respectively what I'd consider...

Agree, looking good already :) I have some comments on individual entries, but I believe that would be easier to discuss on a WIP PR of a branch that has...

I thought I responded yesterday already, but apparently didn't send - sorry about that: The multi-PR thing might not be necessary/useful in the end. Nevertheless the only thing required is...

According to their homepage it can annotate, so I assume it can also read annotations.

To me the main point here is this is cosmetical, low(est) importance, no need for discussion and low effort to fix. Basically the kind of thing that sure, fix it...

A label for devices we haven't seen in ages seems reasonable. I think this could/should live entirely in the web UI code, as you have all the needed info there...

> But isn't this the same thing as the existing "last seen" row? I basically interpret this as a way to make that more discoverable, respectively pull attention to it....