WEBSTANDARDS Archives

UofMN Web Standards

WEBSTANDARDS@LISTS.UMN.EDU

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0 (Apple Message framework v936)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Date: Thu, 3 Dec 2009 11:21:53 -0600
Reply-To: UofMN CSS Web Development <[log in to unmask]>
From: Brian Hayden <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Sender: UofMN CSS Web Development <[log in to unmask]>
Parts/Attachments: text/plain (24 lines)
On Dec 3, 2009, at 11:15 AM, Zachary Johnson wrote:

> That's interesting.  I could see a lot of demand for a unified way  
> to create response content on community-based websites.  Especially  
> if you didn't have to create another user login at each one.
>
> I am somewhat nervous of the web going in that direction, though.   
> What if users *expect* a Google Wave-based comments/response system  
> *but* Google Wave is actually way crappier than some competing  
> product? Or isn't accessible?  That's going to be a very tricky  
> thing to resolve as a developer.


I see this as by far the biggest and most troubling question. You  
could draw an analogy to Paypal's control of the credit-card- 
processing part of online shopping. Their problems are well- 
documented, but unless you're a major retailer people expect you to  
accept Paypal (in order to avoid giving their financial details to  
every Tom, Dick, and Harry). Only thing worse than having that sort of  
gatekeeper with our money is having one for our exchange of ideas and  
technology.

-Brian

ATOM RSS1 RSS2