Read more of this story at Slashdot.
Read more of this story at Slashdot.
Back in May it was announced that the Give 1 Get 1 program would be making a comeback and in June there were indications that it would happen after September 1.
Now IDG News Service broke the news earlier today that Amazon will be running this year's Give 1 Get 1 program from late November until possibly the end of December. This information is based on an interview with OLPC's Matt Keller who works as OLPC's director of Europe, Middle East and Africa.
The brief news release indicates that Give 1 Get 1 will be limited to the United States. Since there had been rumours to also bring the 2008 edition of G1G1 to other places such as Europe this piece of information, if indeed true, will be quite a disappointment for many of us. Especially since a partner such as Amazon would probably be in a very good position to make G1G1 a global program.
Personally I'm sceptical as to whether this information was really intended to go public at this time. The lack of detailed information indicates that something might have been hinted at or said off-the-record which was then picked up by IDG. So let's see whether this story will be followed by an official announcement from OLPC and Amazon in the weeks ahead.
Amazon G1G1 Give 1 Get 1 November comebackby (Christoph Derndorfer) no_spam@olpcnews.com at September 04, 2008 09:00 AM

You already saw Google Chrome's humorous about:internets Easter egg, but reader nettleman points out that Chrome's got several special about: pages that reveal all sorts of interesting information about what's going on behind the scenes. Here's the full list, with screenshots.
Update: Mawin adds that you can also go to two special pages on a per-site basis. view-cache:[URL] shows you some under-the-hood cache details, and view-cache:[URL] shows you the page's markup. (Though you can view source by just right-clicking on a page and choosing, um, "View page source.")
You Mac and Linux users, here are some about: page screenshots:






Find anything interesting in Chrome's about: pages? Let us know in the comments.
The end user license agreement for Google's new browser, Chrome, apparently gives the company the right to all data "submitted" or "displayed" by the browser. But the company now tells Ars it's all a big mistake and that the offending passages are being pulled.
by nate@arstechnica.com (Nate Anderson) at September 03, 2008 07:56 PM

