timeless

What's wrong with mozilla today?

2003-08-05 06:57 UTC  by  timeless
0
0
What's wrong with mozilla today? What's wrong with mozilla today?
  • It's way too complicated.
  • It has way too many preferences.
  • It has way too much text which requires localization.
    • The localization tags are a royal pain.
  • It reinvents too many things.
  • It doesn't integrate with the os.

Doesn't firebird solve that?

No :)

So what could be done?

Well, imagine a browser which had virtually no text in its ui. There's text for error messages and text for preferences, but ideally while browsing you see neither of these.

Note that this pair is a lark. I'm not actively suggesting such a product. It's just an interesting conceptual demonstration of what someone could do.

timeless

Cross Listing bugs.

2003-08-13 01:41 UTC  by  timeless
0
0
problem
solution
db implementation details
sample ui for the product/component fields
timeless

Composing isn't easy

2003-08-19 02:06 UTC  by  timeless
0
0

What should a user be able to do with an editor?

Use composer to Edit this link: first list

What would a user migrating from netscape 4 composer expect to be able to do?

Use composer to Edit this link: this list

timeless

Specifications for MouseBrowser 0.1 final powered by Gecko

2003-08-24 10:44 UTC  by  timeless
0
0
Click to read 7653 words
timeless

A better way to pin DNS entries without suffering from cache poisoning.

2003-08-27 08:13 UTC  by  timeless
0
0
A better way to pin DNS entries without suffering from cache poisoning. A better way to pin DNS entries without suffering from cache poisoning. If the pinned entry is unavailable and the user wants to contact the site, provide a dialog: 
+------------------------------------------------------------+
| Host unavailable: 66.66.66.66 "foo.evil.com"               |
+------------------------------------------------------------+
| -=/ =- The server you are trying to reach is unavailable.  |
|                                                            |
|        Host: foo.evil.com                                  |
|        IP:   66.66.66.66   Protocol: HTTP    Port: 80      | 
|                                                            |
|        The following addresses are listed as alternatives. |
|        If you trust the addresses, you may choose to tie   |
|        them to [66.66.66.66,foo.evil.com].  Otherwise you  |
|        may connect to them and prevent them from accessing |
|        the old entries.                                    |
|                                                            |
|        [x] Do not tie the alternatives to 66.66.66.66      |
|        Alternatives: |[     10.0.0.1]|^|                   |
|                      |[  192.168.0.1]| |                   |
|                      |[  192.168.0.2]| |                   |
|                      |[    127.0.0.1]|v|                   |
|        [ Connect ] [ Replace ] [ Stop ]              ([?]) |
+------------------------------------------------------------+

If the user chooses to tie the alternatives to 66.66.66.66/foo.evil.com then Mozilla will add the selected entries to the DNS cache for foo.evil.com and allow foo.evil.com under any of those IP addresses to read cache data from the others and connect to each-other at will.

If the user chooses to connect and not tie the alternatives to 66.66.66.66/foo.evil.com then all cache entries for 66.66.66.66/foo.evil.com will be unavailable to the new foo.evil.com, and the DNS cache for foo.evil.com will be changed from 66.66.66.66 to the newly selected entries.

Note: there once was a proposal for doing this tossed by me in an email, I need to dig it up and transcribe any useful details into it.

Note: https shouldn't use pinning at all since the certificate should protect the cache.

Back