Interface between the module GUI and the LSPosed manager.

[yashikada]

I'm using the latest version of mywalkb/LSPosed_mod, now the project is abandoned and not archived, I would like to update to this new version of LSPosed, I saw that some patches of mywalkb have been copied from his repository.
Are you planning on importing its API?

I saw you support libxposed, which has also been abandoned.
Can a module control its scope with libxposed?

[JingMatrix]

As project maintainer, I have my own design of architecture, and will listen to user feedback / requests for certain features.
I suggest that you simply try out and share your idea of what you would like have in the future.

There is no reason for me to blindly import some work without deliberation / conception.

libxposed is not abandoned as you may imagine, it is a suit of well-designed API. Not updating doesn't imply deprecation.

Yes, a module can control its scope with libxposed.

[yashikada]

I suggest that you simply try out and share your idea of what you would like have in the future.

I'd like my module to control its scope without being treated as malware.
The original authors of LSPosed always treated modules as malware that shouldn't be able to control anything; only the user can set the scope.
libxposed came out too late, so I started using the mywalkb API.
Now, if libxposed does the same things, it's better, so there's no reason not to use it.

If the module is developed by me or someone I trust, I think it should be possible to configure it on LSPosed so as not to be too annoying with authorization requests.