ifme VS docuseal

ifmeorg/ifme- 2 pull requests

Similarly, I spent a significant amount of time setting up the ruby on rails project of if-me for Hacktoberfest. It was hard and I wanted to give up in the middle, but every time I wanted to quit – there was this invisible force inside me that would kick in and make me go on.

On a more positive note - I did write all the other tests required. I sent a PR anyway, even though I could not cover all lines.

Unknown if it's better or worse but https://support.google.com/docs/answer/12315692?hl=en ("Send signature requests & sign documents with eSignature")

and there have also been a bunch of alleged competitors submitted:

https://github.com/docusealco/docuseal#readme https://news.ycombinator.com/item?id=36798593

https://github.com/OpenSignLabs/OpenSign#readme https://news.ycombinator.com/item?id=38052344

https://github.com/documenso/documenso#readme https://news.ycombinator.com/item?id=38404129

but they're all AGPLv3 and the network effect is very real

Docuseal might also do the same and it's open-source

I mostly agree with the author. After working a couple of years with React client render and API a pure server render seems to be a way more productive. For my recent OSS project (https://github.com/docusealco/docuseal) I use server render everywhere except of the 2 most complex/dynamic UI parts (drag&drop form builder and the signing form). I think just figuring out which approach fits best for which part of the software is the most important thing, doing both SSR and CSR in a single project is completely fine when done right.

There are alternatives: https://github.com/docusealco/docuseal

I would like esignatures to be backed by strong electronic authentication, like EIDAS