AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

[Long Term] New Channel Types

(#929) Feature Under consideration channels
by RexSystem edited originally by @alzalia1 on GitHub

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
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 :/

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #1258 Fediverse channel type for media distribution

RexSystemoriginally by @rogue-agent on GitHub

Report details

Problem

Copy to share and duplicate media and mostly unsearchable are common issues among many communities and forum platforms.

Proposal

Having a sort of media channel that can connect to different instances of fluxer and or fediverse would allow for subscribing to one or more creators that then appear in the media feed or allow for users to post and share posts from and to fediverse through the media channel. fluxermedia Image depicting a gallery view of media that has been shared or subscribed to. A mouse cursor depicts highlighting media that then shows the amount of comments on a media and the user. An arrow next to the user allows to open a a small profile view of the creator and see in a quick view what other media they have on their account. fluxersharedmedia Image depicting a chat view where a discussion has been going on about a video that someone proceeds to link to. The link being a direct view from the media channel. It's titular text is above the media content. Next to the media you have comments made to the video that are public. Next to public comments there is a reply window to discuss about the media. The arrow allowing for a reply to the discussion about the media.
  • 615860256-7c27928e-e4f0-42d2-9e03-a5ee67e7ab3e.png

    615860256-7c27928e-e4f0-42d2-9e03-a5ee67e7ab3e.png

    1465×735 | 391 kB

  • 615861546-967832cd-7f1b-4924-bda5-2a6852a29208.png

    615861546-967832cd-7f1b-4924-bda5-2a6852a29208.png

    1072×690 | 96 kB

Merged from #1257 Threadiverse threads channel system

RexSystemoriginally by @rogue-agent on GitHub

Report details

Problem

Missing threads feature and possibility to make public discussion

Proposal

Having a threads type system for a channel type where users of fluxer and users of threadiverse can interact per topic. fluxerforum Image depicting a list view of some threads in a forum type threaded channel. Image also contains users from outside the fluxer network who have posted, either connecting their account to fluxer or the server broadcasting the forum space publicly. Image also uses fluxer logos for samples as to where an image would be located if the topic contained an image.
  • 615830463-51fb62d9-a374-4876-93c4-eea23dc1d6ef.png

    615830463-51fb62d9-a374-4876-93c4-eea23dc1d6ef.png

    1453×725 | 146 kB

Merged from #1207 A stage voice channel

RexSystemoriginally by @zagiz on GitHub

Report details

Problem

Right now, when people do events in the voice chats, the admins or the mods have to mute everyone from the server or people can talk while the event is continuing. Imagine a voice channel with 25 to 30 people and 5 mods 5 admins 1 event organizer. Even if that is not the case, muting people from the server can cause problems. If users leave while the event is continuing, they may not be able to talk in voice chats before mods or admins unmute them from the server.

Proposed solution

Adding a new channel type, stages.

Merged from #1205 More Channel Types (Rules, Announcements, Discussions)

RexSystemoriginally by @genshintreks-ops on GitHub

Report details

Problem

More Channel Types (Rules, Announcements, Discussions)

Proposed solution

I think it would be great if Fluxer had dedicated rules channels, announcement channels, and discussion channels. This would help servers stay more organized and make it easier for members to find important information and communicate.

Merged from #1139 Wiki-style information channels

RexSystemoriginally by @zulc22 on GitHub

Report details

Problem

Informational channels like "#rules" are very very common in Discord and Fluxer communities alike, and I believe Fluxer could provide something that significantly improves the UX for such channels. The traditional UX is just a text channel, and with that you box yourself in with needing to constantly create, edit, and delete messages to maintain your information text channel, and worry about how long you take between messages when writing something long so that the message doesn't segment and give readers a bad reading experience.

Proposed solution

Fluxer already has link channels, which you could use to solve this problem, and are a very nice feature. However this feature seems designed for you to go fetch additional resources from somewhere else, like a traditional hyperlink. I think Fluxer should add 'articles', which can be edited like a big old markup file, like pages in Obsidian, that hold their own history like a page on a Wiki, with features like replaceable attachments relevant to the page or the community, to enable easier and more accountable collaboration.

Merged from #1101 Threads/Forums & Slash Command

RexSystemoriginally by @ank302003 on GitHub

Report details

Problem

Fluxer plans to introduce threads and forums, but existing platforms like Discord, Slack, and Reddit show common gaps threads are either too chat-focused, too linear, or lack structure for long-term organization. Without a stronger approach, Fluxer risks repeating the same limitations instead of enabling scalable, well-organized knowledge systems.

Proposed solution

Fluxer can improve on existing platforms by combining their strengths while addressing their limitations. A key improvement would be true dual-view support, allowing users to switch between linear chat-style threads and hierarchical structured views. This would enable both casual discussions and deeply organized content within the same system. For organization, a more advanced tagging and filtering system would be essential. Supporting multi-tagging, saved views (similar to smart folders), and metadata like status or progress would allow users to manage content more like a database than a message list. Structured post formatting, including templates and rich embeds, would further improve consistency and usability. Discoverability can be enhanced through optional features inspired by Reddit, such as upvote/downvote systems and sorting options like top, trending, or new. These should remain configurable so communities can decide how they want content to be surfaced. UI flexibility is another area where Fluxer can stand out. Supporting multiple viewing modes—such as a compact list, a card/grid layout similar to Obsidian, and a hierarchical tree view would make navigating large forums significantly more efficient and intuitive. Fluxer could also introduce thread relationships, such as linking threads or enabling backlinks, allowing users to build interconnected knowledge systems instead of isolated discussions. Additional features like private or invite-only threads within public forums, draft threads, and improved archiving (both automatic and manual) would provide better control over content lifecycle and visibility. Beyond forums, extending the slash command system to match and exceed Discord’s capabilities would improve workflows. This includes better command discovery, reusable templates, and lightweight automation such as command chaining or presets for repetitive tasks. Integrating activities like mini-games and richer presence systems could also help increase engagement and make the platform more appealing for communities to adopt.

Notes (optional)

Notes: These suggestions are based on the roadmap and aim to guide implementation early. Features should remain modular and optional to support different community preferences. Focus should be on scalability, discoverability, and long-term usability not just real-time chat. Potential areas: Thread/forum data structure (tags, metadata, relationships) UI/UX for multiple view modes Command and interaction system Search and indexing for better discoverability

Merged from #1087 Channel type ideas inspired by Guilded

RexSystemoriginally by @genna87 on GitHub

Report details

Problem

The types of channels currently available is pretty limited

Proposed solution

Guilded is a no-go for me, but the channel types it offers are really interesting. These are the channel types I'd like to see on Fluxer:
  • Scheduling
  • Calendar
  • List
  • Announcement
  • Forum

Merged from #1079 A channel similar to a link in bio type

RexSystemoriginally by @coldreindeer on GitHub

Report details

Problem

Feature request: Built in link in bio channel type.

Proposed solution

It could look smth along the lines of this perhaps. LinkInBioPageFluxerIdea Tbh, I don't have huge hopes for this actually being added, given there are many link in bio sites out there but having one built in would be cool!

Notes (optional)

Would be useful for servers with several YouTube or content creators. Suggestions are welcome.
  • 559707790-f327b085-27fa-4a44-8224-c37dbc525b28.png

    559707790-f327b085-27fa-4a44-8224-c37dbc525b28.png

    1919×944 | 53 kB

Merged from #1062 "Logging" Channel Type

RexSystemoriginally by @Juliaxe on GitHub

Report details

Problem

Users are currently capable of deleting all of their messages, including servers they're no longer in. This is respectable and very privacy forward. However, it fails to address a moderation issue: evidence preservation.

Proposed solution

I propose that a channel can be marked as a "logging" channel, ONLY when it is initially created. It can be turned into a normal text channel later; but that change is irreversible. When a user deletes ALL their messages through the Privacy Dashboard, messages in channels that are currently logging channels should not be deleted. However, the user may still be disassociated from the message (i.e: "Unknown User" instead of their account showing up). Users should receive a one-time warning whenever they open a logging channel, reminding them that any message sent there will not be deleted if deleted through the Privacy Dashboard. The channel should also have some kind of special icon rather than a "#", reminding existing users as well.

Notes (optional)

The channel still functions as a normal text channel otherwise. It only prevents messages from being deleted through the Privacy Dashboard; messages can still be deleted manually as per usual.

Merged from #1054 Web Exposed channels for Looking

RexSystemoriginally by @Lazorne on GitHub

Report details

Problem

A key consideration when managing a community is that accessing certain information often requires an account. For some channels, it may be good to make content publicly accessible via the web, allowing users to read it without logging in to an application or account.

Proposed solution

Zulip (https://zulip.com/) demonstrates an cool approach by allowing select channels, such as Support, Announcements, and Downtime. to be exposed on the web in a new channel type called "Web Channels". This ensures that critical messages remain accessible without requiring users to log in or create an account and can follow the conversation as it happens.

122 comments

Sign in with Fluxer to comment and vote.
Comment by @Freeplayg
RexSystem 1 vote originally by @Freeplayg on GitHub 2 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
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I agree a server can quickly become cluttered... I have made the experience myself X) I would say, maybe additional organization features, like sub-categories that can be closed / opened (maybe closed by default ?) could be interesting to reduce visual clutter ? But at the end, I feel like, no matter how much you try, if you have a lot of needs, then you'll have a lot of channels and thus a lot of clutter :/
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
Clutter is managable with hiding channels, muting, and copying discord's channel subscription system.
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub 10 replies
An idea for Calendar channels: Calendar Page Basically, You have a page that has a calendar on it and a list of events. The events are tied to that calendar, and can be quickly observed that way. You can create new events by either hitting the "New Event" button or clicking on the day/time and creating a new event similar to the flows on any standard calendar app. Give it a starting time, ending time, set up recurring events, a description, image, etc. This information could become the top post for the integrated forum thread. From there, you have the "I'm Interested" flow that discord has for it's event system. Hitting the bell that you are interested automatically subcribes you to a thread for that event (if that is enable in the calendar settings), and you are notified when the event starts (creating the event gives you reminder options). There should be options for recurring events as well. This is very similar to a forum in discord, and with the stated roadmap goals of exporting forums to web you could export the calendar too if you want. (Note on the image: I clipped the current fluxer UI to do this example, so I'd recommend removing the ability to send messages to such a calendar channel. It's essentially a fancy forum display, allowing you to have threads with date/time information. The subscribers to the thread are the people interested in the event) EDIT: I think there is benefit to keeping calendar events channel based, using channel permissions. In discord, Events are tied to the guild and there is no way to restrict who can see certain events. By keeping events channel-based, guild owners can create things like a "Leadership Calendar". Games where you coordinate with variously trusted individuals you can limit who sees raids or operations (ie: with the game Foxhole, You generally want to invite members of allied orgs into your discord to coordinate, but you dont want to give them full access. Also you may have members in your guild who play against you for a match and then come back, so you want to limit their permissions). This is also useful for guilds that have mixed local IRL friends and internet buddies... you can have a place for just the IRL friends to organize events without every person on the server having access to information like people's physical addresses if they are shared in calendar events. You could achieve Discord's "Events" category by showing the user every event they have access to.
  • 552431048-c938703d-c8a6-453c-a872-8911fd50e55c.png

    552431048-c938703d-c8a6-453c-a872-8911fd50e55c.png

    1424×784 | 129 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Thanks for the very detailed proposal ! I'll be adding your contribution (by putting a link, not copying and pasting your message) to my original message if that's fine by you !
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
I should note, my main desire is to have a calendar for events with my friends group. I frequently host board game nights at my house and trying to get people involved is kind of a pain in the ass. Something like this embedded in the same place we chat and shitpost together would be wonderful
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I took the liberty of making a second version of your proposal, slightly more fluxer-themed (although I am not designer) so we would have a better view of it. Is it along the lines of what you had in mind ? image
  • 552921310-564c0f14-ab37-48b5-8e03-59b8872b80be.png

    552921310-564c0f14-ab37-48b5-8e03-59b8872b80be.png

    1917×918 | 124 kB

Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
yeah, that looks a lot better than I was thinking. I am also not a designer, i just clipped random screenshots and tossed them together in my Obisidan notebook's exaclidraw plugin :P I wonder if it would be worth it to have a way to toggle views for the main calendar panel between a weekly layout, a monthly layout, or agenda list? Kinda like what google calendar has. Also, we should probably stick a month display above the main calendar panel to allow users to move to a different month in the display.
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
Oh, there should probably be a "Create Event" button on here somewhere. I put it in the quick display on the bottom right, but I wonder if we should have a header above the main calendar panel with some controls there including a "Create Event" button
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
Should note, in google calendar, the mini calendar is always on a day-of-month display, not a month-of-year. the reason for this is you can change what type of display for the main panel (daily list, weekly, monthly, agenda mode) and the mini calendar always shows you a reference where you are in time.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I see ! Lots of interesting stuff, I'll see if I have time to make the changes to the model today !
Permalink
Comment by @ShiningVenus
RexSystem 1 vote originally by @ShiningVenus on GitHub
I think a calendar channel would be pretty cool to add! I think being able to like add your Google calendar or calendar from other sites/apps would be useful too. You could add upcoming community events, birthdays of members, etc.
Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
My biggest piece of feedback (which i put in that ticket) is that calendars should not be per community. They should be channels and conform to the permissions system that channels do. This is vital for separating out different types of calendars without having to create additional community servers to do so.
Permalink
Comment by @evoandroidevo
RexSystem 1 vote originally by @evoandroidevo on GitHub
I like the idea of a calendar channel and doc/info channel that can be just a markdown edited document
Permalink
Comment by @jhoshy
RexSystem 1 vote originally by @jhoshy on GitHub 2 replies
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. image image
  • 552977486-e959f780-3004-46cc-b103-d85b06306a6f.png

    552977486-e959f780-3004-46cc-b103-d85b06306a6f.png

    813×503 | 288 kB

  • 552977543-d978c036-b55f-4c45-a84b-c5a06c13d2f3.png

    552977543-d978c036-b55f-4c45-a84b-c5a06c13d2f3.png

    806×505 | 51 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Interesting ! I'll add the "Photo Album" channel type to the main proposal !
Permalink
Comment by @coldreindeer
RexSystem 1 vote edited originally by @coldreindeer on GitHub
The calendar that @RoyAwesome done is a lot better imo. Would be interesting to have a photo album channel though. I think some album software apps have ways to resize how they are displayed etc.
Permalink
Comment by @hazencruz
RexSystem 1 vote Merged from #1007 originally by @hazencruz on GitHub
This would be a wonderful feature to have, and was a huge relief for those of us who stream live to large communities when it was implemented on discord.
Permalink
Comment by @Probioticz
RexSystem 1 vote originally by @Probioticz on GitHub 2 replies
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.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hi ! Sorry for the long waiting... Yes, I didn't include the Forums because it was mentioned on the Roadmap, but I can still add it to the list if you wish ! Also great icons !
Permalink
Comment by @Probioticz
RexSystem 1 vote originally by @Probioticz on GitHub 4 replies
and also the icon concepts concepts-for fluxer
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
Instead of a number maybe it could be a letter C?
Permalink
Comment by @coldreindeer
RexSystem 1 vote edited originally by @coldreindeer on GitHub
@smoky-oni I suggested the c as if you have a bunch of calendar channel icons suddenly change number for the channel type when the date changes, that isn't great for a user experience. A simple C for calendar wouldn't have such an issue. @alzalia1 Any thoughts?
Permalink
Comment by @Zambito1
RexSystem 1 vote Merged from #1062 originally by @Zambito1 on GitHub 8 replies
This may seem obvious to you, but as I am someone who has never moderated a group larger than people I would call my friends, can you elaborate on what the function of "evidence preservation" is? Why do you need that? I will also say, I saw the discussions in the Visionary chat regarding this, and I think that it's safe to say people were misunderstanding and misrepresenting what your are proposing here. Privacy is a touchy subject, and I err against retention that I consider unecessary, but it is clear that you thought about the privacy side of this (in the disaccociation, explicit representation in the UI). The main issue for me is: why?
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
I appreciate you taking the time to understand my position and my reasoning better and I'm glad to be talking to a fellow visionary, so hi! As you probably might've read from that conversation, I am intending on owning large community servers and not those small 10-20 member friend servers where you can trust everyone. Part of moderation of larger servers involves keeping around evidence to support kicks, mutes or bans that are given to users. This is especially useful when the user attempts to appeal and claims they did nothing wrong. They could appeal immediately, or maybe even years later. If the evidence is deleted because the moderator who logged the evidence has deleted ALL their messages via the Privacy Dashboard, then there's no longer a valid record to keep the punishment in place. As a result, I'd realistically have 2 options: unban the user, or keep them banned "just because". How do you think it looks if you can't back up your accusation (the 'accusation' being the reason you banned the user in the first place)? I err on the side of bureaucracy when it comes to moderation. No evidence = no punishment, even if that evidence used to exist and was deleted later. It creates accountability on the part of the offending user, the moderator who issues the punishment and leadership as a whole if that punishment is challenged in the future by the offending user or even moderators internally.
Permalink
Comment by @TheKodeToad
RexSystem 1 vote edited Merged from #1062 originally by @TheKodeToad on GitHub
I think the moderation approach is a little flawed here. There are many cases where you want to delete content to avoid people from being exposed to it. Say somebody posts some not-so-wholesome content in your wholesome community - you probably want to remove that as quickly as possible especially to avoid any younger users seeing it. In fact, in cases like these it's the most important that the user stays banned... and that does mean the evidence is gone... there is no longer concrete proof they did anything. There might be some solutions to this - but this is not addressed here! The most obvious to me would be a separate log view (like https://feedback.fluxer.com/p/1062/c/3020) that can perhaps be restricted based on roles. Bots on Discord also already support logging channels which work pretty nicely in my experience - though I'll admit they aren't very privacy friendly as the messages generally stay there forever unless you delete the channel and recreate it again (and most bots don't have a feature which automates this). This doesn't address a user appealing years after the fact either, but with your suggestion I feel that a moderator could just use the excuse that they deleted the content because it was very bad (which could also be perfectly reasonable) Something else not addressed is the problem of people sending and quickly deleting dubious messages before the moderators see them - which I have seen a lot on Discord - since you suggest that the messages should still be deletable
Permalink
Comment by @Juliaxe
RexSystem 1 vote edited Merged from #1062 originally by @Juliaxe on GitHub
I think the moderation approach is a little flawed here. There are many cases where you want to delete content to avoid people from being exposed to it. Say somebody posts some not-so-wholesome content in your wholesome community - you probably want to remove that as quickly as possible especially to avoid any younger users seeing it. In fact, in cases like these it's the most important that the user stays banned... and that does mean the evidence is gone... there is no longer concrete proof they did anything. There might be some solutions to this - but this is not addressed here! The most obvious to me would be a separate log view (like https://feedback.fluxer.com/p/1062/c/3020) that can perhaps be restricted based on roles. Bots on Discord also already support logging channels which work pretty nicely in my experience - though I'll admit they aren't very privacy friendly as the messages generally stay there forever unless you delete the channel and recreate it again (and most bots don't have a feature which automates this). This doesn't address a user appealing years after the fact either, but with your suggestion I feel that a moderator could just use the excuse that they deleted the content because it was very bad (which could also be perfectly reasonable) Something else not addressed is the problem of people sending and quickly deleting dubious messages before the moderators see them - which I have seen a lot on Discord - since you suggest that the messages should still be deletable
While I understand the privacy concern here, not logging evidence isn't really an option. I could do perfectly fine creating this functionality myself in the form a bot, but I'd prefer it to be a native feature with proper disclosure and consent beforehand (as my original post states). I fully understand that evidence / messages should be deleted after a while (especially upon user request), but your suggestion to just not log evidence is inappropriate for larger servers who value accountability on both sides (the user AND the moderator/moderation team). There could be some kind of compromise, but that compromise should not involve not logging evidence and retaining it for a short period of time.
Permalink
Comment by @TheKodeToad
RexSystem 1 vote Merged from #1062 originally by @TheKodeToad on GitHub
I don't feel like you've addressed my main point here - often as moderators you need to delete stuff to protect your users and with your suggestion this would mean destroying the evidence in cases where you really do want to keep a user banned
your suggestion to just not log evidence
That wasn't my suggestion
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
I don't feel like you've addressed my main point here - often as moderators you need to delete stuff to protect your users and with your suggestion this would mean destroying the evidence in cases where you really do want to keep a user banned
Sorry? I don't understand. With my suggestion, this would mean preserving the evidence (at the very least for a longer amount of time). For example, one could argue that messages in a Logging channel ARE susceptible to being deleted via the Privacy Dashboard, but only after a slightly extended period of time (i.e: 1 month after the initial deletion request or immediately if the message in the Log channel is older than 1 year, whichever is sooner). You saying that it wasn't your suggestion to just not log evidence also confuses me, because you said:
This doesn't address a user appealing years after the fact either, but with your suggestion I feel that a moderator could just use the excuse that they deleted the content because it was very bad (which could also be perfectly reasonable)
And:
There are many cases where you want to delete content to avoid people from being exposed to it. Say somebody posts some not-so-wholesome content in your wholesome community - you probably want to remove that as quickly as possible especially to avoid any younger users seeing it. In fact, in cases like these it's the most important that the user stays banned... and that does mean the evidence is gone... there is no longer concrete proof they did anything.
Maybe I might have misunderstood but the general principle is to always log evidence if you're running a larger server. That being said, what is your "main point" if I keep missing/not addressing it?
Permalink
Comment by @TheKodeToad
RexSystem 1 vote Merged from #1062 originally by @TheKodeToad on GitHub
Do I misunderstand your suggestion? It seems the idea is that the evidence is preserved by keeping the message publicly available - but in my experience usually you want to delete rule breaking messages This feature feels like it would just stop the user from deleting their remaining messages (which probably weren't the reason for their ban anyway) after they're banned?
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
Do I misunderstand your suggestion? It seems the idea is that the evidence is preserved by keeping the message publicly available - but in my experience usually you want to delete rule breaking messages This feature feels like it would just stop the user from deleting their remaining messages (which probably weren't the reason for their ban anyway) after they're banned?
Then you misunderstood my suggestion. A "logging" channel is exactly what it suggests - a channel to log things in such as moderation logs or proof. This channel type would not prevent a user from deleting their own messages manually. Rather, when the Privacy Dashboard is used, messages in a "logging" channel will not be deleted but the user will be disassociated from the message. The offending messages THEMSELVES (which you'd take a screenshot or video of) would be deleted by a moderator, then logged as it's own message in a "logging" channel with the screenshot or video proof attached to that message INSIDE the "logging" channel.
Permalink
Comment by @TheKodeToad
RexSystem 1 vote Merged from #1062 originally by @TheKodeToad on GitHub
Ah, that makes a lot more sense! It sounded like you wanted to make it so the main channels users chat in can't have their messages removed through privacy dashboard (but can be removed manually, seemed quite strange to me)
Permalink
Comment by @Envrince
RexSystem 1 vote Merged from #1062 originally by @Envrince on GitHub 1 reply
I believe there should just be a notification to a user upon joining a server that has logging enabled that would say something along the line "Any messages that are deleted or edited will be saved for X amount of days" with an option of leaving the server within the notification. Now accessing the logs should just be easy like clicking on the guild header and selecting logs.
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
I think that's a good idea but I think it's better if this is applied on a channel level rather than the server as a whole.
Permalink
Comment by @wapachoo
RexSystem 1 vote Merged from #1062 originally by @wapachoo on GitHub 4 replies
hypothetically, the best answer for preservation of evidence while still allowing deletion and cleanup would perhaps be the ability to attach info to a ban, in a "select messages/a range of messages to attach to this" or even in the form of moderation info attached to that user? (for that server specifically, of course.) that way you can retain a record of it in the same way you'd retain, say, a screenshot, but in a cleaner way.
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
That is a decent alternative but it doesn't address cases where the messages have already been deleted or the infraction itself took place in DM and is bad enough to warrant moderation on the server level. Do you have any suggestions for that, maybe?
Permalink
Comment by @wapachoo
RexSystem 1 vote Merged from #1062 originally by @wapachoo on GitHub
technically, both are covered by being able to attach a custom moderation note to the user, since that could include things like image links. of course, this puts the onus on the individual server's moderation to keep proper track of /why/ they banned a user, but they should already be doing that; this would just provide an easier way to store and access said information.
Permalink
Comment by @Juliaxe
RexSystem 1 vote Merged from #1062 originally by @Juliaxe on GitHub
If a moderator deletes all their messages, the image links associated with those messages would also become inaccessible (unless Hampus forgot to delete files belonging to deleted messages?). Servers can keep track of why they ban users, but that does not solve the core issue of having evidence to support that ban, even if you properly logged the why.
Permalink
Comment by @wapachoo
RexSystem 1 vote Merged from #1062 originally by @wapachoo on GitHub
i forgot to include the important detail of hosting said media externally to fluxer, oops. unfortunately, there has to be a compromise between privacy and moderation. if every server permanently logs every message for potential moderation purposes, (which if logging was a thing, would be undoubtedly what any server of even moderate size would do, thus causing it to be effectively ubiquitous) it defeats the point of being able to delete things in the first place. importantly, this is not a court of law. if evidence was had at one time but was later lost for one reason or another, that doesn't make the reasoning of the original ban invalid. a healthy community is much more important than allowing people who have wronged said community to appeal, especially when there are few to no consequences for being banned other than loss of access to that one specific community.
Permalink
Comment by @coldreindeer
RexSystem 1 vote Merged from #1046 originally by @coldreindeer on GitHub
I liked the ideas behind the channel types they had but their UI for it was pretty bad for a lot of the stuff imo.
Permalink
Comment by @coldreindeer
RexSystem 1 vote Merged from #1062 originally by @coldreindeer on GitHub
What if when banning a user you could highlight a bunch of their messages to keep as a reference upon a ban inspection? Since messages typically expire after a few years as far as I can tell (unless it is a massive file) then the reference would exist for those few years. Or you could write a description of why you banned them as an option in a ban screen as they get banned perhaps.
Permalink
Comment by @kenderbard
RexSystem 1 vote Merged from #1046 originally by @kenderbard on GitHub 1 reply
Would love these, ESPECIALLY the calendar and scheduling!
Permalink
Comment by @TheBlindBard1978
RexSystem 1 vote Merged from #1046 originally by @TheBlindBard1978 on GitHub
Yeah, definitely a Calendar would be nice. Guilded seemed to be the only one to have this feature that I know of.
Permalink
Comment by @Zac0511
RexSystem 1 vote Merged from #1046 originally by @Zac0511 on GitHub 1 reply
I remember using Guilded before they killed it, would love to see this channel options added to Fluxer
Permalink
Comment by @astraleph
RexSystem 1 vote Merged from #1046 originally by @astraleph on GitHub 1 reply
If there's one thing I miss the most from Guilded, it's their Media channel type. It's much better than a text channel for community servers with an art channel, because discussion on pieces became comments for specifically those pieces and didn't drown out past submissions.
Permalink
Comment by @slrgt
RexSystem 1 vote Merged from #1139 originally by @slrgt on GitHub
the right side of the ui in the Wiki channels could be the Contents section wikipedia has instead of the user list. instead of relying on fandom we could have communities have their wikis on fluxer. With the ability of having them be public wikis like forums are planned to be so people can browse them without signing up
Permalink
Comment by @Dark-Aeon
RexSystem 1 vote edited originally by @Dark-Aeon on GitHub 5 replies
as #1032 got closed with the note I should move here. Which I do with this post :-)

Problem

In 2: Threads and forums in the Roadmap there was asked for ideas for Threads and forums.

Proposed solution

Reddit as type of Forum was already mentioned A flarum type forum (https://flarum.org/) would also be really nice :-) perhaps its even possible to use an extension to sync the forum inside fluxer to public flarum forum.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hello ! I didn't know about flarum ! That's a cool discovery. I'm more than willing to add this idea to the main message, but could you first explain maybe a bit more what a "flarum type" forum involves? A (very) quick look at it and I'm under the impression it is like a discord forum, with tags that you can apply and then filter with ? Is your proposition more about features or display style ? Thanks a lot !
Permalink
Comment by @Dark-Aeon
RexSystem 1 vote originally by @Dark-Aeon on GitHub
Hi okay I will try to explain what I mean. I think what I mean is a mixture of both feature and display style. I try to keep it short but if it becomes a wall of text I apologize in advance. English is not my native language, so if i write something nonsensical please ask for clarification I will try to rephrase then :-) Starting with how discord does the forum. honestly its visual style is cluttered, unclear and I find it hard to find the right forum threads. I am not sure if just visually changing the display would make it better. I compared the discord style to the flarum forum style to see the difference. here a screenshot side by side of a flarum forum and a discord forum to compare: Screenshot-20260417-001 The Flarum forum has less white-space compared to the discord forum. It adds in categories which is nice and shows who and when has replied to the thread instead of just showing part of the thread starters first sentence. The flarum forum shows the avatar of the thread starter which saves on space making the display more compact and makes the different threads visually more distinct from each other. A discord server can have multiple "forums" which is a cool feature. But sometimes on a discord with lots of channels its hard to find them all. The first ideas come to mind is to have a button that just hides every channel except forum channels. Another idea would be a forum view. It switches to a view similar to flarum and converts the different "forums" and "forum groups" into flarum Categories/sub categories and shows just the threads. screenshot what I mean with forum group and forums: Screenshot-20260417-003 and the last part: a bridge to a public flarum forum option: Making it possible to connect the internal forums of a community to a public forum either all or only some (configurable by Admins/mods) This could be made with a flarum plugin that enables a fluxer bridge. The route of a plugin for a forum software would also make it agnostic to which forum software is used as people who dont want to use flarum as their public forum could just write a plugin for the forum software of their choice and connect the internal forums of their own fluxer comunity to another forum software like phpbb, discourse etc. I think I could write a lot more paragraphs but that would likely go to much into detail how something should look or implementation. I hope my rambling makes half way sense :-)
  • 579993130-cedef6ca-2297-4b41-ab4d-aa444c773508.png

    579993130-cedef6ca-2297-4b41-ab4d-aa444c773508.png

    2196×721 | 305 kB

  • 580006090-b2551a57-42d5-4367-a132-3d4ce8171842.png

    580006090-b2551a57-42d5-4367-a132-3d4ce8171842.png

    536×179 | 35 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I see ! So, to try and recap (tell me if I'm wrong) :
  • Make forums more compact
    • Remove useless whitespace
    • Display things more "inline"
    • Remove useless information
  • Add more complex tags, so that you have categories
  • Add forum groups
  • Ideally, add flarum bridge
If I understood correctly, that indeed seems interesting ! I added this discussion to the main message as part of discussions about the forum channel. Edit: Don't hesitate to expand even more on your ideas ! It can be helpful for devs if they end up wanting to implement this :p
Permalink
Comment by @Dark-Aeon
RexSystem 1 vote originally by @Dark-Aeon on GitHub
yeah that sounds good :-) Your recap feels like a good baseline :-) I will think how to expand my ideas more. Thanks for considering my ideas :-)
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
Couldn't this be done via the CSS stuff or smth?
Permalink
Comment by @slrgt
RexSystem 1 vote originally by @slrgt on GitHub 6 replies
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
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
I completely agree on that, although I imagine it would be a massive project to add smth of a similar quality to it.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
It would be especially game changing if it was easy to set the stuff up for CSS stuff etc for the cool looking things people can do, which on fandom is seemingly rather complicated. Or if it had some kind of built in wiki to show how to do basically everything on it. That brings me to another idea.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
In my idea, this channel would pretty much be a place you can input html and css and just render it. No javascript or any scripting language for very obvious reasons, just raw HTML x CSS, which I believe would still allow to do a lot ! Maybe I can make it a bit clearer in my proposal ? I'll add this discussion as reference for the documentation channel. Or maybe there could be two modes to a documentation channel : a "simple" mode which would be a markdown editor, and then an "advanced" mode where you can do html and css ?
Permalink
Comment by @slrgt
RexSystem 1 vote originally by @slrgt on GitHub
It could just be a markdown so regular people can use it. Html and css is too much for the average person, a markdown file lets you get all the features of wikipedia people need for their own wikis
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
That why two modes could be interesting ! The default would be markdown, so that anyone can use it, but then an advanced mode would let people use CSS to make their own personal themes and such if they want. Although, I do have to recognize that an HTML mode would probably be more work to implement than just a markdown mode. But I still think the two can be interesting !
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
Ah, I missed the part about css and html. But this is what I'd like, specially for people that work on bots and such, would be a nice way of giving them the option to make better interfaces. Simple markdown won't cut it for that tho, and it would feel limited to just wiki type documents which I don't think is lacking as much as better UI features for projects in general. Having both options would be better.
Permalink
Comment by @coldreindeer
RexSystem 1 vote edited originally by @coldreindeer on GitHub 2 replies
Feature request: Built in link in bio channel type. Proposed solution: It could look smth along the lines of this perhaps. image Tbh, I don't have huge hopes for this actually being added, given there are many link in bio sites out there but having one built in would be cool! Notes (optional) Would be useful for servers with several YouTube or content creators. Suggestions are welcome.
  • 579669553-d07c4511-3a6a-4147-bdca-2e34356432ed.png

    579669553-d07c4511-3a6a-4147-bdca-2e34356432ed.png

    1919×944 | 96 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hello ! It does look like a very good idea, especially with how many servers have a "presentation" channel ! I'll add your idea to the main message.
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
Thinking about it, I like this functionality but I don't like it being restricted to channels. Being able to use it in other parts of the platform (like seeing the bio of a user you're talking to in DMs) or use them as shareable cards that then expand to reveal the whole bio would also be great. I think this feature should be be it's own thing, but also have the option of a channel that directly supports displaying a list of members who have opted-in and previewing them how you'd like. That way they could be customized and it would look better multi-platform.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub 6 replies
How about a built in guide book. Could probably add a small guide book icon in top right or smth like that. Guide Book Idea The guide book could take you to a screen showing how to use different things on Fluxer. It could have guides to showing how to use the CSS Fluxer uses for themes, maybe even how to use different channel types added. Etc.
  • 579676318-575f065d-993d-496e-bbe9-20eb8537ed3d.png

    579676318-575f065d-993d-496e-bbe9-20eb8537ed3d.png

    1919×944 | 50 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
