On why this blog has seen a slow and agonizing death

My blogging for I' Been to Ubuntu basically stopped a couple of years ago, and it changed its tone the year before that. There are several reasons.

First, I started this blog as a way to write non-tech friendly howtos for a couple of friends who had decided to try Ubuntu. I chose to use version numbers instead of code names and GUI methods instead of CLI ones for just that reason. Once the apt: standard came, I used that wherever possible. These friends are no longer using Ubuntu, and I had no reason to keep writing generic howtos that probably already existed in the documentation, anyway.

Next, I used my need to keep up with FOSS news to write about changes in the next version of Ubuntu. This was the Digg era, and my blog got several front page placements and hit 100K visitors a month, despite the fact that I never promoted it at all (or submitted those links to Digg). I was one of the few blogs dedicated to talking exclusively about Ubuntu. I did amazing things that others weren't doing ... like checking links, verifying assertions, and proofreading my posts before they went live.

At this point, I was spending my normal three or four hours a day reading tech news, and another one or two setting topics and writing. Once OMGUbuntu and a couple other blogs (WorksWithU and Webupd8, I think) started up and knew how to play the Digg game, I realized that I had competition and needed to step up my game. I needed to learn to promote. I needed a real blogging platform. This blog was going to become another job, and I needed to go big or go home.

So I went home. I didn't want another job. I didn't even try to compete. I just wrote the same kind of stuff I had been writing before, but tried to avoid the topics that OMGU wrote on. The blog became a little more technical and I started writing about more general topics like federated social networking, dogfooding, and Ubuntu spinoffs. Oh, yeah, and then there was that "Screw Ubuntu!" phase where I renamed to blog to "I Been to Debian."

So many times, I wanted to keep this blog going, but I never felt I had anything to offer that other sites weren't already offering, and I didn't want to just add to the noise or waste anyone's time. I didn't do Twitter. I didn't submit to Reddit. When I was on vacation, though, I often still blogged, but my heart wasn't in it.

The kinds of things that I wanted to say belonged on social networks, so that's where I put them. I still put them there. I'll go so far as to say that casual blogging in general should die the same death this blog has.

I post on Google Plus now. You can follow me (edit: or follow my I' Been to Ubuhttps://plus.google.com/b/101853016508805771433/pagesntu page) there, if you like. I'm not saying anything extremely profound, though.

I'm going to pull the plug on this blog. The domain will expire, but the content will still be available at http://ibeentoubuntu.blogspot.com

Time of death: 11:18 a.m., Saturday, November 5th, 2011.

What Does "Online Accounts" Do?

I've been running Oneiric (now 11.10) as my primary desktop since pre-alpha so I thought I had a good handle on it. Well, it turns out that I didn't.

This morning, I stumbled upon Online Accounts in the Me Menu. This appeared to be something that I have been asking for for some time now. Gnome 2 had the About Me dialog, which had the potential to offer all kinds of information about yourself to other applications, meaning that you potentially wouldn't have to enter your account information separately in your mail and chat clients. Unfortunately, security concerns meant that the About Me dialog was never used for that purpose.

Online Accounts came up promisingly. I happily entered my email addresses for Google (the only provider supported at this time), and left Mail, Calendar, Chat, Contacts, and Documents all turned on. I mostly live in the browser these days, but desktop integration sure is nice. I opened Empathy to check that IM was working and was prompted to enter my account details. Hmm. I Tried Thunderbird. No joy.

It turns out that Online Accounts just offers an API. There aren't any applications that actually use that API at this point. Yay! Another half feature from Ubuntu (well, officially it's GNOME's, but Ubuntu shipped it in 11.10). It gets more and more frustrating every year.

How may applications possibly connect in the future?

140 characters and URL Shorteners -- Really?

1. AOL
2. Prodigy
3. Myspace
4. Twitter
5. Facebook
6. URL shortening services like bit.ly

What do all these things have in common? They control(ed) the platform, and companies and individuals gladly changed the way they did business or ran their lives . Some of them are gone, and I'm certain that in another ten years, the rest will be footnotes on the Internet.

URL shorteners are kind of unique in that list -- they exist to serve Twitter, mainly. They exist so that we can talk more in our 140 bytes. Unlike the real URL, they don't last as long as the page and they break. We need special browser extensions so that we know where we are clicking through to.

URL shorteners have become the masks for phishing and spam. How awful, just so that we can get our 140 characters.

I can't help but think that in ten years, we're all going to look back on this with a collective "WTF were we thinking?!?" Right now, the average connection speed for developed countries is right around 10 Mbps. Yet, we're limiting communication more than we were in the 90s. And we're stuffing the Internet full of temporary workarounds to this artificial limit. Youtube videos at TBs a day, though? No problem.

It's all rather silly. Let's get a communication platform that allows expression and permanent, discoverable links.

If Google+ gets a real API and federation, I'm willing to back that.

p.s. Diaspora is asking for donations. O_o

SJVN Claims that SIP doesn't Peer and that XMPP doesn't Federate -- WTF?

Image via Wikipedia

"For example, Iptel, Ekiga.net, and ippi are all fine SIP networks, but if youre only on one of them you cant talk to other SIP VoIP users on the other two and vice-versa. The same is true of XMPP/Jingle networks, and, for that matter all the other VoIP networks." -- http://www.zdnet.com/blog/networking/beyond-skype-voip-alternatives/1061

Huh? SIP supports peering and XMPP supports federation. That means that different networks can talk to one another.

"No Extensions NecessaryBut what does SIP peering mean? Is there some new special protocol required for SIP peering? What problems does peering introduce that arent already covered by the existing specifications and products? Those are good questions. First and foremost, SIP peering does not require any new extensions to SIP. The ability to interconnect provider networks is built into the SIP protocol itself. There is a common misconception that SIP peering requires some kind of special profiling of SIP in order to provide interoperability. That is simply not true. SIP was designed to interoperate, even among implementations that support different extensions and capabilities. SIP networks are interconnecting today without additional extensions. SIP has built-in negotiation capabilities that allow fallback to a common baseline set of capabilities when there is mismatch between sides. As an example, SIP has an extension for preconditions (RFC 3312), which makes sure that a call proceeds only if a quality of service (QoS) reservation exists between the endpoints. What happens if only one side supports the extension? If implementations follow the specifications, they will correctly fall back to baseline operation without this feature. Now, some will argue that this is a problem. We need this feature to always be used between our networks! theyll say. The interesting thing is, the extension is implemented at the endpoints, not in the network servers. Thus, a SIP profile that mandates usage of the extension could not be applied to the SIP servers doing the interconnection. Fortunately, the SPEERMINT working group has recognized that SIP peering is not about SIP profiling. Its charter explicitly rules profiling as out of scope, in fact. So, if SIP peering is not about a SIP profile, what is it about?" --http://www.tmcnet.com/sip/0306/sip-columns-speaking-sip-0306.htm

Also:

"1. Introduction

XMPP Core [1] describes the client-server architecture upon which Jabber/XMPP communication is based. One aspect of such communication is "federation", i.e., the ability for two XMPP servers in different domains to exchange XML stanzas. There are at least four levels of federation:

Permissive Federation -- a server accepts a connection from any other peer on the network, even without verifiying the identity of the peer based on DNS lookups. The lack of peer verification or authentication means that domains can be spoofed. Permissive federation was effectively outlawed on the Jabber network in October 2000 with the release of the jabberd 1.2 server, which included support for the newly-developed Server Dialback [2] protocol.

Verified Federation -- a server accepts a connection from a peer only after the identity of the peer has been weakly verified via Server Dialback, based on information obtained via the Domain Name System (DNS) and verification keys exchanged in-band over XMPP. However, the connection is not encrypted. The use of identity verification effectively prevents domain spoofing, but federation requires proper DNS setup and is still subject to DNS poisoning attacks. Verified federation has been the default service policy followed by servers on the open XMPP network from October 2000 until now.

Encrypted Federation -- a server accepts a connection from a peer only if the peer supports Transport Layer Security (TLS) as defined for XMPP in RFC 3920 [3] and the peer presents a digital certificate. However, the certificate may be self-signed, in which case mutual authentication is typically not possible. Therefore, after STARTTLS negotiation the parties proceed to weakly verify identity using Server Dialback. This combination results in an encrypted connection with weak identity verification.

Trusted Federation -- a server accepts a connection from a peer only if the peer supports Transport Layer Security (TLS) and the peer presents a digital certificate issued by a trusted root certification authority (CA). The list of trusted root CAs is determined by local service policy, as is the level of trust accorded to various types of certificates (i.e., Class 1, Class 2, or Class 3). The use of trusted domain certificates effectively prevents DNS poisoning attacks but makes federation more difficult since typically such certificates are not easy to obtain.

The remainder of this document describes in more detail the protocol flows that make it possible to deploy verified federation, encrypted federation, and trusted federation. Protocol flows are shown for federation attempts between various combinations to illustrate the interaction between different federation policies." -- http://xmpp.org/extensions/xep-0238.html

Sure, they have to be turned on, meaning that Facebpook's XMPP doesn't federate, for instance, but most XMPP networks do, and it's the same for most SIP neworks. In fact, this is from Ekiga:

"Using the Ekiga.net SIP addressThe Ekiga.net service accept calls to its registered users without being registered to Ekiga.net. Just call the sip:user@ekiga.net address directly. " --http://wiki.ekiga.org/index.php/Peering

Peering and federation are the strongest selling points of SIP and XMPP. How could you miss them?

Am I misunderstanding you, SJVN? I hope so.




Personally, I'm waiting for a bunch of providers to step up and provide webmail / SIP / XMPP + social extensions all under one address.

Related articles
Beyond Skype: VoIP Alternatives (zdnet.com)

New video widget

Image via Wikipedia

"For the rest of the changes, we needed a video widget that was more flexible than the X-based one we were using. So from Totem 3.2, we'll start using clutter, and clutter-gst," said Hadess.

What does this mean for Unity, since it uses Compiz? Will Canonical's desktop become more and more divorced from GNOME standard, including the included apps? I'm betting it will. In fact, I've been encouraging Ubuntu to go this direction for quite some time.

The Choice of AMD is Rewarded and Go Ahead with AMD64

Image via CrunchBaseThe last couple of laptops I've bought have been AMD machines, largely from my desire to get the best performance to price ratio, but also because the integrated graphics chips are much better than Intel's. That choice is being rewarded with 11.04. The open-source drivers work extremely well for daily desktop use, though they have half the performance of the Catalyst driver.

Phoronix recently also benchmarked 32-bit, 32-bit PAE, and 64-bit systems, and the 64-bit systems were significantly faster in almost all tests.

The takeaway? If you're going to run 11.04 on a laptop, AMD's Fusion is a good choice, and you'd be best advise to install the AMD64 version.

Related articles

• Dell Inspiron M102z Budget Laptop With AMD Fusion CPU (mydigitallife.info)
• AMD ships 32nm A-Series Fusion APU Llano (geek.com)
• MSI slips AMD's Fusion into 13-inch X370 u ltraportable, hopes you'll notice (engadget.com)

eOS 0.1 (Elementary Jupiter) Released and Reviewed

As I've written before, I've been using Natty and Unity for about three months straight now, and I'm extremely happy with how it's shaping up. I'm always interested in other projects, though, especially ones with a philosophy which includes consistent look and feel. Elementary is a project like that, so I leapt on the release announcement and torrented the 614MB .iso.
Two words described the distro -- fast and elegant.
I first ran the live CD in Qemulator under Natty, but I knew the video drivers were holding me up so I wrote out a USB drive for it and rebooted. Even running from the drive, everything is extremely responsive. It works as expected.
Pros:

• Fast
• Limited, very consistent applications
• Midori is awesome and is  all that I wanted Epiphany to be for years
• Postler only asks for your e-mail address and password to set up common mail options. Amazing and easy
• Looks amazing and the applications take up little vertical space
• Abiword and Gnumeric instead of OO.o or LO
• Traditional GNOME app menu
• I like that the Elementary devs have standardized on Vala and GTK+

Cons:

• Postler had trouble connecting to my GMail account and gave no feedback for about fifteen minutes
• Dexter doesn't use my webmail coontacts
• Empathy's setup screen isn't at Postler's level yet (and why should I have to input my GMail account again?
• Inconsistent configuration options for the non-eOS apps. I assume that they will be modified later
• Midori lacks installed extensions (edit: open the sidebar to find them) and doesn't work with some web apps (e.g. Picasaweb)
• There is a lot of turmoil about the installed apps and that has to be getting in the way of work

This is a 0.1 release, but it's based on Ubuntu 10.10 so it's already quite stable. If the choice of applications settles down (Elementary Nautilus or not?), eOS should be great by 0.2. Who can ask for more than that?

Unity Holds Promise, but Needs Work

Image by Andrew Currie via FlickrFor those of you who have had every Ubuntu news site blocked at the /etc/hosts level for the last ten months and have no idea what Unity is, I'll tell you that the Ubuntu train has jumped the GNOME tracks and gone even further out on its own (just as I called it) by creating its own desktop, called Unity, due to be released with 11.04.

In order to give a proper review, I began using Unity on Natty for daily work almost two months ago, pre-Alpha, and have watched the furious pace of development. Unity's design is brilliant; the implementation isn't. There's still time to fix most of the bugs, but I don't expect to see Unity hit its stride until 11.10 or so, (and 12.04LTS should be solid).

Ayatana didn't follow my suggestion of keeping the UI intact and change the backend. Instead, the team went for a completely different look in order to differentiate Ubuntu from all other OSes. The design is unique and beautiful.

 Despite completely changing the UI, Unity is remarkably discoverable (not intuitive), especially for power Windows users. These users are probably very used to using the super key to get things done, and unity handles that very well. Press super, and the launcher appears; hold the button down, and the shortcuts for the launcher are overlain on the dock buttons themselves; double-press the key, and Unity's search interface comes up. Within fifteen minutes of this overlay feature appearing on my computer, I was using the keyboard shortcuts and saving myself a bunch of time over mouse-keyboard context switching.

Like I said -- "good design; needs work." Stability is a huge problem for my AMD / Radeon laptop. I can't alt-tab without crashing Unity. NVidia has a similar known bug. Even avoiding switching apps this way, which is quite annoying, Unity still crashes once or twice a day on me, leaving me with nothing until I ctrl-alt-F1, login, and enter DISPLAY=":0" unity, then switch back. I don't understand why there's not a process monitor to restart Unity after a crash.

Unity's search system is also painfully slow and inconsistent. Sometimes it returns nothing for an exact application match (e.g. "software" might not give you the Software Center), but pressing backspace to delete a character or two might match the same word (e.g. "softwa" does match). The screen overlay may or may not appear or disappear depending on what you type. Your cursor might be focused in the search box, or you might continue to type and click in the application you just left -- there's no way to know, and that lottery isn't one I want to play with my important documents.

The recent implementation of Places and an API for it mean that not only do we have easy access to apps, files, and people, we could get extras like web search or Google docs integration. As long as it doesn't get overloaded with features, and those stay as optional extensions, all should be good.

Overall, Unity shows great promise, but it's definitely not ready for the average user's desktop ... yet. Give it six months.  

Related articles

• Joe Barker: Ubuntu 11.04 My Experience So Far (joeb454.com)
• Jono Bacon: Working Together To Get Unity Ready For Natty (jonobacon.org)
• Fabien Tassin: Unity in Natty: is it for me? (ftagada.wordpress.com)

Is StatusNet Really an Appropriate Base for a Social Network?

Image via CrunchBase

Why is there so much talk of ditching Facebook? Privacy issues, of course. There's also more. As much as Facebook does (and it does a lot), it fails to do what people need it to. Let's look at Matt Zimmerman's recent post, Optimizing my social network. I'll quote a bit from it.

Here is the arrangement I’ve ended up with:

If you just want to hear bits and pieces about what I’m up to, you can follow me on identi.ca, Twitter or FriendFeed. My identi.ca and Twitter feeds have the same content, though I check @-replies on identi.ca more often.

If you’re interested in the topics I write about in more detail, you can subscribe to my blog.

If you want to follow what I’m reading online, you can subscribe to my Google Reader feed.

If (and only if) we’ve worked together (i.e. we have worked cooperatively on a project, team, problem, workshop, class, etc.), then I’d like to connect with you on LinkedIn. LinkedIn also syndicates my blog and Twitter.

If you know me “in real life” and want to share your Facebook content with me, you can connect with me on Facebook. I try to limit this to a manageable number of connections, and will periodically drop connections where the content is not of much interest to me so that my feed remains useful. Don’t take it personally (see the start of this post). Virtually everything I post on my Facebook account is just syndicated from other public sources above anyway. I no longer publish any personal content to Facebook due to their bizarre policies around this.

Mentioned are identi.ca, Twitter, Friendfeed, Google Reader, LinkedIn, a blog, and Facebook. Matt needs seven services to cover all his bases. Sure, many of the services are syndicated to other services, but he checks some more (Identi.ca) and some less (Twitter).. What happens if I subscribe to the wrong service to follow Matt? Am I relegated to being a second-class social network citizen?

I believe that this situation frustrates the average person as much or more than privacy issues. A lot of people just don't care about privacy, are ignorant of what's being shared, are willing to make the trade-off because of a lack of alternatives, or just don't feel locked in.  You can see the feature creep in Facebook, now many people's main e-mail client, as Facebook tries to be all things to all people.

A week ago, Shashi write a wiki page called "Why build on StatusNet?" Evan Prodromou responded to the article with this dent: "GNUsocial, Diaspora, et. al.: use StatusNet to build your distributed social network. It'd be dumb to start over from scratch." While I agree with the second half of the statement (starting from scratch would certainly be dumb), is it fair to ask a developer to build on SocialNet?

I'm no crack developer, but I'm going to attempt to answer this question by Looking at as many of the Facebook features as possible and comparing them to current StatusNet features as implemented, and try to gauge how difficult adding the necessary elements would be. I'm not going to pull punches. "Let's tie a bunch of unconnected services together and we're done" is not a realistic plan for replacing Facebook (and LinkedIn, and your blog, and ...) successfully. I'll be using the Wikipedia list of Facebook features as a starting point.

1. Publisher: This is the core functionality of Facebook. You post something. It appears on your wall. It appears on your friend's wall in some cases. etc. StatusNet has a similar setup, but it's feed-based network obviously does things a little differently.
   Status(Net): Mostly implemented.
2. News Feed: This is the first page you see when you log into Facebook. Users see updates and can "Like" or comment on these updates. Photos and video posts are viewable on the same page. StatusNet's "Personal" tab is similar, but is not the page seen on login (on Identi.ca, at least). This is easily changed, but the tab lacks threaded comments and direct viewing of multimedia. There is a gallery plug-in, but threaded comments are much more difficult to do. Do they even want to?
   Status(Net): Partially Implemented.
3. Wall: The wall is where all your FB updates go, and where people can respond. SN has your profile page, much the same, but there are, again, missing features like comments.
   Status(Net): Partially Implemented.
4. Photo and video uploads: FB houses many people's online gallery. It handles photos and videos. They can be tagged. There are comments. All this stuff goes to your news feed. SN has nothing like this. The Gallery program has none of these abilities. This is a hard problem.
   Status(Net): Ground Zero.
5. Notes: This is a blogging platform with tags and images. It's limited, but it's far beyond anything that SN has. The only option is to use a Drupal add-on to turn it into an SN hub. What's missing from Drupal? I don't know.
   Status(Net): Ground Zero.
6. Gifts: I know. You're a geek. You hate gifts. You especially hate paying for gifts. Other people give me gifts all the time, though, so there must be some interest. SN doesn't have anything, but gifts seem easy to implement.
   Status(Net): Nothing, but not too difficult.
7. Marketplace: Craigslist on FB? Sure, why not? SN is in the dark here.
   Status(Net): Ground Zero.
8. Pokes: What's a poke? Who knows? Who cares! Still, SN would need them because I cqn guarantee the absence of them would become a big deal. Again, nothing, though not too hard, I'd guess.
   Status(Net): Nothing, but not too difficult.
9. Status Updates: This is what SN is all about, but status updates are public. Could privacy happen on SN? I don't know.
   Status(Net): Mostly there.
10. Events: FB is the event planner and the place to post the pictures after the event. That's really what it excels at. SN? Nowhere?
    Status(Net): Ground Zero.
11. Networks, groups and like pages: SN has groups and is getting Twitter-like lists, but there are no networks as far as I can tell. I can "favorite" a post, but there is no way to create a page for other people to "favorite/like." Networks should be just designated groups. Likes need to be implemented in other places, and could be added pretty easily after that.
    Status(Net): Mostly there.
12. Chat: FB chat sucks, but it exists. SN doesn't really have chat, though there are some IRC and XMPP plug-ins which can fake it. They're not private, though. Ouch. Think someone will get bitten by that one? Sure. Tack on an XMPP server to SN, and you're ready to go.
    Status(Net): Nothing, but not too difficult.
13. Messaging: FB can be your e-mail client. It can even send mail outside the walled garden (last I chacked). SN has a private messaging feature. With federation, this would operate similarly.
    Status(Net): Implemented.
14. Usernames: FB lets you get a page with your name, unless your name is the same as someone famous, that is. ;). SN has your profile at a nice, readable URL by default.
    Status(Net): Implemented.
15. Platform: This is probably the biggest thing FB has brought ot the table and Farmville numbers tell you that it's pretty important. Can SN follow? OpenSocial leads the way. Unfotunately, it doesn't have that viral thing going for it.
    Status(Net): Ground Zero.

So ... where does SN stand as a base for Diaspora to build on? Maybe 50% I guess that's better than nothing. I've heard from a mailing list that the Diaspora guys are going to use OStatus. If that's true, then they might want to think about SN. I understand they have already built a base application, though.

What do you thin? Have I missed any Facebook features that SN needs or already has? Did I get something wrong? Do you think that SN would make a decent social network, or is micro-blogging just the wrong model for it?

Laurent Eschenauer talks about OneSocialWeb with Robert Scoble

Interesting video. Watch the whole 23 minutes:

Morevna: Open Source Anime Using Synfig, Blender, Gimp, and Krita

Image via Wikipedia

Most of the readers of this blog probably already know about Big Buck Bunny, Blender's open movie project codenamed Peach; some may even know about Sintel (Durian). Few, however, know about the Morevna project, an anime project dedicated to using only open-source tools in its production. From the site:

The story is based on the Russian fairy tale “Marya Morevna”. It is completely reworked to futuristic high-tech twist with a large amount of technobabble, expounded in a style specific to anime genre. 

