Conversation
Notices
-
Thursday, 26-Jul-12 16:25:17 UTC from web
-
@killerkiwi117 how is it going today so far
-
@jadenman7 Amaaaaaaaaazing ;3
-
@killerkiwi117 awesome sorry for late response
-
@jadenman7 It's alright bro!
-
@jdl179 thanks man
-
@jadenman7 No problem, I do late responses aaaaall the time!
-
@jdl179 It happened again.
-
@thelastgherkin Awh crap, it seems to only happen whenn I sign into Dozer on the RP site :C
-
@jdl179 I had to some thing all the time so me to
-
@jdl179 See, that's the connection. Your Dozer account's user ID is the same as this random dude's. I just don't know how to stop it from happening.
-
@thelastgherkin It's okay, I will just choose one site or the other :)
-
@thelastgherkin And I choose this site foer now!
-
@killerkiwi117 Excellent choice, sir or madam.
-
@thelastgherkin Isn't it possible to manually change his account ID? Will have to look around to make sure that doesn't cause issues though (or, if @killerkiwi117 uses the same password for both account, change the password on one of the two so logging in on the RP site is less likely to trigger a login here as well?)
-
@thelastgherkin It be sir :3
-
@omni Derp, nevermind, didn't read that the account doesn't belong to @killerkiwi117, it's actually a fairly serious security flaw.
-
@omni And one which should have been resolved way back when. Like, Cabal-in-control way back when. RP-site-newly-born way back when.
-
@thatonepony "delete only if the account is 1. New 2. spammy 3. and posts illegal content."
-
@thatonepony Je n'ai pas l'autorité.
-
@thelastgherkin It seems like the two sites aren't split enough, and StatusNet reads that he is logged in as account number X. To truly fix this, both sites should probably use an independent database and be "jailed" away from each other. Not the easiest solution, though.
-
@omni Something something toasters. When I say it /should/ be fixed, I meant that it WAS fixed. I don't know how it not being fixed became a thing that was happening. Cabal fixed it here: http://rainbowdash.net/notice/127243
-
@thelastgherkin Well, apparently it wasn't completely fixed if it started happening again. Perhaps one more-common issue was fixed, or the fixed was made such a way that it almost never happens, but still has a very minimal chance of occuring.
-
