Live data from Hacker News

Show HN: Never lose a website again

fetching.io

61–70 of 80 posts

Re: Show HN: Never lose a website again

#61
post #21

Two issues with your landing page 1. major - Breaks back button 2. minor(nitpick) - If I click on the green "notify me" button and then "cancel" on the prompt dialog instead of "OK", it still shows me the green "Success - you will be notified" message Good luck though!

"Never lose a website again" ...because you will never leave this one.

Ha!

Re: Show HN: Never lose a website again

#62

To be blunt, this project will never gain traction because not enough people are willing to store their browsing history somewhere outside of their control. The back button issue shows a lack of attention to detail. Something that's extremely important when dealing with sensitive personal data.

Please know this is the first exposure this project has ever had. I really did try, in my spare time, to get this thing perfect before soliciting feedback from this wondrous community but -- alas! -- there be bugs. It's this kind of feedback that I was seeking and I intend to incorporate as I drive towards a broader release.

Part of what I'm trying to validate is exactly the point you raised: will people generally be too freaked out to store their browsing history "in the cloud"?

The next thing I'm hoping to determine is if it'll be enough to encrypt this content is such a way that people are OK with it being stored externally or if only a locally installed version will do. Security aside, there's a great deal of advantage to offer this service hosted.

Thanks for your feedback!

Re: Show HN: Never lose a website again

#63
post #12

Earlier quoted context omitted.

You are right! I'm working on a fix.

Out of curiosity, what are you doing with such a simple site (and I don't mean that in a bad way) that requires any conscious effort to fix? It seems like you really need to go out of your way to fuck up the back button and for a fix to be "work". But, recent nuanced trends in web design/navigation aren't my top skill, so I'm asking the question honestly.

Honestly, I've been taken a bit by surprise that the back button bug has been such a big issue. I did some testing among friends (with a group of five or so startup, programmer types) and, believe it or not, it never came up.. That said, it'll be fixed in short order.

To the other comments, the service is considerably more complex (and yes, built on Meteor, MongoDB and ElasticSearch) as it serves up search results and updates in real time. Though the UI is simple, it does take a fair bit of effort to organize all the browsing information and index such that search results are relevant.

Re: Show HN: Never lose a website again

#64
post #41

Why server side indexing and not use something like lunarjs[1] from the beginning? Like the Idea of fulltext search on history, but I'm not going to send my full history to some random dude on the internet. No offence intended:) [1] ”Simple full-text search in your browser” http://lunrjs.com/

None taken! I looked at lunarjs (and a few other options) but felt that the more sophisticated features of ElasticSearch were worth it (at least to me).

I'm curious, would you be more comfortable if all your content were encrypted such that not even the app developer (me) could read it? Or would only a local index do?

Re: Show HN: Never lose a website again

#65
post #16

Earlier quoted context omitted.

What does indexing mean here? I'm not sure what it means to 'index' but not 'store' webpages as the frontpage says.

I assumed they meant that they extracted meta-data about the page (page mentions "Winnie the Pooh" for example, like a book index) and kept that associated with a key (eg URL) but didn't actually store the content per se . I was hoping the answer to my question would include that sort of detail - what's stored and where.

That's exactly right. The indexed content is stored (as an inserted index) but not the plain text.

Re: Show HN: Never lose a website again

#66

Why do so many sites require cookies just to tell me what they are all about? Yes, I am of the lunatic fringe that blocks all cookies by default... ...and by default more and more web sites lose me as a potential client/user/whatev because they require cookies just to display static welcoming information... ...I lose nothing by this, as far as I can tell. Perhaps ignorance really is bliss. :->

This is a great point and not one I'd ever even considered. You are right, the page you see first -- before signing up -- really doesn't need much. I am, in fact, using the Meteor stack for the entire thing, even the informational pages. But that was mostly a convenience.

Re: Show HN: Never lose a website again

#67
post #12

Earlier quoted context omitted.

You are right! I'm working on a fix.

Out of curiosity, what are you doing with such a simple site (and I don't mean that in a bad way) that requires any conscious effort to fix? It seems like you really need to go out of your way to fuck up the back button and for a fix to be "work". But, recent nuanced trends in web design/navigation aren't my top skill, so I'm asking the question honestly.

[deleted]

Re: Show HN: Never lose a website again

#69
post #41

Why server side indexing and not use something like lunarjs[1] from the beginning? Like the Idea of fulltext search on history, but I'm not going to send my full history to some random dude on the internet. No offence intended:) [1] ”Simple full-text search in your browser” http://lunrjs.com/

None taken! I looked at lunarjs (and a few other options) but felt that the more sophisticated features of ElasticSearch were worth it (at least to me). I'm curious, would you be more comfortable if all your content were encrypted such that not even the app developer (me) could read it? Or would only a local index do?

No, not really

Re: Show HN: Never lose a website again

#70

Cool. I've definitely had a desire for something like this in the past. It's mostly been filled by Evernote and its web clipper now. Any time I have a vague inkling that I might want a page again sometime, I clip it, so I can easily find it with a future search. (Often by accident since you can configure the clipper to show Evernote notes alongside search engine results.) The downside compared to something like this…

Thanks. My hope is that the search is good enough that it doesn't matter how much is indexed -- you'll always be able to find what you are looking for. This is one reason, to start, I felt it was easier to index content server side..

Of course, there's no reason not to do both. A service like yours could catch anything that falls through the cracks with EN. If you could eventually create browser extensions like theirs that add results alongside search engine results, it might would help people rediscover pages they've used in the past.
Post reply on HN