Show HN: Never lose a website again • Hacker News Board

Re: Show HN: Never lose a website again

#11

Post by drdaeman » Wed, Jul 02, 2014, 7:58 PM UTC

I was just looking for such indexer this exact evening.

Unfortunately, logon via Twitter fails with 500 error bar flashing at the site's top and logon via FB fails with "App Not Setup: The developers of this app have not set up this app properly for Facebook Login.", so I can't try it.

Nonetheless, my biggest worry is why this is a service instead of a standalone package. (Actually, I've considered trying with the hope plugin may be possibly FOSS and if so researching whenever it could be hacked to be used with locally-installed Solr/Lucene server) I'm not really comfortable with directly or indirectly sharing my browsing history with most third parties.

Re: Show HN: Never lose a website again

#12

Post by brk » Wed, Jul 02, 2014, 8:06 PM UTC

flippyhead wrote: post #7

jgh wrote: post #4

Your site breaks the back button (Chrome 35 OS X Mavericks)

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.

Re: Show HN: Never lose a website again

#13

Post by flippyhead » Wed, Jul 02, 2014, 8:11 PM UTC

drdaeman wrote: post #11

I was just looking for such indexer this exact evening. Unfortunately, logon via Twitter fails with 500 error bar flashing at the site's top and logon via FB fails with "App Not Setup: The developers of this app have not set up this app properly for Facebook Login.", so I can't try it. Nonetheless, my biggest worry is why this is a service instead of a standalone package. (Actually, I've considered trying with the ho…

Bah, I'm sorry! The Facebook login has now been fixed.

I totally hear you on some people not wanting to share browsing history externally. This first version was easiest to do as a hosted service. Next up I intend to package it up as an installable app.

Re: Show HN: Never lose a website again

#14

Post by flippyhead » Wed, Jul 02, 2014, 8:13 PM UTC

drdaeman wrote: post #11

I was just looking for such indexer this exact evening. Unfortunately, logon via Twitter fails with 500 error bar flashing at the site's top and logon via FB fails with "App Not Setup: The developers of this app have not set up this app properly for Facebook Login.", so I can't try it. Nonetheless, my biggest worry is why this is a service instead of a standalone package. (Actually, I've considered trying with the ho…

That said, I have found it handy to have access to this searchable history for different locations and devices. For example on my phone.

Re: Show HN: Never lose a website again

#15

Post by PeterWhittaker » Wed, Jul 02, 2014, 8:15 PM UTC

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. :->

Re: Show HN: Never lose a website again

#16

Post by gwern » Wed, Jul 02, 2014, 8:15 PM UTC

pbhjpbhj wrote: post #9

Do you just record n-grams indexed against the page url, are you then uploading that index? If you're not uploading it how is there no "local version" available? It's an interesting idea. Personally I have a script that wgets all the pages I bookmark and I very rarely use that content. What use cases are you anticipating?

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

Re: Show HN: Never lose a website again

#17

Post by aeflash » Wed, Jul 02, 2014, 8:16 PM UTC

Ah, so it's like Firefox's URL bar, except with full-text search, rather than just the URL/Title.

Re: Show HN: Never lose a website again

#18

Post by dguaraglia » Wed, Jul 02, 2014, 8:17 PM UTC

PeterWhittaker wrote: post #15

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. :->

I guess most websites nowadays are built using one of the myriad web frameworks out there (Django, RoR, you name it.) Most of this frameworks enable sessions by default, simply because it's what most websites will want if they manage any kind of state. Nothing nefarious about it.

Re: Show HN: Never lose a website again

#19

Post by waterside81 » Wed, Jul 02, 2014, 8:18 PM UTC

flippyhead wrote: post #6

bradbeattie wrote: post #3

Earlier quoted context omitted.

Moreover, how does this work with sites that make use of ajax content? It'd be frustrating to assume that it's recording just fine, only to later find that patches of your history couldn't be recorded.

That's a great point. At the moment it only records what's in the DOM (stripped of all HTML) after the first page load event. I'm working on how to include AJAX content but it's not nearly as straight forward.

Take a look at readability.js (https://github.com/Kerrick/readability-js) and extract/upload the main DOM content after all the JS trickery has completed.

Re: Show HN: Never lose a website again

#20

Post by zevyoura » Wed, Jul 02, 2014, 8:19 PM UTC

brk wrote: post #12

flippyhead wrote: post #7

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.

The site is built with the meteor framework, so it's not just the simple implementation you might expect from the layout. I imagine the features of meteor are useful in the actual app itself, which is probably not a simple site.