Screenplay: Russian, English (draft translation). 

Synfig is an authoring tool designed from the ground up to do smooth animation without drawing multiple frames in between the key frames, a process called "tweening," meaning that the number of artists required to complete a major project is significantly reduced. The artist defines the position of the objects in two keyframes, chooses a path for the movement, and assigns filters or deformations, and the result is computer generated. I understand that normal anime has very few tween frames and limits motion on the screen to limit the amount of work artists have to do. Synfig's method means a smoother-looking movie with thirty frames per second and the ability to add more animated movement.

The Morevna Project also uses Blender for many of the props, such as the helicopter and the motorcycle in teh video below. I find the mix of 3D and 2D animation a little unnerving, but it is a common style these days which again, reduces the amount of time spent drawing individual frames.

Diaspora Focusing on P2P, Shunning S2S

Image via Wikipedia

I sent an e-mail to the guys at OneSocialWeb asking them about their involvement with the Diaspora team.

Does OWS have plans to reach out to Diaspora to work on federation and specifications with them? I've noticed that StatusNet's OStatus fills a very similar role, as well. Could you involve them, as well? And then there's GNU Social ....

I'd really hate to see so much work going on with the same purpose (federated, Free social networking) but end up with incompatible servers and clients.

Anyway, thanks for all the hard and wonderful work.

