Archive for the 'Ideas' Category

02nd Jun 2004

PANs In The Clouds (Just For Plane Folks)


[idea: "Use the Net to make it easy for people on the same
flight to find each other - before, during, and after"

this is an idea that evolved over a few hours of being stuck
on a plane, gradually getting more coherent towards the end ...
and posted a couple of days later]

(more…)

Posted in Ideas | Comments Off

07th Jun 2003

Linux Hydra Work-Alike?

Is there anything like Hydra for Linux yet? Perhaps something that uses Jabber?

A local Linux User Group is electing folks to different positions,
and one of those is “Scribe”. To me, the idea just seems so 20th century.
A few people with wireless latops and a real-time collaborative
editor can take a much more complete set of notes than
any one person. See my earlier post about how well Hydra did
in a conference setting.

So where’s the breakthrough Linux app? I am aware of distributing
Emacs frames to a bunch of X11 servers, but that’s too dependent
on not having the host machine sneeze.

thanks Lazyweb.org readers for any input on this!

Posted in Blogroll, Ideas, Tech | 1 Comment »

03rd Jun 2003

ThereThen Doc Update

Yes, I still think about ThereThen Addresses quite a bit! I am starting to review an unrelated tech book manuscript (paying gig, I like that), so I will have even fewer cycles for TT for the next week or so. It’s still something that I want to at least document.

Any feedback is welcome. I will make pretty HTML later. For now, I am dumping thoughts into Emacs. If I’m hired or otherwise don’t have time for ThereThen in the near term, at least someone will have my notes for reference.

Posted in Ideas, ThereThen | Comments Off

15th May 2003

Two New ThereThen docs

I’ve been writing and researching a bit lately, in my efforts to get ThereThen addresses well-defined. Two new docs:

It should be noted that these, and other docs on my site, are in-progress. I will say that I feel I have the specification nailed down, and that my writing is focused on how best to describe the various aspects and implications.

Posted in Ideas, WebTech | Comments Off

03rd May 2003

ThereThen: How Important Is Altitude?

I’m about to start writing some code to demo the concept of href="http://ThereAndThen.org">ThereThen addressing. A guiding
thought has been to Keep Things Simple, which is why I don’t have
localized notions such as Post Codes (UK) or Zip Codes (US) floating
around in the TT notation. Whatever goes into a TT address must be
universally understood. Components of a URL which follow the TT
sections (Location and Time, always those two, and always in that
order) may certainly be as site-specific in their naming conventions
as they are now. Examples:


http://example.com/
37.749991,-122.45,80F/2003-02-4T13:15:20Z/SF-MOMA.html

http://example.com/
37.749991,-122.45,80F/2003-02-4T13:15:20Z/Store/Books/Dali.html

Which brings me to the notion of altitude. Longitude and
Latitude are universal. As near as I can tell, Altitude
is subject to local-interpretation. I’m happy with Feet.
Some folks from the UK that I have met recently are going
to be happier with meters. I looked for guidance at the RDFIG Geo vocab workspace, and didn’t see
anything nailing down how Altitude should be specified.

My inclination, up till now, could be summed up in two quick examples:
80F for 80 Feet, and 15M for 15 Meters.

Somehow, the notation doesn’t sit well with me. Are there
parts of the world where ‘F’ and ‘M’ aren’t going to be
instantly recognizable as Feet and Meters? Will it lead
to confusion? I wouldn’t want a ThereThen address slamming
into the surface of Mars just because someone got
confused between measurement systems!

One approach would be to put a stake in the ground and say “Altitude
is always Meters”. This would give worldwide consistency
in handling ThereThen addresses. Any application that needs
measurements in Feet can do the trivial conversions to and from
Meters. I like this, because it makes addresses that much
more portable. TT addresses are meant to be processed by programs,
as opposed to interpreted by users, so I am not worried about
my fellow Americans getting confused by seeing meters in the
Location component.

Another approach is to drop Altitude entirely. This changes
my first example to:


http://example.com/
37.749991,-122.45/2003-02-4T13:15:20Z/SF-MOMA.html

It’s certainly a little simpler, but it conveys less information.
Altitude can be important in Urban and Country contexts. There are
Urban contexts where one may want to call attention to the fact they
are posting from the 50th floor of a tall building, or a subway
platform. Bridging from City to Country, someone flying in a plane
may take a certain joy from tagging a blog posting from 10,600
meters up. In the Country, it may make sense for someone to point out
that they are at the top of Glacier Point in Yosemite, as opposed to
the Valley, 900-odd meters directly below. href="http://www.burri.to/~joshua/">Joshua Schachter points out a
tiny GPS device
for $99 USD
, which is one more piece of the “Location from
the Real World maps into the Internet” puzzle.

My conclusion from all of this is that Altitude is certainly
important to enough groups of people to keep it in the ThereThen
addressing scheme. A tangent question to this is “what’s the
default, when no Altitude is specified?” How about 0? (Sea Level)

My other conclusion (this is why I write stuff, it helps me think the
problem through…) is that sticking with Meters should work pretty
well. The conversion to Feet is trivial for local apps that need it,
and it helps ensure that everything in a ThereThen address is universally
understood.

I’d be keen to hear what others think. If you are thinking
within a RDF-centric world, be assured that I intend to work
out how TT addresses can be used in that context. My present
obsession (which is too strong of a word, really…) is that
I needed to focus on what components of ThereThen mean. I have
it down to a universally accepted latitude and longitude, altitude
in meters, and an ISO standard for time. That seems pretty good,
and should remove a lot of obstacles for people in building
some value on top of it.

Posted in Ideas, WebTech | 1 Comment »

01st May 2003

ThereThen update needed

I don’t have time to update my ThereThen address writeup right now, but I do want to make a couple of notes for folks that may have an interest. The gist is: multiple TT addresses are possible for a given doc, could act as a portable method to schlep location/time info around, could fit in with an RDF-based app, uses standard notations, and can be used in web services.

A quick review: a ThereThen address provides a secondary URL to get to a web page or other web resource. An example address: [updated May 10, 2003, to reflect "altitude always in meters"]


http://therethen.example.com/
37.749991,-122.45,15/2003-02-4T13:15:20Z/SF-MOMA.html

Which shows a different method to get to:

http://example.com/Travel/2003/SF/SF-MOMA.html

So, a ThereThen address shows latitude, longitude, altitude, and time. It is not a scheme that’s meant to be typed in an address bar. It’s more oriented towards automatic generation, indexing, and lookup.

  • There can be multiple TT addresses that point to the same document. They can be used to express updates from different times/locations. They can even express something like the location a trackback came from.
  • A TT URL is a portable format, and could be used as a go-between so that other formats (URL and/or RDF based) can convert to and from it (2*N conversion filters), as opposed to a myriad of format A -> format B, format A -> format C, etc. conversions (N^2 conversion filters)
  • A TT address could be used in an RSS 1.0/RDF context – I’m just not up to speed sufficiently to write about that yet.
  • I don’t see anything about the scheme that would preclude it from use in web services apps. example: I could envision an app where you give a Zip code, or in the UK, a Post Code, and get back a TT address with lat/lon coordinates.
  • A valid TT address would have a certain, standard amount of precision for latitude and longitude, and would use the prevailing standard for expressing altitude (is there one? feet or meters?). It uses the ISO 8601 standard to express time. Default placeholders need to be defined for the case(s) where a location or time is not specified. [update, May 10 2003: altitude shall always be in meters]

Posted in Ideas, WebTech | Comments Off

30th Apr 2003

Context, Blogs, and Chameleons

My perspective on blogs and blogging is probably different than that
of many people. I spent so many years (going back 15+ years) in email
and newsgroups, I had a feel for writing for a specific audience.
For whatever reason, I simply didn’t get into blogging until
very recently. The idea of “Chameleon Blog, presentation
based on who’s visiting” appeals to me. I don’t have the answer
of how to go about it though (but let me know your thoughts, just
the same)

When you send email, to a person or a list, you usually have
a good feel for your audience.

When you make a Usenet posting, it is in a focused area, such as
rec.autos.sport.f1.

When you are on IRC, the channel represents some sort of focus.

(psst! buddy, you’ve made your point, let’s move on…)

So… when you blog, who is the audience? Anyone that clicks
your way. Do you know who they are? No. Can a blog become
a chameleon of sorts, featuring topics/categories differently, based
on the context of who is visiting?

Let’s assume for a moment that I am a well-rounded person, and that
I like to write about some serious tech stuff, and light-hearted
things that happen in the course of a day, and add a dash of
political and social musings here and there. I have things
to say about English Premier League Soccer, and Formula One Racing.
I’m chomping at the bit to tell you what I think of certain books, films,
and music.

At any particular moment, I am bound to lose a big chunk of potential
readers, depending on the topics I am currently writing about.

Hmmm, that doesn’t seem good. If I am trying to find a job or a
contract (which I am), I would want to have my more technically
oriented material front and center. If my Mother in law comes to
visit my page, I probably want my political/social posts, along with
some of my light-hearted musings, to be the thing that gets featured.
For other groups, they might be familiar with the high performance
driving school, F1 racing fan side of me. Finally, I want to be able
to write some things here and there that are in the vein of “Comedy,
but not for Kids”.

So that’s a few different audiences, and there can be lots of overlap.
Does one start a few different blogs, and hope to guide some readers
one way, and some another? I’m thinking not.

I thought about having a more “Corporate, we’re damn serious here, we
talk tech, we never smile, we’re hard driving an unwired course into
our fiscal future” blog. You know, something to appeal to hard-boiled
executives that want everything serious – “Scooter! Was that a smile?!
You’re out the door! Guards!”

In real life, you wouldn’t wear a swimsuit to a formal wedding. You wouldn’t go river rafting in a Tux. You are looser around your friends on a Saturday night, than in a Serious Work Discussion. Context context context.

Having separate blogs just seems like a housekeeping headache. Let’s
say I write about GPS position streaming from individual F1 cars
in a real-world race, so that the coordinates can be fed into a realtime
“drive along” game (an idea that a friend and I wrote about a few
years ago: PrixCast). Is it a tech article? Yes. Does it appeal
to my driving friends? Yes. Would Aunt Bessie in Kansas care?
No.

So my conclusion is: I don’t know what to do! I suppose I could
have some checkboxes somewhere on my page – “feature WebTech,
Ideas, and Political, and make me dig for anything else”

In the meantime, I will continue to write about pretty much
the spectrum of things that interest me. I suppose that could
be not so great for those with a “one blog, one subject” mentality.

What do others do? Are there things that you have done in setting up
your blog so that some topics are more prominent for some users,
and not so obvious for others? I’m not interested in hiding anything.
It’s more of a “featuring certain topics, based on context” thought.

Posted in Ideas, Tech | Comments Off

29th Apr 2003

Can Rendezvous be tunneled?

I don’t know enough about networking to answer this, so I will ping LazyWeb, and hope someone can clue me in.

At etech, we saw a lot of people making use of Hydra. Is it possible to somehow tunnel ZeroConf from one local net to another? I am guessing it would involve something like:


virtual_me.local <-> tunnel <-> virtual_you.local

In other words, a second .local identity is constructed on both ends of the connection, and then some network magic passes that traffic back and forth.
I suppose another way would be to go to the port level, on a per-application basis. It just seems that creating some sort of “exists to be tunneled” Rendezvous identity (in addition to the local one) would be a nice higher-level approach.

Doable? (apologies if “tunnel” isn’t the correct description)

Posted in Ideas, Tech | Comments Off

grupa LGBT