You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is somewhat related to my other issue, 'conglomerate multiple hashtags into a single column', but it's a more broad request: it'd be nice if two 'columns' (feeds, whatever you want to call them) could arbitrarily be combined together. It'd be a meta sort of 'super column'; you could add an item to the upper-right-hand 'three lines' button for each column to 'send to super column NameYouEntered', after which the column would be graphically hidden but every post sent to it would appear in the super column with ID NameYouEntered instead. Then, in the NameYouEntered super column (goofy name subject to change, lol), there'd be an option under the upper-right-hand 'three lines' button to separate each column contained within back out into its own column.
This would be one way to add multiple hashtags into a single column. Or, if you ever implemented a new column type to show a remote server's Federated feed, you could create a super column that combines it with your local server's Federated feed (wow, a super-exhaustive Federated feed from a few different servers!). You could put posts from a List into the same feed as a hashtag if you wanted to, for instance, have a column for 'retro games' that featured prominent retro game content creators but also every post with the #retrogaming or #retrogame tags.
I think this would be super useful, super powerful, and easy to understand from a UI standpoint -- although I'm sure it'd be a lot of work to implement!
The text was updated successfully, but these errors were encountered:
This sounds like a more general case of what I'm looking for. If I understand @vencabot correctly, you are looking to combine any arbitrary columns and have a single de-duplicated feed correct?
I am exploring a different way of using Mastodon, having multiple accounts on smaller servers that specialize in topics. What I don't want is to switch accounts a lot to see or interact. Current Sengi is the closest as it doesn't require switching to see timelines. However what I really want is a unified timeline of every account in a single column, deduplicated if I follow the same person in multiples.
Would that be a subset of this issue or a separate request? I forked and brought the code down so I'm happy to play with some proof of concept work if I am capable of it.
Ideally having this global functionality would be the best case, but feel free to open a PR, and if it doesn't fit entirely this one, open a new issue.
This is somewhat related to my other issue, 'conglomerate multiple hashtags into a single column', but it's a more broad request: it'd be nice if two 'columns' (feeds, whatever you want to call them) could arbitrarily be combined together. It'd be a meta sort of 'super column'; you could add an item to the upper-right-hand 'three lines' button for each column to 'send to super column NameYouEntered', after which the column would be graphically hidden but every post sent to it would appear in the super column with ID NameYouEntered instead. Then, in the NameYouEntered super column (goofy name subject to change, lol), there'd be an option under the upper-right-hand 'three lines' button to separate each column contained within back out into its own column.
This would be one way to add multiple hashtags into a single column. Or, if you ever implemented a new column type to show a remote server's Federated feed, you could create a super column that combines it with your local server's Federated feed (wow, a super-exhaustive Federated feed from a few different servers!). You could put posts from a List into the same feed as a hashtag if you wanted to, for instance, have a column for 'retro games' that featured prominent retro game content creators but also every post with the #retrogaming or #retrogame tags.
I think this would be super useful, super powerful, and easy to understand from a UI standpoint -- although I'm sure it'd be a lot of work to implement!
The text was updated successfully, but these errors were encountered: