If creating such a "large scale" issue (in a way, I mean idk) is a problem, I am very sorry for the inconvenience caused :/Removed: -### ChecksRemoved: -Removed: -- ☑ I searched for existing issues and didn't find a duplicate.Removed: -
Show
[Long Term] New Channel Types
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 :
Text
Voice
Link
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
☐ Calendar : To plan events on a calendar, with each channel being its own calendar
Description : We can further imagine each event to be its own "thread", in a way : a place to discuss the event, list information... The content of an event could be spread in two parts : a "header", compiling all the "main" information (a title, a description, a date, maybe a location (of type channel or text), and then maybe some custom fields) and then a second part, the "body", the discussion part, functioning just like a normal text channel. While a message in the body would belong to a specific user, the header could be modified by anyone with the permission to do so. Whether to set those permissions on a calendar or event basis can be debated.
Use cases : Let a team organize meetings ; gamers organize play sessions ; communities plan events in general
See further discussion of the Calendar Channel on this comment
☐ Kanban : To organize tasks more easily
Description : Just like the Calendar, a task could be split in two parts : a header with the main information (title, desc, image, other fields) and a body to discuss . A task would then be a card on a board that can be moved between different categories, defined by the user. Just like the Calendar, the header could be modified by people with the permission to do so while the body would be filled with personal messages. In fact, Kanban could probably be a view type of the Calendar, although I think it would be preferable that the two are dissociated (Or a channel where you can enable / disable each view ?)
Use cases : Let a community plan its next posts on social media ; gamers plan out the next phases in their factory building ; communities keep track of what they need to do in general
☐ Documentation : A blank page to write and document
Description : A page, maybe with tabs, where you write but no answers are expected. Maybe this can be thought as an html canvas where one can build some sort of mini website (with no javascript of course) ? Or maybe a more controlled environment where you let people build with predefined components. Overall : somewhere you are free of the constraints of a normal textual channel, where you can arrange elements in a nice way to make an informative (or not) page. Editing would be restrained page-wide to those with permissions.
Use cases : A content producer presents oneself ; a community exposes rules in a nice way ; someone show a tutorial on how to make a good mock-up
See this comment for further discussion on the Documentation Channel
☐ Photo Album : To share photos in a nice way
Description : In the spirit of a forum, a nice place to share images. We can imagine the ability to comment on images through threads (or not).
Use cases : A cosplayer shows their art ; friends share memories from a trip ; people show off their linux rice
☐ Forum : To talk about various subjects
Description : A simple forum channel, in the type of discord's, with topics and discussions about that topic.
Use cases : A user asks for support ; an activist launches a debate ; a developer plans his API
See this comment for further discussion on the Forum Channel
☐ Bio : To present onseself
Description : A channel where each member has their own "subchannel" where they can present themselves.
Use cases : Many servers have a "presentation" channel, this would be a built-in way of doing it !
See this comment for further discussion on the Bio Channel
☐ Guide : To guide users
Description : A special channel, not in the channels tree, to guide users through the use of the server and fluxer in general
Use cases : A user new to Fluxer discovers it ; a new user in a server is lost
See this comment for further discussion on the Guide Channel
☐ Scheduling: To know when everyone is available
Description : A channel where each member can indicate their availability at multiple dates
Use cases : Planning a meeting ; Planning a gaming session
See this comment for further discussion on the Scheduling Channel
Federation-related channels
Channels with federation capabilities (& that can be connected to the fediverse as well ? Or maybe even native bridges to GitHub Discussions / Discourse ?)
☐ Federation Media Channel: To share media not just on your server
Description : A channel that is connected to other servers (& the fediverse ?) in order to share & receive media from a lot of different places based on what you are subscribed to.
Use cases : multiple communities participating to inktober ; fan communities subscribing to their content creator
See this comment for further discussion on the Federation Media Channel
☐ Federation Thread Channel: To have a shared forum
Description : A channel that is connected to other servers (& the threadiverse ?), in order to form one big forum.
Use cases : several support communities sharing a support channel ; writing communities competing in making stories
See this comment for further discussion on the Federation Thread Channel
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 :/
Edited by Rex
Changes
> *Description :* We can further imagine each event to be its own "thread", in a way : a place to discuss the event, list information... The content of an event could be spread in two parts : a "header", compiling all the "main" information (a title, a description, a date, maybe a location (of type channel or text), and then maybe some custom fields) and then a second part, the "body", the discussion part, functioning just like a normal text channel. While a message in the body would belong to a specific user, the header could be modified by anyone with the permission to do so. Whether to set those permissions on a calendar or event basis can be debated.> *Use cases :* Let a team organize meetings ; gamers organize play sessions ; communities plan events in generalRemoved: -> See further discussion of the *Calendar Channel* on [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-15865506>)Added: +> See further discussion of the *Calendar Channel* on [this comment](<https://feedback.fluxer.com/p/929/c/2306>)- ☐ **Kanban** : To organize tasks more easily> *Description :* Just like the Calendar, a task could be split in two parts : a header with the main information (title, desc, image, other fields) and a body to discuss . A task would then be a card on a board that can be moved between different categories, defined by the user. Just like the Calendar, the header could be modified by people with the permission to do so while the body would be filled with personal messages. In fact, Kanban could probably be a view type of the Calendar, although I think it would be preferable that the two are dissociated (Or a channel where you can enable / disable each view ?)> *Use cases :* Let a community plan its next posts on social media ; gamers plan out the next phases in their factory building ; communities keep track of what they need to do in general- ☐ **Documentation** : A blank page to write and document> *Description :* A page, maybe with tabs, where you write but no answers are expected. Maybe this can be thought as an html canvas where one can build some sort of mini website (with no javascript of course) ? Or maybe a more controlled environment where you let people build with predefined components. Overall : somewhere you are free of the constraints of a normal textual channel, where you can arrange elements in a nice way to make an informative (or not) page. Editing would be restrained page-wide to those with permissions.> *Use cases :* A content producer presents oneself ; a community exposes rules in a nice way ; someone show a tutorial on how to make a good mock-upRemoved: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-16562723>) for further discussion on the *Documentation Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2336>) for further discussion on the *Documentation Channel*- ☐ **Photo Album** : To share photos in a nice way> *Description :* In the spirit of a forum, a nice place to share images. We can imagine the ability to comment on images through threads (or not).> *Use cases :* A cosplayer shows their art ; friends share memories from a trip ; people show off their linux rice- ☐ **Forum** : To talk about various subjects> *Description :* A simple forum channel, in the type of discord's, with topics and discussions about that topic.> *Use cases :* A user asks for support ; an activist launches a debate ; a developer plans his API Removed: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-16562650>) for further discussion on the *Forum Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2330>) for further discussion on the *Forum Channel*- ☐ **Bio** : To present onseself> *Description :* A channel where each member has their own "subchannel" where they can present themselves.> *Use cases :* Many servers have a "presentation" channel, this would be a built-in way of doing it !Removed: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-16598504>) for further discussion on the *Bio Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2343>) for further discussion on the *Bio Channel*- ☐ **Guide** : To guide users> *Description :* A special channel, not in the channels tree, to guide users through the use of the server and fluxer in general> *Use cases :* A user new to Fluxer discovers it ; a new user in a server is lostRemoved: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-16598656>) for further discussion on the *Guide Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2346>) for further discussion on the *Guide Channel*- ☐ **Scheduling**: To know when everyone is available> *Description :* A channel where each member can indicate their availability at multiple dates> *Use cases :* Planning a meeting ; Planning a gaming sessionRemoved: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-16798611>) for further discussion on the *Scheduling Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2364>) for further discussion on the *Scheduling Channel*### Federation-related channelsChannels with federation capabilities (& that can be connected to the fediverse as well ? Or maybe even native bridges to GitHub Discussions / Discourse ?)- ☐ **Federation Media Channel**: To share media not just on your server> *Description :* A channel that is connected to other servers (& the fediverse ?) in order to share & receive media from a lot of different places based on what you are subscribed to.> *Use cases :* multiple communities participating to inktober ; fan communities subscribing to their content creatorRemoved: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-17516590>) for further discussion on the *Federation Media Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2379>) for further discussion on the *Federation Media Channel*- ☐ **Federation Thread Channel**: To have a shared forum> *Description :* A channel that is connected to other servers (& the threadiverse ?), in order to form one big forum.> *Use cases :* several support communities sharing a support channel ; writing communities competing in making storiesRemoved: -> See [this comment](<https://github.com/orgs/fluxerapp/discussions/321#discussioncomment-17516615>) for further discussion on the *Federation Thread Channel*Added: +> See [this comment](<https://feedback.fluxer.com/p/929/c/2383>) for further discussion on the *Federation Thread Channel*### Notes (optional)
Show
[Long Term] New Channel Types
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 :
Text
Voice
Link
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
☐ Calendar : To plan events on a calendar, with each channel being its own calendar
Description : We can further imagine each event to be its own "thread", in a way : a place to discuss the event, list information... The content of an event could be spread in two parts : a "header", compiling all the "main" information (a title, a description, a date, maybe a location (of type channel or text), and then maybe some custom fields) and then a second part, the "body", the discussion part, functioning just like a normal text channel. While a message in the body would belong to a specific user, the header could be modified by anyone with the permission to do so. Whether to set those permissions on a calendar or event basis can be debated.
Use cases : Let a team organize meetings ; gamers organize play sessions ; communities plan events in general
See further discussion of the Calendar Channel on this comment
☐ Kanban : To organize tasks more easily
Description : Just like the Calendar, a task could be split in two parts : a header with the main information (title, desc, image, other fields) and a body to discuss . A task would then be a card on a board that can be moved between different categories, defined by the user. Just like the Calendar, the header could be modified by people with the permission to do so while the body would be filled with personal messages. In fact, Kanban could probably be a view type of the Calendar, although I think it would be preferable that the two are dissociated (Or a channel where you can enable / disable each view ?)
Use cases : Let a community plan its next posts on social media ; gamers plan out the next phases in their factory building ; communities keep track of what they need to do in general
☐ Documentation : A blank page to write and document
Description : A page, maybe with tabs, where you write but no answers are expected. Maybe this can be thought as an html canvas where one can build some sort of mini website (with no javascript of course) ? Or maybe a more controlled environment where you let people build with predefined components. Overall : somewhere you are free of the constraints of a normal textual channel, where you can arrange elements in a nice way to make an informative (or not) page. Editing would be restrained page-wide to those with permissions.
Use cases : A content producer presents oneself ; a community exposes rules in a nice way ; someone show a tutorial on how to make a good mock-up
See this comment for further discussion on the Documentation Channel
☐ Photo Album : To share photos in a nice way
Description : In the spirit of a forum, a nice place to share images. We can imagine the ability to comment on images through threads (or not).
Use cases : A cosplayer shows their art ; friends share memories from a trip ; people show off their linux rice
☐ Forum : To talk about various subjects
Description : A simple forum channel, in the type of discord's, with topics and discussions about that topic.
Use cases : A user asks for support ; an activist launches a debate ; a developer plans his API
See this comment for further discussion on the Forum Channel
☐ Bio : To present onseself
Description : A channel where each member has their own "subchannel" where they can present themselves.
Use cases : Many servers have a "presentation" channel, this would be a built-in way of doing it !
See this comment for further discussion on the Bio Channel
☐ Guide : To guide users
Description : A special channel, not in the channels tree, to guide users through the use of the server and fluxer in general
Use cases : A user new to Fluxer discovers it ; a new user in a server is lost
See this comment for further discussion on the Guide Channel
☐ Scheduling: To know when everyone is available
Description : A channel where each member can indicate their availability at multiple dates
Use cases : Planning a meeting ; Planning a gaming session
See this comment for further discussion on the Scheduling Channel
Federation-related channels
Channels with federation capabilities (& that can be connected to the fediverse as well ? Or maybe even native bridges to GitHub Discussions / Discourse ?)
☐ Federation Media Channel: To share media not just on your server
Description : A channel that is connected to other servers (& the fediverse ?) in order to share & receive media from a lot of different places based on what you are subscribed to.
Use cases : multiple communities participating to inktober ; fan communities subscribing to their content creator
See this comment for further discussion on the Federation Media Channel
☐ Federation Thread Channel: To have a shared forum
Description : A channel that is connected to other servers (& the threadiverse ?), in order to form one big forum.
Use cases : several support communities sharing a support channel ; writing communities competing in making stories
See this comment for further discussion on the Federation Thread Channel
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
☑ I searched for existing issues and didn't find a duplicate.
Original by Rex
Show
[Long Term] New Channel Types
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 :
Text
Voice
Link
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
☐ Calendar : To plan events on a calendar, with each channel being its own calendar
Description : We can further imagine each event to be its own "thread", in a way : a place to discuss the event, list information... The content of an event could be spread in two parts : a "header", compiling all the "main" information (a title, a description, a date, maybe a location (of type channel or text), and then maybe some custom fields) and then a second part, the "body", the discussion part, functioning just like a normal text channel. While a message in the body would belong to a specific user, the header could be modified by anyone with the permission to do so. Whether to set those permissions on a calendar or event basis can be debated.
Use cases : Let a team organize meetings ; gamers organize play sessions ; communities plan events in general
See further discussion of the Calendar Channel on this comment
☐ Kanban : To organize tasks more easily
Description : Just like the Calendar, a task could be split in two parts : a header with the main information (title, desc, image, other fields) and a body to discuss . A task would then be a card on a board that can be moved between different categories, defined by the user. Just like the Calendar, the header could be modified by people with the permission to do so while the body would be filled with personal messages. In fact, Kanban could probably be a view type of the Calendar, although I think it would be preferable that the two are dissociated (Or a channel where you can enable / disable each view ?)
Use cases : Let a community plan its next posts on social media ; gamers plan out the next phases in their factory building ; communities keep track of what they need to do in general
☐ Documentation : A blank page to write and document
Description : A page, maybe with tabs, where you write but no answers are expected. Maybe this can be thought as an html canvas where one can build some sort of mini website (with no javascript of course) ? Or maybe a more controlled environment where you let people build with predefined components. Overall : somewhere you are free of the constraints of a normal textual channel, where you can arrange elements in a nice way to make an informative (or not) page. Editing would be restrained page-wide to those with permissions.
Use cases : A content producer presents oneself ; a community exposes rules in a nice way ; someone show a tutorial on how to make a good mock-up
See this comment for further discussion on the Documentation Channel
☐ Photo Album : To share photos in a nice way
Description : In the spirit of a forum, a nice place to share images. We can imagine the ability to comment on images through threads (or not).
Use cases : A cosplayer shows their art ; friends share memories from a trip ; people show off their linux rice
☐ Forum : To talk about various subjects
Description : A simple forum channel, in the type of discord's, with topics and discussions about that topic.
Use cases : A user asks for support ; an activist launches a debate ; a developer plans his API
See this comment for further discussion on the Forum Channel
☐ Bio : To present onseself
Description : A channel where each member has their own "subchannel" where they can present themselves.
Use cases : Many servers have a "presentation" channel, this would be a built-in way of doing it !
See this comment for further discussion on the Bio Channel
☐ Guide : To guide users
Description : A special channel, not in the channels tree, to guide users through the use of the server and fluxer in general
Use cases : A user new to Fluxer discovers it ; a new user in a server is lost
See this comment for further discussion on the Guide Channel
☐ Scheduling: To know when everyone is available
Description : A channel where each member can indicate their availability at multiple dates
Use cases : Planning a meeting ; Planning a gaming session
See this comment for further discussion on the Scheduling Channel
Federation-related channels
Channels with federation capabilities (& that can be connected to the fediverse as well ? Or maybe even native bridges to GitHub Discussions / Discourse ?)
☐ Federation Media Channel: To share media not just on your server
Description : A channel that is connected to other servers (& the fediverse ?) in order to share & receive media from a lot of different places based on what you are subscribed to.
Use cases : multiple communities participating to inktober ; fan communities subscribing to their content creator
See this comment for further discussion on the Federation Media Channel
☐ Federation Thread Channel: To have a shared forum
Description : A channel that is connected to other servers (& the threadiverse ?), in order to form one big forum.
Use cases : several support communities sharing a support channel ; writing communities competing in making stories
See this comment for further discussion on the Federation Thread Channel
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
☑ I searched for existing issues and didn't find a duplicate.
