Subject: Anyone else having this problem?
Author:
Posted on: 2015-08-04 17:44:00 UTC
For some reason, certain web browsers have been eating posts whenever I try and make posts to the Board. Both Safari and Google Chrome just behave like I never posted anything, but I discovered Firefox works for my purposes.
Darkotas is having the same problem, except he can't find a single browser that doesn't cause his posts to go kaput.
Thoughts?
It's essentially the beta/dev version. Oddly, I've had less problems using it than normal Chrome. It may also be the ads. A ton of people have been getting severe issues with them, and I've seen ads do even stranger things to certain computers. I'm using adblock, so if I were you, I'd give it a shot and see if it's any better afterwards.
Also, I don't know if you noticed, but you put the author and subject lines in the wrong place. They should be reversed, otherwise the rest of us get confused. :)
Are you blocking individual IP address or CIDR ranges?
For zdimensia, we blocked the individual IP, because she was only using one. Ammo Guy originally wandered a bit, so we just blocked the first two sections. His IPv6 is now blocked to three colons; I don't know how precise those things are, so.
hS
That is most likely what is causing your problems. Try blocking CIDR ranges instead of colons. What you blocked could have affected thousands of IPs.
CIDR notation is a syntax for specifying IP addresses and their associated routing prefix. It appends a slash character to the address and the decimal number of leading bits of the routing prefix, e.g., 192.168.2.0/24 for IPv4, and 2001:db8::/32 for IPv6.
Basically, you should so a WHOIS on the IPv6 address and try blocking what it recommends to see if it helps.
I'm not a network expert either, Wikia Stars just have to perform range blocks occasionally. ;)
IPv6 addresses are each 128 bits long. Because each digit in an IPv6 address can have 16 different values (from 0 to 15), each digit represents the overall value of 4 bits (one nibble), with 32 digits total. As with IPv4, CIDR notation describes ranges in terms of a common prefix of bits. For example 2001:db8::/32 means that the range described has the first 32 bits set to the binary digits 00100000000000010000110110101000.
Aren't the first 32 bits the ones you just quoted? So why are you telling it that 2001:db8: is the first 32? Pre...sumably it already knows that?
(YourWebApps certainly does; it specifically blocks 'IP prefixes.)
hS
Alright, if this post goes through, I'll be shocked.
*crosses fingers*
Using Google Chrome at the moment and it posted, apparently. That was just... strange.
Anyway, to answer your earlier question, yes, I was trying the different browsers from the same computer. And it would take me to the vanished post, but when I would hit 'return to messages' it would vanish.
Maybe it was just a one-time situation? I've been using Chrome ever since I joined and everything was fine..