🌀 Misskey 帳戶遷移實際會遷移哪些資料？ / What data is actually migrated during Misskey account migration?
General Discussion
1
Posts
1
Posters
5
Views
-
🌀 Misskey 帳戶遷移實際會遷移哪些資料？ / What data is actually migrated during Misskey account migration? / Misskey のアカウント移行ではどのデータが移行されますか？
⸻
🇹🇼 中文 / Chinese (Traditional)
最近在研究 Misskey 的「帳戶遷移」功能，想更清楚了解它實際會遷移哪些資料。
目前看起來它會轉移「追隨與被追隨」的關係，但我不確定是否也包含：
• 使用者頭像、橫幅與簡介
• 貼文、圖片與附件
• 使用者設定與偏好
另外，如果兩台伺服器之間的聯邦協議（ActivityPub）通訊正常，是否代表遷移時能自動同步所有可用資料？
我想確認 Misskey 的帳戶遷移到底是偏向「社交關係導向」（像 ActivityPub 的 Move 活動），還是能完整搬移內容與媒體的「資料轉移」。
如果有開發者或懂協議的朋友能說明一下，會很感謝 🙏
⸻
🇬🇧 English
I’m trying to understand how Misskey account migration actually works.
From what I’ve seen, it seems to transfer followers and following, but I’m not sure if it also includes:
• Profile info (avatar, header, bio)
• Posts, images, attachments
• User settings or preferences
If both instances communicate properly over ActivityPub, does migration automatically sync all available data?
I’d like to know if Misskey’s migration is more like a “social relationship redirection” (similar to ActivityPub’s Move), or a full “data transfer” including posts and media.
Any insights from developers or experienced admins would be appreciated 🙌
⸻
🇯🇵 日本語 / Japanese
最近、Misskey の アカウント移行 機能について調べています。
実際にどのデータが移行されるのか、もう少し詳しく知りたいです。
現時点では、フォロー／フォロワー関係は引き継がれるようですが、
次の項目も含まれるのでしょうか？
• プロフィール情報（アイコン、ヘッダー、自己紹介）
• 投稿・画像・添付ファイル
• ユーザー設定や環境設定
また、サーバー間の ActivityPub 通信が正常な場合、自動でデータ同期が行われるのでしょうか？
Misskey のアカウント移行は ActivityPub の Move のような「ソーシャル関係の移動」なのか、
それともユーザーコンテンツを含む「完全なデータ転送」に近いのか、
開発者や詳しい方の意見をお聞きしたいです 🙏
⸻
#Misskey #帳戶遷移 #アカウント移行
#ActivityPub #聯邦宇宙 #フェディバース
#Fediverse #DecentralizedSocial #分散型SNS
#AccountMigration #資料同步 #データ移行
#MisskeyDev #技術討論 #技術交流 #技術的議論
#SelfHost #OpenProtocol #オープンプロトコル
#FediverseTech #MisskeyCommunity #Misskey開発
⸻
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@pixelschubsi @tris Yes, agreed. Tremendous value in reusing identities and login credentials. Big skepticism with regards to using AP as a protocol. One can probably kinda make it work… But why? What’s the benefit?
-
@daniel @tris I'm also genuinely surprised that people believe that ActivityPub, a protocol even named after its purpose, to publish activities, is a good protocol to pursue private instant messaging. The goals of those two couldn't be more detrimental.
I do see a purpose of being able to reuse your "ActivityPub identities", which actually are just WebFinger identities. Maybe someone should specify how to discover XMPP accounts via WebFinger and push that as a solution for AP messaging?
-
@tris Soatak is an expert in cryptography. I’m not. I’m more than happy to stand on the shoulder of giants when it comes to E2EE. That’s why we used the Signal Protocol 10+ years ago for #OMEMO and are now looking towards #MLS. However, good, interoperable protocol design is so much more than just E2EE. And maybe I've learned a thing or two about protocol design in my career that they don’t necessarily know.
-
@tris there are three actively developed protocols for federated instant messaging (XMPP, Matrix, Deltachat). At least one of them is very open to new developers and new ideas and has a structure in place to collaboratively work on those ideas and bring various stake holders together. With no disrespect to that individual I don't see why there needs to be a forth protocol loosely based on ActivityPub.
-
@daniel Ah, fair, their work for E2EE Fedi looks interesting: https://github.com/fedi-e2ee/public-key-directory-specification
-
@tris two things: I already said in my follow up post that if someone wants to build their own clients on top of XMPP and prefers MLS over OMEMO, the XMPP community is very open to that. A protocol is much more than just the encryption. They would still benefit from all the other things XMPP has solved.
A lot of what's in that blog post is ill-informed and bordering on disinformation and fear mongering.
-
@daniel Someone have to solve https://soatok.blog/2024/08/04/against-xmppomemo/ issues first
-
@dragospirvu75 @matrix @delta @lazarus The way to achieve interoperability is to stop reinventing the wheel and agree on one standard. Implementing three protocols is completely unfeasible and unnecessary. This worked 20 years ago with MSN, ICQ and AIM when IM protocols had a lot less features and no E2EE. Doesn’t work today.
