En este video se muestra que rapido se prende el sistema operativo Chrome OS, se prende en tan solo 3-4 segundos!!!!

Jisko.net está basado en Jisko el cual es una aplicación microblogging de código abierto. Su código fuente puede ser obtenido aquí. Puedes reportar errores y enviar parches en su página Launchpad.

Puedes actualizar tu estado Jisko.net desde unos pocos lugares:

• Primero, puedes simplemente ir a http://jisko.net, iniciar sesión usando tu nombre de usuario y contraseña, y entonces, puedes escribir tu nota.

• Si el administrador lo ha activado, puedes también actualizar desde tu cuenta Jabber a través de un robot (bot) Jabber. (desactivado actualmente ¬¬’)

• O también puedes actualizar desde tu móvil con el sitio adaptado móvil. Si tienes un iphone o un iphone touch, verás una interfaz agradable adaptada para tus dedos.

Tomado de Jisko.net

Además, tiene integración con Twitter; puedes enviar una nota automática cada vez que tu blog WordPress se actualiza mediante WP2Jisko y también puedes poner tu última nota en Jisko en la barra lateral de tu blog usando Jisko para WordPress.

En lo personal me ha gustado mucho el servicio, partiendo por el hecho de que está basado en código abierto. El diseño del portal es bastante bonito y agradable a la vista (en comparación a Identi.ca, por ejemplo). Además, la gente dentro del sistema, es muy amable (me dieron la bienvenida, y eso que no los conocía ). Lo único que, tal vez, me ha “molestado” un poco es el hecho de que actualmente el bot para Jabber está desactivado, o no funciona, o alguien lo hechó a perder, o no se qué diablos xD. Sin embargo, como dije anteriormente, me gustó mucho Jisko.net.

L@s invito a registrarse, ocupar, y apoyar esta red social por el hecho de estar basada en código abierto y a no usar tanto (y si es posible no usar) servicios como Twitter o Facebook.

Clic para agrandar

Clic para agrandar

¡Saludos!

Setelah jumat lalu saya berhasil update dengan tertatih-tatih (gara-gara internet lemot) . File sebesar iso-nya puppy linux, yaitu 100mb lebih, akhirnya terinstal juga di karmic, sehingga membuat karmic saya paling uptodate! Hehe.

Bukannya saya senang ubuntu saya sudah update, malah manyun. Kenapa? Masalahnya setelah restart, kok sound hilang! Oh… No! Terjadi lagi! Langsung saya cek gnome alsa mixer, namun kok engga ngaruh! Waduh kok gitu sih..

Kembali saya sowan ke embah google, mencari ‘wangsit’. Pas search dengan kata kunci ‘no sound after updating karmic koala’, saya mendapat petunjuk. Rupannya update (salah satu mungkin) file ada yang konflik dengan driver propitery laptop, yaitu modem dialup! Jadi solusinya sederhana, yaitu cuman deactivate atau matiin aja. Trus restart dan niscaya sound kembali normal.

Sebenarnya sedih juga sih mematikan modem dialup di laptop, karena rencananya saya mau nyoba ngenet via telkomnet instant. Segala sesuatu sudah siap padahal, mulai dari menginstal wvdial (sudo apt-get wvdial) gppp (di ubuntu software center) dan sudah mencari referensi orang yang sudah berhasil. Namun rupanya harus ditunda dulu untuk beberapa saat (paling tidak sampai ada patchnya).

Ya memang hidup ini harus memilih. Kita tidak boleh ’serakah’. Harus memilih salah satu, milih internetan di telkomnet apa bisa nonton madtv di youtube (kalau lagi di hotspot ). akhirnya sayah memilih yang kedua deh…

There is a growing interest in self-replicating machines. Beginning with the RepRap project, and now continuing into RepLab, the open source FabLab, there is a serious effort to build machines which can build themselves.

It is a laudable goal. A machine which can make itself can also make an unimaginable variety of other machines, each unique if desired, and promises an era of material abundance and freedom from scarcity. Pursuing that goal, however, has shown the goal itself to be somewhat unclear. This is an attempt to remedy this situation.

What is replication? The production of a replica, but what is a replica? The original meaning was that of a duplicate of a work of art, properly one produced by the original artist.

I propose we define replication precisely, as the transcription of a template into a physical form. This definition is perhaps more general than we are used to, but I believe it accurately captures the use of the word.

