Replies: 22 comments 64 replies
|
The channels list already feels like something that can become cluttered quickly, so one thing I don't really like are the link types. It feels like they could be placed inside of an "information"-type channel instead, or what the documentation type does |
|
I like the idea of a calendar channel and doc/info channel that can be just a markdown edited document |
|
Just adding that some matrix clients do this, like Commet (https://commet.chat/), which has the "calendar" and "photo album" channel types, and these can be useful for some communities/groups. |
|
I think a Hub/Board Channel Type would be very nice to have (just like Discord's forum), for Developer servers a Hub Channel type would be good for searching projects from other people. |
|
as #530 got closed with the note I should move here. Which I do with this post :-)
|
|
is the Documentation channel type for a Wiki style channel? Because having a Wiki on fluxer would be incredible and let us avoid relying on Fandom |
|
I want to also bring up a new channel type that Discord is recently working on, Spoiler Channels. It functionals simliarily to NSFW channels but non-NSFW (same protections are inherited from regular channels) and does not require age verification. This is for communities, where movie/game spoiler matters or talked about heavy subjects, such as polictics or religion. Source: https://xcancel.com/DiscordPreviews/status/2049095808851599738#m |
|
Something that could probably solve a bunch of the clutter problems and make some of these other channel types look nicer would be to have a channel that can behave as a sub-category. At first you'd think of something like discord threads BUT, what I have in mind is a bit more flexible. Basically you'd be able to allow channels to have a collapsible list of other channels attached to it. So you'd have a nice list of link channels that doesn't get messy, or be able to implement this "link in bio" idea a bit more simple and clean. You'd also be able to have different directories (I guess) for the document channel type suggested above. But overall you'd be able to organize the main channel types (text, voice, link) in a way that lets you attach related sub-channels right to them, so you could have a link or voice channel and then have a text channel attached to it. Of course as more channel types get added they'd also benefit from this functionality. I'd imagine tho that you'd want to restrict the depth of sub-categories to just 1 or 2, and default to collapsed, just to avoid making the channel lists look too cluttered and janky. Edit: Also for permissions, I'd imagine you could add a secondary permission list to the main channel so that sub-channels would inherit permissions based on those permissions instead of the main channel's first permissions. So you could have read only and such, but also not have perms become too messy each time you move a channel to a different category or subcategory. Defaults would be something like sub-channels always inherit a main channel's secondary permissions unless otherwise stated, and when moved to a category they'd automatically sync to the category's permissions by default. Edit2: Further clarification, this is not my take on what threads should be like for Fluxer. I think threads and channels should have a clear distinction between each other so they aren't as confusing to navigate (like on discord.) but I plan to make a post later that goes into that in more depth. |
|
edit: Having access to more advanced UI customization than simple markdown would also help with devs not having to host dashboards offsite and making it more accessible. Being able to tab through more than one UI using the same channel will also make stuff appear more clean. That way you can have a channel for all bot UIs with each having their own interactions, and then one for separate documentation on other stuff with their own document trees. |
|
One thing I'm really hoping is for channel types to not be locked behind the community server toggle. I don't really see any reason why a server should have channels tied to the community setting how discord has it. Why tie stage channels, forum channels etc behind community when these are popular features that anyone might want to use. I could understand stage channel being tied to plutonium instead perhaps, but the other ones should at least be usable on regular servers. I could understand announcement channels being part of community but forum channels? No way. To sum up: Any thoughts? |
|
CalDAV / WebDAV support should definitely be a thing, that I can subscribe to the calendar to my phone, computer or email account. And be able to show my events as "busy" to the fluxer client, during my own calendar events, those I choose to share. |
|
Media channel (the default for posted videos, GIFs and images) where they were explicitly posted, and possibly, optionally, a media channel that automatically displays all media in the group. It should be possible to add a reaction on each media.
like: |
|
I wrote this because I thought that forum channels were going to be just like in other social networks but I'm going to put it here just in case it's useful. Right now, on some platforms, when people create a forum channel they have the ability to add tags in their forum channel, allowing people to have a fast way of searching threads, however sometimes tags aren't enough and using too many tags can lead to an uncategorized mess (and people scrolling forever to search for a specific tag). Proposed solutionI propose Subtags. What I mean is basically a way for tags to be categorized. People can have normal tags (the ones that most forum platform implements) and tags that can have more tags inside of them. For example a forum channel for software releases can benefit from Subtags like this:
Subtags will help community owners to categorize tags for easier access and less uncategorized mess. |















Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
First off : this is by no mean urgent. Thanks a lot for all the work produced !
Also, english is not my main language so I excuse for the weird sentences.
Right now there are three channel types :
Per the roadmap, forums, threads and stage channels are also part of the plan.
On the long term, however, I believe it would be interesting to integrate even more channel types.
Caution
Those suppositions are, as their name suggests, purely theoretical. This list is purely here as a suggestion, I am not able to assess the feasibility of those proposal. Please, if one (or all) of the proposals seem inconceivable even in a distant future, notify me so I can remove it. My intention is merely to give ideas and to help group ideas of channels in one issue. By no mean do I intend on putting pressure on anyone !
Proposed solution
Note
It would be cool for those features to not be locked behind a toggle. Most channels presented here should be available to everyone, and not to certain "server types" like on Discord with community settings. ❤️
Note
Not really a channel per say, but it would be cool to be able to ping threads !
General Channels
Some "general" channel ideas
Federation-related channels
Channels with federation capabilities (& that can be connected to the fediverse as well ?)
Notes (optional)
If anyone wishes to add on this, whether by adding on one of the already mentioned proposals, or with a new one, please, do !
This issue is bound to be edited as ideas come and go.
If creating such a "large scale" issue (in a way, I mean idk) is a problem, I am very sorry for the inconvenience caused :/
Checks
All reactions