insult to injury
Mar. 25th, 2020 02:15 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ceagleWell as if this current world situation wasn't already frustrating enough, it looks like as of today, LiveJournal has stopped supporting my older version of the Google Chrome browser (v62) which I really really liked a lot. ;_;
What happens is that the standard login page simply fails, with a redraw, or simply no login at all. Plus it changes the interface to Japanese.
I know that it is still partially working, because the helpdesk page WILL log me in, but it uses a faulty cookie because the login breaks immediately upon going to a subsequent page.
The password is correct, and the password reset and username checker both work, but their persistent cookie system has been broken or deprecated.
Luckily after nearly an hour of fighting it and trying to figure it out in v62, I was able to login with a newer browser, which I did *not* want to have to use for permanent logins.
-
Remember all the big exoduses from LJ when they were b=messing with it big time? It's the main reason the vibrant community (of some 240 friends in my case) dwindled to about 24 , wow, a tenth of what it once was.. and no fault of ours, my friends... this was LiveJournal's doing :\
...and if this is a sign that they are about to %#$@ with it all again, who knows, maybe its days really are numbered. *sigh*
So much for paying for a Permanent Lifetime Account (around $200 I think it was), but it was worth it to me to share our lives in this community of good friends together.
-
EDIT/UPDATE:
Based on what they are telling others in the Support Center, they are referring people to this page: https://www.livejournal.com/support/faq/324.html which suggests that indeed LiveJournal has decided to start trashing older browsers as of March 12th, and I must have just had a cookie that survived before then until I cleared my cache.
What happens is that the standard login page simply fails, with a redraw, or simply no login at all. Plus it changes the interface to Japanese.
I know that it is still partially working, because the helpdesk page WILL log me in, but it uses a faulty cookie because the login breaks immediately upon going to a subsequent page.
The password is correct, and the password reset and username checker both work, but their persistent cookie system has been broken or deprecated.
Luckily after nearly an hour of fighting it and trying to figure it out in v62, I was able to login with a newer browser, which I did *not* want to have to use for permanent logins.
-
Remember all the big exoduses from LJ when they were b=messing with it big time? It's the main reason the vibrant community (of some 240 friends in my case) dwindled to about 24 , wow, a tenth of what it once was.. and no fault of ours, my friends... this was LiveJournal's doing :\
...and if this is a sign that they are about to %#$@ with it all again, who knows, maybe its days really are numbered. *sigh*
So much for paying for a Permanent Lifetime Account (around $200 I think it was), but it was worth it to me to share our lives in this community of good friends together.
-
EDIT/UPDATE:
Based on what they are telling others in the Support Center, they are referring people to this page: https://www.livejournal.com/support/faq/324.html which suggests that indeed LiveJournal has decided to start trashing older browsers as of March 12th, and I must have just had a cookie that survived before then until I cleared my cache.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2020-03-25 11:08 am (UTC)I remember an exodus to Dreamwidth due to complaints over security. I just need to start reading other furs’ journals and add them as friends if I find them interesting. Looking your posts/responses made in the aughts I feel I missed some wondrous times.
no subject
Date: 2020-03-26 05:49 am (UTC)Then for a while I used v 12 but even that one got to where it couldn't handle many sites.... so I finally relented to Chrome v 62 ... but apparently they stopped supporting that March 12th, so now I am using (effectively) Chorme v 69 .. and when that breaks, I guess I will try Opera again...
p.s. thanks for reading the old postings... i hope it's something enjoyable to do in these stay-at-home-more times ^v^ *hugz*