Skip to content

Winners


 

‐ this giveaway is over ‐

Congratulations to this lucky humans.

Winners

  • 1

    @cahlus_1

    02/15/2019
    • Contacted
    • Preparing
    • Shipped
    • Delivered
    • Completed
    completed:
    This winner has posted proof on social media that the prize was successfully delivered. Check out the view proof link below.
  • 2

    @Juzaan_

    02/15/2019
    • Contacted
    • Preparing
    • Shipped
    • Delivered
    • Completed
    received:
    undefined
  • 3

    @Rob3rtJaqu3z

    02/15/2019
    • Contacted
    • Preparing
    • Shipped
    • Delivered
    • Completed
    received:
    undefined
  • 4

    @alvaro_TR7

    02/15/2019
    • Contacted
    • Preparing
    • Shipped
    • Delivered
    • Completed
    completed:
    This winner has posted proof on social media that the prize was successfully delivered. Check out the view proof link below.
  • 5

    @christian_femia

    02/15/2019
    • Contacted
    • Preparing
    • Shipped
    • Delivered
    • Completed
    completed:
    This winner has posted proof on social media that the prize was successfully delivered. Check out the view proof link below.

Frequently Asked Question

  • Five (5) Audio-Technica ATH-M50xBT headphones, with dbrand skins of your choice.

  • Simple - it was a three-step process.

    1. Subscribe to PewDiePie.

    2. Reply to our tweet with a screengrab, showing that you've subscribed.

    3. Retweet.

  • They were randomly selected from the list of users who retweeted and replied with a screengrab as instructed. Click here for more details.

  • We used a custom Python script which was specifically programmed for this giveaway. It used the Twitter Public Rest API to download a list of all @dbrand tweet replies.

    Once the full list was loaded, the script generated a list of IDs. From this pool of unique account IDs, a random entry was picked using a randomly generated seed based on the NumPy project. This random pick was the resulting winner.

    For every subsequent winner selection, the script executed again. This triggered the Twitter Public Rest API to fetch again. The script downloaded the newest replies and kept going until it reached the replies which were downloaded during the previous run. What this did was save us from having to download a full list of replies every time a winner was selected \u2013 while also ensuring that everyone was included and had an equal chance of winning for each random draw.

  • The winners were tagged in this tweet. They were also notified via Twitter direct message (DM) with further instructions on claiming their prizes.

  • Absolutely not. Everything was full paid for by dbrand.

  • 01001111 01100110 00100000 01100011 01101111 01110101 01110010 01110011 01100101 00101110