📋 Summary Add support for linking related game images together as matched packaging sets in LaunchBox and the LaunchBox Games Database. ❗ Problem Some games have multiple official box variants within the same region, such as original releases, Greatest Hits, Player’s Choice, or other re-release packaging. When multiple fronts, backs, and spines exist for the same game, LaunchBox may combine images from different variants when displaying box art or generating 3D boxes. For example, an original front cover could be paired with a Player’s Choice spine or back cover. 💡 Proposal Allow images in the Games Database to be grouped into named or numbered sets. Example: Set 1: Original release front, back, and spine Set 2: Player’s Choice front, back, and spine LaunchBox could then use images from the same set when displaying related artwork or building 3D box views. 🧩 Use Cases Keep original release box images together Keep re-release box images together Avoid mismatched front, back, and spine artwork Improve accuracy for 3D box presentation 📦 Benefits More accurate box art matching Better 3D box results Cleaner Games Database organization Improved preservation of different official packaging variants ⚠️ Considerations The database would need a simple way for contributors or moderators to assign images to the correct set without making image submission too complicated.

HanzJWeasel 11 days ago

2

📋 Summary Add Sega Lindbergh as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem The Sega Lindbergh platform has become increasingly relevant to emulation enthusiasts following the release and continued development of the Lindbergh Loader project for Windows. Currently: Users must manually create the platform in LaunchBox Games are typically categorized under the generic Arcade platform Metadata and media management is less organized than dedicated arcade hardware platforms There is no standard platform entry for users to contribute to or scrape against As support and compatibility improve, more users are beginning to add Sega Lindbergh titles to their collections. 💡 Proposal Add Sega Lindbergh as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization across user collections Easier contribution and moderation of Lindbergh titles Where appropriate, existing Lindbergh games currently categorized under Arcade could be reviewed and reassigned to the Sega Lindbergh platform. 📦 Benefits Improves organization of modern arcade hardware platforms Provides consistency across LaunchBox collections Makes media and metadata management easier Reduces reliance on generic Arcade categorization Supports the growing interest in Sega Lindbergh emulation ⚠️ Considerations Existing Arcade entries may need review to determine whether they should remain under Arcade or move to Sega Lindbergh Platform naming should align with existing LaunchBox platform standards Platform icons, clear logos, and metadata would need to be added to support the new platform

stonev about 1 month ago

2

📋 Summary Add a dedicated Base Game (or Hack Of) field to the LaunchBox Games Database that allows ROM hacks to be linked directly to the original game they are based on. ❗ Problem The LaunchBox Games Database contains an increasing number of ROM hacks, fan modifications, translations, and enhancement projects. However, there is currently no structured way to identify which original game a hack is based on. As a result: Users may not know what game a hack requires It can be difficult to understand the context of a ROM hack ROM hacks cannot easily be grouped by their source game Database relationships between original games and their derivatives are lost For example, a user browsing ROM hacks may not immediately know whether a particular hack is based on: Super Mario World Pokémon FireRed The Legend of Zelda: A Link to the Past without manually researching it. 💡 Proposal Add a new database field: Base Game Or Hack Of This field would: Link directly to another Games Database entry Identify the original game the hack is based on Be available through scraping and metadata downloads Support filtering, grouping, and playlist creation Potential future enhancements could include: Viewing all hacks associated with a specific game Displaying related hacks on a game's database page Creating dynamic playlists such as: "All Super Mario World Hacks" "All Pokémon FireRed Hacks" 🧩 Use Cases A user wants to see all ROM hacks based on a particular game A user discovers a hack and wants to know the original title it requires Collections can be organized around popular hack communities Theme developers can surface related hacks alongside the original game Database contributors can establish clearer relationships between entries 📦 Benefits Improves ROM hack discoverability and organization Creates meaningful relationships between database entries Helps users understand hack dependencies and origins Enables smarter filtering, searching, and playlist generation Lays the foundation for richer metadata relationships in the future ⚠️ Considerations Should support linking to an existing Games Database entry rather than using free text Some hacks may be based on multiple source games or projects Similar relationship systems could potentially be expanded later for: Fan translations Remakes Ports Total conversions Homebrew derivatives

TheNewClassics about 1 month ago

2

