Import / migrate contents of a Discord server

[Gargaj]

Assuming I (as a user) provide access to an existing Discord server (either via Oauth or through an app/bot), would it be plausible to import / migrate the complete contents of a Discord server, including channels, roles, messages, hosted images...?

I'd imagine this potentially may only be relevant for self-hosted servers due to user-association / message backdating, but still.

[LazyCat2]

The best i can suggest you is this: https://github.com/LazyCat2/discord-to-revolt, it can only create channels, roles and setup permissions though.
For copying messages you need to make a bot. Please note revolt will probably be unhappy about the bot sending a lot of messages.

[Gargaj]

If I'm selfhosting, Revolt (as in the service) won't need to care.

[xsyncio]

A practically impossible task.

1. Discord bots have maximum access to the messages of the last 14 days that they can bulk_fetch.
2. And making a full-fledged scraper and legally providing that as a module to revolt will have the team involved in legal repercussions.
3. You can clone a server by making your own bot or by having to call the REST API from Discord and use the API from Revolt.
4. But the contents of a channel won't be able to get transferred, most importantly, unless all the people who've messaged in the Discord server give their user access for Discord and Revolt at the same time.
5. Unless and until there are customizations to the buckets of API from Discord, this is technically impractical.

[aScHEABL]

It's definitely technically possible, but I think it'll cause a heavy burden on revolt's end if everyone is doing it.
It's essentially the following:

1. Convert discord chat history to a json / markdown / html format. Which is relatively easy, tools like DiscordChatExporter has provided a mean.
2. Make a private bot in revolt, parse and post every chat in every text channel recursively. Which is also easy but very inefficient.

The problem with this approach is obvious.
It would be very inefficient if revolt doesn't provide us with an import functionality so we could import the chat history in one go.
With this approach, one would need to self-host the bot and it'll still take weeks if not months even if it's ran continuously.

Not to mention the storage it might take if the server has 20+ text channels dated back from 2016 onwards.
I estimated it'll be somewhere near 10~30 Terabytes. At the very least it'll be a few hundreds Gigabytes.

[Gargaj]

It absolutely wouldn't be a burden on their end if I'm self-hosting the server; and yes, that "import functionality" is the one I'd be interested in.

(And to be clear, I would be perfectly fine if this import functionality bypasses the Revolt API and just writes directly into the message history in the db on the server, which I'd imagine would speed up the process drastically.)

[xsyncio]

It's definitely technically possible, but I think it'll cause a heavy burden on revolt's end if everyone is doing it. It's essentially the following:

1. Convert discord chat history to a json / markdown / html format. Which is relatively easy, tools like DiscordChatExporter has provided a mean.
2. Make a private bot in revolt, parse and post every chat in every text channel recursively. Which is also easy but very inefficient.

The problem with this approach is obvious. It would be very inefficient if revolt doesn't provide us with an import functionality so we could import the chat history in one go. With this approach, one would need to self-host the bot and it'll still take weeks if not months even if it's ran continuously.

Not to mention the storage it might take if the server has 20+ text channels dated back from 2016 onwards. I estimated it'll be somewhere near 10~30 Terabytes. At the very least it'll be a few hundreds Gigabytes.

That is certainly a method of doing things, but the chat exporter itself gets rate-limited a bit too frequently; also, unless the Discord chat stream and socking messages on Revolt are always in constant data transfer, processing a humongous JSON itself consumes a lot of resources. On a general gaming laptop, you can't open the chat itself if it's older than 4 years and it's from an active server. I am using an advanced wrapper for Revolt, and I don't think I've seen webhooks in the docs until now. That makes it more difficult to make a copy of message data from avatars, messages, and/or attachments. Even if it's hosted locally. Unless, that is, you use your own token, like a self-bot (illegal and gets banned within 1000-2000 requests on average) and stream the messages from Discord to Revolt message by message, so it is possible but would be messy at execution. @Gargaj this is a reply for your counter point as well.

[Gargaj]

A couple of megabytes isn't "humongous", and again, self-hosting and rate-limiting makes this trivial: data-in and data-out.

Hell, let's make a concession: give me a way to insert backdated messages into my self-hosted Revolt server and I'll take care of the rest.

[IAmTomahawkx]

we won't be implementing message scraping from discord. You can add records to your database as you wish, but this is not a feature we'll be supporting due to the legal questionability of it. Enabling others to do this on their own instances could still bring us under fire if discord wishes to do so.