The dust hasn’t even settled on Chrome’s release and already Mozilla is feeling the pressure. The company today released a series of benchmarks showing Firefox 3.1 will be faster than anything Google can muster with Chrome.
Chrome is running V8, an open source Javascript engine, which Google claims, is faster than anything currently offered on the Web. And based on our tests of Chrome, we tend to agree.
But in the upcoming release of Firefox 3.1, which should be available by the end of the year, Mozilla will employ TraceMonkey, a new engine that according to one of its coders, Brendan Eich, will easily eclipse even the fastest instance of Chrome.
To prove it, Mozilla tested Firefox running on TraceMonkey and compared it to Google’s Chrome beta using its own benchmarking solution called SunSpider. According to the company, Chrome was 28 percent slower on Windows XP and 16 percent slower on Windows Vista.
Mozilla is quick to point out that TraceMonkey has only been in development for a few months and will only get better before it’s rolled out later this year, but the company has a vested interest in seeing Firefox come out on top in its benchmark testing, so all figures should probably be questioned, to say the least. And the same goes for Google’s five benchmarks.
For now, Chrome is the fastest browser in the market and anyone using both Firefox and Chrome will find that out quickly. But once Firefox 3.1 hits the Web, we’ll find out if Chrome has what it takes to stay on top after TraceMonkey becomes Mozilla’s engine of choice.
Crunch Network: CrunchBoard because it’s time for you to find a new Job2.0
There are interesting changes under way in how software applications are designed and deployed, and I’m curious about the role of Ubuntu will be in this process. I’m thinking about this in terms of three categories:
Examples: OpenOffice.org, Pidgin, Amarok, GIMP
These are our traditional word processors, spreadsheets, messaging clients, music players, and so on.
End users of desktop applications benefit from high performance, access to local data and offline availability, but are hampered by high maintenance requirements and primitive collaborative features.
Developers of desktop applications benefit from access to local OS APIs, a wealth of existing free source code, and relatively low maintenance overhead, but are hampered by a complex distribution model, multiple platform targets, and many versions being actively used in the wild.
Ubuntu specializes in this area today.
Examples: Google Docs, GMail, Facebook, Youtube
They are distinguished from simple websites by virtue of having a consistent look and feel throughout, a high degree of interactivity, and a defined feature set.
End users of web applications benefit from the universal availability of the applications and associated data, advanced collaborative features, and virtually zero maintenance, but are hampered by comparatively low performance, unavailability when offline, primitive user interfaces (though they are getting better), and data privacy issues.
Developers of web applications benefit from a simple distribution model, fewer platform-specific issues, and fewer versions to support at once (typically one), but are hampered by high maintenance (production hosting), a more complex user interaction model, and a comparative scarcity of open source code.
Ubuntu aims to provide an excellent browser experience, but doesn’t go much further than that yet.
Examples: Google Earth, Adobe AIR applications, iPhone widgets
These applications attempt to draw from the best of both paradigms. Some are designed and built similarly to centralized web applications, with HTML/JavaScript user interfaces, but actually run in a local runtime environment on the end user’s system and often (but not always) use web APIs. Others are designed like desktop applications, but rely on web APIs behind the scenes.
Ubuntu doesn’t do much in this area yet.
Ubuntu is, most essentially, a means for users to obtain and use applications, and for developers to create them. Operating systems exist to make these things easier, so changes in this area are highly relevant to us. They may even lead to reinterpretation of some of our most basic principles, for example:
Every computer user should have the freedom to download, run, copy, distribute, study, share, change and improve their software for any purpose, without paying licensing fees.
How does this apply to web applications which need not be downloaded, distributed or copied in order to be run or shared? Is it useful to be able to copy, change and improve the source code for a desktop application if all of the interesting functionality is hidden behind a web API?
To what extent can (or should) hybrid applications truly be a part of a free system? Do they make free software values less relevant, or just less obvious? These questions are the subject of active debate in the media today.
Once we’ve addressed the philosophical issues, how can Ubuntu take advantage of this innovation at a technical level? How can Ubuntu become a superior platform for hybrid web applications? The just-announced Google Chrome has interesting implications, both for bringing web applications further into the desktop and supporting hybrid applications.

Google has posted their official video of the Chrome press event we live blogged earlier today. I still prefer the comic book version, but if you want to see the official presentation, there it is.
Larry Page steps on stage for the last two minutes. He talks about how he’s been using Chrome on an older computer to test how it handles lower end hardware. I’ve been using Chrome today on two Vista computers - one newish desktop and one ultra portable computer running a Via chip. Chrome works great on both.
Crunch Network: MobileCrunch Mobile Gadgets and Applications, Delivered Daily.
Shared by maco
Digg to get Gwibber some attention?
Micro-blogging is all the rage nowadays, though if you don’t know what it is you might want to check out Twitter Explained for a little tutorial. The default way to handle micro-blogging and updates is to keep refreshing a page in your browser over and over, but since that can be a bit of a pain, having a desktop client to poll for updates is very handy.
But then let’s face it, Twitter’s not the only micro-blogging platform out there, and it’s definitely not the only program that lets you have status updates. That’s why having a Twitter-only client doesn’t really make a whole lot of sense. I was using Twitux before, but since then I joined a fully open-source micro-blogging platform called Identi.ca. Probably by virtue of being open-source software, it has a large Linux-user population, so I had to join. And Twitux doesn’t work with it. Enter Gwibber.
Gwibber is a status-update client for a lot of services. I’m just using it for Twitter and Identi.ca, but it also works for Digg, Jaiku, Facebook, Pownce, and Flickr. It’s actively developed, and the developer (Ryan Paul of ArsTechnica) seems to be listening to user input, so that’s definitely a plus.
Right now, though, I just really like its flexibility. It uses WebKit for rendering, so it can get pretty fancy. Take a look at the screenshot below. I configured it to use dark blue for Identi.ca updates and light blue for Twitter updates, so they match each site’s theme. You can pick whatever color you want for each, but I thought it was easier to remember this way.

You can also see that where someone replied to me the message is outlined in red. That’s pretty useful. New messages are outlined in light blue to highlight them.
Perhaps my favourite feature is the duplicate detection. See that plus sign on my message? Here’s what happens when you click it:

It detected that I tweeted and dented the same thing and displayed the status update only once. This happens when I post from within Gwibber or when one of my friends that uses both does so. It just helps tidy up the interface a bit, I think. And then of course there’s the requisite “Reply” button in the bottom right corner of whichever notice has focus.

If you’d like to try it out:
Please note, though, that Gwibber is still in Alpha. I haven’t noticed any issues with it, but being alpha software does mean there are big changes happening fairly often. I think duplicate detection was added last week. I’m with everyone that’s requesting a “Replies” tab. Ryan says he’ll make it a priority.
Windows and Mac users? You’re out of luck. This application is only supported for Linux, but if you get it to compile and run on other Unix-based OSes, let me know.
More from MakeUseOf.com :
- MakeUseOf Directory : Read about up-to 5 truly useful web apps on a daily basis.
- MakeUseOf ‘Geeky Fun’: - Fun Geeky Pics, Cartoons and Videos.
Mackenzie is a college student who likes to promote Linux and Free/Libre Software. Most of her free time is spent on the computer, helping new users, or hanging out with some of the friends she’s made in the Linux community. Check out her blog, Ubuntu Linux Tips & Tricks.
Read more of this story at Slashdot.

Update: Google has posted on its official blog saying they screwed up by mailing this cartoon out early. A beta version of Chrome will be made available tomorrow in over 100 countries - but, alas, for Windows only to start, with Mac and Linux on the way.
Update 2: It looks like Google has at least semi-launched its Chrome site here. It provides this screenshot of the browser.

Google Blogoscoped has published a lengthy cartoon sent to them by Google and drawn by Scott McCloud that provides the first public details about Google Chrome, an open source browser based on WebKit and powered by Google Gears that has been rumored but never before confirmed.
According to the cartoon (which can be seen in its entirely here - thanks Marshall), the Google Chrome project has already undergone a substantial period of development with engineers working to create a product that’s secure, user friendly, fast, stable, safe, and easily testable. No word yet, however, on when it will be released.
This is a straight shot over the bow of Microsoft, which has tightly integrated its Live Search offering into its dominant Internet Explorer browser (and which, surprise, is in turn tightly integrated into Windows). It also makes for an awkward relationship with Mozilla, whose Firefox browser Google basically funds.
The cartoon breaks down Google Chrome’s features into the following four topics:

Unlike other modern web browsers, which can only run one process at a time, Google Chrome will give each tab its own process. This speeds up overall performance and saves the entire browser from crashing when one tab causes problems.
The multi-process design requires more memory allocation up front but less memory over time as users tend to multitask. It also prevents your computer from slowing down after you browse for an extended period of time and open/close lots of tabs.
Google Chrome also features a task manager that can be used to determine just which tabs and plugins are hogging just how much memory. It’s main purpose is to spot bad actors and close them before they ruin your browsing experience.
Google is leveraging its massive server infrastructure to run automatic performance tests for Chrome. The company is claiming that its Chrome Bot can test the browser on tens of thousands of different webpages within 20-30 minutes of each build. These webpages are chosen on the basis of their popularity, which has already been determined by Google with the data it collects from its search users. When Google started testing Chrome, it only rendered 23% of those pages correctly (no word on how many it gets right as of today now it apparently renders 99% correctly).
Google decided to implement the Webkit rendering engine (also found in Safari and the forthcoming Android mobile platform) because of its speed and simplicity.
To improve the performance of JavaScript processes, Google also decided to build its own JavaScript virtual machine (called V8) from the ground up. The virtual machine leverages the concepts of hidden class transitions, precise garbage collection, and machine code generation to make JavaScript-heavy applications snappier. It will also be made freely available for other browsers to use if they so please.

Google Chrome will feature a few peculiar design choices as well. Most noticeably, tabs will be displayed at the top of the browser window instead of below the address bar and other buttons.
The address bar (which Google is calling the “omnibox” in contrast to Firefox’s “awesome bar”) is intended to make very helpful and unobtrusive suggestions.
The search box not only displays your favorite search engine but also detects what site-specific search engines you’ve used so you can use them from the Chrome toolbar later. For example, if you’ve searched on Amazon, you can do so again in the toolbar by hitting the letter “a” and the tab key before you type your keywords.

A starting page not unlike Opera’s own Speed Dial page gives quick access to your most frequently visited sites and search engines, as well as your recent bookmarks and page visits.
Google Chrome will also let you open a so-called “Incognito” window that doesn’t record anything you do there (a similar feature to the one introduced by Internet Explorer 8 that has been dubbed “porn mode”).
To keep annoyances to a minimum, pages won’t be allowed to pop up new windows outside of their original tabs.
Windows can also be opened without an address bar and other superfluous buttons, allowing certain web applications to appear as though they don’t depend on a browser.
Google Chrome is being developed with the assumption that you will encounter malware online. Each tab is contained within its own sandbox that stops malicious behavior.
Google will also continually download a list of phishing sites and list of malware sites to your computer, which will be used to warn you when you visit them. Site owners will be notified when their sites are put on either of the lists so false positives can be remedied.

With Chrome, Google appears to be making incremental yet important improvements that could add up to something very appealing. If the browser catches on, it will provide a distribution mechanism for Google Gears and help the company fend off Silverlight, Microsoft’s own rich internet app platform.
It has yet to be seen what the response from Mozilla will be like. The foundation can’t be happy that Google has snatched up two of its engineers who are now working on Chrome. But some reinforcement in the attack against Microsoft IE and in support of the open browser movement can’t hurt.
At the very least, Chrome sounds perfect for our tablet.
Crunch Network: CrunchGear drool over the sexiest new gadgets and hardware.
Here's a funny short video of Chinese people being exposed to fortune cookies (an American invention) for the first time:
Americans find high emotional attachment to the slips inside their cookies, looking to them for winning lottery numbers and becoming upset when the fortunes inside are unfortunate. The Chinese, on the other hand, would often tell me after trying the curved vanilla-flavored wafers, “Americans are so strange, why are they putting pieces of paper in their cookies?”Introducing Fortune Cookies to China (Thanks, Tim!)

The RIAA shut down Muxtape but that doesn’t mean its memory won’t linger on the hearts of those who must share their love of the Hold Steady with the world. Enter OpenTape, an open source package that essentially recreates the Muxtape experience on a personal level. You simply download the application, unpack it on your web server, and then upload songs. It took me about two minutes to set-up OpenTape on CrunchGear’s server [embed works below but the main page doesn't... checking with opentape on Twitter] and a few more minutes to upload music. Voila!
I actually applaud OpenTape for offering this tool. While it’s fairly basic, it creates hundreds, if not thousands, of targets for the RIAA and while they wrangle messily with poor Muxtape the concept will already be ubiquitous. Projects like these and OpenClip are cries for help - we want this functionality and we will take it by force if need be. Or maybe people just really like mixtapes.
Crunch Network: CrunchGear drool over the sexiest new gadgets and hardware.
The People's Republic has pardoned iTunes after access to the online music store was apparently blocked in reaction to selling a new Tibet-themed album during the Olympic games.…
| » Login With Sessions by sde |
There has been many inquiries/posts regarding login and sessions, I decided to create and test some scripts to share. I've made a mock-up site consisting of 8 pages: Code:
// these files should be put in a directory named 'inc' inc/auth.php // the meat and potatoes of this subject inc/connect.php // an excellent connection script inc/nav.php // navigation include for site // these files should be on the web root index.php // main page of site link_1.php // page of site link_2.php // page of site link_3.php // page of site logout.php // destroy session and re-direct to login Code:
CREATE TABLE users ( user_id int(10) unsigned NOT NULL auto_increment, username varchar(20) NOT NULL default '', password varchar(20) NOT NULL default '', PRIMARY KEY (user_id) ) TYPE=MyISAM; inc/auth.php PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
|

Managing the daily onslaught of incoming email with filing systems, keyboard shortcuts, and batch processing will only get you so far. When a flurry of new email snows you in within an hour of every inbox sweep, it's time to dig in and get to the source of your email traffic. You've accumulated a sizable email archive over the years, and a new breed of analysis tool can extract meaningful statistics from that data to help you conquer email overload. Who sent you the most email messages last year? What hour of the day do you receive the most new messages? Which of all the mailing lists you're on are the most active? A new command line tool called Mail Trends works with Gmail over IMAP and can give you all that information and more.
Let's take a look at what Mail Trends tells you and how to run it on your Gmail account.
To start analyzing your email usage with Mail Trends, you'll need:
After you run Mail Trends from the command line with Python, you'll get a regular web page full of interesting information about your email usage. Mail Trends logs into your Gmail account, grabs the "message headers" (sender, recipient, subject, date) from your Gmail "All Mail" folder, and generates charts and lists with statistics.
See an example of Mail Trends charts based on a set of email from Enron employees.
My Mail Trends results reveal a few too many email addresses to post in full, but here's my daily email traffic chart, which shows I receive the most email around 10-11AM each day:

Here's what the month of March 2008 looked like on my personal Gmail account. Notice the lower activity on weekends. (Not surprising.)

When I ran Mail Trends on my Lifehacker email account, I wasn't surprised to find out that Adam is my most frequent sender and recipient. However, people listed a few lines down on my Top Sender and Top Recipient list did surprise me. Who you email and how often can give you interesting insight into your communication habits.

While it may seem like self-indulgent data-wanking, Mail Trends and tools like it can help you make informed decisions about how you handle email. For instance, you may find out that the person you send the most email to is your co-worker two cubicles down—and decide to meet in person on a regular to discuss more things offline. If that mailing list you lost interest in months ago is generating a lot of inbox traffic, you could unsubscribe. If you want to process your email in batches, at certain times of day, you could use Mail Trends' time of day chart to figure out what hour brings the most email to your inbox on average, and schedule your processing time around it.
Before we start with Mail Trends, know that this is a command line operation using the Python scripting language. Judging from the comments on the project homepage, some users have run into kinks setting it up (though I got it down with just a couple of tries.) Comfort with the command line and a little past experience with Python will make using Mail Trends easier. If that all doesn't sound like your cup of tea, check out the lower section on easier-to-setup alternatives to Mail Trends.
Still with me? Ok, assuming you've already got Python installed on your machine, here's how to get Mail Trends going. (Note: these instructions assume you know how to navigate directories from the command line. See also Mail Trend's Getting Started page.)
cd into that directory.sudo.C:\Python25\Lib\site-packages\Cheetah and remove the version from the filename so it's just _namemapper.pyd.)cd into the mail-trends directory, and execute the Mail Trends command. See the Getting Started page for a rundown of the options. I used the following command:
Note that you can tell Mail Trends what addresses you send mail from (using the me= parameter, and also exclude mail based on criteria (like --filter_out=to:tips@lifehacker.com.) Play with the program options to come up with the best recipe for your Gmail setup.
Once Mail Trends completes processing, simply open the mail-trends/out/index.html file in your favorite web browser to check out your charts and lists.
Previously mentioned Outlook plugin Xobni is still in invite-only beta, but it looks like one of the best up and coming email analysis tools for Outlook users. Check out the video below for a Xobni demo.
The Seek Thunderbird extension adds "faceted search" to the 'bird. While it doesn't generate usage reports a la Mail Trends, it does list frequency numbers based on date and recipient as you search. Here's a video demo of Seek:
Have you given Mail Trends or other similar tools a run on your email archive? Find out anything interesting? Tell us about it in the comments.
Gina Trapani, the editor of Lifehacker, is cutting off email overload at the source. Her weekly feature, Geek to Live, appears every Monday on Lifehacker. Subscribe to the Geek to Live feed to get new installments in your newsreader.
Read more of this story at Slashdot.
A few weeks ago, Matt announced the new Launchpad plugins for Bugzilla and Trac.
The plugins allow bidirectional communication between Launchpad and the remote bug trackers that have them installed. Obviously, we need to test the plugins - and that’s where we need your help.
If you know of any Trac or Bugzilla instances whose administrators might be interested in installing the requisite Launchpad plugin - or indeed if you run such a bug tracker yourself - you can find details on how to install the plugins and what you need to do to get Launchpad to work with your bugtracker on the Launchpad Help wiki:
So, what will installing the plugins do? Well, initially, installing one of the plugins will mean that:
Once we’re happy that the plugins are working correctly we can use them to add some even cooler functionality to Launchpad:
The Bugzilla plugin is licensed under the Mozilla Public License and the Trac plugin is licensed under GPLv2.
If you’ve got any questions, don’t hesitate to contact us by email at feedback@launchpad.net.
Read more of this story at Slashdot.
MMARated Radio was rolling with the big dogs today as we welcomed Donald Trump Jr. (left) to the program to talk, what else, Affliction.
Some of the topics we touched on included:
* His role with Affliction
* Why did the Trumps decided to get involved in MMA?
* Why not build their own promotion?
* His take on the inaugural show
* An update on the Tito Ortiz situation
* Was he surprised at how much Ortiz demanded?
* Will Affliction look to secure a network television deal (potentially with NBC)?
* The thought process behind Affliction's large payroll
* What we can expect from "Day of Reckoning" on October 11th
| | submitted by Saydrah to worldnews [link] [48 comments] |
I consider this the golden rule of source control:
Check in early, check in often.
Developers who work for long periods -- and by long I mean more than a day -- without checking anything into source control are setting themselves up for some serious integration headaches down the line. Damon Poole concurs:
Developers often put off checking in. They put it off because they don't want to affect other people too early and they don't want to get blamed for breaking the build. But this leads to other problems such as losing work or not being able to go back to previous versions.My rule of thumb is "check-in early and often", but with the caveat that you have access to private versioning. If a check-in is immediately visible to other users, then you run the risk of introducing immature changes and/or breaking the build.
I'd much rather have small fragments checked in periodically than to go long periods with no idea whatsoever what my coworkers are writing. As far as I'm concerned, if the code isn't checked into source control, it doesn't exist. I suppose this is yet another form of Don't Go Dark; the code is invisible until it exists in the repository in some form.
I'm not proposing developers check in broken code -- but I also argue that there's a big difference between broken code and incomplete code. Isn't it possible, perhaps even desirable, to write your code and structure your source control tree in such a way that you can check your code in periodically as you're building it? I'd much rather have empty stubs and basic API skeletons in place than nothing at all. I can integrate my code against stubs. I can do code review on stubs. I can even help you build out the stubs!
But when there's nothing in source control for days or weeks, and then a giant dollop of code is suddenly dropped on the team's doorstep -- none of that is possible.
Developers that wouldn't even consider adopting the old-school waterfall method of software development somehow have no problem adopting essentially the very same model when it comes to their source control habits.
Perhaps what we need is a model of software accretion. Start with a tiny fragment of code that does almost nothing. Look on the bright side -- code that does nothing can't have many bugs! Test it, and check it in. Add one more small feature. Test that feature, and check it in. Add another small feature. Test that, and check it in. Daily. Hourly, even. You always have functional software. It may not do much, but it runs. And with every checkin it becomes infinitesimally more functional.
If you learn to check in early and check in often, you'll have ample time for feedback, integration, and review along the way. And who knows -- you might even manage to accrete that pearl of final code that you were looking for, too.
| [advertisement] Peer Code Review. No meetings. No busy-work. Customizable workflows and reports. Try Jolt Award-winning Code Collaborator. |
With the release of wordpress 2.6.1 I have once again updated my hackergotchi. This will be my third hackergotchi since 2006, and the original image was taken by my mother at our cottage in Pointe au Baril, and yes I am sitting on the barrel that markes the site of the original barrel that the town gets its name from.