Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| platform_vision_guide [2025/09/21 18:49] – [Example user stories] sarah | platform_vision_guide [2025/10/26 18:02] (current) – [Example user stories] sarah | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| ===== Example user stories ===== | ===== Example user stories ===== | ||
| We can prioritise these to identify core functionality and non-essential functionality (e.g. MoSCoW prioritisation) | We can prioritise these to identify core functionality and non-essential functionality (e.g. MoSCoW prioritisation) | ||
| + | |||
| + | For more detail, see [[Use cases for digital town squares]] | ||
| **In an emergency** | **In an emergency** | ||
| Line 44: | Line 46: | ||
| * | * | ||
| * Needs to be FOSS, standards based, interoperable, | * Needs to be FOSS, standards based, interoperable, | ||
| + | |||
| + | Beyond these, here are several big categories of issues that need to be addressed for successful community-run digital spaces, including: | ||
| + | |||
| + | * Online vs real-world identities: policies and enforcement | ||
| + | * mitigating bots, bad actors | ||
| + | * removing and banning users who behave badly | ||
| + | * allowing anonymity for stigmatised and sensitive topics | ||
| + | * allowing anonymity for illegal topics, people who would want to hide identity from police, whistleblowing? | ||
| + | * meeting U16 social media requirements (legislation and duty of care) | ||
| + | * Ease of signup and sign-on vs security | ||
| + | * reduce usability barriers for platform signup and sign-on | ||
| + | * balance with security: password strength, 2FA, password resets | ||
| + | * requirement to provide validated email address? | ||
| + | * ability to change email? | ||
| + | * Moderating online discussion | ||
| + | * establishing enforceable rules that balance community expectations | ||
| + | * addressing disinformation / misinformation | ||
| + | * encouraging decent behaviour | ||
| + | * recruiting, training, retaining volunteer moderators | ||
| + | * compensating toxicity vs decent behaviour | ||
| + | * Tech skills and capabilities | ||
| + | * What skills and capabilities are needed of our tech ops teams? admins? community moderators? | ||
| + | * minimum viable workforce to run things? (assume e.g. | ||
| + | * Ongoing viability and financial considerations | ||
| + | * potential uptake for Merri-bek residents: ~20% of 180,000 = 36,000 users. | ||
| + | * Ongoing hosting / data centre needs (balancing with contemporary user expectations) | ||
| + | * recruiting, training, retaining volunteer mods, admins and tech support ongoing | ||
| + | * compensation for workers? | ||
| + | * how many mods / admins needed per 1000 users? | ||
| + | * Long-term user engagement and utility | ||
| + | * main factors that would drive uptake (signup?) | ||
| + | * main factors that would drive ongoing use? | ||
| + | * success factors e.g. | ||
| + | * Info & comms platform of choice for Merri-bek non-profit groups; | ||
| + | * Merri-bek residents use as platform of choice for connecting with neighbours (e.g. freecycle / good karma group equivalent; asking for local info or recommendations) | ||
| + | * platform of choice for Merri-bek Council to inform & engage with community | ||
| + | * new Merri-bek arrivals sign up as a way to access community info; | ||
| + | |||