46 lines
2.7 KiB
Plaintext
46 lines
2.7 KiB
Plaintext
---
|
|
title: Revisions and Response
|
|
author: Carl Colglazier
|
|
---
|
|
|
|
**Provide background for the recommendation system**
|
|
|
|
> - Identify key examples of the kinds of systems/features the one you have proposed/created aligns with.
|
|
>
|
|
> - Situate your approach in relation to key prior work that motivates the approach you pursue
|
|
|
|
I added two sections to the background section of the text which describe recommender systems/collaborative filtering and trade-offs in different methods of evaluation. This system connects with prior work from HCI researchers, e.g. in the GroupLens lab, to build discovery and recommender systems.
|
|
|
|
**Elaborate the design rationale for the system in the text.**
|
|
|
|
> - Why recommend small/specific servers?
|
|
>
|
|
> - What key related work justifies the approach you pursue to designing the system in the way you do?
|
|
|
|
In addition to the previous survivor models, I added a logistic regression model based on a continuous measure of server "generality" to support the decision to steer newcomers toward more topic-based and smaller servers. Future work can look at specific users to see if engagement with hashtags and local timelines is indicative of better retention.
|
|
|
|
I added more information to the...
|
|
|
|
**Spell out some "user stories"/examples and use these to illuminate system performance/constraints**
|
|
|
|
> + Elaborate the hci.social example in the text
|
|
>
|
|
> + Identify some hypothetical users/interests and explore system outputs/performance for each
|
|
>
|
|
> + Identify/elaborate some of the tradeoffs/constraints (e.g., emacs + gardening; privacy/trust/safety of tags; need for opt-in)
|
|
|
|
I added a description of what the hci.social example illustrates (clusters of servers with related topics of focus). In the [appendix](https://files.carl.cx/junior-sheer/#user-stories), I listed a few starter "user stories" and descried their performance. I have elaborated further about tradeoffs and design choices in the "Constraints and Evaluation" subsection.
|
|
|
|
## Address system evaluation more directly in the paper
|
|
|
|
> - Explain, justify, and interpret the evaluation that is present in the paper
|
|
>
|
|
> - Elaborate/justify additional system evaluation plans (e.g., usability; robustness to dropping servers/tags; balancing tradeoffs; navigating privacy/trust/safety concerns)
|
|
|
|
I have added more background information on evaluation and added fruther explainations for the current evaluation within the paper as well as plan for future work and improvments in this area.
|
|
|
|
## Clearly identify the research/design contributions of this system
|
|
|
|
> - Both at present and assuming your proposed development plans move forward
|
|
|
|
I have added more information to the discussion section to clearly identify the research and design contributions of this system. |