Where Does Moshidon Store Accounts and Drafts?
Moshidon keeps accounts and drafts in private storage under its verified Android package, with settings import and export for logged accounts.
Last updated
Moshidon is a Mastodon fork with the package to prove it. The verified ID comes straight from the build file, distinguishing it from similarly named clients. Accounts multiply inside with cross-posting across them.
Drafts and scheduled posts live locally with editing in-app while timelines refetch from servers. Settings export covers logged accounts without sessions. Internal database names stay unquoted for lack of documented sources.
Where Moshidon stores this, by platform
/data/data/org.joinmastodon.android.moshinda
Private storage for the build-file-verified fork package with accounts and local drafts inside. Settings export covers preferences without sessions. Internal filenames stay unpublished.
Frequently asked questions
How do I move Moshidon to a new phone?
Use the settings import and export flow for logged accounts, which covers preferences but not sessions. Drafts and scheduled posts stay in local storage with server timelines refetching on login. Repos span GitHub, Play and F-Droid with matching builds.
What is the real Moshidon package name?
Use org.joinmastodon.android.moshinda from the build file and store listings. Similarly named variants belong to other forks. Nightly builds add suffixed IDs of their own, so match the variant before scripting paths.
Do Moshidon drafts sync?
They persist as local drafts with editing and scheduling in-app. Server timelines refetch while unsent work stays on the device. Export settings separately since drafts travel outside that file.
Notice an outdated path? Let us know.