typio-form-recovery-reboot

typio-form-recovery-reboot copied to clipboard

I hope you continue with the update of this project.

This extension is absolutely necessary, and there is no alternative.

I'm not programming savvy, but there are users on Reddit who can help with upgrading to Vue 3.x:

https://www.reddit.com/r/chrome/comments/10kuzoq/any_alternative_to_typio_form_recovery/

I hope you continue with the update of this project.

This extension is absolutely necessary, and there is no alternative.

I'm not programming savvy, but there are users on Reddit who can help with upgrading to Vue 3.x:

https://www.reddit.com/r/chrome/comments/10kuzoq/any_alternative_to_typio_form_recovery/

cool you're amonteirosantos ?

How exactly do I implement / install this please? https://github.com/tsukumijima/typio-form-recovery-reboot/issues/2

So I download typio-form-recovery-reboot-master.zip or typio-form-recovery.zip? And then what please?

I really appreciate you forking the defunct Typio. Looks like it is working for me now. I know that it will be necessary to update the manifest.json to the v3 standard this year. I'd be happy to donate to help get that across the finish line.

I hope you continue with the update of this project. This extension is absolutely necessary, and there is no alternative. I'm not programming savvy, but there are users on Reddit who can help with upgrading to Vue 3.x: https://www.reddit.com/r/chrome/comments/10kuzoq/any_alternative_to_typio_form_recovery/

cool you're amonteirosantos ?

How exactly do I implement / install this please? #2

So I download typio-form-recovery-reboot-master.zip or typio-form-recovery.zip? And then what please?

Sorry I didn't realize the Issue had been up for a while. I forgot to put on [Watch] when I forked it, so I was not notified that the Issue had been commented on.

I am surprised that this fork is being talked about in the international community. I am Japanese and do not use Reddit. This fork was also developed as an adaptation for the time being, as I was in trouble myself. Note that I am not motivated enough to upload the file to the Chrome Web Store. I am not even sure if it will pass the screening process.

ctsstc is trying to migrate this fork to Vue 3.x, but it is a work in progress and currently not working properly. Manifest V2 is supposed to be deprecated by the end of 2023, in a manner of speaking. However, it is believed that it may actually be postponed indefinitely. Of course, I would not recommend new adoption. Against this background, this fork aims to keep changes to the source code to a minimum, and to make it work as it always has.

The original source code is very good, but the code is legacy as of 2023 (it is not even written in TypeScript!). I am not motivated enough to continue maintaining this fork. Nevertheless, I have a local install of this extension and use it daily, so if it ever stops working again due to browser spec changes, I will try to fix it to work as well as possible.

@tsukumijima that makes sense. Either way thanks a lot!

I will follow @ctsstc with the efforts and try to help if possible.

Haha I didn't realize someone forked it and created a buzz.

I halted work on it when the whole licensing aspect came up after I had starting doing some larger refactors across the code base trying to modernize it. It has been running just fine on my machine for quite some time. I just didn't know about moving forward with it all since my main focus was going to be to take it over, remove donation links in case the original author truly is gone so that people aren't donating to a black hole potentially. That all felt quite iffy with the license in place.

@ctsstc the license issue is IMHO a non-issue - see the dual-licensing I proposed in https://github.com/ctsstc/typio-form-recovery-reboot/issues/6#issuecomment-1508489357

The only issue which will remain is the donations. But that is actually not our issue - it is simply an issue of the donators.

Thank you so much @tsukumijima !