Skip to content

RFC: Don't expose ROMs, embargo? #240

Open

Description

@avivace

We already have "metadata-only" entries, but we may want a flag/metadata entry (or an embargo?) to not expose or allow download of the binaries.

This may also overlap with the 'playable' flag.

Activity

  1. transferred this issue fromgbdev/homebrewhubon May 31, 2024
  2. aaaaaa123456789 commented on May 31, 2024

    @aaaaaa123456789
    Member

    What would the purpose of this be?

  3. avivace commented on May 31, 2024

    @avivace
    SponsorMemberAuthor

    What would the purpose of this be?

    E.g.: you are publishing a commercial game, want to prepare it to be digitally preserved with solid metadata but you don't want the binaries to be public/distributed through the Homebrew Hub API yet, so you could upload them, maybe let a single ROM file to be playable (like a demo?) and the rest (e.g. the full ROM file) you can already prepare but set an embargo of 5-10-20 years (when the 'commercial' life of the release is over) so your work is not lost

  4. pinobatch commented on May 31, 2024

    @pinobatch
    Member

    Wouldn't it be already public at https://github.com/gbdev/database/tree/master/entries? We'd need to build some sort of time capsule functionality outside public GitHub for this.

  5. added this to the Schema Draft 5 milestone on Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions