3 ms·
Fair-ish. Certainly some types of services have an incentive to allow you to import, as a way of making it easier to move to them. Like an email hosting servi
by kelnos 3y ago
Fair-ish. Certainly some types of services have an incentive to allow you to import, as a way of making it easier to move to them. Like an email hosting service would want to make it easy for you to move your old emails to them when switching.
I could understand why a Twitter alternative might not want you to be able to import a ton of old posts at once. But this is why we need open standards and open source. Some random large Mastodon instance might not want to allow imports, but you should at the very least have the option to spin up your own instance, import all your old Twitter posts, and still participate in the ecosystem.
As others have pointed out, an @tag can still be useful by linking back to the original service. Or the importer can support a username mapping so it can rewrite names from the old service to names to the new service. Sure, all of this requires extra work, but it can be possible if people care enough.
Regardless, export functionality at the old service is the first necessary step. Even if there's no import on the other side now, someone might build one eventually. And even if that never happens, being able to archive your old data is useful by itself.