4 ms·

Thank you. I was thinking of showing multiple tabs/views at the same time, but only from the same source. Maybe we could have one tab with the original conten

by simedw 1y ago

Thank you. I was thinking of showing multiple tabs/views at the same time, but only from the same source. Maybe we could have one tab with the original content optimised for cli viewing, and another tab just doing fact checking (can ground it with google search or brave). Would be a fun experiment.

phatskat 1y ago
> I was thinking of showing multiple tabs/views at the same time, but only from the same source. I think the primary reason I use multiple tabs but _especially_ multiple splits is to show content from various sources. Obviously this is different that a terminal context, as I usually have figma or api docs in one split and the dev server on the other. Still, being able to have textual content from multiple sources visible or quickly accessible would probably be helpful for a number of users
wrsh07 1y ago
Would really love to see more functionality built into this. Handling post requests, enabling scripting, etc could all be super powerful
nextaccountic 1y ago
In your cleanup step, after cleaning obvious junk, I think you should do whatever Firefox's reader mode does to further clean up, and if that fails bail out to the current output. That should reduce the number of tokens you send to the LLM even more You should also have some way for the LLM to indicate there is no useful output because perhaps the page is supposed to be a SPA. This would force you to execute Javascript to render that particular page though
- simedw 1y ago
  Just had a look and three is quite a lot going into Firefox's reader mode. https://github.com/mozilla/readability https://github.com/mozilla/readability
  - dotancohen 1y ago
    For the vast majority of pages you'd actually want to read, isProbablyReaderable() will quickly return a fair bool guess whether the page can be parsed or not.
myfonj 1y ago
Interestingly, the original idea of what we call a "browser" nowadays – the "user agent" – was built on the premise that each user has specific needs and preferences. The user agent was designed to act on their behalf, negotiating data transfers and resolving conflicts between content author and user (content consumer) preferences according to "strengths" and various reconciliation mechanisms. (The fact that browsers nowadays are usually expected to represent something "pixel-perfect" to everyone with similar devices is utterly against the original intention.) Yet the original idea was (due to the state of technical possibilities) primarily about design and interactivity. The fact that we now have tools to extend this concept to core language and content processing is… huge. It seems we're approaching the moment when our individual personal agent, when asked about a new page, will tell us: Well, there's nothing new of interest for you, frankly: All information presented there was present on pages visited recently. -- or -- You've already learned everything mentioned there. (*) Here's a brief summary: … (Do you want to dig deeper, see the content verbatim, or anything else?) Because its "browsing history" will also contain a notion of what we "know" from chats or what we had previously marked as "known".
- ffsm8 1y ago
  > Well, there's nothing new of interest for you, frankly For this to work like a user would want, the model would have to be sentient. But you could try to get there with current models, it'd just be very untrustworthy to the point of being pointless beyond a novelty
  - myfonj 1y ago
    Not any more "sentient" than existing LLMs even in the limited chat context span are already. Naturally, »nothing new of interest for you« here is indeed just a proxy for »does not involve any significant concept that you haven't previously expressed knowledge about« (or how to put it), what seems pretty doable, provided that contract of "expressing knowledge about something" had been made beforehand. Let's say that all pages you have ever bookmarked you have really grokked (yes, a stretch, no "read it later" here) - then your personal model would be able to (again, figuratively) "make qualified guess" about your knowledge. Or some kind of tag that you could add to any browsing history entry, or fragment, indicating "I understand this". Or set the agent up to quiz you when leaving a page (that would be brutal). Or … I think you got the gist now.
baq 1y ago
wonder if you can work on the DOM instead of HTML... almost unrelated, but you can also compare spegel to https://www.brow.sh/ https://www.brow.sh/

by simedw 1y ago

phatskat 1y ago

> I was thinking of showing multiple tabs/views at the same time, but only from the same source. I think the primary reason I use multiple tabs but _especially_ multiple splits is to show content from various sources. Obviously this is different that a terminal context, as I usually have figma or api docs in one split and the dev server on the other. Still, being able to have textual content from multiple sources visible or quickly accessible would probably be helpful for a number of users

wrsh07 1y ago

Would really love to see more functionality built into this. Handling post requests, enabling scripting, etc could all be super powerful

nextaccountic 1y ago

In your cleanup step, after cleaning obvious junk, I think you should do whatever Firefox's reader mode does to further clean up, and if that fails bail out to the current output. That should reduce the number of tokens you send to the LLM even more You should also have some way for the LLM to indicate there is no useful output because perhaps the page is supposed to be a SPA. This would force you to execute Javascript to render that particular page though

simedw 1y ago
Just had a look and three is quite a lot going into Firefox's reader mode. https://github.com/mozilla/readability https://github.com/mozilla/readability
- dotancohen 1y ago
  For the vast majority of pages you'd actually want to read, isProbablyReaderable() will quickly return a fair bool guess whether the page can be parsed or not.

myfonj 1y ago

Interestingly, the original idea of what we call a "browser" nowadays – the "user agent" – was built on the premise that each user has specific needs and preferences. The user agent was designed to act on their behalf, negotiating data transfers and resolving conflicts between content author and user (content consumer) preferences according to "strengths" and various reconciliation mechanisms. (The fact that browsers nowadays are usually expected to represent something "pixel-perfect" to everyone with similar devices is utterly against the original intention.) Yet the original idea was (due to the state of technical possibilities) primarily about design and interactivity. The fact that we now have tools to extend this concept to core language and content processing is… huge. It seems we're approaching the moment when our individual personal agent, when asked about a new page, will tell us: Well, there's nothing new of interest for you, frankly: All information presented there was present on pages visited recently. -- or -- You've already learned everything mentioned there. (*) Here's a brief summary: … (Do you want to dig deeper, see the content verbatim, or anything else?) Because its "browsing history" will also contain a notion of what we "know" from chats or what we had previously marked as "known".

ffsm8 1y ago
> Well, there's nothing new of interest for you, frankly For this to work like a user would want, the model would have to be sentient. But you could try to get there with current models, it'd just be very untrustworthy to the point of being pointless beyond a novelty
- myfonj 1y ago
  Not any more "sentient" than existing LLMs even in the limited chat context span are already. Naturally, »nothing new of interest for you« here is indeed just a proxy for »does not involve any significant concept that you haven't previously expressed knowledge about« (or how to put it), what seems pretty doable, provided that contract of "expressing knowledge about something" had been made beforehand. Let's say that all pages you have ever bookmarked you have really grokked (yes, a stretch, no "read it later" here) - then your personal model would be able to (again, figuratively) "make qualified guess" about your knowledge. Or some kind of tag that you could add to any browsing history entry, or fragment, indicating "I understand this". Or set the agent up to quiz you when leaving a page (that would be brutal). Or … I think you got the gist now.

baq 1y ago

wonder if you can work on the DOM instead of HTML... almost unrelated, but you can also compare spegel to https://www.brow.sh/ https://www.brow.sh/