If you have an email ending in @hotmail.com, @live.com or @outlook.com (or any other Microsoft-related domain), please consider changing it to another email provider; Microsoft decided to instantly block the server's IP, so emails can't be sent to these addresses.
If you use an @yahoo.com email or any related Yahoo services, they have blocked us also due to "user complaints"
-UE
Suggest forum changes/features and report bugs here!
Comments
Doing that now. Also, anyone with an incorrect inbox count due to the old bug can PM me with the number of messages I need to adjust.
EDIT: The remainder of the bugs with it *should* be fixed now.
When I hover over it it shows a message "This website does not supply identity information"
Is this happening to anyone else?
The current favicon, however...well, take a guess what it is.
The mouseover text is indeed standard, it's built into the browser mainly for identification of ssl-based sites.
As for the favicon, look harder and you'll see it. In the interim, blame boredom being linked to this thread
FATAL ERRORS
MORE FATAL ERRORS
Line 470 seems to not like me
I'm just going to post these errors as I get them
Huh. Same error again
EDIT: Oh a new one!
Fatal error: Out of memory (allocated 6815744) (tried to allocate 42 bytes) in /home/ijbm/public_html/forums/plugins/HtmLawed/htmLawed/htmLawed.php on line 437
Fatal error: Out of memory (allocated 7340032) (tried to allocate 19456 bytes) in /home/ijbm/public_html/forums/library/vendors/Smarty-2.6.25/libs/Smarty.class.php on line 1664
And the errors that appeared when I tried to post this
Fatal error: Out of memory (allocated 1310720) (tried to allocate 4864 bytes) in /home/ijbm/public_html/forums/library/core/class.controller.php on line 1158
Fatal error: Out of memory (allocated 5767168) (tried to allocate 32 bytes) in /home/ijbm/public_html/forums/library/core/class.pluginmanager.php on line 347
Fatal error: Out of memory (allocated 1310720) (tried to allocate 48 bytes) in /home/ijbm/public_html/forums/library/core/class.controller.php on line 1101
Apache needs to be shot. That is all.
EDIT: reverted a change I did about a couple hours ago, hopefully that stops apache from vomiting.re-applied after going on a mass spam killing spreeso does at&t, just for good measure
EDIT:
welp, found the root of the problem. spam getting through to another site on the same server. gimme a little bit while I go on a destruction mission~ *grabs the nearest chainsaw*
EDIT 2: That should stop it from asploding.
Alternatively, I think the server was not very happy about having a picture of a user's dick posted on it.
AND PISS OFF LINE 79!
Curses, line 143! And line 68!
of course it wasbut seriously, I think it was something memory spiking for a moment. the fun part was I was figuring it out and ended up somehow not being able to see what I was typing :P
We could just turn any NSFW images in that thread to hyperlinks. And/or enforce our right to ban any images we deem unacceptable without explicit criteria, even if the thread containing them is marked "NSFW", since mods reserve that right anyway.
That sounds like a good idea to me. I am generally of the opinion that NSFW images, if allowed, should be made so that people are clearly aware what they are and so only people who want to see them have to be exposed to them. I feel like that is the best way to avoid upsetting those who may find them disturbing, gross, and inappropriate. Basically, I think forbidding the posting of NSFW pictures is the right move.