sajolida wrote (14 Mar 2016 14:24:49 GMT) : > Granted. "Watch Thread" could work. It adds an "eye" icon by the thread > (see attachment). I'll ask frontdesk whether if it's good enough for them.
... and then I suspect that one can use some filter / dynamic search / whatever it is called to look at watched threads only :) >>> Then, what about forcing them to paste the full public key (and not only >>> the key ID or a link)? This would prevent us from fiddling with key >>> servers while still allowing us to solve "1) Verify that the key matches >>> the email address of the user." and "2) Verify that the key exists.". >>> It doesn't solve "3) Be nice to people sending many reports" for these >>> persona and actually make the situation a little worse for them; but way >>> nicer for the ones who have their private key in Tails, so maybe that's >>> fine. >> >> Sounds good wrt. scoping and end results. Plus, it addresses my >> concerns about who will maintain that code once it's been written. > I'll update this on the blueprint at some point. I'm glad we reach an > agreement on the engineering side of things. Same! > I still haven't received > feedback from frontdesk since November 30 so it seems like my "clients" > are not really in a hurry. Yay, that's about future plans anyway, and Alan probably has other things to finish before starting this one, so I guess we can take it easy :) _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
