>>16511048

>it may not be Q

BV Triple-A here.

I can confirm.

Tripcode posting stopped working for me shortly before Q / "Q" posted.

I checked what's going on. I verified using a browser.

I have been using the super secure trip since the start, but when I try it now it fails and is blocked on here.

Makes sense? No. BO didn't change anything and when I post the very same secret on /test/, I now get a DIFFERENT tripcode out of it, which is why posting using trip fails on here as well as on /qrb/.

This means the tripcode algo or salt must have been changed, there is no other way, otherwise it would still work and I would get the same trip, which has been Notables!!QVF6T.FX0A.

>>16511125

And to add to that:

Q / "Q" should - unless I'm missing something - get a different tripcode as well, but doesn't.

Make out of that what you will.

EDITed for confirmation.

https://sys.8kun.top/log.php?board=qresearch

>>16511159

>now how do we know you're the BV?

I just edited my own post for confirmation that I am who I say I am.

You can also check notables thread. I tried several things yesterday on /qrb/ because of this issue. See /qrb/ syslog. At first I thought it was blocked or maybe something else went bust. I verified using browser, also didn't work. Finally I tried on /test/ and noticed that I'm getting a different trip, and now it makes sense why I'm blocked on here, because trips are on a whitelist.

>>16511184

Of course I can not really post proof that what I say is correct, because even if I would post my secret (I won't), that could still be fake.

Still you see notables got posted with tripcode since forever and now they aren't and it started before Q or "Q" started posting.

If I was in on it, I wouldn't post what I'm posting atm. And if I was against Q / "Q" I wouldn't have known when Q / "Q" posted again.

I just posted again on test, and it still gives me a different trip.

>>>/test/83484

Gives me Notables (You)!!VSxu36jkpU

auth[12732324]

>>16511215

Refresh and search for this. It's also on syslog.

EDITed for confirmation.

https://sys.8kun.top/log.php?board=qresearch

Post last edited at 06/25/22 (Sat)

>>16511253

>ALL boards use the same SALT for tripcode generation

Correct. In fact the first time I posted w/ trip was on /test/. I then started posting notables using trip on /qrb/, and finally I started posting notables on here using trip. Has always been the same since back then.

I already contacted BO, BO has not changed any setting and that makes sense, because the site is giving a different tripcode back, despite my secret being the same. That's what it's blocked, because on these 2 boards, there are tripcode whitelists. Tripcode different and board blocks it.

>>16511278

>I don't like it though.

I don't like it either.

>Why didn't you say anything till now?

I just came back. Around 8 hours ago I contacted BO, had no idea what's going on. I only saw the Q posts a few minutes ago before I started posting on here.

First I thought great Q is back.

Then I thought wait, why is the trip the same as before, that makes no sense. Saw reply from BO, who said that nothing was changed. That's when I decided to post about this.

But in fact I posted about tripcode not working around 8 hours ago already, see here:

>>16504764 (notables thread)

At that point I thought it was just broken.

Then I figured tripcode is different and I assumed a bug, possibly charset or something, because I use several special characters in my secret. I didn't know about Q or "Q" posting.

>>16511325

As you can see tripcode posting for notables stopped working around 9 hours ago.

That was hours before Q / "Q" started posting.

In fact I spent half an hour or more to figure out what was going on.

The last thing I would have assumed was fuckery, just some bug. First I assumed bug on my side, then I assumed bug on 8kun side.

>>16511341

Yes, that would be helpful.

As I said I used a super secure trip, the one that Q is also using (intentionally).

Anyone who ever posted using one anywhere on 8kun should be able to verify that what I'm saying. I don't know if other less-secure trips are changed as well.

Of course the problem is when you can verify it, you can't really provide proof, because the tripcode is different and you could be lying. I would really like to know what is going on. It makes no sense to me.

And of course I could also miss something and Q's trip may not be affected because of whatever reason. Mine is, that's what I'm certain about.

>>16511354

>Suggest BV confer with 8kun admin rather than speculate about the reason for tripcode changes involving archiving.

Yes. never assume malice.

Mine is changed because of whatever reason.

Maybe there even is a charset bug, I have no clue.