#Up vs. Down
1 messages · Page 100 of 1
476
375
474
352
349 Omg hi I haven’t seen you all day
i was playing mine craft
348 oh lol
347
I pinged you like 5 times in #1144322866616221716 lol
oh
346
oh you dont wanna run :(
okay gn
337 okay :)
335 k cya
334
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
472
480
479
480
486
487
488
487
488
sorry i didnt know 
no worries, you may count again now 
490
489
490
491
492
491
492
493
494
495
496
497
496
497
498
499
500
499
500 back
501
500
499
have i misunderstood this or do we have to either reach 0 or 1000 right?
498
Yes
thank you!
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
515
516
515
516
515
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
556
560
you can only count once per minute 
565
566
567
568
569
570
571
585
586
585
584
585
584
585
584
581
580
581
572
571
568
569
570
this is an unexpected direction 
569
568
567
566
565
564
563
562
561
560
559
558
557
556
555
554
553
554
553
554
Still opponents, but this time the other way around 
Lol
553
554
553
552
551
550
549
548
547
546
545
544
543
542
541
540
539
538
537
536
535
534
533
532
531
530
529
528
527
526
525
524
523
522
521
520
519
518
517
516
515
514
513
512
511
508
494
493
492
491
490
489
483 oh thanks!
480
479
478
477
476
475
474
473
472
471
468
467
464
461
460
459
458
457
456
455
451
450
449
448
447
442
441
440
439
438
437
428
427
426
425
424
423
422
421
420
419
420
419
418
419
416
415
414
413
412
411
410
409
408
407
406
405
404
403
402
401
400
399
398
397
396
395
394
393
392
391
390
389
388
387
386
385
384
383
382
381
380
379
378
377
376
375
374
373
372
371
370
369
368
367
366
365
364
363
364
363
364
363
362
361
361
360
359
358
you put a purple heart?
359
358
359
358
357
358
357
356
357
356
355
354
353
354
353
354
353
352
351
dude wait
352
351
350
351
350
349
350
349
348
349
348
347
348
347
346
345
344
345
344
345
344
343
344
343
342
343
342
341
342
341
340
341
340
341
340
341
340
339
338
337
336
337
336
335
334
333
332
331
330
329
328
327
326
325
324
323
322
321
320
319
318
317
314
313
312
311
310
309
308
305
304
303
296
291
287
286
283
280
279
278
277
276
275
272
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
299
421
422
423
Btw if you want me to stop fighting fire with fire, make sure to be a little less strict with your interpretation of the rules. I will follow. (Oh and maybe don't explain to others that they should only place one count/minute while doing the same yourself
)
424
425
426
427
428
429
430
431
432
433
434
wow ok
302
301
read rule 3a lol
- Up to my interpretation, everything within the past 24h was recent
- There was no flow at all, chat was dormant for a few minutes already when I corrected.
437
438
298
If you don't want to engage in discussion, we can't get to an agreement and have to get @tranquil oar involved
439
Then let's wait for a decision.
k
I want you to think about one thing though: If nobody is allowed to void posts that are more than 30 away, it would be rules as written to get away with cheating after just 30 minutes. And that does not make sense.
I'm all for going with the spirit of rules instead of going with the written implementation. But recently there has been an increase in people who go by RAW and if we want to go there, I will be a part of it.
My voiding is a statement that I will not play nice while others apply rules selectively to fit their own goals.
i aint readin allat
tl;dr
I'm german, I like rules and know how they work.
If you use rules as a tool to victory, I will too.
ok
So I'll offer you a compromise: we split the difference and start again at 360?
361
personally i just want to see you suffer tryna get it back to 500 i gotta sleep soon lol
360
361
360
361
373
376
377
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
432
433
434
435
436
439
442
443
444
445
446
447
448
449
450
451
452
455
456
457
460
464
465
466
478
479
480
483
490
493
497
498
499
500 back
499
496
495
497
498
if there is no bad intent you can correct it (in this case we have one invalid down count, so we correct by +1)
if we think there is malice, we can void what happens after. this is for extreme cases ONLY.
if that sounds good we can amend it
499
500
Sounds like a lot of work as one would have to count how many invalids there are... But we can change it in that way.
I'd also appreciate something along the lines of "please restart your application before invalidating counts in direct conflict with your own count" in order to avoid wrong accusations.
When we send messages "at the same time" it is possible or even quite likely that your message appears to be first on your device while it reached the server after mine.
In that case the only way to determine the correct order is to either reload or ask a third party who was not involved in the conflict, as this gets both messages from the server (and thus in the correct order).
i don’t think that’s required because of the informally agreed on “cooldown resets on each new minute” rule
It's just annoying when somebody refuses to accept blame because "it works on my device"...
500
499
500
it’s already back at 400s