You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
one flavor embeds the library (and splits per ABI)
one flavor simply adds support for loading it from an external app, but falls back to using the default/native HTTPS Security Provider if it isn't found
if the author wants to merge my branch he can..
strictly speaking, there's not currently any merge conflict.
the changes are pretty extensive though, so it's unlikely that he will.
actually.. come to think of it,
since I split the original project in half.. merging won't work;
he would need to cherry-pick my commits (skipping the 1st one that removes half the repo).
A really great project and I am very thankful, that it exists.
I used this project a lot, sadly the author does not have much time, so I am creating a fork in rust right now, with a rest AP rather than this line based API the original repo has.
I will support the line based API in my fork, but will not add any features to it, my new API might get.
admittedly, I haven't used it very much.. but it seems to work perfectly.
I can certainly see situations where it will be incredibly useful.
that said.. I forked your repo.. twice:
but falls back to using the default/native HTTPS Security Provider if it isn't found
on the free-tier of the hosting provider: render.com
this was mainly done for fun.. and for my own use,
but I figured I'd share links in case anybody else here might find it useful.
thanks again.. great app!
The text was updated successfully, but these errors were encountered: