Found it, it's handshakes. They are not filtered out by conspiracies.win site rules but they are filtered out on scored.co. Interesting that two different rulesets are in play! Makes me wonder what else I've been missing ....
I am looking out, but you are right I spoke too soon. It would seem to be something differing in style or filter rules but it's mysterious what. Maybe it should go up to c/Meta.
u/B1-66ER, I apologize, I can't figure it out either. The login glitch you describe is mostly normal, it's associated with cookies not being exactly what the system wants, while the 503 error was reported on as only happening twice in site history. But persistent selective display of posts? That's new to me!
The 503 the other day was weird, I couldn't even access the .win and other times the 503 happened to scored.co the win was still up, so I think it was weird but I don't know nuthin
Found it, it's handshakes.They are not filtered out by conspiracies.win site rules but they are filtered out on scored.co. Interesting that two different rulesets are in play! Makes me wonder what else I've been missing ....Thanks for look'n out!
Edit: but one of the same users on both screenshots are a handshake b1-66er, or do I misunderstand something
I am looking out, but you are right I spoke too soon. It would seem to be something differing in style or filter rules but it's mysterious what. Maybe it should go up to c/Meta.
u/B1-66ER, I apologize, I can't figure it out either. The login glitch you describe is mostly normal, it's associated with cookies not being exactly what the system wants, while the 503 error was reported on as only happening twice in site history. But persistent selective display of posts? That's new to me!
The 503 the other day was weird, I couldn't even access the .win and other times the 503 happened to scored.co the win was still up, so I think it was weird but I don't know nuthin
Doggos shows that one of our vendors set an arbitrary cache limit of 1802 (communities) that we blew past mysteriously.