Comments

5

emma wrote

buy celeste 350 times and make a 'home office' rig

4

emma wrote

wow, daddy tim doesn't fuck around

3

emma wrote

i never did this trick, and with the exceptions of ads, my timeline has been chronological since september. pretty sure there's a setting for it somewhere, but i can't find it.

4

emma wrote

having a healthy sex life is self-care. thus, i am now the proud owner of a dildo.

3

emma wrote

they shou8ld just arrest david schwimmer. the character of ross was a crime against humanity.

4

emma wrote

wow. pretty disrespectful against the hero who blew up more american planes than the vietnamese.

2

emma wrote

all those nerds who RGB mod their shit are gonna want this

3

emma wrote

Theory: the IP address seen by Postmill is that of a reverse proxy which sends the actual end user's IP thorugh X-Forwarded-For or similar. However, Postmill/the web server hasn't been configured to use these headers, and the random bans happen because the reverse proxy used in the moment of posting has an IP address with a ban meant for another user.

Also worth noting that users marked as 'trusted' aren't subject to IP ban checks, but explicitly marking everyone as trusted is a pain in the butt of course.

5

emma wrote

its like when you do a terrible job of applying concealer and end up with tons of it in your eyelashes, then don't use any other makeup. looks pretty ghosty to me.

7

emma wrote

im a ghost every day, it's pretty ok

3

emma wrote

$('[title=Upvote]').click()

feels better

5

emma wrote

Very interested in reading this, but I have to accept the new terms of service to read the post, and apparently that's not a thing I should just do.

7

emma wrote

list of gaming crimes:

  1. sonic without shoes
  2. shaved mario
  3. the diving animation in breath of the wild which kills your height when you want to glide and i'm totally not mad about this at all
2

emma wrote

This is probably not the reason. You'd still have to accidentally enter a ban reason, accidentally hit 'ban', then accidentally go to the ban list and accidentally remove my ban to cause what I've been experiencing.

My only guess is the site's setup results in invalid IP addresses being sent to the ban check function, and for some reason it gives a false positive. I can't replicate this locally, though, would have to look more into what Heroku(?) does.