Here was the response.

We got in touch with them (Diaspora) but at this stage it seems they are looking into a peer-to-peer approach using Gnu encryption (GPG). So, on a technical level, our projects are quite different. We will however keep in touch with them, like we are with the get6d guys, the GnuSocial mailing list, the other XMPP efforts, and the work at the W3C.

I personally think that competition is good. I don't see it as competition in fact, more as various groups experimenting with different ideas. They are so many ways to solve this: P2P vs client-server, HTTP only vs XMPP, Atom/AS vs RDF, OpenID&OAuth vs FOAF+SSL, End to end encryptions, DRM, etc etc ... I'm sure that out of these various attempts, some good ideas and concepts will emerge. It will be then the responsibility of the bigger players & standard committees to put some order in there.

At our level, we are actively engaged with the XMPP community and the W3C Social Web working group. So I'm confident that we can converge towards a good set of protocols in the near future.

Cheers and thank you for your ongoing support !

It appears that we now have very many competing projects. I hope one of them makes it. I'm much more optimistic about S2S for the average user than I am about P2P. Very few people leave their computers on all the time, a requirement for this type of communication if it's peer to peer. Server to server seems much more likely to enable social interaction when one of the parties isn't available.

F-Spot is Gone: Now Can We Get Rid of Tomboy?

Image via Wikipedia

F-Spot has been voted off the island by developers at UDS this week. The Mono application will be replaced by Shotwell, written in Vala. Since the only other Mono application I see in the default install is Tomboy, would it make sense to conspire to kick Tomboy Notes off the show next week and Mono off the CD the following episode?

This isn't a political demonization of Mono -- I'm actually quite surprised that F-Spot got the boot since so much work was done to it in order to have it be a stand-in for the Gimp. Still, it makes little sense to keep Tomboy and the Mono runtime when space could be freed on the CD by using Gnote, a C+ program that is basically a drop-in replacement for Tomboy.

TerminateSafe, Save-free Applications, and oom_adj

Image via Wikipedia

There's a good proposal going through the rounds on the FreeDesktop.org mailing list which seeks to help the kernel decide which process(es) to kill first in the event of memory pressure. The proposal is simply adding a TerminateSafe=true key to the .desktop files of applications which are stateless or which constantly save user data. Examples of stateless applications might be the character map and calculator tool. Applications which save continuously might include Tomboy. Terminals, office suites, and IDEs would not have this key set to "true."

The Linux kernel's OOM (out of memory) Killer has a method to determine which processes get killed first in a critical situation: it's called "magic." No, not really. It is complicated, though, and it offers a "user-friendly" way to help the kernel make its decision. oom_score is located in /proc/ under the number of each running process. The oom_score for each process is based on factors such as memory use and running time. The process directory also contains oom_adj, which, as the name suggests, allows one to adjust the score of the process. Think of it like nice, but for killing, not running.

If TerminateSafe=true were implemented on Linux, it would likely signal the desktop environment to adjust oom_score to put the application on the top op the assassination list using oom_adj. Other OSes might use a different method or not support the key at all.

The problem with this approach is that the process the .desktop file spawns may not even be the main process if the file calls a script. The situation is made worse by processes that fork. Luckily, the kernel offers process groups to handle this situation, something Systemd is planning to use.

I hope you've heard of Systemd, the init/upstart replacement with a model half way between launchd and inetd. If you haven't you should take a look at it.

First Impressions of the New Unity Netbook Interface

Mark Shuttleworth and Canonical unveiled the new Ayatana work that has been happening. Unity is a new interface for Ubuntu Netbook Edition which targets the instant-on market. Other instant-on players include Phoenix Hyperspace, ASUS Express Gate (Splashtop), and Xandros Presto. Linux basically owns the space with OEMs. These OSes are stripped down to almost nothing and typically don't access the filesystem at all, instead running stateless. Expect ChromeOS to compete strongly in this market when it's released later this year.

Ubuntu will be following the normal market trend of releasing custom-built images for OEM hardware, working with the manufacturers to get the boot time as low as possible. Shuttleworth is claiming that Unity will have a 7 second boot time using SSD.

What does Unity look like on my netbook? Take a look.

Compare this to Hyperspace:

And to Express Gate / Splashtop

Unity give more of a functional look to the genre, departing from the other's spartanism, which I think will give customers a feel of more control and greater ability.

As far as I can tell, it is not possible to modify the left launcher directly. I tried to add Chrome (my preferred browser), but couldn.t do it until I already had Chrome launched and the icon appeared in the launcher, allowing me to right-click and pin the application to the panel. You can use the top folder icon to gain access to installed applications not on the launcher panel. If that icon choice seems unintuitive to you, know that you are not alone in thinking that.

The interface is clean and easy to use. Within two minutes, I had discovered everything I needed to know to get to work. The panel iicons have an arrow on the left side when they are running, and the active application is identified by an arrow on the right. If you have more than one window of a given application open, right clicking will give you a scaled view of all the application's windows.

My one complaint about the interface is that it is quite easy to get notification windows which bleed off the bottom of the screen., but that shouldn't be a problem for most people using the interface as designed. Unity is already 90% there, and you can expect that Maverick (to be released 10/10/10 -- is he a numerologist?) will operate amazingly well with this interface.

New Project: Live Help Links

Image via Wikipedia

While sitting in http://webchat.freenode.net/?channels=ubuntu-classroom on Monday, I decided that adding links like that one to the Ubuntu docs would add some "Live Chat" feel to Ubuntu. I proposed the idea to the Docs Team, didn't get much in the way of negative feedback, and decided to go forward with the plan.

There are several things that need to be worked out:

• Since throwing everyone into #ubuntu would be a bad idea, we probably need to use application-specific links
• Are these for Ubuntu only (#ubuntu-application) or do we use the official channel?
• Do we include support for all applications (a huge undertaking) or just default ones (easily manageable)?
• How do we make this prominent and easy to understand?
• Since not all applications have official support channels on Freenode, how do we handle the others?
• Create new channels on Freenode. This answer is especially useful if we went with #ubuntu-application channels and less appropriate if we want official channels.
• Use a service like Mibbit.com. We are depending on a third party, which is not something I want to do long term.
• Launch Empathy. Empathy's IRC support is terrible, and it doesn't support passing irc:// URIs now.
• How do we handle internationalization. My thought is to leave that up to the language teams. They can decide what channels to use based on whether they exist and/or are populated.

Quite obviously, I'm not the first person to think of this: there are two projects on Launchpad that are similar (but dead). They depended on GAIM, though (and that should tell you their age), while I am proposing a method which works without an installed IRC client and which works across all flavors of Ubuntu. There have been many moves to get XChat into the default install to push more live help.

Thoughts?

Too many places to click!

What's the problem with tabs (or any other MDI)? I suddenly have two place to click to choose which application to use. We've tried fiing this problem for years. First, when we use mostly SDIs, the computers weren't powerful enough to make this a problem. When it did become a problem, we tried grouping windows together in the same taskbar entry. People hate it. They lost windows all the time. Later, we "solved" this problem by using tabbed interfaces to simplify the taskbar, but we've really only moved the problem.

Like a lot of people, I run 60-70% of my apps in the browser. Maybe more on some days. A lot of these applications are my first choices. It screws with me. Let's say I'm listening to music and I want to change my playlist. Do I go to the taskbar (if I'm listening in Rhythmbox), Go to the notification area (if RB is hidden there), or go to one of my browser tabs, possibly in another browser window (if I'm using Pandora or the like)? I can't train myself because the situation is always different?

I have taskbar buttons and tabs, then I have more tabs inside my tabs for apps like Zoho, and I have the system menu, the application menu, and quite possibly a third menu inside my browser. I can't even remember whether the web page I'm looking at is even in the web browser, or whether it's in Miro or Rhythmbos. Arrrrgghh!

Are a global menu and a tabbed window manager part of the answer? I don't know. What do you think?

Ubuntu 10.04 LTS, Amazon S3, and OVF

I want to throw up a video about OVF and virtual server portability which I think is worth watching owing to Canonical's intent to move more into cloud services for its servers.

Ubuntu Week's Social From the Start Session -- Ubuntu Updates and the MeMenu

Image by parttimesock via Flickr

I posted a suggestion to jcastro which he seemed to like: setting up Gwibber on OS installation to be set following Ubuntu and Ubuntu One announcements so that users can be aware of major bugs in updates (and not update or find the fix) and know about Ubuntu One outages.

I understand that Ubuntu (or Canonical) runs its own StatusNet server, so accounts could be given to new users during the installation if they didn't already have one. More integratiion could be found between help and application resources using status update messages.

There were many proposed services: Google Buzz has planned support, PicasaWeb was suggested, and there was even official talk of linking F-Spot to Gwibber's new API to allow viewing friend's photos inside F-Spot.

Qense also mentioned using Software Center to share thought about a certain application. I suppose it could be used to ask questions, as well.

There is talk of getting the Gwibber service to run headless on an Ubuntu server installation so that LoCo teams can use their new StatusNet subdomains automatically.twitter

Ubuntu Open Week's Ubuntu One Session.-- Music Overages Handled, and The Future of Sync'ed Preferences

Maverick might end up eschewing GConf for DesktopCouch in order to have preference sync'ing. Is this more of a sign of Ubuntu drifting from GNOME?

<rodrigo_> daengbo, I am planning on writing a gsettings (gconf replacement) backend that stores config settings in desktopcouch

[11:40] <qense> Please not that GConf is planned to be deprecated in the future in favour of GSettings/DConf.

[11:40] <qense> note*

[11:40] <rodrigo_> daengbo, so yeah, once that is available, you could have all your settings on desktopcouch

Also, the music overage problem has been handled by simply allowing it.

daengbo asked: How are music purchases handled when your 2GB quota has been reached?

[11:53] <+aquarius> Music purchases can still be made if you've reached your quota