While that's a very good idea, I do not know if it is in the scope of this discussion, as this seems like a new Fluxer feature and not "just" a new channel type ? But yeah, a built-in sort of documentation of Fluxer would be cool !
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
Well.. I'd be down for it to be a channel type if it wasn't just a thing in top right only for Fluxer to use. Could be cool if it were for both. Could be like an actual book thing with pages that turn or smth.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
So would the servers you're in be able to edit the book, like add chapters / pages ? Or would this only be a global fluxer thing ?
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
It could be both. A channel type that works like how the one that is shown in the app would theoretically work.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I added the channel type in my original message, as well as a link to this discussion. If you want to expand on your idea here, don't hesitate to !
Permalink
Comment by @vkyfox
RexSystem 1 vote originally by @vkyfox on GitHub

Document channels

TL;DR — As a compromise between a fully-fledged in-app document-editing tool and some way to go beyond markdown. I propose a very simple PDF-display channel.
Hampus — Today at 3:53 yeah, before you know it you've reimplemented Google Docs there are so many features people want when having a WYSYWIG editor for long-form text like that, including real-time collaboration and an edit history and stuff I went down that rabbit hole a long time ago trying to figure out how to implement that into Fluxer I feel like I need a more well-defined scope first :P Lilith — Today at 3:55 halfway to google slides with latex rendering North — Today at 3:55 Collaborative WYSYWIG in a chat app seems misplaced. But I guess I could see value if it was a standalone channel? kulupu sewimonsutatenpo — Today at 3:57 i do agree WYSIWYG is within scope for fluxer given discord has it. i just dunno if a reimplementation of gdocs is worth it Hampus — Today at 3:58 Discord doesn't have what I was referring to though: document channels k_tan — Today at 3:58 sounds great, it would be good support for collaborative works like notion, slack, or asana Hampus — Today at 3:58 i.e., here's a canvas to write on but what if others want to write on it simultaneously? and what if you want to revert to an older revision in history? it just spirals from there
>
Lilith — Today at 4:01 hot take Chat apps that build their own implementations or link other implementations of WYSYWIG into their app (looking at you slack, teams, and a few others) all tend to suck. I have yet to see any that don't make the app feel clunky or bogged down Hampus — Today at 4:01 yeah I really don't want to have that, it's just massive scope creep what we could have though is a middle ground where you still write regular messages Lilith — Today at 4:10 Agreed - if we ever do go into the realm of expanded wysiwyg - It will likely just build bridges that other open source projects can use to connect to (not even display in app).
To follow-up on this discussion that took place in the FluxerHQ; I wanted to propose what I think would be a very good middle-ground — A Document channel, as Hampus coined it; which would be a very basic in-app PDF viewer. I know this might sound very lackluster compared to the scope evoked in the discussion (trimmed for your convenience); but hear me out!
  1. First off, I think the production cost of an in-app PDF viewer should be very cheap, especially compared to the idea of full-blown collaborative editing; given that Fluxer is a webapp first and most web browsers feature a native PDF viewer (but I might be very wrong on how easy that should be).
  2. PDF is probably the most broadly supported format. Pretty much every software in existence has a way of exporting to PDF, be it text apps, drawing software, etc. etc. and if worse comes to worst, everything that is printable can be saved to PDF.
  3. I personally think giving users the opportunity to display their end-result rather than offering the tool to create it has the advantage of giving them the freedom to use whatever they need. As Lilith and Hampus highlighted, we are bordering on out-of-scope territory in making a fully-fledged collaborative editor in Fluxer and many other options already exist for that. By giving the ability to simply display PDFs, we give users the possibility of going beyond simple markdown with their own, preferred method. Call me old-school but I absolutely adore LaTeX, and I can't count the number of times I would have wanted to be able to share my nerdiness right there in-app rather than having to host and link to it.
    • The — moderate — downside is that the document channel is only updated as you re-upload the PDF; but I personally don't think that's really a big deal? If it's important enough to be a document rather than a chat, you probably don't want to share it mid-edition.
    • As mentioned the biggest upside to me is the ability for the user to scale their tool to their need. Want a simple text? Write it on LibreOffice and be done with it. Want a portfolio? Export it from your favourite software. Want to work on a full technical book? Host the LaTeX project on git for extensive versioning and collaborative editing. Etc, etc.

