Replies: 2 comments
0 replies
|
This has moved to feedback.fluxer.com: https://feedback.fluxer.com/p/1202 Comments and votes came along with it. Sign in with your Fluxer account, then go to Settings > GitHub account to claim your posts and comments from GitHub. This thread is now locked. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Problem
People who migrate from Discord to Fluxer often lose their entire history in the process. For example I have a private server with my friends that I've had for 2 years now, and the discussions there are precious to me, so I am planning to make my own script to transform an export of that history into a somewhat convincing Fluxer history on a self-hosted instance.
Proposed solution
It would be insanely useful if Fluxer supported that out of the box. It would be a lot better if everyone could benefit from something like this even on the main instance.
The biggest issue to think about is how accounts should be handled in a feature like this. There would need to be a tool to associate a specific user ID with a Fluxer account, but there would need to be stuff in place to prevent people from being able to easily fabricate messages and make it seem like a Fluxer account really said them. Maybe something like, prompt the user for consent just like the way user invites work, or have some history claiming system where a Fluxer account joins the server and an interface allows them to claim that this account was their messages and have the admin confirm.
Notes (optional)
No response
Checks
All reactions