Anonymous ID: 07ef9a Dec. 29, 2020, 12:07 a.m. No.12220027   🗄️.is 🔗kun   >>0127

>>12219881

If only this site would support filtering based on picture-hash. That way it would work automatically.

 

btw. anyone got any idea how to upload MP3s on here? Some shill yesterday did so several times, when I try it, I get an error message.

Anonymous ID: 07ef9a Dec. 29, 2020, 12:29 a.m. No.12220209   🗄️.is 🔗kun   >>0238 >>0241

>>12220176

How can you be certain that one baker id in one thread is the same person in the follow up thread?

And what happens if the baker loses internet connection and an IP change happens? The baker would get another user id.

 

If there were trips for bakers, one could easily track that, but that isn't the case.

Anonymous ID: 07ef9a Dec. 29, 2020, 12:38 a.m. No.12220266   🗄️.is 🔗kun   >>0276 >>0316

>>12220241

Yeah, that's right, at the same time I have seen quite a few threads that filled up without the baker posting a link to the follow up thread, so I don't consider that a proper way.

 

And as I said what happens when the baker has an IP change. Then the user id would change mid-thread, which means using it wouldn't be accurate all the time either.

 

And yes, screenshots are meaningless.

Anonymous ID: 07ef9a Dec. 29, 2020, 12:44 a.m. No.12220298   🗄️.is 🔗kun   >>0337

>>12220276

>any suggestions?

As I said, the only proper way would be trips, because you can't really rely on the user id, because it may change and there is no way for the user to provide proof.

 

I understand why they aren't allowed on here except for Q, it still sucks, because that way baker changes could get detected easily and even automatically by software.

 

Of course there would be other ways, like PGP verification or something like that, similar to a trip, but within a post, but that would be complicated and I doubt it would work properly all the time anyway.

Anonymous ID: 07ef9a Dec. 29, 2020, 12:54 a.m. No.12220363   🗄️.is 🔗kun   >>0397

>>12220337

A trip can be any trip, it's not about verification, but to identify bakers, not even over time, but for the bakes themselves.

 

I personally would even recommend that bakers use new trips on every bake session.

 

With trips, every handshake could be a simple protocol and software could verify what is going on, plus identify baker changes too.

 

Shill bakers can already coordinate from outside of this and identify another (which probably already happened), so I don't see such a change opening any door. It's already open.

Anonymous ID: 07ef9a Dec. 29, 2020, 1:06 a.m. No.12220414   🗄️.is 🔗kun   >>0447 >>0483 >>0534

>>12220397

There is no way to pass a private message on here, and it wouldn't be needed. There could simply be some protocol like current baker quoting the follow-up baker and saying "hand off confirmed" or something like that.

And a hand off could only be done against another anon with a trip code.

 

The trip is just for identifying unique bakers even when a user id change happens as well as in multiple threads (which also changes the user id). It's not about tracking bakers over days and that would only be possible anyway if the baker never changes his/her trip, which I wouldn't recommend anyway.

Anonymous ID: 07ef9a Dec. 29, 2020, 1:12 a.m. No.12220453   🗄️.is 🔗kun   >>0477 >>0517

>>12220431

>this is still operating undera a paradigm of attempting to prevent shills from entering the kitchen

One of my reasons for this handshake would be so that software can easily and accurately identify baker changes.

 

Atm this is not possible. If anyone did so, it would be guess work and guess work sucks.

 

I agree on the anon collected notables. Right now software is collecting notables for each thread. If any baker would remove certain notables in the follow up threads, these notables would not get removed for that software. In fact when new notables are added, these are in fact getting added, but existing notables are never deleted.

Anonymous ID: 07ef9a Dec. 29, 2020, 1:14 a.m. No.12220471   🗄️.is 🔗kun   >>0486

>>12220447

Exactly.

 

Doesn't have to be of course, but that's what I have in mind. One could also keep tripcodes and such to identify yourself as this or that baker.

As previously said based on OPSEC I would not recommend doing so. Tracking more than needed is bad, but we actually want to know who is the baker and the only one who can really verify that (except for IP changes) is the BO and BVs.