Open links by default for issues and mr #3

...so Labnex will open when I click a gitlab.com or any other server I logged in link

I think we are talking about something like deep links here.

For that, I will need to collect some data on the popular instances.

1- https://gitlab.com
2- https://framagit.org
3- https://dev.gajim.org
4- https://gitlab.alpinelinux.org
5- https://code.videolan.org
6- https://gitlab.xfce.org
7- https://invent.kde.org
8- https://gitlab.gnome.org
9- https://code.briarproject.org
10- https://salsa.debian.org
11- https://gitlab.e.foundation
12- https://git.fosscommunity.in
13- https://gitlab.freedesktop.org
14- https://git.coop
15- https://gitgud.io
16- https://gitlab.haskell.org
17- https://git.jami.net
18- https://lab.libreho.st
19- https://git.oeru.org
20- https://0xacab.org/
21- https://git.pleroma.social

Please add other popular servers in the comments section.

I think we are talking about something like deep links here.

yes, but in the Android UI it's not called "deep links" :)

Please add other popular servers in the comments section.

about that, can these be added by the app, eg. I log with https://dev.gajim.org, can the app add this to the "open by default"?

Because this "feature" sounds more targeted to siloed sites that have one client, one domain. Eg. If self-host my Gitlab do I need to fork your app? That's dum- 🤷

yes, but in the Android UI it's not called "deep links" :)

Dayum... :)

Last time I checked this for GitNex, unfortunately, Android does not add anything to the Manifest file at runtime. To make this work, it has to be added before compiling.

If anyone knows another way to do this, I’m completely open to it.

Regarding adding instances, I’m fine with adding personal ones as well.

I like the way LabCoat does it (though incomplete):

1. use labcoat:// URL scheme for any gitlab instance.
2. handle at least 1 well-known URL (gitlab.com)
3. have some app to translate https://known.gitlab.instance to labcoat://known.gitlab.instance

The latter app has alternatives for now:

1. https://gitlab.com/nomadlabs/deeplinks/
2. https://github.com/TrianguloY/UrlChecker/issues/389

@ildar Thanks for your input.

I am personally not in favor of using another app for deep links. LabNex can handle that when implemented properly.

The LabCoat deeplinks app work the same way by adding domains to the Manifest file and opening them via the LabCoat URI to launch the LabCoat app.

That is the reason I asked to share as many popular links as possible here.

GitNex right now does this too.
https://codeberg.org/gitnex/GitNex/src/branch/main/app/src/main/AndroidManifest.xml#L203
gitnex/GitNex@9673def07c/app/src/main/java/org/mian/gitnex/activities/DeepLinksActivity.java

I would be interested to know what they are doing differently without the Manifest file.

fine!
then take a look at https://gitlab.com/nomadlabs/deeplinks/issues/

• https://gitlab.alpinelinux.org/

Have eta for this issue? I see the new major releases out...

No eta. I just pick and choose issues or features to add.

But if someone want to work on it, they are most welcome to send a PR. :)

It might be possible to design labnex directly as a browser application, so that the system can select labnex when it opens.
of course, it would also be possible to maintain a list of mainstream instances at the same time.

to design labnex directly as a browser application

