• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (28)

1 localhost commented Permalink

I use lynx. Everything is text.

2 localhost commented Permalink

what about txt.weather.com? oh wait -- isn't that what wml and wap were for?

 
so much for websites "degrading gracefully", i guess...

3 localhost commented Permalink

Wayne has the solution, but we need people to a) recognize the need and b) provide text-only versions of their content.

 
.txt domains is interesting, but there are some obvious problems. For instance, what is the .txt equivalent for foobar.com? foobar.txt? Then what about foobar.org? foobar.net?
 
Do we then provide .pdf domains for people who insist on slow-and-buggy-yet-typographically correct content?
 
What about url's? I'm happy to jettison most html, but the anchor tag really needs to stay.
 
To really get this ball rolling, what you need to do is create a text-only alternative to the anchor tag and then get advertisers (AdSense?) to start providing ads in the text-only format.
 
Oh, and also allow for image-only pages. Nothing but the graphic. So you can still have pictures, linked to from the plain text page, cause sometimes, you just need the picture.

4 localhost commented Permalink

"every website registered would automatically get a .TXT domain name equivalent" does no one else see a problem with this?

 
If I own ABC.ca and Disney owns ABC.com who gets ABC.txt?

5 localhost commented Permalink

wayne's solution doesn't seem to fit well with the given scenario. if you're in an airport and you want a quick and dirty text-only version of a website, how do you configure your browser to negotiate text only? i don't know how, and i imagine most browser users don't either. a separate url would do the trick.

6 localhost commented Permalink

1. Use Opera2. Set style to User Mode - Text only3. ??????4. PROFIT!

7 localhost commented Permalink

it's call RSS

8 localhost commented Trackback

Please lookup the definition of irony in a dictionary. Next think about the proposals for a .mobi and other TLD's.

9 localhost commented Trackback

Restrictions have a tendency to encourage experimentation and stretching of borders.

 
Within hours of the launch of .txt, a huge surge of ASCII art will happen, no doubt including tutorials such as 'How to do rounded corners in TXT!!!11'.
 
And any visions of legibility or clarity through a restricted medium fade away quickly :)
 
J

10 localhost commented Trackback

I love the basic concept, but I think we just to try and use existing standards to make all of this possible.

 
First, are we talking plain text, or XHTML w/ CSS. Of course, the CSS needs to be graphic free itself.
 
Could we rely on a convention in the url? For example, throw your browser into 'light' mode, and then every request it makes out to the web will have "text_only_mode=true". The web devs can then see that and swap templates.
 
What do ya think?

11 localhost commented Trackback

Follow-up:

 
I saw this mentioned over at Reddit, and raldi stated that it would make more sense if we used 'txt' as a subdomain.
 
I agree. http://txt.ibm.com. Could be pretty useful and easy for the reader.

12 localhost commented Trackback

I don't think creating a new top-level domain is the best approach, but a naming convention to find well formated tag-free text mode versions of documents would be very nice.

 
When formatting text (for the web as well as for print), I prefer using text markup formats like reStructuredText to XML or word processors. So the base format itself is readable, well formated plain text which can be transformed to various output formats (HTML, LaTeX source, PDF, PS, ...) easily. So the text source might be of use for the readers of the documents too.
 
I'm running a little (German language) website featuring textmode software, you'll find the HTML version using the URLhttp://www.automatisch.cc/automatisch.htmland a (reStructured-) text version usinghttp://www.automatisch.cc/automatisch.txt.
 
I think using the convention to point out the file format using a filename extension is the cleaner solution, but I completely agree that providing information in plain text format makes much sense.
 
P.S.: you blog looks great in w3m ;-)

13 localhost commented Permalink

Hey! Good idea!

 
http://txt.ibm.com + monospace font
 
and your browser would look just like DOS!

14 localhost commented Permalink

what about just a plugin for the browser that could only allow text of a website to come through... then just type '.txt' after any page, and the browser does the rest...

 
ie: normal=www.weather.com Text=www.weather.com.txt
 
so simple, now someone just needs to write the plugin and make it free...

15 localhost commented Permalink

good idea, not thought out. theres sites that are thisdomain.com, and thisdomain.net, and thisdomain.org, and thisdomain.nu, and thisdomain.cx. only one of those can have thisdomain.txt

 
still, good idea. and not just any old text only, xml.
 
this way, and imagine the possibilities, you can add your own CSS to every single site out there.
 
imagine surfing the web with your own personal skin?

Add a Comment Add a Comment