missing localy received #channels in chat activity #5

New Issue

2026-10-27T15:24:25+01:00

adam commented

2026-10-27 15:24:25 +01:00

I wonder why chat activity did not show more #channels which where localy used by meshers and received by pyMC. I think I understood that the dashboard didn't know which hash could be which #channel-name.

Is there a possibility to feed the dashboard with local known hash / name combinations?

e.g. in config, sqlite-database or plain-textfile

I wonder why chat activity did not show more #channels which where localy used by meshers and received by pyMC. I think I understood that the dashboard didn't know which hash could be which #channel-name. Is there a possibility to feed the dashboard with local known hash / name combinations? e.g. in config, sqlite-database or plain-textfile

adam commented

2026-10-27 15:24:26 +01:00

I like this idea, we're definitely on the same page.. chatting with RightUp about a solution.

I like this idea, we're definitely on the same page.. chatting with RightUp about a solution.

adam commented

2026-10-27 15:24:26 +01:00

Perhaps it's because some channels are broadcast with regions and some aren't. Maybe channels with regions aren't being recognized correctly?

Perhaps it's because some channels are broadcast with regions and some aren't. Maybe channels with regions aren't being recognized correctly?

adam commented

2026-10-27 15:24:27 +01:00

I'll investigate that. Everything should be wired up for for regions — but never hurts to double check!

The decoder brute forces channels based on common channel names... all of this is done in english... so if it's not a common name, it won't get decoded. Probably the most user-friendly solution to add a way to input channels and store them on the backend (in addition to automatic decoding)

I'll investigate that. Everything should be wired up for for regions — but never hurts to double check! The decoder brute forces channels based on common channel names... all of this is done in english... so if it's not a common name, it won't get decoded. Probably the most user-friendly solution to add a way to input channels and store them on the backend (in addition to automatic decoding)

adam commented

2026-10-27 15:24:28 +01:00

Is there a way to automatically calculate this backwards using the key? That would save us the trouble. There are a huge number of unknown #channels; finding and entering them all would certainly be difficult.

Is there a way to automatically calculate this backwards using the key? That would save us the trouble. There are a huge number of unknown #channels; finding and entering them all would certainly be difficult.

adam commented

2026-10-27 15:24:28 +01:00

... Probably the most user-friendly solution to add a way to input channels and store them on the backend (in addition to automatic decoding)

I would love this solution - manually adding channels like done in app with name/key

> ... Probably the most user-friendly solution to add a way to input channels and store them on the backend (in addition to automatic decoding) I would love this solution - manually adding channels like done in app with name/key

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/pymc_console-dist#5