Let’s take the test case: an artist producing a replica of her own painting. The original painting may have taken many months, while the replica may take only a day or two at most. The artist is using tools, a brush and palette, and materials, canvas and paint, to make a copy of a template, the original work.

How about DNA self-replication? We have a toolchain of proteins, from DNA Transcriptase on, which transcribe a template, the DNA, into a copy of itself, using materials (ATP, other nucleic acids, caffeine if there’s some in the organism in question) both extrinsic to the cell and fabricated within it.

Note that in the first case the template resembles the result, while in second case, if we consider the result a new cell rather than new DNA, the result doesn’t resemble the template at all. This is immaterial to the act of replication; a high-resolution inkjet printer and a scanner could replicate the artist’s original work, faster and more accurately than she could, and in this case the template would be stored as bits within a computer.

The rest of this discussion will focus on replication in the context of human-tool interaction.

This means replication of an object, from a template, through the combined efforts of at least one human with at least one tool. We call this a ‘tool’ rather than a ‘machine’ for greater generality.

The earliest form of replication was a human using a tool to make a copy of an object. Our paradigm case for this is a scribe copying a scroll. A human can’t do this without the materials (paper, ink) and tools (quill, sharpener) required for the act. With those tools, a human can copy a scroll in a certain amount of time.

A few observations here: the tool enables, the human works. A faster tool, let us say a pen rather than a chisel on stone, allows for faster work, but more copies will always take more human time. We will call this Type 1 replication. It is characterized by modest gains in efficiency for mass production and poor scaling characteristics.

A second form of replication came about when humans began using tools to automate aspects of production. By investing time in setup, many copies can be replicated much faster. The work is still done by humans, with tools; but by doing the work intelligently, many copies can be made with comparatively low effort. We call this Type 2 replication.

The paradigm case for Type 2 is the printing press. By investing considerable effort in building a press, casting type, and laying out a document, one is rewarded by the ability to print as many copies as one wants, with speed and reliability which increase over time. Type 2 replication has good scaling characteristics and rewards mass production. It is characteristic of the Industrial Age.

Type 2 production next evolved in two directions the first of which we’ll call Type 2a: significant setup time followed by fully automated production. Newspaper presses work in this fashion, although the most recent ones are Type 3. Type 2a has significantly better scaling characteristics than Type 2, and mostly displaces it when developed.

Type 2b replication is where there is significant tool investment, but negligible setup time and non-automatic production. The matching paradigm for this is a Xerox machine, though like newspaper presses these have become increasingly Type 3 over time. An early Xerox would make a copy of anything that fit on the glass, or even a hundred copies, but a human had to stand around feeding it sheets and doing things like collation by hand. This has poor scaling qualities, being labor intensive, but it favors customization over mass production.

Type 3 replication has negligible setup times and fully automatic production. Our paradigm case here is a laser printer. Even a desktop laser printer can print replicas of stored data, each different, for many hours without needing attention. The factory scale printers can make entire books without human intervention. Type 3 replication is characteristic of the Information Age, or Industrial Revolution 2.0.

Type 3 has good scaling characteristics and rewards customization over mass production. One can make an arbitrarily large number of copies off any given template, but there’s little to no advantage over using many different templates.

These are the essential distinctions:

Many FabLab technologies, such as laser cutters, hobby-scale 3d printers, and CNC mills, are Type 2b. What’s interesting about 2b replication is that it’s often a small step away from being Type 3, needing only, for example, a small conveyor belt. I hope that by drawing attention to the radical difference in scaling quality between Type 2b replication and Type 3 replication, I can encourage open-source hardware developers to strive for Type 3 tools whenever possible.

A Type 2b tool is a creative enabler, while a Type 3 tool is both a creative enabler and an economically disruptive force, because it can compete effectively with 2a mass-production technologies. It also frees human labor for other pursuits, which is an important goal for many.

So this is replication; what of self-replication? This is the second concept I hope to make clear with this essay. Self-replication is not different from replication, except that, in the context of human-tool interaction, that which is being replicated is a part of the tool itself. I refer to this as recursion, because that’s what it is.

Note that there are several Type 1 replicators with a high degree of possible recursion. The lathe is a classic example: one can hand-turn many of the components for a lathe on itself, and even bootstrap a lathe by building the spindle and using it to make other components. A kiln is another example, since a kiln can be used to fire refractory bricks to make another kiln. In fact I might argue that a kiln exhibits the highest recursion of any Type 1 replicator, in that a kiln can be nothing but stacked bricks and a fire, and the bricks can all come from a kiln.

Note, however, that this still has poor scaling qualities, though it favors custom production. The Dave Gingery approach of contributing massive human inputs to a bootstrapped machine shop is noble, but it will never be an economic force. It is simply too easy to identify the main shapes needed, turn them over to Type 2 or 2a production, and swamp the market.

The RepRap project faces exactly this dilemma. RepRap knocked the bottom out of 3-d printing, but it did this mostly by making the MakerBot possible. The RepRap is a 2b replicator, which requires human tending during the entirety of the recursion process. This makes it easier and cheaper to simply make a chassis on a faster 2b tool, namely an Epilog laser cutter that NYC Resistor happens to already own, and sell that. If the RepRap were a Type 3, with an automatic conveyor, it might be a different story, since a RepRap could then print its chassis parts at a rate of a few complete sets a week with minimal human inputs. For that matter, a MakerBot with a conveyor belt would be a Type 3 replicator, albiet one exhibiting less recursion than a Darwin or a Mendel.

Let me conclude by suggesting that the RepLab project needs to place priority on Type 3 replication, not on a maximum level of recursion for the whole system. Recursion, I think I’ve shown, is no great trick if it takes a human hand-holding the machine through the whole process, since this is how machine tools have always been built, on other machine tools.

The power of Industrial Revolution 2.0 lies in developing machines which exhibit Type 3 replication. If the outputs of those machines are sufficiently general than the toolset as a suite can exhibit economically significant recursion. An example would be an open-source toolchain for automated printing and assembly of PCB boards. Such a suite would be able to print its own control hardware in addition to any other circuit that can be designed and mounted with a pick-and-place, which is most of them.

The RepLab project should focus on tools exhibiting Type 3 replication for a variety of economically significant goods. Recursion is an emergent result which can lend exponential momentum to the deployment of RepLab technology. By approaching the project goals in this order, we have a rational approach to an open source hardware platform for Industrial Revolution 2.0.

O Febootstrap é uma ferramenta que cria um sistema Linux baseado no Fedora dentro de uma pasta. Ele pode ser usado para criar um sistema totalmente funcional. Ele pode ser baixado no site: http://people.redhat.com/~rjones/febootstrap/ ou nos repositórios de sua distro. As distros baseadas no Debian podem usar o Debootstrap.

Para usá-lo, digite “febootstrap fedora-versao pasta “, onde “versao” é a versão do Fedora a ser instalada e pasta o nome da nova pasta para criar o sistema.

Obi und ich wollen etwas besonderes in Angriff nehmen: Wir entwickeln unsere erste Anwendung speziell für den Mac.

XCode ist wahrlich keine einfache Programmiersprache, aber wir werden uns einarbeiten (müssen) und bald entsteht ein neues Projekt: Der YouTube-Manager.

Ich hatte schon vor langer Zeit eine Idee. Wie wäre es, wenn man mit einer Anwendung YouTube organisieren und verwalten kann und seine wichtigsten Videos immer mit dabei hat, auch wenn man mal nicht online ist? Dies und viel mehr soll das Programm können. Es soll Videos in einer ganz neuen Art präsentieren, anzeigen und verwalten können. Selbstverständlich mit Login und allem was dazugehört.

Das Programm wird nicht gerade eine leichte Anwendung die man so eben in 2 Stunden programmiert. Unser erstes Ziel wird es sein, alle Funktionen des regulären YouTubes zu implementieren. Doch wir gehen einen Schritt weiter. Wir werden die Geschwindigkeit erhöhen und die kleinen Mankos ausarbeiten, die die Onlineversion von YouTube besitzt. Außerdem werden wir umfangreiche Organisations- und Archivierungsfunktionen implementieren, die so zuvor noch nicht bekannt waren. Features, die wir planen, sind (unter anderem):

• Revolutionäre, geschwindigkeitsbringende Benutzeroberfläche mit Drag&Drop Features und exzellentem Design
• Archivierungsfunktion, um alle seine Favoriten, Abbonements, einzelne Videos oder sogar alle angeschauten Videos immer dabei zu haben
• Bessere Tagging- und Suchfunktion
• Mehrere Favoritenlisten und verbesserte Playlistfunktionen
• Umfangreiche Verwaltung von Abonnements
• Neuartige Kommentarfunktion mit History und vielem mehr
• Verbesserte Administration des eigenen Kanals
• und vieles mehr…

Das alles hört sich ziemlich theoretisch an, und das ist es auch. Es wird allerdings das nächste Projekt werden. Wir werden zusammen daran arbeiten. Das Programm wird mit XCode programmiert und ist nur auf OSX lauffähig. Eine Windows- und Linuxversion wird es nicht geben! Ich habe mich dazu entschieden, regelmäßig den genauen Projektverlauf auf meinem Blog zu veröffentlichen. Sobald das Programm lauffähig ist, wird es höchstwahrscheinlich Weekly Builds geben.

Und jetzt das Wichtige: Das Programm wird komplett Freeware und OpenSource (Lizenz ist noch nicht entschieden)!

Und zum Schluss noch eine wichtige Aufforderung an meine Leser. Wie ihr sicherlich gemerkt habt, sprach ich vom “Programm”, denn das Projekt hat bislang noch keinen Namen. Es wäre nett, wenn ihr ein paar Namensvorschläge als Kommentar hinterlasst. Vielen Dank und schönen Sonntag noch!

Recently, I have been involved into the development of an open source project, that is currently under major modifications. Seeing this change happening before my eyes got me to think, how do open source projects evolve, and how do exiting well matured (old) projects reached their current state.

I feel that most open source projects start with a crazy idea, usually driven by some sort of need (the itch as called by The Cathedral and the Bazaar). But when one thinks about it, not many people have the guts to go out in the open to satisfy that drive. Mostly people who do aim to get an up and running prototype that shows the idea to the community. This is mainly to get people in the community excited, and people who had a similar itch involved.

To reach that initial prototype, the team working is often small, as the community knows nothing yet. The lack of the outsider perspective might limit the developers to their own coding style, and the drive of getting a prototype out might loose focus on certain coding aspects.

After the prototype is out, the effects of the bazaar model is seen, where bugs are fixed, code is optimized, improved, and documented. At this stage, the project takes it’s first step to maturity.

The changes over time could range the minor to the drastic. The main issue that developers wanting to get involved  with an evolving project, whether rapidly or slowly, patience is need. This is due to the need to take time to obtain a deep understanding of the code. Furthermore, patience is needed when a project is changing rapidly, as they mostly could end up in code breaks, but keep in mind they will eventually be fixed (possibly by you). Such an aspect also requires high flexibility.

After these many iterations by the community, the project starts to stabilize into a state of maturity. Usually this is called the 1.0 release. After that stage, progress starts to slow down, and focus starts to go to having new features. The main code base is rarely changed unless with major following released, or core feature additions that require that due to the structure of the code.

Sono molto legato ai colori della bash di linux. Con i file colorati in base al loro tipo.

In oltre programmando spesso via ssh con vim, ormai mi sono affezionato a questo semplice e free editor.

Quindi ho voluto mettere anche sul mio mac le stesse caratteristiche.

Iniziamo dal principio:

Come colorare la nostra bash

il file in questione è

/private/etc/bashrc

Questo file è il file base che viene letto ogni volta che apriamo una shell.

E le caratteristiche che troviamo al suo interno vengono applicate ad ogni utente.

A meno di creare un file ~/.bash_profile all’interno della home dell’utente che vuole delle caratteristiche aggiuntive o comunque diverse da quelle di default.

Se non esiste (di default non c’è) creiamolo:

touch ~/.bash_profile

e all’interno mettiamo:

LSCOLORS='ExFxCxDxBxegedabagacad'
export LSCOLORS
export CLICOLOR=1

(NB: se avessimo voluto applicare gli highlight a tutti gli utenti, sarebbe bastato aggiungere queste righe al file /private/etc/bashrc)

Adesso riavviamo bashrc:

. ~/.bash_profile

C’è differenza?

PS: se volete cambiare i colori consultate il manuale di “ls” con il comando “man ls” e cercate CLICOLOR

Andiamo ora ad aggiungere qualche funzionalità a vim

Come per bashrc c’è un file base anche per vim:

/usr/share/vim/vimrc

e un file che appartiene ad un utente specifico (che di default non esiste, ma lo sappiamo creare con il comando touch):

~/.vimrc

Noi modificheremo quest’ultimo, creandolo e aggiungendo al suo interno:

set tabstop=4           " spazi del tab
set number              " mostra i numeri di riga
set cindent shiftwidth=4    "indenta in automatico
                            "dopo una parentesi
                            "graffa di 4 spazi
set background=dark     " così si vede meglio il colore
set ai                  " auto indenting
set history=100         " tiene 100 linee di history
set ruler               " mostra la posizione del cursore
syntax on               " highlighting per la sintassi
set hlsearch            " illumina l'ultima parola cercata
filetype plugin on      " use the file type plugins

" Quando editiamo un file, salta sempre all'ultima
" posizione del cursore
autocmd BufReadPost *
\ if ! exists("g:leave_my_cursor_position_alone") |
\ if line("'\"") > 0 && line ("'\"") <= line("$") |
\ exe "normal g'\"" |
\ endif |
\ endif

Provate ora ad aprire un file sorgente con vim… notate differenze?

Après vous avoir parlé du le forum PHP non-stop, je vous devais un petit compte-rendu.
Cette année, le forum PHP a été placé sous le signe de l’interactivité, avec ou non des rencontres IRL.

L'équipe d'organisation une fois le forum fini, photo par Arnaud Limbourg

Le lieu

La Cité des Sciences est connu de tous les parisiens, mais c’est plutôt vaste. C’était un nouveau lieu, pour nous, et il a tenu ses promesses en termes de charge. Les bénévoles qui tenaient le vestiaire étaient un peu excentrés de la manifestation, et les visiteurs du Colloque sur Alzheimer voisin prenaient un peu leurs aises (ils essayaient de laisser leurs affaires dans notre vestiaire, ou pire, de les récupérer, sans penser qu’ils les avaient déposé ailleurs).
Cette année, nous avions 1 amphithéâtre et 2 salles de conférences, plus une salle réservée aux projets opensource francophones autour de PHP. C’était plutôt difficile de s’ennuyer.

Accueil des participants (photo :Arnaud Limbourg)

La salle Projets est une idée que nous avons eu sur le tard, et elle s’est avérée être une excellente idée, autant pour les développeurs des projets qui ont pu discuter avec d’autres développeurs et un public que pour les visiteurs qui ont pu découvrir qui était derrière les projets.

Les participants

Nombreux au rendez-vous et toujours aussi intéressés. Nous avons fait salle pleine à toutes les sessions, et ce avec 3 tracks de conférences en parallèle. L’événement s’agrandit donc indubitablement, et si vous n’y étiez pas, vous pourrez toujours participer l’an prochain.

Auditeurs (photo: Arnaud Limbourg)

Cette année, nous avions décidé de transmettre sur écran le Live Twitt du forum, avec le hashtag #afup et c’était un bon moyen de communication, avec des reprises des fortunes des conférenciers, de l’interaction.
Moosh a lancé un hashtag #afupnotes pour les twitts concernant le forum et les comptes-rendus.
N’oubliez pas que l’AFUP aussi twitte, d’ailleurs !

Les conférences

Pour ma part, j’ai passé du temps à l’Accueil, dans la salle VIP, et sur le stand Sensio Labs. Je n’ai pu assister à aucune conférence en entier, toujours quelque chose à faire d’autre, pour le confort des visiteurs ou des intervenants. Du coup, je laisse ceux qui ont assisté aux mirifiques conférences (Monty, Anna Filina, ou encore la Bingo Conf) vous en parler.
Heureusement, PHP TV a couvert l’événement et cette année, ils ont enregistré les conférences en audio. Il ne vous reste plus qu’à changer de slide au bon moment, en écoutant la conférence, puisque les slides sont disponibles en PDF sur le site web du Forum PHP.

Audience du forum PHP 2009 (photo: Arnaud Limbourg)

PHP TV a profité de ses caméras pour interviewer les conférenciers et autres stars présentes au forum PHP 2009. Vous retrouverez, petit à petit (il faut leur laisser le temps de faire la post-prod) ces interviews sur le site web de PHP TV : phptv.fr.

Du coup, je laisse la parole à ceux qui ont assisté aux conférences, et les ont commentées :

Vous trouverez les photos sur FlickR, dans le Pool Forum PHP, cette année, le photographe officiel était Arnaud Limbourg.

Et avec mon aggrégateur magique, j’ai créé une page listant les billets et articles qui rendent compte du forum PHP 2009.

Google, da poco ha annunciato la nascita di Go! il loro nuovo linguaggio di programmazione opensource. Dalla home del sito, pare che sia facile, veloce sicuro etc etc. Il mio pensiero è: “Ce n’era veramente bisogno?” ai posteri l’ardua sentenza, io intanto appena avrò un po’ di tempo lo proverò.

Breve y aun asi practica informacion sobre que es el OS de Google (Chrome OS) creo que va a estar muy padre sobretodo porque se bootea en tan solo 4 segundos!!! Y es opensource (gratis)!!!

Me entero vía OSNews que los fenomenos de la gran G han dado a conocer en una conferencia de prensa detalles de lo que se esperaba fuera vaporware.

Aparentemente estaremos hablando de un Linux pelado con un navegador web, resultando todas sus aplicaciones (salvo esas que necesitamos para que la maquina levante) web. Es decir, todo online. NO COMPRO.

Lo bueno de este linux con un navegador Chrome es que es un OS (del real, no este engendro web) tan estrecho, que desde el BIOS hasta el navegador bootea en 7 segundos. Lo cual no es un detalle menor considerando que mi telefono tarda al menos 10″, eso es muy bueno.

Respecto al storage local, funciona como cualquier linux pero con un par de detalles, la partición root (“/” para quien no esté en el tema) será read only (solo de lectura) y los home de cada usuario del equipo estará encriptado. Aparentemente está muy enfocado a la seguridad el asunto, al punto que si hay validaciones del CRC del filesystem que se corrige en caso de inconsistencia.

El código fuente? Pues bien, por acá

En fin, en la web? No compro, gracias, sigo con mis dos OS actuales.

Hay videos también, los cuales obviamente me voy a tomar un tiempo para ver:

Sebelumnya saya pernah mencoba nintendo emulator di windows yang lancar-lancar saja saya memainkannya. bahkan di windows program untuk memainkannya sangat berlimpah, alias banyak. nah, sekarang saya penasaran di ubuntu. apakah bermain Nintendo di ubuntu akan sama mudahnya dengan di windows. mari kita coba.

Pertama, saya sowan dulu ke embah google, mencari tahu keberadaan si emulator untuk ubuntu, setelah mencari akhirnya saya menemukannya. rupanya ada loh di add/remove atau ubuntu software center

selanjutnya setelah saya install maka saya mencobanya…

configurasi dulu gamepadnya… dengan mengetik 2 kali (tombol yang sama) untuk konfirmasi setiap tombol…

trus pilih configurasi video (kalau saya mending jangan diubah (karena masih menggunakan vga standard intel...) )

kalau sudah cari tempat rom di save (ke MAIN lagi) dan mainkan!

execute!

tapi kok… belom 5 menit sudah ngehang?… ooo… enggak tahunya (setelah saya cari referensi ke ubuntu forum) masih ada bug! payah nich! masa semenjak jaunty saya gagal melulu memainkan game nintendo di ubuntu! :angry: terpaksa deh harus ke windows tercinta lagi …

teman-teman ada yang punya referensi untuk memperbaiki bugnya??? atau punya aplikasi emulator untuk ubuntu selain FCEU ini …. kasih tahu saya donk!

sekian dulu posting (via Bilbo) tau bagus tau engga hasilnya pake tambahan foto

]]> http://ayekat.wordpress.com/2009/11/19/pinguine-ohne-grippe/ Thu, 19 Nov 2009 21:11:22 +0000 ayekat http://ayekat.wordpress.com/2009/11/19/pinguine-ohne-grippe/

… oder weshalb Linux keine Viren kriegen kann:

evilmalware 0.6 (beta)

Copyright 2000, 2001, 2003, 2005
E\/17 |-|4><0|2z Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is
NO warranty; not even for MERCHANTABILITY, COMPLETE DESTRUCTION OF IMPORTANT
DATA or FITNESS FOR A PARTICULAR PURPOSE (eg. sending thousands of Viagra
spams to people accross the world).

Basic Installation
==================

Before attempting to compile this virus make sure you have the correct
version of glibc installed, and that your firewall rules are set to 'allow
everything'.

1. Put the attachment into the appropriate directory eg. /usr/src

2. Type 'tar xvzf evilmalware.tar.gz' to extract the source files for
   this virus.

3. 'cd' to the directory containing the virus's source code and type
   './configure' to configure the virus for your system.  If you're
   using 'csh' on an old version of System V, you might need to type
   'sh ./configure' instead to prevent 'csh' from trying to execute
   'configure' itself.

4. Type 'make' to compile the package. You may need to be logged in as
   root to do this.

5. Optionally, type 'make check_payable' to run any self-tests that come
   with the virus, and send a large donation to an unnumbered Swiss bank
   account.

6. Type 'make install' to install the virus and any spyware, trojans
   pornography, penis enlargement adverts and DDoS attacks that
   come with it.

7. You may now configure your preferred malware behaviour in
   /etc/evilmalware.conf .

SEE ALSO
   evilmalware(1), evilmalware.conf(5), please_delete_all_my_files(1)

Quelle: GNU

I’ve uploaded some screenshots from the presentation on flickr.

edit: More on the official google blog and some more videos here.

ifPeople is honored to be a nominee for the YouTopia grant of $15,000 of branding services from Free Range Studios. To win this, we need your vote! Can you please take 3 minutes to register on the website and vote for our “Collaboration for Social Innovation” idea?

Our idea is to build a community of social innovators leveraging web technology to increase their impact. This community, which is already forming based on the work of our clients and our partners, will share lessons, exchange ideas, and collaborate. This community would include other partners and their clients who share the desire to build strategic and technology capacity in the sector.

We’re asking for your help in making this nascent community grow and thrive by supporting our YouTopia proposal! Why do we want to do this? Technology is a big challenge for most social enterprises, yet it’s also necessary for magnifying their impact.We use Plone and Salesforce.com to radically increase our clients capacity for communication, engagement and action. We believe this network will improve collaboration and knowledge sharing amongst organizations using similar tools and facing similar challenges.

Better Tech skills = Bigger Impact = A Better World

Voting is easy. You just need to create an account on the UserVoice website and then you can distribute 3 votes in the “Socially Responsible Business” category (you can give all three to one or distribute them). Vote for ifPeople here.

Please let us know any questions about the proposal in the comments. Thanks for your support!

The easiest way to get apps.

1. Pick the apps you want.
2. Start your customized installer.
3. You’re done!

Ninite installs apps with default settings and
says “no” to browser toolbars and other junk.

Ninite checks your PC’s language and 64-bit support
to install the latest, best version of each app.

Ninite runs on Windows XP/Vista/7 and works
in the background 100% hands-free.

All Ninite does is install the apps you choose.
Not even Ninite is installed.

Ninite

Ok, you are in right place if you need to validate a date from date_select helper.
Expecially if your problem is an invalid date like ‘31/02/2009′  that becomes ‘02/03/2009′ on rails!
If you don’t want to waste your time read here and don’t go immediatly to rails date validation plugin .

validates_timeliness plugin introduces a lot of great features to validate a date but its documentation is not so cool (this is my absolutely wrong opinion). You have to read it completly or take a look here about 3 important points:

• I18n
  if you don’t use :en locale you have to implement validates_timeliness default translation in your translations file (for ex. config/locales/it.yml) or you will waste your time to debug stupid exceptions. Default plugin translation file can be found in vendor/plugin/validates_timeliness/lib/validates_timeliness/locale after installation;
• Validate invalid date (like 31/02/2009 becomes 02/03/09) from select helpers
  You need to know that validates_timeliness doesn’t fix this problem automatically as you expect!
  You have to manually enable validates_timeliness workaround if you need to validate invalid date on rails.
  Put ” ValidatesTimeliness.enable_datetime_select_extension! ” your environment.rb (EOF) to enable validate_timeliness workaround and catch bad dates.
  Note: Patch to ticket #10556 introduced this problem: rails accepts invalid dates from input (instantiate Time object and convert it back to a date).  This problem generates a lot of confusion, checks on controllers, horrible workarounds and so on… A valid reason seems to exist! But WTF!!! People in panic and code with consistency problems…

Any other information (and download) can be find on validates_timeliness at github.

Have a nice day!

Ok, these errors are not good. They didn’t tell much about what happended.
But you can’t do as I did. Don’t wander on the dark side of the system…
Just try to execute your FCGI as your lighttpd did.
Find your lighttpd user in lighttpd configuration file (debian: /etc/lighttpd/lighttpd.conf).
On my configuration I see:
server.username  = “www-data”

so…

$ su
# cd /my_rails_root/public
# sudo -u www-data ./dispatch.fcgi

Read what’s happen and solve.
That’s all!