pear:// URI scheme

[ryanramage]

I’m one of the maintainers of pears.com, an open-source p2p platform that also defines a custom URI scheme: pear://.

We recently have got reports by users and devs who've noticed that PearCleaner seems to also register the same pear:// handler. “pear” is a great name! — but it’s started to cause some conflicts when both are installed.

I see your deep link guide and I understand that these can be used by users to navigate to parts of the app and to add app paths.

In our case a pear://key is used to launch an app and pear://key/path/name can be used to deep link to an app. for example in keet.io we use pear:// to pass around invites to rooms.

Would you be open to chatting about this overlap? We’d love to find a path that avoids confusion for users on both sides. We can share a bit more background and see what options might make sense.

Warm regards,
Ryan

[alienator88]

Hey Ryan,
Yeah we can discuss it for sure, what sort of options were you thinking?

To add some background:

1. Pearcleaner also has a CLI utility called "pear", so these labels match in 2 places for me. If I changed one, I'd probably have to do both.
2. I know some extensions (ex. Raycast, Alfred, Automator) have been built around Pearcleaner's deep link feature using pear:// handler. All of these will break if I were to change it now.
3. From my perspective, not being familiar with your app, it would seem changing yours from pear to pears would likely make the most sense? Unless there's some requirement for it being pear in your codebase of course.

Let me know what other ideas you might have!