Hi all, First off, I got to say, congrats on the great browser. I have an old laptop and firefox just takes ages to load. Dillo, on the other hand, is lightning fast! Great! The only thing I'm missing is Gmail. Does Dillo work with gmail? Do I need to do any special tricks? I compiled the latest DIllo2 from svn and I did enabled https so I can get past the login page but then I'm stuck at a warning page about a non-standard redirect and, the link on that page does not work. The link is: https://www.google.com/accounts/CheckCookie?continue=http%3A%2F%2Fmail.google.com%2Fmail%2F%3Fui%3Dhtml%26zy%3Dl&service=mail<mpl=default&chtml=LoginDoneHtml Thanks for the great work Daniel
On Thu, Dec 04, 2008 at 10:17:00PM -0200, Daniel Victoria wrote: Hi there,
The only thing I'm missing is Gmail. Does Dillo work with gmail? Do I need to do any special tricks?
I have it "working" with dillo1, and don't see why it shouldn't work in the same way with dillo2. "Working" means "I can read and write mail, http only" -- but only after I've got the authentication cookie with a different browser. (My dillo1 doesn't do https.) If that's good enough for you, then you can try the same with dillo2 and report on whether it still works. My cookiesrc says: DEFAULT DENY mail.google.com ACCEPT I use a mozilla browser to sign in, and then I don't sign out so as not to invalidate the cookie on the server. It seems to remain valid for a couple of weeks, so I occasionally have to redo this part. Find the cookie called GX, and write it to a file in the correct format -- 7 tab-separated fields. My current one is a file ~/gmcookie which looks like this (apart from the value of the cookie, which has been modified): mail.google.com TRUE /mail FALSE 2000000000 GX DQAAAIIAAACY9ABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFHELLOKITTYEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEF__p_abcdef Then, to load or reload the cookie into dillo, I do pkill -HUP cookie pkill cookie cat $HOME/gmcookie >> $HOME/.dillo/cookies.txt And then I go to my bookmarked gmail page at http://mail.google.com/mail/?ui=html&zy=n and it all Just Works. If I get redirected to a https page, that indicates that the cookie is absent or invalid, so I put it back or get a fresh one. No guarantees that it will keep working, of course. The gmail folk can change their authentication requirements at any stage. And you miss out on the javascript goodness that is a large part of the gmail experience. And there was a stage when the html returned was broken in a way that dillo couldn't usefully handle, although that has since been changed back. But for straightforward mail tasks, it works well enough for me. Couple it with a lightweight gmail-notifier script, and you don't have to hit reload to see the new news. Good luck, f -- Francis Daly francis@daoine.org
Wow, that's a lot of things for a newbie to do... I guess I'll just keep firefox along with dillo. One for gmail and the other for quick things Thanks for your help anyway Daniel On Fri, Dec 5, 2008 at 11:56 AM, Francis Daly <francis@daoine.org> wrote:
On Thu, Dec 04, 2008 at 10:17:00PM -0200, Daniel Victoria wrote:
Hi there,
The only thing I'm missing is Gmail. Does Dillo work with gmail? Do I need to do any special tricks?
I have it "working" with dillo1, and don't see why it shouldn't work in the same way with dillo2.
"Working" means "I can read and write mail, http only" -- but only after I've got the authentication cookie with a different browser. (My dillo1 doesn't do https.)
If that's good enough for you, then you can try the same with dillo2 and report on whether it still works.
My cookiesrc says:
DEFAULT DENY mail.google.com ACCEPT
I use a mozilla browser to sign in, and then I don't sign out so as not to invalidate the cookie on the server. It seems to remain valid for a couple of weeks, so I occasionally have to redo this part. Find the cookie called GX, and write it to a file in the correct format -- 7 tab-separated fields. My current one is a file ~/gmcookie which looks like this (apart from the value of the cookie, which has been modified):
mail.google.com TRUE /mail FALSE 2000000000 GX DQAAAIIAAACY9ABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFHELLOKITTYEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEFABCDEF__p_abcdef
Then, to load or reload the cookie into dillo, I do
pkill -HUP cookie pkill cookie cat $HOME/gmcookie >> $HOME/.dillo/cookies.txt
And then I go to my bookmarked gmail page at
http://mail.google.com/mail/?ui=html&zy=n
and it all Just Works. If I get redirected to a https page, that indicates that the cookie is absent or invalid, so I put it back or get a fresh one.
No guarantees that it will keep working, of course. The gmail folk can change their authentication requirements at any stage. And you miss out on the javascript goodness that is a large part of the gmail experience. And there was a stage when the html returned was broken in a way that dillo couldn't usefully handle, although that has since been changed back. But for straightforward mail tasks, it works well enough for me.
Couple it with a lightweight gmail-notifier script, and you don't have to hit reload to see the new news.
Good luck,
f -- Francis Daly francis@daoine.org
Hi Have you tried http://gmail.com? I can see mails from there. I modified dillo HTTP request header so some modification might be needed. Regards, furaisanjin
participants (4)
-
corvid＠lavabit.com -
daniel.victoria＠gmail.com -
francis＠daoine.org -
furaisanjin＠gmail.com