this approach is overcomplicated. The best approach IMHO is to have an own
URL scheme (like labnex://...) and URL translator like
https://github.com/TrianguloY/URLCheck/issues/389#issuecomment-2408463033

I'd also vote for solution like @ildar suggests, or something similar, as I'd very like to use LabNex not only for links to "popular" instances, but (mostly) to my private instances.
And IIRC, manifest thing is not the way for this, as it doesn't allow to make dynamic lists, or modify it after installation (or does it?)

Alternatively, it is possible to use "*" as supported domains (as, for example, openkeychain does), I guess?
It will make it possible to select labnex in "open with" dialog.

I'd also suggest something like "gitlab.*", but not sure, if it is supported at all.

But yes, idea with custom scheme + some url rewriter looks kinda acceptable too, I guess

It seems most users are comfortable with a custom URL scheme such as labnex://. In this case, the URL will be handled by another app, reducing the burden on LabNex. :)

I can't promise an exact timeline, but I plan to implement this in one of the upcoming releases.

To recap:

• LabNex will implement the labnex:// custom URL scheme.
• Third-party apps can redirect traffic to LabNex via labnex://.
• Other apps provider will need to include labnex:// in their apps.

It seems most users are comfortable with a custom URL scheme such as labnex://. In this case, the URL will be handled by another app, reducing the burden on LabNex. :)

I can't promise an exact timeline, but I plan to implement this in one of the upcoming releases.

To recap:

• LabNex will implement the labnex:// custom URL scheme.
• Third-party apps can redirect traffic to LabNex via labnex://.
• Other apps provider will need to include labnex:// in their apps.

+1 for this. I always use Gitlab links from browsers and messaging apps and would love for LabNex to handle them directly via deep links

@Sahibishere it will not be directly handled by LabNex. You will need another app to redirect you to LabNex. Browsers, email clients and messaging apps does not have url scheme handling for individual apps like LabNex.

Flow:
Link in email -> Third party app -> LabNex

@Sahibishere it will not be directly handled by LabNex. You will need another app to redirect you to LabNex. Browsers, email clients and messaging apps does not have url scheme handling for individual apps like LabNex.

Flow:
Link in email -> Third party app -> LabNex

Sorry would any app that intercept links to browsers support this app or would you need a specific app which allows you to create rules for certain urls, I am kind of confused. Thanks much

Sorry would any app that intercept links to browsers support this app or would you need a specific app which allows you to create rules for certain urls, I am kind of confused. Thanks much

@Sahibishere let me explain.

I don't know about any app which currently has labnex:// scheme and no app I can recall for now would do url forwarding. Other users can help each other and mention the app names. And if possible open an issue or PR in that project to add labnex:// url scheme.

Ok, now to the explanation bits. Let's say you have a URL from gitlab issue for a project which you received via an email. You click on the link in the email, a third party app which you would have installed (and has labnex:// support) will intercept the URL and opens LabNex app. From there LabNex will handle the URL and forward you to the issue in the app.

Other apps only need to implement labnex:// URL scheme to forward all requests to LabNex, that's it. The rest LabNex will take care of.
So any app which has labnex:// support will work.

This feature is not added to LabNex yet, will be added in the next release which is 7.0.0.

Hope this clears the confusion.

Sorry would any app that intercept links to browsers support this app or would you need a specific app which allows you to create rules for certain urls, I am kind of confused. Thanks much

@Sahibishere let me explain.

I don't know about any app which currently has labnex:// scheme and no app I can recall for now would do url forwarding. Other users can help each other and mention the app names. And if possible open an issue or PR in that project to add labnex:// url scheme.

Ok, now to the explanation bits. Let's say you have a URL from gitlab issue for a project which you received via an email. You click on the link in the email, a third party app which you would have installed (and has labnex:// support) will intercept the URL and opens LabNex app. From there LabNex will handle the URL and forward you to the issue in the app.

Other apps only need to implement labnex:// URL scheme to forward all requests to LabNex, that's it. The rest LabNex will take care of.
So any app which has labnex:// support will work.

This feature is not added to LabNex yet, will be added in the next release which is 7.0.0.

Hope this clears the confusion.

Ok thanks much, I understand now, I have created issue of my app that I currently use which purpose is to allow choosing which app to open from links, thanks

I don't know about any app which currently has labnex:// scheme and no app I can recall for now would do url forwarding.

This is URLCheck app I mentioned in https://github.com/labnex/LabNex/issues/3#issuecomment-2410525306

It can mutate normal URLs like http://gitlab.YOUR_PRIVATE_INSTANCE.com/... to labnex://gitlab.YOUR_PRIVATE_INSTANCE.com/... and launch this new URL. Then Labnex is opened to handle it.

Gitnex got deeplinks recently. Hope Labnex will reach the same soon!

LabNex will have custom URL scheme labnex:// and some deeplinks in the next release.

now deeplinks work in GitNex. Hope we'll see in LabNex quite soon..

@ildar yes, it is coming to LabNex too in 7.0.0.