I've noticed that, when switching back to the "Default Frontend", there is an added option to manage room servers. Any chance this is in the development pipeline for pyMC:Console?
I've noticed that, when switching back to the "Default Frontend", there is an added option to manage room servers. Any chance this is in the development pipeline for pyMC:Console?
<!-- github-sync-id:3907468923 -->
How is this working out. Any features, additions, adjustments that you'd like to see?
I don't use room servers very often, so would love any feedback!
How is this working out. Any features, additions, adjustments that you'd like to see?
I don't use room servers very often, so would love any feedback!
<!-- github-comment-id:3961856123 -->
Frankly we're kind of struggling to find a really good use case for Rooms
as well. We like the persistent message storage but the on-board
implementations are memory starved and don't persist much (~32 messages?).
That might be able to be rectified by having the room data stored on a
system with a lot more memory...
Thanks
Cal
On Wed, Feb 25, 2026 at 12:28 PM Treehouse⚡️ @.***>
wrote:
Frankly we're kind of struggling to find a really good use case for Rooms
as well. We like the persistent message storage but the on-board
implementations are memory starved and don't persist much (~32 messages?).
That might be able to be rectified by having the room data stored on a
system with a lot more memory...
Thanks
Cal
On Wed, Feb 25, 2026 at 12:28 PM Treehouse⚡️ ***@***.***>
wrote:
> *dmduran12* left a comment (dmduran12/pymc_console-dist#3)
> <https://github.com/dmduran12/pymc_console-dist/issues/3#issuecomment-3961856123>
>
> How is this working out. Any features, additions, adjustments that you'd
> like to see?
>
> I don't use room servers very often, so would love any feedback!
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/dmduran12/pymc_console-dist/issues/3#issuecomment-3961856123>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AD3O2DMLY5EOXUICKJFK7VD4NYAXFAVCNFSM6AAAAACUH33NTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNRRHA2TMMJSGM>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
<!-- github-comment-id:3962229645 -->
thanks, ok, glad to hear we're not crazy — feels like a great concept with a poor execution. The execution might be limited by the protocol, but I'm wondering if a poll or request based system hosted by pyMC's might be something to tinker with.
RightUp and I have chatted about it, and it'll take some thinking to sketch out the user interaction flow, but it's something we're both interested in looking at someday.
a simple lightweight text based call/response interface:
R Read messages
N Read new messages
P Post a message
E Enter a reply
K Kill (delete) your message
S Scan message areas
J Jump to message area
L List message areas
just a whisper of a dream of an idea for right now...
thanks, ok, glad to hear we're not crazy — feels like a great concept with a poor execution. The execution might be limited by the protocol, but I'm wondering if a poll or request based system hosted by pyMC's might be something to tinker with.
RightUp and I have chatted about it, and it'll take some thinking to sketch out the user interaction flow, but it's something we're both interested in looking at someday.
a simple lightweight text based call/response interface:
R Read messages
N Read new messages
P Post a message
E Enter a reply
K Kill (delete) your message
S Scan message areas
J Jump to message area
L List message areas
just a whisper of a dream of an idea for right now...
<!-- github-comment-id:3962387404 -->
I agree that something that felt a bit more like a more modern packet bbs
kind of arrangement could still have some wow factor but also make some of
the older hams feel welcome. As you say, maybe someday. I feel like there
are a LOT of opportunities still ahead of us.
Cal
On Wed, Feb 25, 2026 at 2:09 PM Treehouse⚡️ @.***>
wrote:
thanks, ok, glad to hear we're not crazy — feels like a great concept with
a poor execution. The execution might be limited by the protocol, but I'm
wondering if a poll or request based system hosted by pyMC's might be
something to tinker with.
RightUp and I have chatted about it, and it'll take some thinking to
sketch out the user interaction flow, but it's something we're both
interested in looking at someday.
a simple lightweight text based call/response interface:
R Read messages
N Read new messages
P Post a message
E Enter a reply
K Kill (delete) your message
S Scan message areas
J Jump to message area
L List message areas
just a whisper of a dream of an idea for right now...
I agree that something that felt a bit more like a more modern packet bbs
kind of arrangement could still have some wow factor but also make some of
the older hams feel welcome. As you say, maybe someday. I feel like there
are a LOT of opportunities still ahead of us.
Cal
On Wed, Feb 25, 2026 at 2:09 PM Treehouse⚡️ ***@***.***>
wrote:
> *dmduran12* left a comment (dmduran12/pymc_console-dist#3)
> <https://github.com/dmduran12/pymc_console-dist/issues/3#issuecomment-3962387404>
>
> thanks, ok, glad to hear we're not crazy — feels like a great concept with
> a poor execution. The execution might be limited by the protocol, but I'm
> wondering if a poll or request based system hosted by pyMC's might be
> something to tinker with.
>
> RightUp and I have chatted about it, and it'll take some thinking to
> sketch out the user interaction flow, but it's something we're both
> interested in looking at someday.
>
> a simple lightweight text based call/response interface:
>
> R Read messages
> N Read new messages
> P Post a message
> E Enter a reply
> K Kill (delete) your message
> S Scan message areas
> J Jump to message area
> L List message areas
>
> just a whisper of a dream of an idea for right now...
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/dmduran12/pymc_console-dist/issues/3#issuecomment-3962387404>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AD3O2DPWJQCMLXTU2LNKS334NYMQZAVCNFSM6AAAAACUH33NTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNRSGM4DONBQGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
<!-- github-comment-id:3963240234 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I've noticed that, when switching back to the "Default Frontend", there is an added option to manage room servers. Any chance this is in the development pipeline for pyMC:Console?
Looking great so far. Thank You.
How is this working out. Any features, additions, adjustments that you'd like to see?
I don't use room servers very often, so would love any feedback!
Frankly we're kind of struggling to find a really good use case for Rooms
as well. We like the persistent message storage but the on-board
implementations are memory starved and don't persist much (~32 messages?).
That might be able to be rectified by having the room data stored on a
system with a lot more memory...
Thanks
Cal
On Wed, Feb 25, 2026 at 12:28 PM Treehouse⚡️ @.***>
wrote:
thanks, ok, glad to hear we're not crazy — feels like a great concept with a poor execution. The execution might be limited by the protocol, but I'm wondering if a poll or request based system hosted by pyMC's might be something to tinker with.
RightUp and I have chatted about it, and it'll take some thinking to sketch out the user interaction flow, but it's something we're both interested in looking at someday.
a simple lightweight text based call/response interface:
R Read messages
N Read new messages
P Post a message
E Enter a reply
K Kill (delete) your message
S Scan message areas
J Jump to message area
L List message areas
just a whisper of a dream of an idea for right now...
I agree that something that felt a bit more like a more modern packet bbs
kind of arrangement could still have some wow factor but also make some of
the older hams feel welcome. As you say, maybe someday. I feel like there
are a LOT of opportunities still ahead of us.
Cal
On Wed, Feb 25, 2026 at 2:09 PM Treehouse⚡️ @.***>
wrote: