A recent version of handles some SE links in posts and show native UI instead of webview. This supports a search URL, but negative tag search URL makes wrong queries:

Of course, handles both correctly.


This will be fixed in 1.5.5 or 1.6.0.

The app will be able to handle foo+-bar, foo+[[[-[[[bar]]]]]], and foo%20not%20bar.

There are a still complex queries the app won't be able to handle, [foo] or [baz] not [bar] is currently treated as ([foo] or [baz]) and not [bar]) rather than [foo] or ([baz] not [bar]). Similarly [foo][baz] or [bar] is treated as [foo] or [baz] or [bar]. This is because the app doesn't yet support a complex tag query language.

| improve this answer | |
  • Is there any beta builds including this fix? – unarist Aug 16 '16 at 2:13
  • @unarist Not yet. I'm doing a major overhaul of the app architecture and haven't built out a beta since before I fixed this. – Brian Nickel Aug 16 '16 at 19:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .