{
  "id": 207899,
  "title": "Competition Update",
  "url": "/competitions/cassava-leaf-disease-classification/discussion/207899",
  "author_name": "",
  "post_date": "2020-12-31T20:32:11.444018800Z",
  "votes": 26,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Hello Kagglers,</p>\n<p>As you may be aware, a recently disclosed vulnerability allowed teams to view their own private leaderboard score prior to the deadline. We have released a statement describing the bug at <a href=\"https://www.kaggle.com/private-leaderboard-bug-dec-2020\" target=\"_blank\">https://www.kaggle.com/private-leaderboard-bug-dec-2020</a>.</p>\n<p>Since the vulnerability was publicly disclosed for approximately five hours, a small number of teams accessed their team’s private score. Because this competition still has ~2 months left, we are leaving it as-is. With ample time left to improve on existing scores, we do not believe the bug materially impacts the course of competition and its final outcomes. </p>\n<p>Thank you for your participation, and best of luck in this competition!</p>",
  "messages": [
    {
      "id": "1134099",
      "postDate": "12/31/2020 20:32:11",
      "content": "<p>Hello Kagglers,</p>\n<p>As you may be aware, a recently disclosed vulnerability allowed teams to view their own private leaderboard score prior to the deadline. We have released a statement describing the bug at <a href=\"https://www.kaggle.com/private-leaderboard-bug-dec-2020\" target=\"_blank\">https://www.kaggle.com/private-leaderboard-bug-dec-2020</a>.</p>\n<p>Since the vulnerability was publicly disclosed for approximately five hours, a small number of teams accessed their team’s private score. Because this competition still has ~2 months left, we are leaving it as-is. With ample time left to improve on existing scores, we do not believe the bug materially impacts the course of competition and its final outcomes. </p>\n<p>Thank you for your participation, and best of luck in this competition!</p>",
      "rawMarkdown": "Hello Kagglers,\n\nAs you may be aware, a recently disclosed vulnerability allowed teams to view their own private leaderboard score prior to the deadline. We have released a statement describing the bug at https://www.kaggle.com/private-leaderboard-bug-dec-2020.\n\nSince the vulnerability was publicly disclosed for approximately five hours, a small number of teams accessed their team’s private score. Because this competition still has ~2 months left, we are leaving it as-is. With ample time left to improve on existing scores, we do not believe the bug materially impacts the course of competition and its final outcomes. \n\nThank you for your participation, and best of luck in this competition!",
      "votes": null
    },
    {
      "id": "1134852",
      "postDate": "01/01/2021 16:29:45",
      "content": "<p>Thanks for the update <a href=\"https://www.kaggle.com/juliaelliott\" target=\"_blank\">@juliaelliott</a> .Taking into account the time left for this competition, this seems to be the right decision. However, competitors which got time to see different private leaderboard scores for their submissions, are having a little edge, knowing what worked and what not directly from the private set.</p>",
      "rawMarkdown": "Thanks for the update @juliaelliott .Taking into account the time left for this competition, this seems to be the right decision. However, competitors which got time to see different private leaderboard scores for their submissions, are having a little edge, knowing what worked and what not directly from the private set.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1134852,
      "author_name": "vladvdv",
      "author_url": "",
      "post_date": "01/01/2021 16:29:45",
      "content": "<p>Thanks for the update <a href=\"https://www.kaggle.com/juliaelliott\" target=\"_blank\">@juliaelliott</a> .Taking into account the time left for this competition, this seems to be the right decision. However, competitors which got time to see different private leaderboard scores for their submissions, are having a little edge, knowing what worked and what not directly from the private set.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1134099": "Hello Kagglers,\n\nAs you may be aware, a recently disclosed vulnerability allowed teams to view their own private leaderboard score prior to the deadline. We have released a statement describing the bug at https://www.kaggle.com/private-leaderboard-bug-dec-2020.\n\nSince the vulnerability was publicly disclosed for approximately five hours, a small number of teams accessed their team’s private score. Because this competition still has ~2 months left, we are leaving it as-is. With ample time left to improve on existing scores, we do not believe the bug materially impacts the course of competition and its final outcomes. \n\nThank you for your participation, and best of luck in this competition!",
    "1134852": "Thanks for the update @juliaelliott .Taking into account the time left for this competition, this seems to be the right decision. However, competitors which got time to see different private leaderboard scores for their submissions, are having a little edge, knowing what worked and what not directly from the private set."
  },
  "source": "meta"
}