- Decentralized online communication: This was suggested by a viewer in a blog comment last week, and I think it's an important topic. I'll be looking at this from three angles: why it is important, what has gained traction and what has not, and what tools exist right now with an emphasis on "real time" communication ala Jabber and identi.ca.
- Node.js: I've been using Node.js for a while and have found it to be an interesting approach to web services. This neatly fits with the first topic in some way, so what better excuse than to give a "50,000 foot view" of this rather cool project along with maybe making a case for why we should care about this stuff more on the desktop, too.
- Color management: Also a viewer suggested topic, this is another area of progress for Free software when it comes to graphics. We'll look at some of the management tools and what it does for the desktop, applications and people doing serious graphics work.
- Q&A: Otherwise known as "chaotic happy fun time" in which you ask questions and I do my best to foment further discussion. :)
See you there on Google+ Hangout tomorrow (Thursday) at 20:00 UTC. You can watch the live feed (assuming all that magical hangout stuff decides to work) or afterwards at your leisure on my Youtube channel.
5 comments:
Could you please explain why no real decentralized encrypted P2P file sharing and messaging (F2F) tool exit in standard KDE SC installs?
I think such a tool would be very valuable to next to everybody, especially in oppressive countries.
I know somebody has to do the work, but what I want to know is why in the big KDE community there is no concensus that such a tool would be needed. IMHO every FOSS desktop should include such a tool, it would make the world a better place.
Is it just that the mostly US/EU devs are fine with G+ and Facebook and just don't care enough or are there technical reasons?
(The good folks at retroshare do an amazing job, maybe invite them to a KDE meeting or something)
Hi Aaron,
With Plasma Workspaces 2, you will be able to run both Plasma Active and Plasma Desktop on the same device, thus having both Active and Desktop applications available. Do you intend to have every type of application available everywhere, or will you have only applications suited for the current shell? I think the latter would be the best approach, as Windows 8 shows that using a touch-optimised interface with a mouse is almost as unpleasant as using a desktop-centric application on a touchscreen. But then you need a way for the environement to know whether an application is for touch or for desktop. Are you considering such thing?
For application where both touch and desktop versions are available (Kontact/Kontact Touch, Calligra/Calligra Active, Okular/Okular Active,...), I think right now they are separate applications based on the same core code. Do you intend to follow the same approach as for the shell, one single application with different profiles depending on the current shell?
I'm quite sure this is not clearly defined yet, but I would like to have your views on these issues. Thanks.
I played a bit with Node.js as well and I think it has the potential to be used for testing our client applications, e.g. for quickly writing simple mock servers.
You might want to check out buddycloud.
It is a federated social network based on XMPP. Parts of it are implemented in node.js.
Aaron you are fantastic....
I didnt know exactly what color management was, so you made me curious... :) I installed the packages you described by using:
http://userbase.kde.org/Color_Management/en#Requirements
for opensuse was extremely ease...
After the installation everything changed... My plasma became colorful... oxygen theme finally gained what was missing and oxygen icons became live... I think this is very important and must be broadcasted some how to the users.
The contrast from the colors in fantastic... :)
Thank you a lot again....
Post a Comment