@chr you'll have to add it probably; what i remember is this:

column settings are stored by type, regardless of whether the column is pinned, eg "public" or "hashtag:#{tag}" (i don't remember the strings exactly). if you somehow managed to open two columns of the same type at once, they'd share settings. (some people don't like this behavior, but.)

so what you'll need to do is add a new prop to THAT object, and do everything based on that

@kibi yeah yeah yeah i think i've got it!

also, the onlyMedia property was already special and stored on the column rather than the timeline type! i kept that behavior in this PR by having the settings read out of the column props instead of the timeline props if a column ID is available

@kibi incidentally i'm thinking of writing a second PR to make every column setting work that way, since the way it is right now makes pinning the same column multiple times kinda pointless

@chr i think things are set up fairly automagically to where if you just dispatch/map from the new prop name, everything else will fall into place. and then when it comes to which timeline to subscribe to, you'll need to (a) use the prop rather than the URL to determine, and (b) set it up to unsubscribe/resubscribe to the correct timeline on prop change

@kibi yeah all that stuff was already set up, it was just a matter of adding onlyMedia to mapStateToProps so that it actually is based on the redux state instead of being set on creation of the component

@chr okay cool cool :) sounds like you're doing good things 😉⭐️