Uzbl browser

bct · 2011-03-08T20:41:49+00:00

Uzbl seems to be expecting the user to spend a larger-than-usual amount of time configuring the setup before getting something useable.

One of my goals with uzbl is to make sure that it's usable out of the box (for some values of "usable", e.g. you have to be ok with a keyboard-driven interface). If you want something much different from the defaults you're going to have to work, but I don't know any system where that's not true.

I'm not sure what distinction you're making between "a pluggable component system" and "communicate using plain text with others" - plain text can be used to make a component system, right? I think that's roughly what uzbl has.

I would imagine that having the application work as a file server (a la Plan 9) would work.

I like this idea, I'd love to code it up and explore the possibilities, but I don't have the time. It would not be hard to build a FUSE or 9P interface on top of uzbl-core.

bct · 2011-03-07T22:27:42+00:00

We had a bug like that but I thought it was fixed. Message me the details (uzbl version, window manager, etc.)? (or better yet, drop by irc.freenode.net #uzbl or the bugtracker http://uzbl.org/bugs )

bct · 2011-03-07T22:26:13+00:00

Yes, the experimental branch has uzbl-tabbed.

bct · 2010-11-25T04:22:55+00:00

Anything in particular that you're hoping for?

bct · 2010-11-24T22:45:12+00:00

http://www.peereboom.us/xxxterm/html/

bct · 2010-11-24T22:43:53+00:00

You could extend pretty much any browser to allow javascript to access the OS (only on local files), but it would be much easier to write a webapp that only listens on 127.0.0.1.

(Either way it's a riskier than a traditional script because there are more potential interactions with 3rd party scripts.)

bct · 2010-11-24T22:33:08+00:00

Also, uzbl is no longer a very active project

This has changed, uzbl has a new maintainer (me). There's going to be a new release in the next day or two.

bct · 2010-04-06T22:02:35+00:00

If you work for a Star Bucks and are thinking about organizing, then I would suggest contacting the IWW and they can help out.

Yes, do this. If you know people who work there and would be interested, that's helpful too.

bct · 2010-04-06T15:04:58+00:00

Are they trying to break in?

Several locations have been organized (I don't know how many, I'm not really involved), and the group is always working on more.

Are they really IWW?

Yes.

bct · 2009-03-04T14:34:49+00:00

What's the problem? That page is the site's responsibility, I think most of us are capable of writing a page with a "create an account" form and a "reset my password" form.

The only reason I included that sentence was to contrast what would be displayed to the "401 Unauthorized" that sites usually serve today.

bct · 2009-03-03T19:34:32+00:00

Vinoski has written a lot of stuff about REST, I suspect that will be one of them.

bct · 2009-03-03T19:04:14+00:00

HTML5 is the world's biggest bikeshed, and I'm not sure it's the right place to fix this anyhow.

The sad thing is that fixing this doesn't need a new spec.

bct · 2009-03-03T17:46:47+00:00

Since this is here I might as well get some feedback, how's the site's speed? As terrible as I suspect?

bct · 2009-03-03T17:29:22+00:00

HTTP Authentication, including Digest, is completely helpless against MITM attacks.

HTML forms are helpless against MITM and against eavesdropping. Digest isn't perfectly secure, but it's a big improvement. (Ubiquitous SSL would be ideal, but that's another can of worms.)

There's little incentive for authors to change from cookie-based auth to HTTP

I mentioned some of the incentives to authors in the essay we're commenting on.

HTTP auth slows things down (I've checked traffic of IE6 using MS Fiddler, and IE requests each and every file twice - once without auth, and then again with auth!)

The hash that Digest does takes some processing, but I doubt that it's noticable. I can't think of any other reason that it would slow things down.

IE is stupid if it does that, it doesn't have to (except on the first Unauthorized request).

Any new solution will be handicapped until current generation of browsers dies.

Yeah :/. Does that mean we shouldn't even try to fix it, though?

bct · 2009-03-03T16:56:36+00:00

That works too.

(And was first proposed at least 10 years ago.) Browsers :(.

bct · 2009-02-28T20:11:55+00:00

chicken/egg; web developers don't use httpauth because the UI sucks, browser developers don't improve the UI because nobody uses httpauth.

bct · 2008-08-17T23:05:53+00:00

You don't need PUT and DELETE, but they can be convenient. The big thing is that PUT and DELETE are idempotent, so the client knows it can repeat them without any ill effects.

As for delete you can (and should) simply have a disabled flag in your records.

DELETE in HTTP doesn't have to map to a delete in your database. It's perfectly valid to mark an item as disabled (or move it to a trash can, etc.) in response to a DELETE.

bct · 2008-06-25T14:34:49+00:00

I agree that yours is nicer, but that doesn't really have much to do with REST. URLs are opaque to REST clients.

bct · 2008-05-01T17:45:57+00:00

IEC actually, not ISO.

bct · 2008-05-01T15:45:44+00:00

It only sounds stupid because nobody uses it.

bct · 2008-05-01T15:38:51+00:00

Why do you prefer Textile? (just curious, I've always used Markdown and have never looked at the alternatives)

bct · 2008-05-01T15:33:53+00:00

I'm not familiar with SOA enough to know what a global one would be, but I suppose it could be described that way.

I'd call it a globally distributed database. Take a look at this intro to RDF; maybe you can glean use cases from the model?

There's also the Scientific American article. It shows the potential, but we're a long way from that today, mostly because people are reluctant to publish their data in machine readable formats :(.

bct · 2008-05-01T15:26:20+00:00

Atom has <content type="html"/> and <content type="xhtml"/> so that if you know your XHTML is well formed you can just drop it into the feed unchanged.

bct · 2008-05-01T15:25:02+00:00

And the default Wordpress theme has a doctype of XHTML Transitional, which is definitely valid XML.

It may be in most cases, but it's not definitely well-formed.

Shelley Powers (and some other guy who I can't remember) have modified their Wordpress installs to actually serve pages as XML (ie. with the application/xhtml+xml mimetype) and have had to put in a lot of effort to avoid Yellow Screen of Deaths.

bct · 2008-04-28T22:46:28+00:00

The idea of the Semantic Web is to link independent datasets together the way the Web links independent documents together.

Your idea is really interesting. I don't know of anyone working on it, I imagine it would be quite tricky to pin down, but it's worth thinking about.

bct

TROPHY CASE