As we feared, the owner of the old domain has already betrayed the community and redirected the domain. After the redirect propagates, hundreds of thousands of loyal patriots may not know where to find home!
Spread the word that we've moved! Gab, Twitter, etc! Here's an example (Also, new Gab account for the new domain name):
https://gab.com/PatriotsDotWin/posts/105594470022099271
Edit-
A lot of concerns have actually been answered by more technically savy users in the comments,
No, they said if you were logged out, that was bad. And that the new site would likely blindly accept the first password provided. I was not logged out. My browser does not remember passwords, so it could not have logged me back in. Or... It's all bullshit and it's been compromised for a while already. Probably back when that 'hold the line' lie started.
the cookie is still valid, which means that the front end hosts are the same, the back end db is the same. URL may be different, but everything else is the same. Even the ssl cert is the same.
Yep. The fact the domain changed and SSL didn't freak out is a good thing. To every pede that doesn't know what that means... it means a ton of extremely annoying extra measures on your computer designed to warn you if something's amiss, aren't ringing. And trust me, they got super annoying the past 2 years. So I feel safe. The token is still valid, the cert is good, AND the domain name changed... even the most secure site will freak out if you change a domain name, unless you've set up a line of trust. Well it looks like they setup a line of trust. So there.
EDIT-
Dusted off the old poorly underused, but verified, thedonaldreddit Gab account for additional verification:
https://gab.com/thedonaldreddit/posts/105595244151890950
Edit- As far as media posts go, it's fixed for new posts, being worked on for old ones.
Hey, Um.... Didn't this exact thing happen like a month's or two ago?
Only when that happened, they clearly still had the backend database because my username with an incorrect password didn't work. I was only able to log in after a few attempts when I finally remembered my password.
A fake site would have accepted any password I gave it since they wouldn't have had the backend data.
The Great Password Forgettening is simultaneously proof of the system's validity, and the tragic loss of too many good accounts...
I was never able to remember my password.
Username checks out
yupp
Having done stuff dealing with login info before.... I have a few bits of info for non-techies reading this post...
it's very poor practice to actually store a plain text copy of the password. What is usually done is to take a hash value of a server specific value (set in configs or other handy spot) and the hash value. When someone logs in, the server will accept their plain text password (hopefully over SSL) and recalculate the hashed value. It will then compare the 2 hashes to see if they match up.
Hashes are a one way function. You should not be able to take the hash and then calculate the inputs to it.
Cookies can save your session, allowing future access without logging back in... until they expire or the host is identified as something else. The reason you need to log back in for reason #2 should set off a red flag... big red flag.... almost CHINA red flag.