The broadcasts method of the Turbo::Broadcastable concern creates Turbo Streams. By default for a Model user creations go to
users, updates and destroys to
Having an always present, endless scrolling index table next to my edit page I am afraid it is not a good idea to connect each visitor to hundreds of
user_[id] streams to keep them up to date. On the other hand the defaults of Turbo::Broadcastable.broadcasts seem to promote this approach.
Unfortunately I cannot find any good documentation or examples for this problem (if it is one). How would you do it? Do you have experience with lots of open streams in real-world applications?