Botting be like
Botting be like
The rectangle was placed by piXelBow@toast.ooo, with the pixel times sometimes matching to the millisecond.
What's the QR code? Dominion?
yeah thats the only big QR code around. whoever is doing the botting, does not like vegans.
Do you have a template for that QR-Code? Also did you tell @grant@toast.ooo about this? They are able to block the person and also revert the pixels. (Even though they might be busy rn)
And here I am trying to manually spell my url concisely.
Just saw this
during the time this was posted there was a bug that allowed for pixels to be stacked up very high and also the canvas wasn't properly syncing
if you do notice anyone else doing botting send a message about it on Matrix or Discord
took a peek at their previous pixels and the more recent ones don't look suspicious as well
The user's whole history is extremely suspicious and composed of actions like that. Here is just one random example from two days after the alleged botting took place:
Line 617339: 2024-07-15T18:26:26.209Z piXelBow@toast.ooo pixel_place 606 54 FFFFFF Line 617340: 2024-07-15T18:26:26.210Z piXelBow@toast.ooo pixel_place 606 55 FFFFFF Line 617341: 2024-07-15T18:26:26.211Z piXelBow@toast.ooo pixel_place 606 56 FFFFFF Line 617342: 2024-07-15T18:26:26.211Z piXelBow@toast.ooo pixel_place 607 50 FFFFFF Line 617343: 2024-07-15T18:26:26.212Z piXelBow@toast.ooo pixel_place 607 51 FFFFFF Line 617344: 2024-07-15T18:26:26.216Z piXelBow@toast.ooo pixel_place 606 50 FFFFFF Line 617345: 2024-07-15T18:26:26.359Z piXelBow@toast.ooo pixel_place 605 56 FFFFFF Line 617346: 2024-07-15T18:26:26.363Z piXelBow@toast.ooo pixel_place 607 54 FFFFFF Line 617347: 2024-07-15T18:26:26.642Z piXelBow@toast.ooo pixel_place 607 55 FFFFFF Line 617348: 2024-07-15T18:26:26.643Z piXelBow@toast.ooo pixel_place 607 56 FFFFFF Line 617349: 2024-07-15T18:26:26.643Z piXelBow@toast.ooo pixel_place 608 51 FFFFFF Line 617350: 2024-07-15T18:26:26.644Z piXelBow@toast.ooo pixel_place 608 52 FFFFFF Line 617351: 2024-07-15T18:26:26.644Z piXelBow@toast.ooo pixel_place 608 55 FFFFFF Line 617352: 2024-07-15T18:26:26.645Z piXelBow@toast.ooo pixel_place 608 56 FFFFFF Line 617353: 2024-07-15T18:26:26.645Z piXelBow@toast.ooo pixel_place 609 51 FFFFFF Line 617354: 2024-07-15T18:26:26.646Z piXelBow@toast.ooo pixel_place 609 54 FFFFFF Line 617355: 2024-07-15T18:26:26.646Z piXelBow@toast.ooo pixel_place 609 55 FFFFFF Line 617356: 2024-07-15T18:26:26.647Z piXelBow@toast.ooo pixel_place 609 56 FFFFFF Line 617357: 2024-07-15T18:26:26.647Z piXelBow@toast.ooo pixel_place 610 50 FFFFFF Line 617358: 2024-07-15T18:26:26.647Z piXelBow@toast.ooo pixel_place 610 53 FFFFFF Line 617359: 2024-07-15T18:26:26.648Z piXelBow@toast.ooo pixel_place 610 54 FFFFFF Line 617360: 2024-07-15T18:26:26.648Z piXelBow@toast.ooo pixel_place 610 55 FFFFFF Line 617361: 2024-07-15T18:26:26.649Z piXelBow@toast.ooo pixel_place 610 56 FFFFFF Line 617362: 2024-07-15T18:26:26.649Z piXelBow@toast.ooo pixel_place 611 49 FFFFFF Line 617363: 2024-07-15T18:26:26.650Z piXelBow@toast.ooo pixel_place 611 55 FFFFFF Line 617364: 2024-07-15T18:26:26.650Z piXelBow@toast.ooo pixel_place 611 56 FFFFFF Line 617365: 2024-07-15T18:26:26.651Z piXelBow@toast.ooo pixel_place 612 49 FFFFFF Line 617366: 2024-07-15T18:26:26.651Z piXelBow@toast.ooo pixel_place 612 50 FFFFFF Line 617367: 2024-07-15T18:26:26.651Z piXelBow@toast.ooo pixel_place 612 51 FFFFFF Line 617368: 2024-07-15T18:26:26.652Z piXelBow@toast.ooo pixel_place 612 52 FFFFFF Line 617369: 2024-07-15T18:26:26.652Z piXelBow@toast.ooo pixel_place 612 55 FFFFFF Line 617370: 2024-07-15T18:26:26.653Z piXelBow@toast.ooo pixel_place 612 56 FFFFFF Line 617371: 2024-07-15T18:26:26.653Z piXelBow@toast.ooo pixel_place 614 50 FFFFFF Line 617372: 2024-07-15T18:26:26.654Z piXelBow@toast.ooo pixel_place 614 52 FFFFFF Line 617373: 2024-07-15T18:26:26.654Z piXelBow@toast.ooo pixel_place 614 53 FFFFFFThat's 35 pixels placed in less than half a second.
Yep, I saw that after the event concluded
The user did get punished during the event for exploiting that bug tho