Here is a proof of concept of what it could look like

Sorry if the pixelate effects hurts your eyes, I only had a private document on hand :( poc-document-channel
  • 583862022-a4004670-da96-4c85-aa1e-fad808c9cd0a.png

    583862022-a4004670-da96-4c85-aa1e-fad808c9cd0a.png

    1071×957 | 46 kB

Permalink
Comment by @AxtraFire
RexSystem 1 vote originally by @AxtraFire on GitHub 1 reply
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
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
I wouldn't be surprised if it will happen, but I am a little surprised it would have been leaked on there instead of on here or just actually announced.
Permalink
Comment by @noisieev
RexSystem 1 vote edited originally by @noisieev on GitHub 7 replies
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.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
On PC this could be good but for mobile use I can't think of how this would work well at all.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
In terms of user friendliness I mean, since the only way I can think of would be it would collapse the list at a tap of a button every time you want to change a channel. The only reason I suggested a link in bio one work that way would be cause you probably wouldn't use it all of the time. so that hindrance wouldn't be a big problem. But if there is some way to make your suggestion user friendly I'd be happy with that.
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
On PC this could be good but for mobile use I can't think of how this would work well at all.
I was actually thinking of another solution a day after posting that, but basically a way to have channel lists with layers, and I think on mobile that may work better. Specially because my idea was you could pin whatever channels from deeper layers you'd like to see all the time on the first layer of channels for quick access, but then I thought how tedious it would be finding channels on PC having to navigate multiple layers. So I guess maybe it's better to have a different solution for each?
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
A different solution for each can be confusing for people new to the app as well as people who don't have the best memory (which seems to be like half of people over 40) lol
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
I mean a different solution for Mobile and PC. Navigating different channel types with different layouts can be just as or even more confusing. My current worry right now is that links can start to take up a lot of space for what they do, which even on mobile can be annoying to navigate if the amount of channels gets too long. But it's also nice having them be readily available from other parts of the community unlike if you were to make a channel with a bunch of links (which would be more annoying to navigate between on mobile).
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
In terms of user friendliness I mean, since the only way I can think of would be it would collapse the list at a tap of a button every time you want to change a channel. The only reason I suggested a link in bio one work that way would be cause you probably wouldn't use it all of the time. so that hindrance wouldn't be a big problem. But if there is some way to make your suggestion user friendly I'd be happy with that.
I think being able to pin channels you always want to see and have access to would solve this, but the point is to be able to organize the channel list in a way that lets you have channels you won't always use without them getting in the way. Collapsing and opening the list would only be a problem before you pin a channel you're interested in. I have no idea how well this would work for the "Link in Bio" on mobile tho, since I feel that channel type would better suited having its own type of list to be able to search members and possibly view a bit more details while navigating the list of bios before opening them (on mobile).
Permalink
Comment by @noisieev
RexSystem 1 vote originally by @noisieev on GitHub
Okay, after going over this again, I think having the option to pin channels is fine. But to better serve mobile users you could allow nested channels whose entire navigation depends on a main channel and add a "home button" between the "back button" and nested channel's name in the channel header. That way the main channel can use whatever channel template you feel like to better present what it's trying to do. Either way, discussing mobile right now is almost pointless since the Flutter app may handle the channel list differently and the layout may work better to handle these sorts of issues.
Permalink
Comment by @GooDDDevil
RexSystem 1 vote originally by @GooDDDevil on GitHub 5 replies
Guilded had some cool options for different channels; they were a huge help in organizing work and teams. That’s always been the feature I wanted most in Discord. If these new channels are available, I’ll switch everything over to Fluxer in a heartbeat. mceclip0
  • 586882468-f86f6b19-726e-44a2-a92f-a2a6bbc9b3c1.png

    586882468-f86f6b19-726e-44a2-a92f-a2a6bbc9b3c1.png

    656×754 | 66 kB

Permalink
Comment by @RaeASunshine
RexSystem 1 vote originally by @RaeASunshine on GitHub
This doesn't feel like a channel, but maybe a tool like discord's poll feature
Permalink
Comment by @GooDDDevil
RexSystem 1 vote originally by @GooDDDevil on GitHub
image These are entire channels with their own structures; if they were polls, they would be impossible to read
  • 586887063-bf0af480-c782-45b4-b31d-680d7c8a78bd.png

    586887063-bf0af480-c782-45b4-b31d-680d7c8a78bd.png

    3526×2072 | 583 kB

Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
If they do add this it would be nice if you could toggle it between a vertical layout and horizontal for showcasing the schedules. As in it could show times on top and days on left and time on top, like how twitch does it.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
I wonder who is in charge of the design for ui stuff. I'd be down to help with that stuff tbh (as in create a picture not via coding)
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hello ! I added your proposal to the main message, sorry for the long delay !
Permalink
Comment by @noisieev
RexSystem 1 vote edited originally by @noisieev on GitHub
I'm surprised that no one's mentioned it by now (nvm, just saw the part about css and html here, however I don't think simple markdown is enough for what I'd like out of something like this), but seeing as css customization is a thing and also community themes being added eventually, I think a channel that could benefit from that would be one that has its own customizable objects and classes for bot devs or any other dev to add better interfaces for their projects. 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.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub 1 reply
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: Forum channel should not be a community channel thing. Neither should stage channels. Announcement channels is fair enough to be a community tied thing if any channels should/has to be. Any thoughts?
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hello, yeah I agree ! I added a note on the original post to mention that ^^
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub 4 replies
For threads, I think we should be able to pin the thread itself into a channels pinned messages. On discord the best you can do is reply to a thread message then pin the reply. image
  • 611163448-7eb8800f-3283-4f51-9ae2-f55a5b9a4566.png

    611163448-7eb8800f-3283-4f51-9ae2-f55a5b9a4566.png

    1137×458 | 48 kB

Permalink
Comment by @coldreindeer
RexSystem 1 vote edited originally by @coldreindeer on GitHub
@alzalia1 I'm not sure how exactly it'd look as a pinned message but I was thinking it would just say the threads name and the fact it is a thread using the thread channel symbol.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
I was also thinking you could create a thread with threads listed in the thread in a nested way, which might be cool.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
Discord does this with threads already, so I'm guessing Fluxer probably will as well since threads are basically just links to a channel.
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
I agree this would be cool ! Adding it to the main message.
Permalink
Comment by @rogue-agent
RexSystem 1 vote originally by @rogue-agent on GitHub
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.
Permalink
Comment by @rogue-agent
RexSystem 1 vote originally by @rogue-agent on GitHub 3 replies
Problem Copy to share and duplicate media and mostly unsearchable are common issues among many communities and forum platforms. Proposal Having a sort of media channel that can connect to different instances of fluxer and or fediverse would allow for subscribing to one or more creators that then appear in the media feed or allow for users to post and share posts from and to fediverse through the media channel. fluxermedia Image depicting a gallery view of media that has been shared or subscribed to. A mouse cursor depicts highlighting media that then shows the amount of comments on a media and the user. An arrow next to the user allows to open a a small profile view of the creator and see in a quick view what other media they have on their account. fluxersharedmedia Image depicting a chat view where a discussion has been going on about a video that someone proceeds to link to. The link being a direct view from the media channel. It's titular text is above the media content. Next to the media you have comments made to the video that are public. Next to public comments there is a reply window to discuss about the media. The arrow allowing for a reply to the discussion about the media.
  • 616548339-dac1d532-1a5f-4d89-bc4c-3bcd64f23890.png

    616548339-dac1d532-1a5f-4d89-bc4c-3bcd64f23890.png

    1465×735 | 391 kB

  • 616548380-19a3fa36-9b6a-4389-bbdb-6266c02932b3.png

    616548380-19a3fa36-9b6a-4389-bbdb-6266c02932b3.png

    1072×690 | 96 kB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
While being able to connect to the fediverse is a REALLY cool idea, I think it may deserve its own proposal ? Like, this is a proposal for federation with this channel as a by-product (to me at least). But I can definitely still put your idea in the main message if you want !
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
No problem then ! I'll add it right away ^^
Permalink
Comment by @rogue-agent
RexSystem 1 vote originally by @rogue-agent on GitHub 1 reply
Missing threads feature and possibility to make public discussion Proposal Having a threads type system for a channel type where users of fluxer and users of threadiverse can interact per topic. fluxerforum Image depicting a list view of some threads in a forum type threaded channel. Image also contains users from outside the fluxer network who have posted, either connecting their account to fluxer or the server broadcasting the forum space publicly. Image also uses fluxer logos for samples as to where an image would be located if the topic contained an image.
  • 616549020-01531d09-b9a3-43dd-91bc-2fefe40eac80.png

    616549020-01531d09-b9a3-43dd-91bc-2fefe40eac80.png

    1453×725 | 146 kB

Permalink
Comment by @duckiducksi
RexSystem 1 vote originally by @duckiducksi on GitHub 2 replies
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. A sort option date or user filter will be also nice. 1_ZirXVTTHHL94aS2hyFEVTA like: https://support.guilded.gg/hc/en-us/articles/360038935434-Media-channels
  • 626649347-ec95fb7c-9f6e-47ea-ae06-555cd4ed006a.png

    626649347-ec95fb7c-9f6e-47ea-ae06-555cd4ed006a.png

    1307×914 | 1.0 MB

Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
As mentioned by rogue-agent, Media Channels are already present in the name of "Photo Albums" !
Permalink
Comment by @Antonio225t
RexSystem 1 vote originally by @Antonio225t on GitHub 1 reply
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 solution

I 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:
Without Subtags: Supports: Windows, Supports: MacOS, Supports: Linux, Type: Utility, Type: Fun (5 tags in total) With Subtags: Supports: [Windows, MacOS, Linux], Type: [Utility, Fun] (Only 2 tags where the first one has 3 Subtags and the second one has 2 Subtags)
Subtags will help community owners to categorize tags for easier access and less uncategorized mess.
Permalink
Comment by @coldreindeer
RexSystem 1 vote originally by @coldreindeer on GitHub
How would selecting the subtag work in practical use?
Permalink
Comment by @Data-Hoarderr
RexSystem 1 vote edited originally by @Data-Hoarderr on GitHub 1 reply

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 ?)
  • [ ] 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

  • [x] I searched for existing issues and didn't find a duplicate.
Kamalaja said to add my old post here, so I'm just going to link it: https://feedback.fluxer.com/p/1345
Permalink
Comment by @alzalia1
RexSystem 1 vote originally by @alzalia1 on GitHub OP
Hello ! There should already be a mention of "Forum Federation" on the main post ^^ I will add a mention of Discourse and GitHub Discussions still.
Permalink
Comment by @Data-Hoarderr
RexSystem 1 vote originally by @Data-Hoarderr on GitHub
I know my previous request for ethereal channels (create on join, remove when empty with channel settings in control of the person who it was created under) was closed do to the fact it can be achieved with bots. But I do think its a useful enough feature to warrant considerations for native implementations. I'd prefer not to use a bot for something like that if possible, I think not requiring a bot to achieve this would be a good feature draw to the platform.
Permalink
Comment waiting for review
Hidden by a moderator2 replies
Comment by @coldreindeer
RexSystem 1 vote Merged from #1079 originally by @coldreindeer on GitHub
If you don't mind me asking why? Is it just to de-clutter? I'll go and do that now but just curious.
Permalink