[Feature] Add 2fas import option

[vertigo220]

Describe the problem this feature would solve

Currently can import accounts from Aegis and another authenticator via .json file, but cannot import from 2fas using their .2fas file format.

Describe the solution

Add another import option for 2fas accounts.

Describe alternatives you've considered

May be able to go from 2fas > Aegis > 2fast, but more of a hassle and more risk of something going wrong.

Additional context & Screenshots

[vertigo220]

Update: Discovered that despite using a .2fas extension, their files are supposedly .json files, so tried renaming it and using both Aegis and AndOTP options but both gave errors. Not sure if due to being password-protected (though I of course entered the password, twice to be sure I was typing it correctly, but maybe it's a matter of how it's protected), or a different .json format, or the fact you have to specify the type and it's neither of those, and maybe it's very specific based on that (maybe there should just be a generic option). In any event, these two apps do not seem compatible, which is problematic and holds both back.

[jp-weber]

The different services have their own format and need to be adapted. I'll have to see if i can support new formats in the next version.

[vertigo220]

When doing this, I'd suggest making the file selection accept both .json and .2fas so the user doesn't have to worry about changing the extension or even knowing about that. I've suggested to them they change to a .json extension, but better to not depend on that.

[jp-weber]

Yes the file extension is adjusted accordingly. If individual services would switch to a file extension like .json there would be no advantage as it depends on how it is structured internally and pretty much most of the ones I have seen are JSON based. The 2fast app uses .2fa as the file extension, which internally contains an encrypted JSON format.

[vertigo220]

Yes the file extension is adjusted accordingly. If individual services would switch to a file extension like .json there would be no advantage as it depends on how it is structured internally and pretty much most of the ones I have seen are JSON based. The 2fast app uses .2fa as the file extension, which internally contains an encrypted JSON format.

Right, but my point is that currently, the file selection dialog in 2fast limits it to .json, so it won't even show their .2fas files, regardless of the fact they're really .json files. So the file type in the selector needs to be adjusted to even be able to see and select them.