RBN issues with the public web (1.0.11)

[n9jr]

I performed a fresh install on N9JR-4 and I observed the following.

Without logging in, I was seeing RBN spots.

After logging in but with RBN disabled for user N9JR-10 I continued to receive RBN spots. My filter settings are as follows:

Filters for N9JR-10
[rbn]
accept/rbn 1 call N9JR
[spots]
accept/spots 1 by_zone 3,4,5

After enabling RBN my RBN filters were not being applied,

I did notice that I was seeing a FT-8 RBN spot.

BUT, RBN spots for FT8 are not enabled at the node level.

[n9jr]

Wrong spot. It was on 50.313 and had the RBN flag and included the comment field.

[AI3I]

Implemented locally for 1.0.11.

Changes made:

• Public websocket live spots now use the same RBN visibility policy and stored user filters as /api/spots. The browser passes the current web session token on the websocket URL because websocket clients cannot send X-Web-Token headers.
• Public stats and leaderboard now use the same viewer policy, so anonymous or RBN-disabled users do not have RBN spots counted into Top Mode/leaderboards.
• RBN classification now also considers stored raw/protocol fields, so PC11/PC61 spots marked with an RBN flag outside the comment field are treated as RBN.
• Peer ingest now applies RBN-disabled policy to PC11/PC61 spots whose raw fields carry the RBN marker.
• SysOp Spots source filtering/badging now uses the same raw/protocol-aware RBN classification.

Validation: pytest tests/test_public_web.py tests/test_telnet_commands.py::test_publish_spot_starts_new_line_after_keepalive_prompt tests/test_telnet_commands.py::test_readline_keepalive_marks_prompt_open_for_writer tests/test_app_ingest.py::test_ingest_pc61_drops_rbn_spots_when_peer_rbn_access_disabled tests/test_app_ingest.py::test_ingest_pc61_drops_rbn_spots_when_rbn_flag_is_in_trailer tests/test_web_admin.py::test_api_spots_can_filter_cluster_vs_rbn_sources (59 passed).

Retest focus: anonymous public page should not show RBN live spots, logged-in users with RBN disabled should not receive RBN live spots, logged-in users with RBN enabled plus accept/rbn filters should only see matching RBN spots, and FT8-marked RBN spots from peers should be classified as RBN rather than normal cluster spots.

[AI3I]

Fixes committed in 2f97284, pushed to main, and deployed to pycluster.ai3i.net. Production doctor and HTTPS checks pass and the host reports pyCluster 1.0.11. Please retest anonymous, RBN-disabled, and RBN-filtered logged-in public views, including websocket updates and FT8 spots carrying an RBN protocol marker.