I've never used Pocket, and upon seeing it in the Firefox UI, immediately searched for how to hide it. I'm the wrong person to ask. :)

But if I were to embrace such features, I'd have a naive question: why do I need to unclutter an article to access them? If I'm perfectly happy reading a normally rendered page and see a phrase I want to annotate, I won't want to break my flow by uncluttering first. This emphasizes to me that these features feel like they belong in two separate extensions.

Good point. I actually wanted to address this "breaking the flow" with the "keeping the style of the original site" approach for Unclutter, vs. reader modes that have a totally different reading UI.

But maybe that's not working out completely. Thanks for the feedback!

Yeah, I think the re-render(?) breaks flow as completely as traditional reader mode, it doesn't matter that the uncluttered version retains some of the look of the original. If the text doesn't stay in the same place, flow is broken. In addition it seems there's some animation affect in the original->uncluttered transition that makes it slightly more jarring, but is not fundamental.

Thanks for unclutter, careful listening to feedback in this Show HN post, and pointing out your inspirations at https://news.ycombinator.com/item?id=33718859! Though I've never connected with its functionality beyond reader mode (in any tool), I'd love to at some point, but it's hard to get right in a way that doesn't become burdensome or transitory. I want browsers to become much more powerful user agents. Stuff like hypothes.is that I see you've integrated with is super cool, just not there for me yet. Godspeed!

That would require to sync your library on your Firefox account, right?

Yep, Pocket has an API for this.