PUBLIC MARKS with search people

an interesting conclusion about how to turn new and casual contributors into long-time community members: the key is to distribute ownership.

To wrap up, there were several things that motivated me to stay active in the Mozilla community: * A belief in the mission of the project — to create a web browser that supports and promotes the use of open standards * An interest in the technology — initially with the Gecko logo as my hook * The feeling of belonging in a community of people with similar interests * The desire to give something back to a project that gave (and still gives) me the best browser in the world for free * The experiences gained by managing a website — HTML, CSS, server configurations, and perhaps most importantly, the English language * The recognition and respect from Mozilla project members for my contributions * The pride of being responsible for an important piece of the project

In an effort to make the code useful to as many people as possible, we've split it into several packages:

* The main package (probably the thing you're looking for) is the publishing system, known as ebpub.

* Second, the packages ebdata and ebgeo contain Python modules for processing data and making maps.

* Third, the packages ebinternal and everyblock round out the code that powers EveryBlock.com. They're internal tools and are likely not of general use, but we're including them to be complete.

* Finally, ebblog and ebwiki are our blog and wiki software, respectively. Because, dammit, the world needs another Django-powered blogging tool.

Show support for the people who fight for democracy at Iran, and change your Twitter avatar to have green overlay or green riboon (green is the official color of the movement).

All you need to do is click here to add green overlay or to click here to add a green ribbon and your avatar will be updated and a support Tweet will posted on your behalf ("Show support for #iranelection add green overlay to your Twitter avatar with 1-click - http://helpiranelection.com/").

I did want to apologize for assuming that the XHTML errors I had recently were due to WhatWG members having fun at my expense. I've had people deliberately break my XHTML-based comments in the past when I've written about XHTML, and the break was documented with a screenshot in the web site of a WhatWG member. I put 2 and 2 together and came up with 5. (1/10/2009)

Anne VK est taquin (see via). -- Ceci dit j'admire Shelley pour maintenir ses sites en full xhtml + extensions > svg+rdfa. Mais Dieu que la route est difficile avec des navigateurs si peu adaptés. (Firefox et son yellow screen of death)

If you maintain a lot of social networks, like many artists and musicans, it’s often difficult for people to find all your different profiles without you sending them direct (and often long) links. Today i got an email from my friend deepchild, a musician and avid internet user, with a brilliant new way to simplify everything.

Check out his new email signature:

www.deepchild.com/twitter

www.deepchild.com/flickr

www.deepchild.com/youtube

www.deepchild.com/myspace

www.deepchild.com/facebook

Criticism • Side effects often dominate over intended consequences of any project or endeavor. • Abstract views may make us callous or may badly reflect ground truth. • Ignorance is bliss. The world is filled with sob stories. Best to not dwell? • Such services may be used solely for the most banal aspirations and goals. • Struggle may be important - making things too easy may harm fitness and lower diversity of skills and abilities over long term. • What about poor people who are outside of any implied technological social network? • Why not just help people around you? • Any technology should go hand in hand with day to day personal practice that is unmediated? • Feedback loops may be created that accelerate and disrupt society. • Virtual and visual only for curators; not tactile; uses only one sense. A concern?

A session talking about what people can/are doing with proximity sensing (and how/why in many cases, locative services aren't about absolute (geo) location, but relative location. Covering implementation and code of Bluetooth in particular, including information on the setup I used at Where 2.0 and WhereCamp 2008. (The morning session already covered lots of concerns about privacy that are applicable here, so this session will focus on cool stuff you can do and how to get out there and do it)