Hash issues analytics

[MultiMote]

Hello! I really enjoyed testing your project, it looks very nice.

First of all, it would be great to have a hash table here, just like the one implemented in CoreScope.

Thanks for your work!

[RikoDEV]

Implemented in 1c4f8d4, update :)

[MultiMote]

Thanks!
Is it supposed to be that colorless? The occupied cells are barely distinguishable from the rest.

It also doesn't seem like the byte switch is doing anything.

[RikoDEV]

Thanks! Is it supposed to be that colorless? The occupied cells are barely distinguishable from the rest.

No, actually, with a small number of nodes, it's hard to tell which destinations are occupied - this needs to be fixed. As for the 1/2/3-byte switches, this is likely related to the poor contrast mentioned above.

[MultiMote]

I don't think it related to contast. "Prefix space used" still says "of 256 possible" on any byte size, percentage in not changed too. "Using X-byte ID" number is same for all ID modes.

Also, what possible conflict means? IDs are unique.

[RikoDEV]

I don't think it related to contast. "Prefix space used" still says "of 256 possible" on any byte size, percentage in not changed too. "Using X-byte ID" number is same for all ID modes.

Bug, value always counted from 1-byte. Fixed.

Also, what possible conflict means? IDs are unique.

The potential conflict posed a risk when changing the hash, which was quite confusing. I updated the descriptions and provided more details on the actual conflicts. I also updated the colors because, with only one node, the difference between the empty field was not visible. Applied in dev docker image.

[MultiMote]

This number still not changed after switching

[RikoDEV]

This number still not changed after switching

Can't replay on my instance.

[MultiMote]

Same images in docker-compose. Other fixes applied, but not this particular one. Clearing cache and testing other browsers gives the same result.

vivaldi_fEnrPEA6Ea.mp4

Nevertheless, it works normally at https://litescope.riko.dev

[MultiMote]

I noticed another issue. A hash overlap between companions is also treated as a collision. Companions do not participate in routing.

[MultiMote]

What about "Using X-byte id" - I think the problem is that liteScope can't yet predict which mode the repeater is operating in (based on last adverts hash size).