What is necessary to make Lazarus Recovery reappear in Chrome?

[benelot]

Hello there!

I really liked the Lazarus Recovery extension and was sad when it was suddenly gone from the store. I would like to help out making it available again on the store. I am not sure if I am suitable as a maintainer after that, but I think getting it up and running would be a great start.

That is why I ask here:

• Is this the original source of the Lazarus Recovery Extension for Chrome?
• What is required to add it to the Chrome Store again?

[orschiro]

@benelot check https://chrome.google.com/webstore/detail/form-recovery/hbeeodhdgnjpdiioghaojiajkaomnjed.

[benelot]

Nice, thanks for doing this. Is this the version that is in this repository? Or are you maintaining it somewhere else? I think announcing it and allowing the community to help you maintain it would simplify the maintenance for you.

[orschiro]

Nice, thanks for doing this. Is this the version that is in this repository?

Yes. I just did some minor changes for the manifest file to validate.

Or are you maintaining it somewhere else?

I forked it https://github.com/orschiro/form-recovery

I think announcing it and allowing the community to help you maintain it would simplify the maintenance for you.

Ideally we all keep contributing to this parent repository. I will ensure to feed those improvements back to my fork which is then published onto the extension store.

[Billiam]

@orschiro It appears yours has now been removed from the Chrome store as well, why is that?

[orschiro]

I have no idea, sadly.

Billiam notifications@github.com schrieb am Mi. 19. Feb. 2020 um 20:52:

@orschiro https://github.com/orschiro It appears yours has now been removed from the Chrome store as well, why is that?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lazarus-recovery/chrome_patched/issues/6?email_source=notifications&email_token=AABJXQ4P5OHCXN6KE3IOKBLRDWEY3A5CNFSM4GHPQMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMJINPQ#issuecomment-588416702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJXQ4INVWKBR2H2SKATPLRDWEY3ANCNFSM4GHPQMOA .

[benelot]

I think you need to reupload at some frequency for an extension to be considered "Maintained". Check if you can reactivate it again and upload a "new" version.

[devnoname120]

@orschiro Your fork still has a greyed out extension button on the current Chrome version (104.0.5112.79 (Official Build) (arm64)). Any ideas how to fix it?

[orschiro]

Sorry, but I currently don't have any time to work on a fix. :(

On Mon, 8 Aug 2022, 09:45 Paul, @.***> wrote:

@orschiro https://github.com/orschiro Your fork still has a greyed out extension button on the current Chrome version (104.0.5112.79 (Official Build) (arm64)). Any ideas how to fix it?

— Reply to this email directly, view it on GitHub https://github.com/lazarus-recovery/chrome_patched/issues/6#issuecomment-1207781184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJXQZDZVDNAD6SVM5NGA3VYC3JZANCNFSM4GHPQMOA . You are receiving this because you were mentioned.Message ID: @.***>

[sierracircle]

None of us are

[janez33]

RIP Lazarus 👋

[devnoname120]

I've been using Form History Control (II) as an alternative and I haven't had any issues so far.