Change Details

Hi @TheDJ, @Enterprisey and @Nakon (tagging you three as you're listed as members of #navigation-popups-gadget ) I'm filing this task to give a heads-up about the work that #trust_and_safety_product_team is doing as part of #fy2024-25_we4.2, to build {T384725}. There's a certain amount of overlap between what navigation popups provides when hovering over user links, and what we intend to build with the UserInfoCard. A couple of differences: - We're building the UserInfoCard into an extension (CheckUser for now, perhaps split to another one later) - We'll be computing most of the data server side with a single API request to fetch data, for performance purposes - We intend to make this tool available to logged-in users by default, with an opt-out option - Our tool requires pressing a button instead of using mouse over, so it can work on mobile/desktop, and so we can understand usage more clearly Our tool won't interfere with how Navigation Popups functions on user pages, but eventually we should figure out what would make sense to move into the UserInfoCard and what to retain in the Gadget. We intend to make the UserInfoCard extensible, so perhaps the code in the Navigation Popups gadget could eventually extend the UserInfoCard to provide additional data / functionality we aren't including in our initial version. Your thoughts and suggestions are very welcome. Thanks!

Hi @TheDJ, @Enterprisey and @Nakon (tagging you three as you're listed as members of #navigation-popups-gadget ) I'm filing this task to give a heads-up about the work that #trust_and_safety_product_team is doing as part of #fy2024-25_we4.2, to build {T384725}. There's a certain amount of overlap between what navigation popups provides when hovering over user links, and what we intend to build with the UserInfoCard. A couple of differences: - We're building the UserInfoCard into an extension (CheckUser for now, perhaps split to another one later). This makes our code discoverable via codesearch, allows us access to testing frameworks and linters, and makes it easier for other extensions to extend the feature. - We'll be computing most of the data server side with a single API request to fetch data, for performance purposes - We intend to make this tool available to logged-in users by default, with an opt-out option - Our tool requires pressing a button instead of using mouse over, so it can work on mobile/desktop, and so we can understand usage more clearly Our tool won't interfere with how Navigation Popups functions on user pages, but eventually we should figure out what would make sense to move into the UserInfoCard and what to retain in the Gadget. We intend to make the UserInfoCard extensible, so perhaps the code in the Navigation Popups gadget could eventually extend the UserInfoCard to provide additional data / functionality we aren't including in our initial version. Your thoughts and suggestions are very welcome. Thanks!

Hi @TheDJ, @Enterprisey and @Nakon (tagging you three as you're listed as members of #navigation-popups-gadget ) I'm filing this task to give a heads-up about the work that #trust_and_safety_product_team is doing as part of #fy2024-25_we4.2, to build {T384725}. There's a certain amount of overlap between what navigation popups provides when hovering over user links, and what we intend to build with the UserInfoCard. A couple of differences: - We're building the UserInfoCard into an extension (CheckUser for now, perhaps split to another one later). This makes our code discoverable via codesearch, allows us access to testing frameworks and linters, and makes it easier for other extensions to extend the feature. - We'll be computing most of the data server side with a single API request to fetch data, for performance purposes - We intend to make this tool available to logged-in users by default, with an opt-out option - Our tool requires pressing a button instead of using mouse over, so it can work on mobile/desktop, and so we can understand usage more clearly Our tool won't interfere with how Navigation Popups functions on user pages, but eventually we should figure out what would make sense to move into the UserInfoCard and what to retain in the Gadget. We intend to make the UserInfoCard extensible, so perhaps the code in the Navigation Popups gadget could eventually extend the UserInfoCard to provide additional data / functionality we aren't including in our initial version. Your thoughts and suggestions are very welcome. Thanks!