📋 Summary Add support for series/franchise metadata within the LaunchBox Games Database, allowing games to be associated with one or more series that can be synced directly into LaunchBox. ❗ Problem Currently, the Series field in LaunchBox is entirely user managed and is not populated from the Games Database. As a result: Users must manually assign series information Series organization is inconsistent between collections Large libraries require significant manual maintenance Users cannot benefit from community curated franchise information However, series classification is often subjective and can vary depending on the user's goals. For example: A user may want: Mario Another user may prefer: Mario Kart Mario Party Mario Sports Others may want both simultaneously There is no universally accepted hierarchy for many franchises. 💡 Proposal Add series support to the Games Database while accommodating different levels of franchise organization. Potential approaches could include: Option A: Multi-Level Series Structure Games can belong to: Primary Series Sub Series Examples: Super Mario Kart Primary Series: Mario Sub Series: Mario Kart Mario Party 3 Primary Series: Mario Sub Series: Mario Party Option B: Multiple Series Assignments Games can have multiple series tags: Mario Mario Kart This provides flexibility while allowing users to filter or group based on either level. Option C: Series Taxonomy System A more advanced hierarchy where: Mario Mario Kart Mario Party Mario Sports Paper Mario can coexist within a parent-child structure. 🧩 Use Cases Users automatically receive franchise information when scraping metadata Collections can be grouped by franchise without manual work Smart playlists can be built around series data Users can browse all entries in a franchise across platforms Big Box themes can surface franchise collections more effectively 📦 Benefits Reduces manual metadata management Creates more consistency across collections Enables richer filtering, searching, and playlist creation Supports franchise based browsing and discovery Opens the door for future series focused features throughout LaunchBox ⚠️ Considerations Series definitions can be subjective and sometimes controversial A simple single value field may not be sufficient for complex franchises The database should support both broad and granular franchise groupings Clear moderation guidelines would be needed to ensure consistency

lappen about 2 months ago

1

Java ME / Java Phone Games is currently missing from the LaunchBox Games Database and would be a valuable addition as a dedicated platform. Before Android and iOS became dominant, Java ME was one of the most important mobile gaming platforms of the 2000s. Many phones supported Java-based games, and the platform had a large library of commercial releases, licensed titles, ports, and original mobile games. Examples include: God of War: Betrayal Doom RPG Wolfenstein RPG Bounce Tales Gameloft titles EA Mobile titles Gangstar series Currently, users may be forced to place these games under Android, Apple iOS, or other fallback platforms, which does not accurately represent the original platform or era. Adding Java ME / Java Phone Games as its own platform would allow: Dedicated platform metadata More accurate organization of mobile game history Proper contribution of Java phone game entries Separate media and metadata from Android and iOS titles Better preservation of early mobile gaming libraries This platform represents a significant part of mobile gaming history and deserves its own dedicated entry in the LaunchBox Games Database.

Drodrick about 2 months ago

2

📋 Summary Add dedicated Play Mode metadata to the LaunchBox Games Database so games can be categorized by how multiplayer actually works. ❗ Problem LaunchBox can display Play Mode locally, but the Games Database does not appear to store detailed Play Mode values for regular game entries. Instead, Play Mode is generally inferred from broader metadata such as whether a game is cooperative or how many players it supports. This makes it difficult to accurately track and search for specific multiplayer types, such as: 3-player simultaneous 4-player simultaneous 2-player alternating Competitive player-versus-player Cooperative multiplayer 💡 Proposal Add Play Mode as a proper editable metadata field in the LaunchBox Games Database. Supported values could include: Single player 2-player simultaneous 3-player simultaneous 4-player simultaneous 2-player alternating 4-player alternating Cooperative Player versus player These values should be available for database contributors to submit, edit, and correct. 🧩 Use Cases Find all 4-player simultaneous games on a platform Separate co-op games from competitive multiplayer games Improve metadata for platforms where multiplayer details are currently vague Let contributors correct missing or incomplete multiplayer information 📦 Benefits More accurate multiplayer metadata Better filtering and playlist creation More useful Games Database search results Improved community data over time ⚠️ Considerations Play Mode values should have clear definitions so contributors apply them consistently. Broad values like “Multiplayer” may still be useful when exact behavior is unknown.

Rinuschh about 2 months ago

2

📋 Summary Add an option for LaunchBox to query the online Games Database directly when scraping metadata, instead of always downloading a local copy of the database first. ❗ Problem LaunchBox currently downloads a local copy of the Games Database before scanning for metadata. This has useful benefits, especially for offline setups, but it also creates friction for users who are always online: Users are prompted to download a fresh database copy regularly Metadata scans are delayed while the database file downloads New or recently updated database entries are not available until the local copy is refreshed The workflow can feel unnecessary on machines with constant internet access For some users, especially those regularly importing or updating games, waiting 20–30 seconds each time adds up. 💡 Proposal Add a metadata lookup option that allows LaunchBox to query the online Games Database directly. Possible options: Use Online Games Database Lookup Query the live database during scraping Always access the latest metadata and updates Use Local Games Database File Keep the existing offline-friendly workflow Continue supporting arcade cabinets and offline builds This could be exposed as a preference, allowing users to choose the workflow that best fits their setup. 🧩 Use Cases A user with an always-online PC wants faster metadata scans without downloading the database first A contributor adds or updates a game and wants those changes available immediately An arcade cabinet user keeps the current offline local database workflow Users choose between speed, freshness, and offline reliability based on their setup 📦 Benefits Reduces friction during metadata scans Makes new database updates available immediately Preserves existing offline workflows Gives users more control over how LaunchBox interacts with the Games Database Improves day-to-day usability for online systems ⚠️ Considerations Online lookup should gracefully handle connection failures Local database mode should remain available for offline users Caching could still be used to reduce repeated requests Server load and API performance would need to be considered

AstroBob about 2 months ago

I recently came across this system whilst browsing some old catalogs and decided to add it to my LB collection. The console was produced by Memorex and distributed in collaboration with Tandy in the early 90’s. It took me a couple of weeks but I managed to locate covers, snaps and other media items for all the released software (about 50 CD’s). The system was similar in concept to the Philips CDi and 3D0 in that it was mainly educational/informational multimedia but had a few games. The VIS stands for “Video Information System”. I am using MAME as the emulator and it runs the software flawlessly. So I would like to share all of this unique and now complete collection with the LB community but am unsure how to do this. If one of the devs creates a new entry in the database I will happily upload all items and metadata to the new entry.

k1w1b1rd 2 months ago

📋 Summary Allow users to reset or clear their cloud synced game statistics, giving them control to resolve sync issues or start fresh. ❗ Problem The current cloud stats system has no way to reset server data: Cloud stats can overwrite newer local progress when re-enabling sync No option to clear or reset cloud stored values Users can become stuck with incorrect or outdated data Only workaround is to manually fix values or abandon sync This creates frustration, especially when sync behaviour is unclear or incorrect. 💡 Proposal Introduce a cloud stats reset option: Allow users to: Clear all cloud stored game stats Optionally reset stats for individual games Provide this option within: LaunchBox settings Or user account / cloud settings Include confirmation prompts to prevent accidental data loss Optionally allow: “Reset and use local data” on next sync 🧩 Use Cases A user wants to fix incorrect cloud synced playtime A user switches devices and wants a clean sync state Sync issues cause mismatched or duplicated stats A user prefers to restart tracking from scratch 📦 Benefits Gives users control over their cloud data Resolves sync conflicts and inconsistencies Reduces support requests around stats syncing Improves trust in the cloud sync system ⚠️ Considerations Must clearly communicate that data will be permanently deleted Should include safeguards to prevent accidental resets May need to consider partial vs full reset options ✅ Outcome Providing a way to reset cloud stats gives users a reliable escape hatch for sync issues, improving confidence and usability of the system.

AstroBob 3 months ago

📋 Summary Allow users to request or suggest new platforms directly during the submission process when an appropriate platform does not already exist. ❗ Problem Contributors currently face friction when submitting content for unsupported platforms: No way to request a new platform during submission Submissions are rejected due to missing platform support Contributors are unsure where to submit edge case content Platform requests require separate forum posts or workflows This creates confusion and discourages contributions, especially for niche or emerging systems. 💡 Proposal Integrate platform requests directly into the submission flow: When selecting a platform: Provide an option like “Request New Platform” Allow users to submit: Platform name Basic description or context Queue platform requests for review Notify users when the platform is approved and available Optionally allow users to continue their submission once the platform is created 🧩 Use Cases A user submits content for a niche handheld or emulator based system A contributor encounters a missing platform and requests it immediately Platform requests are tied directly to real submission needs Users avoid needing to leave the flow to post on forums 📦 Benefits Reduces friction in the submission process Encourages contributions for new and niche platforms Streamlines platform request workflow Improves overall database coverage ⚠️ Considerations Requires moderation or approval workflow for new platforms Should prevent duplicate or low quality platform requests Platform creation may still need validation before being added ✅ Outcome Allowing platform requests during submission creates a smoother, more intuitive workflow, helping expand database coverage while reducing contributor friction.

