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
This service is super useful in certain cases, one of them being deep links within pages that explain XPrivacy restriction, such as this Linux man page. I'd be happy to contribute deep links to XPrivacy, and I expect that the project's maintainer will want to ensure that the links will stay functional for a while.
Hence, what are the long-term plans for linklink? A domain name would be a good start to suggest a more stable operation.
The text was updated successfully, but these errors were encountered:
Glad to hear it. I definitely think a lot of sites and users could benefit from having more control over what they link to. I see linklink as a potential counterpart to bitly.
I expect that the project's maintainer will want to ensure that the links will stay functional for a while.
I plan on supporting linklink url formats as they evolve. I have ideas on making the url formats easier to digest.
I also want to switch to a better deep linking algorithm that fixes a bunch of the cross-device issues. This would only result in additional information in the url, keeping the support of older link structures.
What are the long-term plans for linklink?
I originally just built this as a prototype. I have a few ideas moving forward:
Switch to a GPL license only to prevent others from forking it for profit.
This service is super useful in certain cases, one of them being deep links within pages that explain XPrivacy restriction, such as this Linux man page. I'd be happy to contribute deep links to XPrivacy, and I expect that the project's maintainer will want to ensure that the links will stay functional for a while.
Hence, what are the long-term plans for linklink? A domain name would be a good start to suggest a more stable operation.
The text was updated successfully, but these errors were encountered: