WordPress released version three point eight, that brings significant design update and high touch-screen optimizations!
WordPress released version three point eight, that brings significant design update and high touch-screen optimizations!
Gnome Chat is a new Instant Message Client from Gnome Community that embraces the latest Interface Guidelines of Gnome3. (more…)
Polari is an IRC client written from scratch that will make its debut in Gnome 3.12. (more…)
Apps Menus seems to be the No1 issue in Gnome usability. Version 3.12 will try to make things slightly better. (more…)
Just a screencasting that demonstrate how good Fedora 20 behaves in everyday common tasks. (more…)
Whats? Shell Search will provide results for the current running Terminals, and bring focus to the relevant window/tab! (more…)
A new Gnome goal is about to bring more pleasure to our eyes and further improve our user experience. (more…)
Logs is a new application designated for GNOME 3.12, that gives us a -limited- interface to Systemd-Journal, the log service of Systemd. On the left, Lennart Poettering, the creator of Systemd. (more…)
Linux Desktop isn’t just about GNOME and Ubuntu. KDE 5 is going to be released in 1st half of 2014 and brings a set of amazing technologies like QT5/QML, Wayland and much much more! (more…)
The unstable 3.11.x version of gEdit acquires the new Tab Styling and looks pretty nice! (more…)
The latest versions of core GNOME components as well as a selection of apps are available as a bootable virtual machine image. (more…)
A few hours ago, Matthias Clasen added a new page to Initial Setup that allows us to choose our region. (more…)
Valve announced the release of Steam OS (a new Linux based OS) around two months ago and they now ( Dec 4) join Linux Foundation ahead of SteamOS launch!
Nelson Mandela died in December 5th, 2013. (more…)
Software evolves impressively fast and for version 3.12 brings an application rating system, a search provider that discovers apps directly from shell ..and much much more!
GNOME Videos 3.12 will be a totally different application than 3.10 ..but a small detail attracts the attention.. flat tabs? (more…)
GNOME Sound Recorder is a new application for GNOME 3.12 developed by Meg Ford (on the left) and designed by Reda Lazri that let us ..record sound in various formats. (more…)
The best open source flight simulator is taking care of its Achilles heel in the upcoming 3.0 version… (more…)
The latest OpenMW release brings many improvements, fixes and new features for the popular open source game engine. (more…)
Once it launches for general use, Flowhub is the fruition of the project initiated by our successful NoFlo Development Environment Kickstarter from last August.
Flowhub will provide a development environment for your flow-based programs, allowing you to collaborate and build things inside the same interface whether you're targeting the client-side or the server-side of the web world. And thanks to the efforts on creating a standard protocol for flow-based runtimes, Flowhub will be able to work with other environments as well. To get a glimpse of this potential, take a look at Jon Nordby's work on Arduino programming with NoFlo UI and what Lionel Landwerlin is doing with NoFlo in the Linux desktop development world.
While NoFlo is and will remain our main focus, we should embrace the different ideas and different projects out there. One of the key points of FBP is everything can be modeled as a black box with input and output ports. With this level of abstraction, and a standard communications protocol, the different systems will be able to work together. Flowhub can be the central point for enabling that.
NoFlo is open source, and so is the development environment we're building for it. For developing things on your own, this is pretty much all you'll need, especially if you're willing to set up things like the NoFlo environment for Node.js yourself.
The role of Flowhub as a service is analogous to what GitHub provides for traditional software development. Anybody can serve git repositories and issue trackers on their own, but having a third party to take care of that gives a much simpler, smoother experience. And even more importantly, having a central point where multiple projects reside enables much better collaboration and discovery between teams and projects.
This is the essence of what Flowhub will provide:
As promised in our Kickstarter, the service will open to the public in the early summer of 2014. Our Kickstarter backers will gain an early access and have already service plans provided for them. With our Flowhub pre-order campaign, those who missed the Kickstarter opportunity have still a way to get in with early adopter pricing.
Like NoFlo itself, Flowhub is also an exploration of various new technologies. From the layout technologies and the use of Web Components, and the flow-based payment processing infrastructure handling both BitCoin and credit card transactions that we built in NoFlo — there are many things being dogfooded on the service.
At this stage of the game there are sure to be some rough edges, but by the time Flowhub opens to the public there should've been enough time at both our end, and with web browsers to mature to the point where these things provide a smooth experience.
The user interface we showed in September, and user-tested in the NodeCopter NoFlo event has since seen quite a lot of improvement based on what we've learned. The new version has been rebuilt ground-up with Polymer and NoFlo, and is a lot more efficient and touch-friendly.
It is still not perfect, but having used it on various devices from small tablets through laptops to huge touch-screen PCs, I feel we're definitely on the right track. Having a user interface where you can see the connections and data flows of your software in real time, and can rewire any part when needed is incredibly powerful. And once component editing is working fully with the runtimes, I can't really see myself wanting to go back to text-only development.
Here is a sneak peek (click to see a bigger version):
To see more of what we're building, visit flowhub.io, play with the demo we have there, and make sure to watch the intro video. Preorder today to help fund the hosted and open source version of Flowhub!
Last month I announced Yorba was sponsoring a $500 bounty to backport Geary 0.4 to Precise Pangolin 12.04 and elementary’s Luna. I’m pleased to announce two new developments toward that goal.
First, since then six forward-thinking people added another $100 to the bounty, making the total pot $600. Thank you! This was the part of the experiment I was most interested in. Backporting Geary to 12.04 was a highly-requested task, and I wondered if the people who wanted it would be willing to contribute a little money toward that goal. At least some people did think it worthwhile enough, and collectively they added 20% to Yorba’s initial offer.
Second, I’m pleased to announce that the goal has been reached. Tom Beckmann put in a lot of hours and considerable blood, sweat, and tears to port Geary back to 12.04, but he did it and so he claims the bounty. I’ve run his version of Geary on both Precise and elementary Luna and am quite impressed. It uses our new symbolic icon layout, it’s integrated with Precise’s message indicator, and offers every feature in Geary 0.4, including full-text search and the stability improvements we added to 0.4.1. Best of all, he packaged it up on a Launchpad PPA, meaning it’s a snap to install.
If you’re running Precise Pangolin 12.04 or elementary Luna and you’d like to upgrade your version of Geary, I recommend the following directions. Open a terminal window and type the following:
$ sudo add-apt-repository ppa:tombeckmann/geary $ sudo apt-get update $ sudo apt-get install geary
If you’re already running Geary 0.3.1, this new version will update your old database and you’ll be good to go.
A few notes about this release:
(One further note: due to some technical issues, the original Bountysource.com page was moved here. Other than the URL, all details have remained the same.)
Congratulations Tom, and thanks!
As every year many ideas came up during the WebKitGTK+ hackfest presentation, but this time there was one we all were very excited about, the multiple web processes support. Apple developers already implemented the support for multiple web processes in WebKit, which is mostly cross platform, but it requires the network process support to properly work (we need a common network process where cookies, HTTP cache, etc are shared for all web processes in the same web context). Soup based WebKit ports don’t implement the network process yet, so the goal of the hackfest became to complete the network process implementation previously started by EFL and Nix guys, as a first step to enable the multiple web processes support. Around 10 people were working on this goal during the whole hackfest, meeting from time to time to track the status of the tasks and assigning new ones.
After all this awesome work we managed to have the basic support, with MiniBrowser perfectly rendering pages and allowing navigation using the network process. But as expected, there were some bugs and missing features, so I ran the WebKit2 unit tests and we took failing tests to investigate why they were failing and how to fix them.
So, we are actually far from having a complete and stable network process support, but it’s a huge step forward. The good news is that once we have network process implemented, the multiple web processes support will work automatically just by selecting the multiple web process model.
All this sounds like a lot of work done, but that’s only a small part of what has happened this week in Coruña:
And I’m sure I’m missing more great stuff done that I could not follow closely. It’s definitely been a very productive hackfest that it would haven’t been possible without the sponsors, Igalia and the GNOME Foundation. Thanks!
Oop’s ! I am sorry If I am confusing you with your OOPs concepts!! But I found them cool and simply wished to share. See! how beautifully the concept of operator overloading is depicted with the help of the following picture. And here’s a very cute example for the parameter passing: I am learning Java […]
So for the 5th time I attended the WebKitGTK+ hackfest and as usual I spent most of the time working on Multimedia-related tasks, well just one this year actually, WebRTC.
I think WebRTC is quite an important HTML5 specification, we all want to get rid of Skype and embrace the world of open web video-conferencing, right?
To reach this goal we have mainly two big milestones. The first one is about letting the browser access the audio/video device if the user allows it and use <audio>/<video> elements to display the live feed. This part of the spec is called getUserMedia, I got it working in a branch, the patches are being upstreamed and hopefully we will turn this feature on soon in WebKitGTK+!
The second, and biggest, milestone is about actually establishing a peer-to-peer connection between multiple browsers over the internets. Based on some work done by Ericsson 3 years ago I started working on a PeerConnectionHandler for WebKitGTK+. The ICE agent it embeds is using libnice to handle the gathering of Candidates and NAT traversal. The backend is not yet functional, ICE negotiation is quite buggy, but I will keep working on the backend.
Once this is done there will be new features from the spec to support, like the Data channel, DTMF, Statistics gathering and it would also be cool to investigate on the screen sharing that's not (yet?) in the spec but supported in Chrome. Exciting times ahead!
Once more the event wouldn't have been possible and successful without sponsors, so big thank you to the GNOME Foundation and Igalia!
Nowadays, digital content is all about the cloud. Indeed, in GNOME we’ve been pushing to integrate with cloud-based content through our new content apps, like Documents, Photos, Music and Videos. This is important work and needs to continue.
However, local files are still central to the way that many people work, and are an essential part of lots of workflows. This means that, while cloudy things are important, it is also important that we pay attention to the experience of working with local files in GNOME. It is for this reason that a group of us has been working on a plan to improve the state of Nautilus, our venerable file browser.
The new designs are fairly extensive and cover a lot of ground. In the rest of this post I’ll try to describe as much as I can. As always, they are not set in stone and will evolve. Questions, comments and feedback are most welcome, and will help us to develop them further.
The most important thing in the Files app is, well, your files. If Nautilus is going to provide the kind of experience that we want it to, it needs to do a better job at making your files easy to recognise, look good, and take centre stage. This requires lists and grids that have even spacing, helpful zoom levels, and big, clear thumbnails.
The designs feature new lists and grids, which should hopefully be possible with GTK’s new grid and list widgets. The grids we have in mind will be responsive, so that the content will scale to fit the size and shape of the window (without large spaces between cells or gutters on one side). Lists will feature thumbnails and have separators between rows to aid readability.
The designs also include mockups for an updated view “menu”. This contains all the existing options, except with nicer controls.
Being able to inspect the content of a file is often essential to identifying it, such as when you have lots of similar photos, or PDFs with unhelpful file names. Nautilus already has a previewing feature, but it functions as an optional extra and can easily be missed. The new designs make previewing much more central to the browsing experience. They also include actions alongside previews, so that you can quickly act on the file that’s in front of you.
One thing that you can’t see in this mockup – we also want to make it possible to browse between files from the preview – so you can flip back and forth between images or documents in order to compare them.
Generating previews like this may well require new infrastructure. Specifically, it is likely that we will need a new library for generating previews.
Many of the ideas for the new sidebar design came from the awesome António Fernandes.
The main objective for the places sidebar is to make it more focused on the things you care about. Right now, the sidebar automatically includes every available volume and drive. This can lead to a cluttered sidebar which contains lots of items that you never use. These often get in the way and distract from the items that you use all the time.
We want to rebalance the sidebar: more things you care about, less things you don’t. To achieve this, we want to make adding drives to the sidebar a manual action. In this way you will be able to customise the sidebar to your needs.
Clarification: manual addition won’t be necessary for removable drives – they will be automatically added to the sidebar as they are now. Also, once an internal volume or remote drive is added, it will persistent even when it’s not mounted.
A new add drive dialog is a key part of the new sidebar design. This will allow you to quickly add both local and remote locations to the sidebar all from the same dialog. It is also an attempt to clean up the various network browsing features that are currently available in Nautilus, and consolidate these features into one place.
The reimagined sidebar also contains a new feature which will be really handy: starred files. Being able to mark items that you want to keep track of is such as obvious feature, and I’m sure it will be useful to many people. In UI terms it’s a fairly simple thing to do.
Selection mode is a design pattern that we’re using extensively in the other GNOME 3 applications. It’s nice because it makes contextual actions much more discoverable. It also allows us to use single click (rather than the undiscoverable and inconsistent double-click) throughout.
The best way to think of the use of selection mode here is as a discoverable context menu. Existing methods of selecting multiple items, like holding ctrl and shift in combination with the mouse button, will continue to work.
It’s amazing how many undiscoverable conventions that we acclimatise ourselves to, and an old app like Nautilus has a lot of them. At some point in the past, we all learned to double-click to open, to press return to finish naming a new folder, or that Ctrl+V pastes content into the current location. All of this is totally unobvious to new users, of course, and there can be embarrassing moments when you watch someone use an app like Nautilus for the first time.
The new Nautilus designs bring a lot of hidden functionality to the surface, and they make an effort not to assume prior knowledge. Much of the functionality that is currently hidden in the background has been brought to the surface: there are visible buttons for common tasks like pasting items or creating folders, for example. Simple things – like using a dialog for creating new folders – are designed to eliminate basic usability bugs.
Finally, this brings us back to content selection. A next generation replacement for the existing file selection dialog is something that has been mooted for a long while. To make it happen, a number of other long-term initiatives need to come together: the new set of content selection applications needs to come together, and we need the previewing library that I mentioned about above.
This latest round of Nautilus design work was in part motivated to keep these content selection plans moving forward, and the Nautilus designs were developed at the same time as a new set of content selection mockups. This is to ensure that the file browser keeps in step with our longer term plans.
The new content chooser is designed to allow you to select content items from a range of sources. These can be local files or content items that are stored in the cloud. This is where the various new content applications come in – each one is designed to act as a cloud-based content provider. With this approach, you should be able to use the Photos app to select images from Flickr, for example.
The initial view provides a grid of recently used items. After that, you can choose a particular content provider. Content apps can then present their own content. Notice that, after opting to view files, the familiar places sidebar from Files slides in.
If you want to help us make these designs a reality, there are many things that we need help with, both large and small. I will be busy turning the designs into bug reports over the coming weeks, and will be keeping the design page up to date as the plans take shape. You can subscribe to the page if you want to follow what’s happening. Otherwise, just get in touch. We would love to hear from you, even if you are just interested.
For the fifth year in a row the fearless WebKitGTK+ hackers have gathered in A Coruña to bring GNOME and the web closer. Igalia has organized and hosted it as usual, welcoming a record 30 people to its office. The GNOME foundation has sponsored my trip allowing me to fly the cool 18 seats propeller airplane from Lisbon to A Coruña, which is a nice adventure, and have pulpo a feira for dinner, which I simply love! That in addition to enjoying the company of so many great hackers.
The goals for the hackfest have been ambitious, as usual, but we made good headway on them. Web the browser (AKA Epiphany) has seen a ton of little improvements, with Carlos splitting the shell search provider to a separate binary, which allowed us to remove some hacks from the session management code from the browser. It also makes testing changes to Web more convenient again. Jon McCan has been pounding at Web’s UI making it more sleek, with tabs that expand to make better use of available horizontal space in the tab bar, new dialogs for preferences, cookies and password handling. I have made my tiny contribution by making it not keep tabs that were created just for what turned out to be a download around. For this last day of hackfest I plan to also fix an issue with text encoding detection and help track down a hang that happens upon page load.
Martin Robinson and myself have as usual dived into the more disgusting and wide-reaching maintainership tasks that we have lots of trouble pushing forward on our day-to-day lives. Porting our build system to CMake has been one of these long-term goals, not because we love CMake (we don’t) or because we hate autotools (we do), but because it should make people’s lives easier when adding new files to the build, and should also make our build less hacky and quicker – it is sad to see how slow our build can be when compared to something like Chromium, and we think a big part of the problem lies on how complex and dumb autotools and make can be. We have picked up a few of our old branches, brought them up-to-date and landed, which now lets us build the main WebKit2GTK+ library through cmake in trunk. This is an important first step, but there’s plenty to do.
Under the hood, Dan Winship has been pushing HTTP2 support for libsoup forward, with a dead-tree version of the spec by his side. He is refactoring libsoup internals to accomodate the new code paths. Still on the HTTP front, I have been updating soup’s MIME type sniffing support to match the newest living specification, which includes specification for several new types and a new security feature introduced by Internet Explorer and later adopted by other browsers. The huge task of preparing the ground for a one process per tab (or other kinds of process separation, this will still be topic for discussion for a while) has been pushed forward by several hackers, with Carlos Garcia and Andy Wingo leading the charge.
Other than that I have been putting in some more work on improving the integration of the new Web Inspector with WebKitGTK+. Carlos has reviewed the patch to allow attaching the inspector to the right side of the window, but we have decided to split it in two, one providing the functionality and one the API that will allow browsers to customize how that is done. There’s a lot of work to be done here, I plan to land at least this first patch durign the hackfest. I have also fought one more battle in the never-ending User-Agent sniffing war, in which we cannot win, it looks like.
I am very happy to be here for the fifth year in a row, and I hope we will be meeting here for many more years to come! Thanks a lot to Igalia for sponsoring and hosting the hackfest, and to the GNOME foundation for making it possible for me to attend! See you in 2014!
This was a year of consolidation for us, and I think we’ve succeeded in getting Firefox for Android in a much better place in the mobile browser space. We’ve gone from an (embarrassing) 3.5 average rating on Google Play to a solid 4.4 in just over a year (!). And we’re wrapping up 2013 as a pre-installed browser in a few devices—hopefully the first of many!
We’ve just released Firefox for Android 26 today, our last release this year. This is my favourite release by a mile. Besides bringing a much better UX, the new Home screen lays the ground for some of the most exciting stuff we’ll be releasing next year.
A lot of what we do in Firefox for Android is so incremental that it’s sometimes hard to see how all the releases add up. If you haven’t tried Firefox for Android yet, here is my personal list of things that I believe sets it apart from the crowd.
The new Home in Firefox for Android 26 gives you instant access to all your data (history, bookmarks, reading list, top sites) through a fluid set of swipable pages. They are easily accessible at any time—when the app starts, when you create a new tab, or when you tap on the location bar.
You can always search your browsing data by tapping on the location bar. As an extra help, we also show search suggestions from your default search engine as well as auto-completing domains you’ve visited before. You’ll usually find what you’re looking for by just typing a couple of letters.
Firefox for Android does a couple of special things for readers. Every time you access a page with long-form content—such as a news article or an essay—we offer you an option to switch to Reader Mode.
Reader Mode removes all the visual clutter from the original page and presents the content in a distraction-free UI—where you can set your own text size and color scheme for comfortable reading. This is especially useful on mobile browsers as there are still many websites that don’t provide a mobile-friendly layout.
Secondly, we bundle nice default fonts for web content. This makes a subtle yet noticeable difference on a lot of websites.
Last but not least, we make it very easy to save content to read later—either by adding pages to Firefox’s reading list or by using our quickshare feature to save it to your favourite app, such as Pocket or Evernote.
If you’re into blingy UIs, you can install some lightweight themes. Furthermore, you can install and use any web search engine of your choice.
An all-new panning and zooming framework was built as part of the big native rewrite last year. The main focus areas were performance and reliability. The (mobile) graphics team has released major improvements since then and some of this framework is going to be shared across most (if not all) platforms soon.
From a user perspective, this means you get consistently smooth panning and zooming in Firefox for Android.
We develop Firefox for Android through a series of fast-paced 6-week development cycles. In each cycle, we try to keep a balance between general housekeeping (bug fixes and polishing) and new features. This means you get a better browser every 6 weeks.
Firefox for Android is the only truly open-source mobile browser. There, I said it. We’re a community of paid staff and volunteers. We’re always mentoring new contributors. Our roadmap is public. Everything we’re working on is being proposed, reviewed, and discussed in Bugzilla and our mailing list. Let us know if you’d like to get involved by the way :-)
That’s it. I hope this post got you curious enough to try Firefox for Android today. Do we still have work to do? Hell yeah. While 2013 was a year of consolidation, I expect 2014 to be the year of excitement and expansion for Firefox on Android. This means we’ll have to set an even higher bar in terms of quality and, at the same time, make sure we’re always working on features our users actually care about.
2014 will be awesome. Can’t wait! In the meantime, install Firefox for Android and let us know what you think!
This week started out with a search for some mechanism for building portable bundles for 64bit GNU/Linux systems. I looked at various bundler implementations, 0install, chakra, Alexander Larsson’s glick and glick2 to name a few of the implementations I found. Finally I found this gem called AppImageKit by Simon Peter (I refer to my own fork of his repository because it contains some patches I needed, however there is a pull request, which I think is the custom when doing things on github.com).
Before I continue, I should make clear what were my motivations and why I chose AppImageKit over any other existing options.
Why Bundled Applications ?
Bundled applications is a concept prominent in OSX and has been considered and reconsidered a lot by the general GNOME/GNU/Linux communities, I refer to Alex’s blog for some ideas on the concepts of bundling applications, you may also want to read this article by Lennart Poettering on the subject of Sandboxed Applications for GNOME (if you haven’t already seen his talk).
So first let me explain the motivations behind my hacking:
Why did I choose AppImageKit ?
If you’re already familiar with the scene of Application Bundles out there, then you’ve already probably guessed why I made my choice.
In my search for application bundling mechanisms out there, I found a few options (as I mention in the beginning of this post). I quickly realized that most of the projects I found were either targeting a specific OS/distribution (i.e. chakra) or at least required the user to install some kind of mechanism to run the bundle (i.e. 0install). While I really do respect and admire the work done by Alexander and the advocacy by Lennart, pushing for a new concept of packaging in GNU/Linux systems, my requirements were simply different (and perhaps once sandboxed applications for GNOME actually exist, I will be able to switch to that new mechanism).
My requirement is, again, to be able to download and run an application on your 64bit GNU/Linux platform, I don’t care if it’s Fedora, GNOME OS, Debian, Arch Linux, Ubuntu, Chakra, I just wanted it to run.
How does it work ?
After reading the first paragraphs of the AppImageKit documentation I was sold. This is a simple and nifty idea of simply creating a compressed ISO image with an ELF binary header, it uses libz to decompress itself and fuse to mount itself into a temporary directory, and then it just runs a script, letting you modify your environment and launch your App from within the unpacked bundle environment (actually the AppRunScript.sh is my own addition to AppImageKit). It also uses libglib for some obscure reason, so the best practice is to build the bundling mechanism with the oldest version of libglib possible (as this will become a base runtime requirement for the user).
So basically the requirements are:
After that, the system requirements depend entirely on what you put in the bundle.
Please test my Glade bundle !
After 2 days of hacking I was finally able to get a GTK+ application running (Glade) with the Adwaita theme fully functional, and self contained. This involved much ldd and strace in the bundle environment, ensuring that the runtime doesn’t touch any system libraries or auxiliary data, the discovery of this nifty chrpath tool, and much grepping through various sources and figuring out how to properly relocate these modules with environment variables. I had to strangle Pango, until it finally yielded, after I thoroughly deformed pango’s face with this downstream patch. I also needed to rediscover hicolor-icon-theme’s location on fdo, since everything breaks down without an index.theme file in the right place (one of the various things jhbuild forgets to do properly).
You might be interested to peek at the README which is a thorough breakdown on how to create portable bundles of Glade in the future, the application startup script is also of particular interest as it shows what environment variables you really need to relocate GTK+ apps.
Finally, I was able to produce this bundle.
In addition to the AppImageKit system requirements listed above, we require:
(Technically these could also be included in the bundle, it would require that we install fonts as well, and I just wanted to avoid that telling myself that most GNU/Linux distributions have this already).
The above bundle should be able to ‘just run’, just download it and run it without any special privileges… PLEASE !
We will greatly appreciate any testing on various 64bit GNU/Linux platforms, after some testing we will start to advertise downloadable bundles of bleeding edge Glade for any users of stable GNU/Linux distributions.
And of course, Enjoy !
Posted on 13 December 2013 | 12:00 pm
Posted on 13 December 2013 | 12:41 am
Posted on 12 December 2013 | 11:00 pm
Add link to 12.04 backport information
Posted on 12 December 2013 | 10:57 pm
Posted on 12 December 2013 | 8:46 pm
Posted on 12 December 2013 | 7:40 pm
Posted on 12 December 2013 | 5:10 pm
Posted on 12 December 2013 | 12:37 pm
link Smuxi's wiki page and added a note about Smuxi's multi-protocol architecture
Posted on 12 December 2013 | 12:16 pm
Posted on 12 December 2013 | 10:49 am
Posted on 12 December 2013 | 8:29 am
Posted on 12 December 2013 | 7:36 am
Posted on 12 December 2013 | 4:30 am
Update changed links
Posted on 12 December 2013 | 2:01 am
Posted on 12 December 2013 | 1:56 am