dw_maintenance | (no subject)

We've just done a quick code push to get some fixes live (other changes in this push are here!), so if you spot anything awry, give us a holler. This push also should get Google indexing back (for those who have chosen to make their journals indexable) after the next crawl! 🤞 (We had to block an incredibly large range of hosted IPs in order to tackle our persistent and ongoing spam and flooding problem and there was a little too much splash damage.)

If you are not using a VPN and you regularly get the captcha from our hosting provider (the graphical one instead of the DW-native text one), please email support@dreamwidth.org with your IP address and we can see if we can add you to the bypass list after you've run a network and virus scan to make sure the reason our hosting provider is blocking you isn't because your network has a compromised machine on it. I am incredibly sorry that we won't be able to add any VPN IP addresses that are on the "suspicious activity and so receive a captcha" list to the exceptions list: we are very well aware of the security and privacy reasons to use a VPN service for internet browsing, and we really wish we didn't have to put those barriers in the way of some of the VPN services people use to access the site, but the overwhelming majority of our abusive traffic comes from free VPN services. It's been getting sharply worse lately, and we've needed to take some radical steps to curtail it. I apologize profusely to those of you who are using those services legitimately for the inconvenience you've been experiencing.

Flat | Top-Level Comments Only

Thank you!

I don't know if this is related, but today I posted an entry for the first time since the code push, and the rich text mode box isn't showing, just the html one (Firefox 111.01. (most recent) on Win10 64 bit (all updates installed, no VPN). I've already deleted cookies and cache and checked for updates.

We'll take a look at it, but the rich text editor is very old and breaks very easily in modern browsers -- it's very likely that your browser updated and broke it or you have extensions that are interfering with it. We're in the process of replacing it for the new update page. It should be considered an "as is" thing until then! (It's literally the same version of the package that LJ was using when I started working there in 2002.)

Thank you, also for the explanation! I wasn't aware about the reason for the editor breaking. I've experienced it before, and then it's indeed been right after new updates of the browser. Not this time, though, also not any extension (I tried using it without any), the only change I was aware of was the DW code push. It's working again already, so thank you very much, and even more so for working on a replacement! ♥