News for hackers. Stuff that matters.
Re:Memex: Browser Extension to full-text search your browsin... by BlackForestBoy on Monday October 21, 2019 @06:55AM (#21310830)
Oliver here, from the Memex team

By default that setting is disabled, but you can change to full indexing in the onboarding or in the settings.

Re:Memex: Browser Extension to full-text search your browsin... by rane on Monday October 21, 2019 @10:09AM (#21312414)
Thanks, I found it.

The label for the setting is unclear.

> [ ] Visited for at least n seconds

Given that the setting above it says "Make title and URL always searchable (recommended)", I think the setting for this option also should be something like:

> [ ] Make pages visited for at least n seconds full-text searchable

It's difficult to connect the grey text that says "Which websites do you want to make full-text searchable?" to the label of the option that controls full-text searching.

context: https://i.imgur.com/2p7OyHJ.png

Re:Memex: Browser Extension to full-text search your browsin... by BlackForestBoy on Monday October 21, 2019 @11:07AM (#21313132)
Great feedback. Will incorporate it in the upcoming UX/UI updates. Thanks for the effort to make us aware.
Re:Memex: Browser Extension to full-text search your browsin... by tiborsaas on Monday October 21, 2019 @09:29AM (#21311995)
> By default that setting is disabled

Why, might I ask? Your tagline is full text search, but I have to turn it on?

"Full-Text Search your Web History & Bookmarks"

I'd reconsider the landing page hero section design. Don't write with black on darkgray background.

https://imgur.com/a/hgZrerp

Re:Memex: Browser Extension to full-text search your browsin... by BlackForestBoy on Monday October 21, 2019 @11:10AM (#21313171)
> Why, might I ask? Your tagline is full text search, but I have to turn it on?

It was a trial we added in the last onboarding overhaul 2 weeks ago. Will already be changed in the next update.

> I'd reconsider the landing page hero section design. Don't write with black on darkgray background.

Yeah that is a bug from the last (automatic) wordpress update. Will be fixed soon too. Thanks for making us aware. :)