Sometimes we need text so that we can document history, such as the death of our beloved smart phones. But, our phones are not smart; smart things do not fill themselves with nonsense. For some reason, the number of chatting, texting, mailing, talking channels is constantly increasing, which is also increasing the amount of “garbage information” that is entering our brains. Sometimes there is so much that I have to cut off myself off from the channels. Maybe my phone shouldn’t have a text function at all! It needs to be saved.
In a future post, I will discuss how we might mitigate this by adjusting our habits, but considering that all of these messages contain text, my smart phone should be able to consolidate, cross-reference, reply in-line, or find a way reduce the number of channels and the number of taps required to explain something.
A smart phone does not walk itself into traffic because it needs to reply to so many messages. Poor phones.
consistent control over more AWS services with aws-cli, a single, powerful command line tool from Amazon
Readers of this tech blog know that I am a fan of the power of the command line. I enjoy presenting functional command line examples that can be copied and pasted to experience services and features.The Old World
Users of the various AWS legacy command line tools know that, though they get the job done, they are often inconsistent in where you get them, how you install them, how you pass options, how you provide credentials, and more. Plus, there are only tool sets for a limited number of AWS services.
I wrote an article that demonstrated the simplest approach I use to install and configure the legacy AWS command line tools, and it ended up being extraordinarily long.
I’ve been using the term “legacy” when referring to the various old AWS command line tools, which must mean that there is something to replace them, right?The New World
The future of the AWS command line tools is aws-cli, a single, unified, consistent command line tool that works with almost all of the AWS services.
Here is a quick list of the services that aws-cli currently supports: Auto Scaling, CloudFormation, CloudSearch, CloudWatch, Data Pipeline, Direct Connect, DynamoDB, EC2, ElastiCache, Elastic Beanstalk, Elastic Transcoder, ELB, EMR, Identity and Access Management, Import/Export, OpsWorks, RDS, Redshift, Route 53, S3, SES, SNS, SQS, Storage Gateway, Security Token Service, Support API, SWF, VPC.
Support for the following appears to be planned: CloudFront, Glacier, SimpleDB.
The aws-cli software is being actively developed as an open source project on Github, with a lot of support from Amazon. You’ll note that the biggest contributors to aws-cli are Amazon employees with Mitch Garnaat leading. Mitch is also the author of boto, the amazing Python library for AWS.Installing aws-cli
I recommend reading the aws-cli documentation as it has complete instructions for various ways to install and configure the tool, but for convenience, here are the steps I use on Ubuntu:sudo apt-get install -y python-pip sudo pip install awscli
Add your Access Key ID and Secret Access Key to $HOME/.aws/config using this format:[default] aws_access_key_id = <access key id> aws_secret_access_key = <secret access key> region = us-east-1
Protect the config file:chmod 600 $HOME/.aws/config
Optionally set an environment variable pointing to the config file, especially if you put it in a non-standard location. For future convenience, also add this line to your $HOME/.bashrcexport AWS_CONFIG_FILE=$HOME/.aws/config
Now, wasn’t that a lot easier than installing and configuring all of the old tools?Testing
Test your installation and configuration:aws ec2 describe-regions
The default output is in JSON. You can try out other output formats:aws ec2 describe-regions --output text aws ec2 describe-regions --output table
I posted this brief mention of aws-cli because I expect some of my future articles are going to make use of it instead of the legacy command line tools.
So go ahead and install aws-cli, read the docs, and start to get familiar with this valuable tool.Notes
Some folks might already have a command line tool installed with the name “aws”. This is likely Tim Kay’s “aws” tool. I would recommend renaming that to another name so that you don’t run into conflicts and confusion with the “aws” command from the aws-cli software.
[Update 2013-10-09: Rename awscli to aws-cli as that seems to be the direction it’s heading.]
*[Update 2014-10-16: Use new .aws/config filename standard.]
Original article: http://alestic.com/2013/08/awscli
In this week’s show:-
- We take a look at what’s been happening in the news:
- Open Source is full of horrible people
- All your books are belong to Adobe
- NVidia pick Wayland… and Mir?
- Microsoft CEO reinforces sexist messages
- Chromebook ponders dropping support for Linux ext filesystems
- Protect your privacy online with anonabox
- Google discover a POODLE
- Google announce new Android version, and new devices to run it
- Gaming news happened!
- We take a look at what’s been happening in the community:
We’ll be back next week, when we’ll be talking about diversity at events like OggCamp and looking over your feedback.
Please send your comments and suggestions to: firstname.lastname@example.org
Join us on IRC in #uupc on Freenode
Leave a voicemail via phone: +44 (0) 203 298 1600, sip: email@example.com and skype: ubuntuukpodcast
Follow us on Twitter
Find our Facebook Fan Page
Follow us on Google+
We need your help and test results, both positive and negative. Please head over to the milestone on the isotracker, select your favorite flavor, and perform the needed tests against the images.
If you've never submitted test results for the iso tracker, check out the handy links on top of the isotracker page detailing how to perform an image test, as well as a little about how the qatracker itself works. If you still aren't sure or get stuck, feel free to contact the qa community or myself for help.
Thank you for helping to make ubuntu better! Happy Testing!
We have been informed that Gracenote (formerly Tribune Media Services) will be ending the guide data service currently used by most users of Schedules Direct. Their plan is to end support for this service on November 1, 2014.
A service is being developed to mimic the DataDirect feed. It has most, but not all of the data currently in the Data Direct feed and will be updated daily. What does this mean for Schedules Direct?The guide data provider (Gracenote) that Schedules Direct uses is changing how they present the guide data to users. Schedules Direct has taken it upon themselves to write a server side compatibility layer so existing applications will continue to get guide data. This does require a change in the URL that applications use to download which is why an update to MythTV is necessary.What does this mean to you as a user?If you have a paid subscription to Schedules Direct that will continue the way it has worked previously. A simple update to MythTV will be required for users on a supported version of MythTV.
Users that have enabled the MythTV Updates repo and are on a current version of MythTV and a supported version of Ubuntu will receive the fix for this via regular updates. The Mythbuntu team has always recommended enabling the MythTV Updates repo in the Mythbuntu Control Centre and staying up to date on fixes builds. The fix for this issue was added to our packages in the versions in the below table. More information on the Mythbuntu provided MythTV Update repo can be found here.
Users on builds prior to 0.27 (eg. 0.26, 0.25) will need to either upgrade to a supported build version (see Mythbuntu Repos) or use one of the workarounds (See MythTV Wiki)
MythTV Version Fixed in version 0.28 (development)2:0.28.0~master.20141013.4cb10e5-0ubuntu0mythbuntu# 0.27.X2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu# Prior to 0.27.XWILL NOT BE FIXED, please either update or see the MythTV Wiki for a workaround
For more information on this issue, please see the writeup on the MythTV wiki. Questions can be directed to the MythTV-Users mailing list
A friend of mine sent me a link from her "+" account last night, publicizing a fundraising effort...
Admittedly, I've never been impressed with "+", so I rarely (if ever) look at it. Because she was a friend, and I like to help friends, I decided to go in and see what the link was about. I ended up staying longer than I originally planned and took a look around.
What did I see? I saw a lot of people who used to make Planet Ubuntu a lively, exciting, and vibrant place writing prolifically on "+" instead. Sadly and disappointingly, they rarely post on Planet these days.
Are you one of these people?
Friends, do consider the effect of the following:
When you upload, submit, store, send or receive content to or through our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content. The rights you grant in this license are for the limited purpose of operating, promoting, and improving our Services, and to develop new ones. This license continues even if you stop using our Services ...
Something smells wrong with this.
Friends, it's really not that difficult to host a blog and to use a more respectful service. I hope you'll consider that one small step in the sprit of not becoming the product, or even better, in the spirit of making Planet Ubuntu *the* place for Ubuntu happenings.
image by Terry O'Fee
Last month I posted about packaging and why it takes time. I commented that the Stable Release Update process could not be rushed because a regression is worse than a known bug. Then last week I was pointed to a problem where Baloo was causing a user's system to run slow. Baloo is the new indexer from KDE and will store all your files in a way you can easily search for them and was a faster replacement for Nepomuk. Baloo has been written to be as lightweight as these things can be using IONice, a feature of Linux which allows processes to say "this isn't very important let everyone else go first".
Except IONice wasn't working. Turns out Ubuntu changed the default Linux scheduler from CFQ to Deadline which doesn't support IONice. Kubuntu devs who had been looking at this for some time had already worked out how to change it back to the upstream defaults in our development version Utopic and in the backports packages we put on Launchpad. Last week we uploaded it as a proposed Stable Release Update and as expected the SRU team was sceptical. We should have been faster with the SRU which is our fault. They're there to be sceptical but the only change here is to go back to using upstream defaults. After much wondering why it was changed in the first place it seems that Unity was having problems with the CFQ scheduler and so it was changed, now we have suggestions that Baloo should be changed to adapt to that which is crazy. Nobody seems to have considered fixing Unity or that making the change in the scheduler in the first place would affect software outside of Unity. We tried taking the issue to the Ubuntu Technical Board but their meeting didn't happen this week.
So alas no fix in the immediate future, if it bothers you best use Kubuntu Backports. When someone on the SRU team is brave enough to approve it into -proposed we'll put out a call for testers and it'll get into -updates eventually. It's what happens when you have a large project like Ubuntu with many competing demands, but it would be nice if the expectation was on Unity to get fixed rather than on Kubuntu to deal with the bureaucracy to workaround their workarounds.
Scopes come with a very flexible customization system. From picking the text color to rearranging how results are laid out, a scope can easily look like a generic RSS reader, a music library or even a store front.
In this new article, you will learn how to make your scope shine by customizing its results, changing its colors, adding a logo and adapting its layout to present your data in the best possible way. Read…
In September 2014, 3 contributors have been paid for 11h each. Here are their individual reports:
Compared to last month, we have gained 5 new sponsors, that’s great. We’re now at almost 25% of a full-time position. But we’re not done yet. We believe that we would need at least twice as many sponsored hours to do a reasonable work with at least the most used packages, and possibly four times as much to be able to cover the full archive.
We’re now at 39 packages that need an update in Squeeze (+9 compared to last month), and the contributors paid by Freexian did handle 11 during last month (this gives an approximate rate of 3 hours per update, CVE triage included).Open questions
Dear readers, what can we do to convince more companies to join the effort?
The list of sponsors contains almost exclusively companies from Europe. It’s true that Freexian’s offer is in Euro but the economy is world-wide and it’s common to have international invoices. When Ivan Kohler asked if having an offer in dollar would help convince other companies, we got zero feedback.
What are the main obstacles that you face when you try to convince your managers to get the company to contribute?
By the way, we prefer that companies take small sponsorship commitments that they can afford over multiple years over granting lots of money now and then not being able to afford it for another year.Thanks to our sponsors
Let me thank our main sponsors:
- Gold sponsors:
- Silver sponsors:
- AD&D – David Ayers – IntarS Austria
- Domeneshop AS
- Trollweb Solutions
- Université Lille 3
- Bronze sponsors:
- Freeside Internet Service
- Intevation GmbH
- Linuxhotel GmbH
- Nantes Métropole
- Offensive Security
- Seznam.cz, a.s.
I just created an add-on that literally just changes the one bit* needed to disable SSL 3.0 support in Firefox
You can get it here: https://addons.mozilla.org/en-US/firefox/addon/disable-ssl-30/
*It’s trivial to do in about:config, yet I don’t really want to recommend that to anyone..
I started transitioning from 1024D to 4096R. The new key is available at:
and the keys.gnupg.net key server. A very short transition statement is available at:
and included below (the http version might get extended over time if needed).
The key consists of one master key and 3 sub keys (signing, encryption, authentication). The sub keys are stored on an OpenPGP v2 Smartcard. That’s really cool, isn’t it?
Somehow it seems that GnuPG 1.4.18 also works with 4096R keys on this smartcard (I accidentally used it instead of gpg2 and it worked fine), although only GPG 2.0.13 and newer is supposed to work.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1,SHA512 Because 1024D keys are not deemed secure enough anymore, I switched to a 4096R one. The old key will continue to be valid for some time, but i prefer all future correspondence to come to the new one. I would also like this new key to be re-integrated into the web of trust. This message is signed by both keys to certify the transition. the old key was: pub 1024D/00823EC2 2007-04-12 Key fingerprint = D9D9 754A 4BBA 2E7D 0A0A C024 AC2A 5FFE 0082 3EC2 And the new key is: pub 4096R/6B031B00 2014-10-14 [expires: 2017-10-13] Key fingerprint = AEE1 C8AA AAF0 B768 4019 C546 021B 361B 6B03 1B00 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQ9j+oACgkQrCpf/gCCPsKskgCgiRn7DoP5RASkaZZjpop9P8aG zhgAnjHeE8BXvTSkr7hccNb2tZsnqlTaiQIcBAEBCgAGBQJUPY/qAAoJENc8OeVl gLOGZiMP/1MHubKmA8aGDj8Ow5Uo4lkzp+A89vJqgbm9bjVrfjDHZQIdebYfWrjr RQzXdbIHnILYnUfYaOHUzMxpBHya3rFu6xbfKesR+jzQf8gxFXoBY7OQVL4Ycyss 4Y++g9m4Lqm+IDyIhhDNY6mtFU9e3CkljI52p/CIqM7eUyBfyRJDRfeh6c40Pfx2 AlNyFe+9JzYG1i3YG96Z8bKiVK5GpvyKWiggo08r3oqGvWyROYY9E4nLM9OJu8EL GuSNDCRJOhfnegWqKq+BRZUXA2wbTG0f8AxAuetdo6MKmVmHGcHxpIGFHqxO1QhV VM7VpMj+bxcevJ50BO5kylRrptlUugTaJ6il/o5sfgy1FdXGlgWCsIwmja2Z/fQr ycnqrtMVVYfln9IwDODItHx3hSwRoHnUxLWq8yY8gyx+//geZ0BROonXVy1YEo9a PDplOF1HKlaFAHv+Zq8wDWT8Lt1H2EecRFN+hov3+lU74ylnogZLS+bA7tqrjig0 bZfCo7i9Z7ag4GvLWY5PvN4fbws/5Yz9L8I4CnrqCUtzJg4vyA44Kpo8iuQsIrhz CKDnsoehxS95YjiJcbL0Y63Ed4mkSaibUKfoYObv/k61XmBCNkmNAAuRwzV7d5q2 /w3bSTB0O7FHcCxFDnn+tiLwgiTEQDYAP9nN97uibSUCbf98wl3/ =VRZJ -----END PGP SIGNATURE-----
Filed under: Uncategorized
I love movies. I especally love seeing movies in an old-fashioned movie theatre. The smell of popcorn. The immersiveness. The whole sensory experience. Well, almost...
Why oh why must I, my friends, and my family be subjected to nonsense warnings that precede every movie shown in a theatre? You know the ones: "Silence your phone", "Silence is golden", "It only takes one phone call to ruin a movie", etc, etc.
Even with all that preamble, there is inevitably someone at the theatre that ignores it, or is too distracted by their phone to see the warning. So, the messages are largely ineffective. Oh, the irony!
Let's think about this for a minute. According to the MPAA, "More than two thirds of the U.S./Canada population...227.8 million people went to the movies at least once in 2013"
Let's take the most conservative view of this statistic. Assume that the total number of person-movies that year was 227.8 million. And, let's also assume that each one of these movies was preceded by a 10-second "Silence your cell phone" message.
That amounts to over 632,000 hours , or 26,365 days, or 72 years of lost time, in one year. "Smart" phone manufacturers, this is a problem you could have solved years ago. For just how many years has this been a solvable problem? My guess is 10.
"Smart" phone manufacturers, you are wasting my time. You are forcing theatres to air useless reminders and distractions. In economic terms, that's called an externality: pushing the costs onto others so you don't have to incur them yourself.
That's right. 720 years lost, in North America alone.
Stop this nonsense. Humanity has better things to do.
I'm sorry "smart" phones. You are as dumb as the day you were born. Think about it. It's really not that hard. Don't be fooled by the name. Movie theatres don't move. You know when you're inside one. Maybe it's time to pay attention?!
With the upcoming Ubuntu Phones, perhaps we, the people that believe in our shared humanity, can give back humanity this precious time it needs to get on with life and perhaps the chance to use this time to solve just one problem to make the world a better place...
Our best chance at a phone that respects humanity is here:
More reasons "smart phones aren't are here:
image by daniel
This is a guest post from Will Cooke, the new Desktop Team manager at Canonical. It’s being posted here while we work to get a blog setup on unity.ubuntu.com, which is where you can find out more about Unity 8 and how to get involved with it.Intro
Understandably, most of the Ubuntu news recently has focused around phones. There is a lot of excitement and anticipation building around the imminent release of the first devices. However, the Ubuntu Desktop has not been dormant during this time. A lot of thought and planning has been given to what the desktop will become in the future; who will use it and what will they use it for. All the work which is going in to the phone will be directly applicable to the desktop as well, since they will use the same code. All the apps, the UI tweaks, everything which makes applications secure and stable will all directly apply to the desktop as well. The plan is to have the single converged operating system ready for use on the desktop by 16.04.The plan
We learned some lessons during the early development of Unity 7. Here’s what happened:
- 11.04: New Unity as default
- 11.10: New Unity version
- 12.04: Unity in First LTS
What we’ve decided to do this time is to keep the same, stable Unity 7 desktop as the default while we offer users who want to opt-in to Unity8 an option to use that desktop. As development continues the Unity 8 desktop will get better and better. It will benefit from a lot of the advances which have come about through the development of the phone OS and will benefit from continual improvements as the releases happen.
- 14.04 LTS: Unity 7 default / Unity 8 option for the first time
- 14.10: Unity 7 default / Unity 8 new rev as an option
- 15.04: Unity 7 default / Unity 8 new rev as an option
- 15.10: Potentially Unity 8 default / Unity 7 as an option
- 16.04 LTS: Unity 8 default / Unity 7 as an option
As you can see, this gives us a full 2 cycles (in addition to the one we’ve already done) to really nail Unity 8 with the level of quality that people expect. So what do we have?How will we deliver Unity 8 with better quality than 7?
Continuous Integration is the best way for us to achieve and maintain the highest quality possible. We have put a lot of effort in to automating as much of the testing as we can, the best testing is that which is performed easily. Before every commit the changes get reviewed and approved – this is the first line of defense against bugs. Every merge request triggers a run of the tests, the second line of defense against bugs and regressions – if a change broke something we find out about it before it gets in to the build.
The CI process builds everything in a “silo”, a self contained & controlled environment where we find out if everything works together before finally landing in the image.
And finally, we have a large number of tests which run against those images. This really is a “belt and braces” approach to software quality and it all happens automatically. You can see, we are taking the quality of our software very seriously.What about Unity 7?
Unity 7 and Compiz have a team dedicated to maintenance and bug fixes and so the quality of it continues to improve with every release. For example; windows switching workspaces when a monitor gets unplugged is fixed, if you have a mouse with 6 buttons it works, support for the new version of Metacity (incase you want to use the Gnome2 desktop) – added (and incidentally, a lot of that work was done by a community contributor – thanks Alberts!)
Unity 7 is the desktop environment for a lot of software developers, devops gurus, cloud platform managers and millions of users who rely on it to help them with their everyday computing. We don’t want to stop you being able to get work done. This is why we continue to maintain Unity 7 while we develop Unity 8. If you want to take Unity 8 for a spin and see how its coming along then you can; if you want to get your work done, we’re making that experience better for you every day. Best of all, both of these options are available to you with no detriment to the other.Things that we’re getting in the new Ubuntu Desktop
- Applications decoupled from the OS updates. Traditionally a given release of Ubuntu has shipped with the versions of the applications available at the time of release. Important updates and security fixes are back-ported to older releases where required, but generally you had to wait for the next release to get the latest and greatest set of applications. The new desktop packaging system means that application developers can push updates out when they are ready and the user can benefit right away.
- Application isolation. Traditionally applications can access anything the user can access; photos, documents, hardware devices, etc. On other platforms this has led to data being stolen or rendered otherwise unusable. Isolation means that without explicit permission any Click packaged application is prevented from accessing data you don’t want it to access.
- A full SDK for writing Ubuntu apps. The SDK which many people are already using to write apps for the phone will allow you to write apps for the desktop as well. In fact, your apps will be write once run anywhere – you don’t need to write a “desktop” app or a “phone” app, just an Ubuntu app.
The easiest way to try out the Unity 8 Desktop Preview is to use the daily Ubuntu Desktop Next live image: http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ This will allow you to boot into a Unity 8 session without touching your current installation. An easy 10 step way to write this image to a USB stick is:
- Download the ISO
- Insert your USB stick in the knowledge that it’s going to get wiped
- Open the “Disks” application
- Choose your USB stick and click on the cog icon on the righthand side
- Choose “Restore Disk Image”
- Browse to and select the ISO you downloaded in #1
- Click “Start restoring”
- Boot and select “Try Ubuntu….”
- Done *
* Please note – there is currently a bug affecting the Unity 8 greeter which means you are not automatically logged in when you boot the live image. To log in you need to:
- Switch to vt1 (ctrl-alt-f1)
- type “passwd” and press enter
- press enter again to set the current password to blank
- enter a new password twice
- Check that the password has been successfully changed
- Switch back to vt7 (ctrl-alt-f7)
- Enter the new password to login
Here are some screenshots showing what Unity 8 currently looks like on the desktop:
The people working on the new desktop are made up of a few different disciplines. We have a team dedicated to Unity 7 maintenance and bug fixes who are also responsible for Unity 8 on the desktop and feed in a lot of support to the main Unity 8 & Mir teams. We have the Ubuntu Desktop team who are responsible for many aspects of the underlying technologies used such as GNOME libraries, settings, printing etc as well as the key desktop applications such as Libreoffice and Chromium. The Ubuntu desktop team has some of the longest serving members of the Ubuntu family, with some people having been here for the best part of ten years.How you can help
We need to log all the bugs which need to be fixed in order to make Unity 8 the best desktop there is. Firstly, we need people to test the images and log bugs. If developers want to help fix those bugs, so much the better. Right now we are focusing on identifying where the work done for the phone doesn’t work as expected on the desktop. Once those bugs are logged and fixed we can rely on the CI system described above to make sure that they stay fixed.
Link to daily ISOs: http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
IRC: #ubuntu-desktop on Freenode
The criu project has been working hard to make application checkpoint/restart feasible. Tycho has implemented lxc-checkpoint and lxc-restart on top of that (as well as of course contributing the needed bits to criu itself), and now shows off first steps toward real live migration: http://tycho.ws/blog/2014/09/container-migration.html
- Review ACTION points from previous meeting
ACTION: all to review blueprint work items before next weeks meeting
- U Development
- Server & Cloud Bugs (caribou)
- Weekly Updates & Questions for the QA Team (psivaa)
- Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
- Ubuntu Server Team Events
- Open Discussion
- Announce next meeting date, time and chair
- Check on FTBFS packages — seems like there has been good progress
- Make sure are up to date, if resources are needed now is the time to ask.
- Release bugs, no high priority ones, juju mirs and openstack bits are being worked.
- kickinz1 brought up two bcache bugs (LP #1377130 and LP #1377142) to the kernel team for help.
NoneAgree on next meeting date and time
Next meeting will be on Tuesday, Oct 14th at 16:00 UTC in #ubuntu-meeting.IRC Log
Welcome to the Ubuntu Weekly Newsletter. This is issue #387 for the week October 6 – 12, 2014, and the full version is available here.
In this issue we cover:
- Watch Netflix in Ubuntu today
- Ubuntu Stats
- Kubuntu: KDE Plasma 5 beta 1 in next ppa ready for testers. Please read on for known issues.
- Svetlana Belkin: Start Planning For 14.11 UOS
- Randall Ross: Discount Offer for Ubuntu Members – Get Certified!
- Scott Kitterman: Thanks Canonical (reallly)
- Kubuntu Wire: Weta Uses Kubuntu for Hobbit
- Scarlett Clark: Kubuntu: KDE Frameworks 5.3.0 Now released to archive.
- Forums Council: Happy Birthday Ubuntu Forums & Support for Other Operating Systems
- Nekhelesh Ramananthan: Clock App Reboot Backstory
- Randall Ross: Why Smart Phones Aren’t – Reason #1
- Canonical News
- Sleek Mini-ITX industrial PCs come in four Intel flavors
- Canonical Offers OpenStack and Ubuntu Cloud Training in Paris
- Other Articles of Interest
- Featured Audio and Video
- Weekly Ubuntu Development Team Meetings
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04 and 14.04
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Elizabeth K. Joseph
- Paul White
- And many others
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License
The gig is up: our telephones aren’t smart, and they can’t save themselves. But, maybe you can!
By far, the dumbest feature of today’s “smart” phones is the phone itself. There is a growing number of people who never use their mobile devices to make calls. This begs the question of whether or not the feature should exist at all (or why even call them phones?). “How silly,” you say; of course, there are justified applications for calling someone who is in the middle of dinner or on a crowded train. However, there is a lack of control over (loco) this function. Your phone doesn’t know how to suitably deal with and classify a call event (i.e. call-typing beyond known and unknown numbers) and this makes it both not smart, and not safe (for itself).
How many phones have been physically harmed due to phone-call malpractice?
They fly out your car window. They drop from your ear. They get thrown across the room. All because of the wrong call at the wrong time.
You can prevent this, and you can save the phone feature of your mobile device. You can have a say in how your mobile device is programmed.