Comment by adhesiveCheese on 03/05/2022 at 22:36 UTC*

4 upvotes, 2 direct replies (showing 2)

Things to be aware of, since this is an alpha:

There's a minor bug I'm aware of, in that fetching more resets the results length counter.
~~a link with options doesn't populate form fields yet - this is a thing I've still got to implement~~
~~There's no notification if a search fails/pushshift is down, it'll just sit on "Searching..." forever.~~
~~searching on mobile or otherwise small screens gets megasquooshed, especially if there's a thumbnail.~~

Differences from camas:

Search defaults to posts instead of comments, since this is generally my use-case
Text posts no longer show blank thumbnails, better using the available space
If searching comments, there's a "comment" title that's the link instead of the entire body serving as a link, because...
post's render markdown to html by default (there's a checkbox to toggle it off for anyone who wants to look at the raw markdown instead)
search terms are highlighted by default (again, with a textbox to toggle this off if you don't want it)
Option to disable display of thumbnails (if you don't wanna risk seeing an untagged NSFW thumbnail, for example)
Buttons to expand images in posts or comments if they're direct png, jpg, or gif links (a la RES, but without the ability to resize the image; you can only either open or close it)

I'd be happy for you or anyone else to play with it! Please lemme know if you run across any bugs/have feature requests.

Replies

2 upvotes, 1 direct replies

Please note that it's making get requests to your service with the search parameters in the referrals for most searches when searching submissions.

I'm seeing hits to `https://adhesivecheese.github.io/chearch/nsfw` and `https://adhesivecheese.github.io/chearch/default`

Seems to only occur when requesting results with thumbnails.

1 upvotes, 1 direct replies

This is very nice! It's also just 1/6th the (download) size of Camas.

Two small thoughts:

Rendered `Inline code` sticks out too much IMO.
Might be nice if the SEARCH FOR field persisted across visits in a cookie or local storage. (Your preference for Posts is fine, but this would allow us to choose.) I do like that the other fields *do not* persist; this was a minor annoyance for me w/Camas since the first thing I always had to do was clear out the fields.