AstroBob 3 months ago

📋 Summary Introduce automatic and assisted duplicate detection for media to reduce redundant uploads and improve database cleanliness. ❗ Problem Duplicate media is a recurring issue: Identical or near identical images are uploaded multiple times Duplicate entries clutter media categories Moderators must manually identify and resolve duplicates Users may download redundant or unnecessary assets This leads to inefficiency and reduced data quality. 💡 Proposal Implement duplicate detection systems: Detect duplicates during upload using: File hashing Image similarity checks Prompt users when a potential duplicate is found Allow moderators to: Flag and merge duplicates Easily remove redundant entries Optionally suggest replacing lower quality images with higher quality versions 🧩 Use Cases A user is warned before uploading an identical image A higher quality version replaces an existing lower quality image Moderators quickly resolve duplicate submissions Media categories remain clean and organized 📦 Benefits Reduces clutter and redundancy Saves moderation time Improves overall media quality Creates a cleaner and more efficient database ⚠️ Considerations Needs tolerance for small differences between images Should avoid blocking legitimate variations UI should clearly explain duplicate warnings ✅ Outcome Duplicate detection improves data quality and efficiency, reducing clutter while making moderation and uploads more streamlined.

AstroBob 3 months ago

📋 Summary Allow users to save incomplete submissions and return to them later, rather than requiring everything to be submitted in a single session. ❗ Problem The current submission flow requires users to complete everything at once: Large or complex submissions take significant time Contributors may lose progress if they leave or refresh No way to gradually build high quality submissions Discourages contributions for more detailed or niche entries This creates friction and reduces contribution quality. 💡 Proposal Introduce draft support for submissions: Allow users to: Save submissions as drafts Return and edit later Support drafts for: Game entries Media uploads Metadata edits Provide a simple “My Drafts” section for management Allow users to submit once ready 🧩 Use Cases A contributor gathers metadata over multiple sessions A user uploads media gradually instead of all at once A detailed submission is refined before being submitted Contributors avoid losing progress due to interruptions 📦 Benefits Encourages higher quality submissions Reduces frustration and lost work Supports more complex contributions Improves overall contributor experience ⚠️ Considerations Draft storage and cleanup policies may be needed UI should clearly distinguish drafts from submitted items Should remain simple and lightweight ✅ Outcome Draft support allows contributors to work more flexibly, leading to better quality submissions and a smoother contribution experience.

AstroBob 3 months ago

📋 Summary Require moderators to provide structured, standardized feedback when rejecting submissions to improve clarity and consistency. ❗ Problem Rejection feedback is currently inconsistent: Some rejections include little or no explanation Feedback varies widely in quality and detail Contributors struggle to understand what went wrong Repeated mistakes occur due to lack of clear guidance This leads to frustration and unnecessary resubmissions. 💡 Proposal Introduce structured feedback requirements for rejections: Require moderators to select a reason when rejecting: Incorrect category Incorrect region Duplicate Low quality Other (with optional note) Allow optional additional comments for more context Standardize feedback format across all rejections Surface this feedback clearly to submitters 🧩 Use Cases A contributor quickly understands why their image was rejected Common mistakes are reduced through consistent feedback Moderators spend less time writing repetitive explanations Submissions improve in quality over time 📦 Benefits Improves clarity and transparency Reduces repeated errors and resubmissions Creates a more consistent moderation process Helps educate contributors over time ⚠️ Considerations Should not overly slow down moderation workflow Predefined options must be clear and comprehensive Additional comments should remain optional ✅ Outcome Structured feedback ensures contributors receive clear, actionable guidance, improving both submission quality and overall database consistency.

AstroBob 3 months ago

📋 Summary Establish clear standards and system improvements for region tagging to ensure consistent usage and predictable media downloads. ❗ Problem Region tagging is currently inconsistent and often misused: Media is incorrectly tagged as “World” instead of a specific region Duplicate images are uploaded for identical assets across regions Contributors apply personal preferences rather than consistent rules Users receive unpredictable downloads when using region priorities Ongoing moderation conflicts around what constitutes the “correct” region This creates confusion and reduces the reliability of the database. 💡 Proposal Improve region tagging through a combination of standards and system support: Define clear guidelines for region usage: When to use specific regions vs “World” How to handle identical assets across regions Introduce validation or prompts during submission: Flag potential duplicate region uploads Suggest merging into a single “World” entry where appropriate Provide clearer visibility of region usage during moderation Ensure consistent handling of region priorities in media downloads 🧩 Use Cases Identical logos for NA and EU are tagged once as “World” Region specific box art is clearly differentiated and tagged correctly Contributors follow consistent rules instead of personal preference Users can reliably control downloads based on region priorities 📦 Benefits Improves consistency across the database Reduces duplicate or redundant media Minimizes moderation conflicts Creates predictable and reliable media downloads ⚠️ Considerations Needs clear and agreed upon definitions Must balance flexibility with standardization Should integrate with future tagging system ✅ Outcome Standardized region tagging improves consistency and predictability, making the database more reliable for both contributors and users.

AstroBob 3 months ago

1

📋 Summary Introduce tools that allow moderators to communicate, discuss, and collaborate on submissions directly within the Games Database. ❗ Problem Moderation is currently isolated and lacks collaboration: No way for moderators to discuss unclear or controversial submissions Decisions are made independently, often leading to conflicts Repeated “edit wars” occur without resolution No shared space to ask questions or get second opinions This leads to inconsistency and frustration among moderators. 💡 Proposal Introduce lightweight collaboration tools for moderators: Add a discussion or comment thread on submissions Allow moderators to: Ask questions Provide reasoning Flag uncertainty Optional “needs discussion” or “review required” state Keep discussions structured and tied to specific submissions 🧩 Use Cases A moderator is unsure how to classify media and asks for input Conflicting votes are resolved through discussion instead of repetition Moderators share knowledge on edge cases or unclear rules Complex submissions receive more consistent decisions 📦 Benefits Reduces moderation conflicts and inconsistencies Encourages knowledge sharing among moderators Improves quality of decisions Reduces repeated submission cycles ⚠️ Considerations Should remain lightweight, not a full forum replacement Discussions should be easy to follow and not overly noisy May need moderation to prevent misuse ✅ Outcome Moderator collaboration tools create a more consistent and informed moderation process, reducing conflict while improving overall database quality.

AstroBob 3 months ago

📋 Summary Introduce versioning and change history for media entries, allowing moderators and contributors to track, review, and revert changes to assets over time. ❗ Problem Media changes are currently difficult to track: Images are frequently deleted and reuploaded No visibility into who changed what and why Ongoing “edit wars” between contributors and moderators Lost assets can be difficult or impossible to recover Moderation decisions lack historical context This leads to frustration and instability in the database. 💡 Proposal Add versioning and history tracking for media: Track all changes to media entries: Uploads Deletions Edits (type, region, etc) Provide a visible change history log per asset Allow moderators to: View previous versions Restore or revert changes Optionally show reason for change where applicable 🧩 Use Cases A deleted image can be restored without needing reupload Moderators review past changes before making decisions Repeated disputes over the same asset are easier to resolve Contributors understand why an image was changed or removed 📦 Benefits Reduces moderation conflicts and repeated work Prevents loss of valuable media Increases transparency and accountability Improves overall stability of the database ⚠️ Considerations Storage implications for version history UI needs to remain simple and readable Access to revert functionality may need restrictions ✅ Outcome Media versioning provides transparency and control, reducing conflicts while protecting valuable contributions within the database.

AstroBob 3 months ago

1

📋 Summary Introduce curated “default” media sets for platforms that can be optionally locked or prioritized, ensuring users always have access to a consistent, high quality baseline of assets. ❗ Problem Media quality and consistency can vary significantly: Official categories are often mixed with fanart or inconsistent assets High quality community sets exist but are not standardized in the database Media can be repeatedly changed, moved, or overwritten Users may end up with incomplete or inconsistent downloads This creates an unpredictable experience when scraping media. 💡 Proposal Introduce curated default media sets: Define a “default” set of high quality assets per platform: Box art, carts, logos, etc Allow these sets to be: Prioritized in downloads Optionally locked to prevent frequent changes Credit contributors where applicable Allow users to choose between: Default curated sets Full database (including fanart and alternatives) 🧩 Use Cases A user wants a clean, consistent SNES library with minimal setup A contributor’s high quality set becomes the default baseline A user avoids downloading inconsistent or low quality media Moderation disputes are reduced for “baseline” assets 📦 Benefits Improves consistency and quality for all users Reduces clutter and unpredictability in downloads Highlights high quality community contributions Provides a better out of the box experience ⚠️ Considerations Requires clear criteria for what qualifies as a default set Needs moderation or admin oversight Should not restrict user customization ✅ Outcome Curated default media sets provide a reliable foundation for users, improving consistency while still allowing flexibility for customization.

AstroBob 3 months ago

📋 Summary Create a fully updated, centralized set of moderation and submission guidelines hosted on the LaunchBox Help Center, replacing outdated and fragmented documentation. ❗ Problem Current moderation guidelines are: Outdated and scattered across old forum posts Difficult to find and not centrally maintained Inconsistent or unclear on key topics Not aligned with how the database is used today This leads to: Conflicting moderation decisions Ongoing disputes around naming, regions, and media types Confusion for new contributors Reduced trust and consistency in the database 💡 Proposal Rebuild the moderation and submission guidelines as a dedicated Help Center resource: Create a centralized, easy to navigate documentation hub Clearly define standards for: Naming conventions (games, developers, publishers) Region tagging Media classification and usage When to accept, reject, or modify submissions Include real examples and edge cases where relevant Keep documentation versioned and regularly updated Link directly to these guidelines from the Games Database interface 🧩 Use Cases A new contributor quickly understands how to submit media correctly A moderator references clear rules when reviewing a submission Disputes are reduced because expectations are clearly defined Contributors feel more confident their submissions will be handled fairly 📦 Benefits Improves consistency and quality across the database Reduces moderation conflicts and ambiguity Lowers the barrier to entry for new contributors Builds trust within the community Creates a scalable foundation for future improvements ⚠️ Considerations Guidelines should remain clear and concise, not overly complex Should evolve alongside features like tagging and new media types Requires ongoing ownership to keep documentation up to date ✅ Outcome A modern, centralized Help Center for moderation guidelines creates a shared standard for contributors and moderators, improving consistency, clarity, and overall database quality.

AstroBob 3 months ago

1

📋 Summary Introduce a standardized system for developer and publisher naming, including optional parent company linking to group variations under a single entity. ❗ Problem Developer and publisher names are currently inconsistent across the database: Multiple variations exist for the same company, for example: Capcom, Capcom Ltd, Capcom Co., Ltd. No clear standard for naming conventions Difficult to filter, search, or group games accurately Moderators often conflict on what the “correct” name should be This leads to fragmented data and poor discoverability. 💡 Proposal Introduce a structured system for developer and publisher entities: Define a standardized “primary name” for each company Allow aliases or variations to map to that primary name Introduce optional parent company relationships: For example, subsidiaries grouped under a parent entity Apply consistent naming rules across the database Provide guidance within moderation tools for naming decisions 🧩 Use Cases All variations of “Capcom” are grouped under a single canonical entry Users can filter games by a developer without missing entries due to naming differences Subsidiaries can optionally roll up under a parent company Moderators no longer debate minor naming differences 📦 Benefits Improves search, filtering, and organization Reduces duplicate or fragmented entries Creates consistency across the database Simplifies moderation decisions ⚠️ Considerations Defining parent relationships can become complex Clear boundaries are needed to avoid overcomplication Migration of existing data will require careful handling ✅ Outcome A standardized naming system improves data integrity and usability, making the database more reliable and easier to navigate.

AstroBob 3 months ago

2

📋 Summary Introduce a lightweight appeals system that allows submitters to respond to rejection feedback and provide additional context before a final decision is made. ❗ Problem Currently, there is no way for submitters to respond to feedback on their submissions: Rejection feedback is one-directional Submitters cannot clarify intent or provide additional context Misunderstandings often result in unnecessary rejections Contributors feel disconnected from the moderation process This can lead to frustration and reduced contribution quality over time. 💡 Proposal Add a simple appeals and feedback loop to the submission system: Allow submitters to respond to rejection feedback Provide an “Appeal” or “Add Context” option on submissions Surface this response to moderators during review Keep interactions structured and limited to avoid abuse 🧩 Use Cases A contributor explains why an image was categorized a certain way A submitter provides a source or reference that validates their submission A misunderstanding is resolved without needing resubmission Moderators can make more informed decisions with added context 📦 Benefits Improves communication between contributors and moderators Reduces unnecessary rejections and resubmissions Encourages higher quality contributions Builds trust and transparency in the moderation process ⚠️ Considerations Appeals should be limited to avoid spam or misuse Moderators should not be required to engage in long discussions A simple, structured format is preferred over open-ended threads ✅ Outcome A lightweight appeals system creates a more collaborative moderation process, improving submission quality while reducing frustration for contributors.

AstroBob 3 months ago