January 17, 2018 Adem Bilican No comments

How I implemented canSnippet’s newsletter campaign with MailChimp

“An email subscriber is worth 100x twitter or LinkedIn followers or whatever other stuff is out there. An email = a real channel” Andrew Chen

    A newsletter is an essential part of your online business/blog/project. It helps you reach your auditors more easily and keep them informed about any update regarding your project. I recently implemented a newsletter for canSnippet, my snippet management tool. I have already heard a lot about MailChimp and as it is the most commonly used service (and you can create a free account for small projects) I decided to go with it. I had some difficulties to create my first campaign (I didn’t even know what that meant at the time) so I wanted to share some essential points to help you in the creation of your first newsletter.
    There are 4 easy steps to follow for implementing a newsletter with MailChimp (without counting the fact that you already have a MailChimp account…).

1. Create a List

    This list will contain all the email addresses related to your project. You can have different lists for different projects. Connect to your MailChimp account and click on the Lists button on the top menu.

    Click the Create list button and confirm the creation of a new list. Fill the form with all the required information (you can see an example below).

Click Save to create your first list.

2. Design your forms

    Every event can be linked to a form, be it signup, unsubscibe… You can design all of these forms one by one and with great details. After creating your first list, you can click on the Signup forms tab and select General forms.
    For this simple example of a newsletter, all the forms that we will use are located under General forms except for the “Subscribe” form that will be located under Embedded forms.
There are 5 forms that are useful in case of a newsletter implementation. You can see the details of the required forms in the image below.

Click the image to see the full resolution PDF

You can select every form one by one and modify them as you like. I find the default forms already pretty good, I just added the logo and name of canSnippet on the header for additional personalisation.

3. Creating your first campaign

    You can now create your first Campaign that will correspond to your Welcome message. You can actually implement the Welcome message already in the Signup forms section, under Final Welcome email and tick the Send a final welcome email. Alternatively, you can create a Campaign and send a more personalized email every time a new user subscribes to your newsletter. That’s what we will do now, you can also refer to this approach next time you will create a Campaign.

Go to Campaigns and click Create Campaign, click Create an Email and give a name to your campaign.

Select Automated as we want the email to be sent every time a new user registers to our newsletter and select Welcome new subscribers.

In the next step just select the list we created earlier (so-called newsletter).
The final window corresponds to the heart of your campaign and will contain all the required information.
To send an automatic email every time an event is detected you need to adjust the trigger. Click Edit trigger and on the Delay section click on the drop-down menu and select Immediately and click Update Trigger.

4. Design your Welcome email

    Click Design Email and fill the form as you wish with the Email subject and Preview Text (optional) information. Then, select a template and start designing your welcome email. That’s where all the craziness starts as you can do everything you want. For a welcome email you can just start with a Basic – 1 Column layout and modify the text accordingly by adding an image for example. Then you can simply click Save and Close and click Save and Continue once you are done.

Click Next and review your workflow. If there is any issue, MailChimp will let you know. Finally, click Start workflow and confirm.

That’s it, you are done, enjoy your newsletter and share as much as you can‚ú®

November 24, 2017 Adem Bilican 13 comments

Upload/download images to/from AWS S3 in React-Native: a step-by-step guide

I recently struggled a lot to be able to upload/download images to/from AWS S3 in my React Native iOS app. I wanted to allow users to upload images to S3 and access some of the images from other users… I have a server running on Express (nodejs) and here is how I solved my problem.

1. Create an IAM user

Go to the IAM section on your AWS dashboard, select the Users category from the left side menu and press the Add user button.
1.1 Enter a username (test_user in this example) and select the access type Programmatic access, click Next:Permissions.

1.2 Leave this section as is and click Next:Review.

1.3 Finalize the creation of the user by clicking the Create user button.

1.4 Your new IAM user is created, click the Download .csv button and keep the file somewhere safe as it contains the Secret Access Key of your user. We will need this information later to create pre-signed URLs.

2. Create an AWS S3 bucket

Go to the S3 section on your AWS dashboard and click the + Create bucket button.
2.1 Enter a name for your bucket (test-bucket-tutorial in this example), the name has to be unique. Click Next.

2.2 Leave the default parameters in the Set properties section and click Next (you can always change them later)

2.3 Same for Set permissions, leave the default parameters and click Next

2.4 Review and click Create bucket

2.5 Go to your freshly created bucket and click + Create folder . Name your new folder images.

3. Create policy for your IAM user

So far we created our IAM user and our S3 bucket with an images folder. We now need to give permissions to our IAM user to access the S3 test-bucket-tutorial/images folder.
3.1 Go to your IAM section on your AWS dashboard and click the Policies section.

3.2 Click Create policy and select the JSON tab, then copy-paste the text below on the text input.

  "Version": "2012-10-17",
  "Statement": [
      "Effect": "Allow",
      "Action": ["s3:ListBucket"],
      "Resource": ["arn:aws:s3:::test-bucket-tutorial/images"]
      "Effect": "Allow",
      "Action": [
      "Resource": ["arn:aws:s3:::test-bucket-tutorial/images/*"]

It should look like the picture below:

3.3 Click Review policy, give a name to your policy (test-bucket-tutorial-policy in this example) and click Create policy

4. Attach policy to your IAM user

Now we need to attach the policy to the user.
4.1 On the Policies section, select our freshly created policy.

4.2 Go to the Attached entities tab and click Attach

4.3 Select the IAM user that we created at Step1 and click Attach policy

Now the user has the permissions (listed in the policy) to access the test-bucket-tutorial/images folder in your S3 bucket.

5. Generating pre-signed URL on the server side

Pre-signed URLs allow you to create a unique URL based on the credentials that you will provide and to safely use this URL on your client-side (without providing the Secret Access Key). As written earlier, I am using expressjs as a back-end, however the code below can easily be adapted to other alternatives.
5.1 Install the node aws-sdk package.

npm install aws-sdk

5.2 Copy-paste the following code to your main javascript code when running your server, this will output the generated pre-signed URL to the console.

var AWS = require('aws-sdk');
var s3 = new AWS.S3({accessKeyId:'XXXXXXXXXXXX', secretAccessKey:'YYYYYYYYYYYY', region:'REGION'});

var params = {Bucket: 'test-bucket-tutorial', Key: 'images/myimage.jpg', ContentType: 'image/jpeg'};
s3.getSignedUrl('putObject', params, function (err, url) {
    console.log('Your generated pre-signed URL is', url);
  • Replace XXXXXXXXXXXX by your user’s Access Key ID that you can find on the csv file previously downloaded (Step 1.4)
  • Replace YYYYYYYYYYYY by your user’s Secret Access Key that you can find on the csv file previously downloaded
  • Replace REGION by the region of your AWS S3 bucket, you can find this information here

6. Upload images to S3 from the client-side

My client-side is implemented in React-Native. To allow the user to select a picture and send it to our S3 bucket we will use the ImagePickerIOS component (which is not very highly documented…). Put the code below on your RN app wherever you want it to be run.

ImagePickerIOS.openSelectDialog({}, imageUri => {
    const xhr = new XMLHttpRequest()
    xhr.open('PUT', presignedUrl)
    xhr.onreadystatechange = function() {
        if (xhr.readyState === 4) {
            if (xhr.status === 200) {
            console.log('Image successfully uploaded to S3')
        } else {
            console.log('Error while sending the image to S3')
xhr.setRequestHeader('Content-Type', 'image/jpeg')
xhr.send({ uri: imageUri, type: 'image/jpeg', name: 'myimage.jpg'})
}, error => console.log(error));

I adapted the original code that I found in this very helpful article. Change the presignedUrl value with the pre-signed URL that you generated on your server (Step 5.2).

7. Downloading images from the client-side

If you want to download some images to your client app, you need to follow a similar approach with some slight changes:

  • remove the ContentType attribute from the params array
  • use the getObject method instead of putObject

The code will then look like:

var params = {Bucket: 'test-bucket-tutorial', Key: 'images/myimage.jpg'};
s3.getSignedUrl('getObject', params, function (err, url) {
    console.log('Your generated pre-signed URL is', url);

This code will generate a unique URL to access your image.
Check the AWS.S3 Documentation page if you want to learn more about the different methods that are available.

8. A concrete example

I personally use these examples in my own project as follow :
1 – The user selects a photo from the Gallery
2 – The RN app sends a request to my Express server with the name (and ID) of the user as the image filename
3 – The nodejs server generates the pre-signed URL adapted to the image filename using the AWS SDK
4 – The server sends the generated pre-signed URL to the RN app
5 – The RN app performs a HTTP request with the pre-signed URL to upload the image to S3

Let me know how it goes for you in the comments ūüôā

We can work together

Share this post on social media:

August 10, 2017 Adem Bilican No comments

How to get a specific sequence (chromosome, start, end) from the command line?

In several of my projects, I have to focus on specific regions of a genome, let’s say while looking for binding peaks. It is quite common to download a full genome as a fasta file, or each chromosome separately from Ensembl or NCBI. However, it is difficult to get a specific region of a genome (chromosome, start, end). I didn’t find any easy solution for it so far. Therefore, I focused on using tools available directly from NCBI, the e-utilities.

To get a specific region of the genome one needs to know the GI identifier of the chromosome of interest. Let’s say we are interested in sequences from chromosome 2L of Drosophila melanogaster. The first step is to search for it on the Nucleotide database of NCBI.

Here, we have to note the GI identifier (667674288)

Then, the command to run is

efetch -db=nuccore -format=fasta -id=667674288 -seq_start=12200 -seq_stop=13000

This will return the sequence of chromosome 2L between positions 12200 and 13000 in fasta format as follow:

>AE014134.6:12000-12200 Drosophila melanogaster chromosome 2L

This command gets really handy when working with multiple regions. One could save all the regions of interest in a tab separated file with one column containing the start position and the other the end positions such as:

12000    12200
13500    13700

and then use awk to get the sequences for all those regions and save it as a fasta file:

awk '{ system("efetch -db=nuccore -format=fasta -id=667674288 -seq_start="$1" -seq_stop="$2" ") }' dmel_chr2L_peaks.txt > dmel_chr2L_peaks.fasta

Enjoy and let me know if you have any alternative solution for this problem.

June 17, 2017 Adem Bilican 14 comments

How to submit an Electron app to the mac appstore?


1- Create a Bundle ID for your app

The very first step to be able to send a mac app to the appStore is to create a unique Bundle ID for it:

  • go to your Apple Developer Account
  • click Certificates, IDs & Profiles
  • select macOS in the top-left dropdown list
  • click on App IDs under the Identifiers menu
  • click the + sign on the upper-right part of the screen
  • give a description to your app, choose Explicit App ID and enter a Bundle ID (usually something like com.domain.appname)
  • click Continue and then Register


2- Create your developer certificates

You need two types of certificate as a developer to submit an app to the mac appStore:

  • click Certificates, IDs & Profiles
  • select macOS in the top-left dropdown list
  • click on All under the Certificates menu
  • click the + sign on the upper-right part of the screen
  • in the Production section choose Mac App Store
  • in the next page select Mac App Distribution, click Continue
  • create your Certificate Signing Request as indicated, click Continue
  • load your CSR file and download the generated certificate

In addition to the Mac App Distribution certificate, one also need a Mac Installer Distribution certificate. You need to perform the same steps as previously and select Mac Installer Distribution on step 5.
All your certificates should be ready now.

3- Package your Electron app

It is now time to prepare your app for the submission. You  first need to install electron-packager. This module will be helpful to create the .app and package everything we need. To install :

npm install electron-packager -g

And then run:

electron-packager . --appname=appName --app-bundle-id=com.domain.appname --version=ELECTRON_VERSION --overwrite --platform=mas --arch=x64 --icon=../appName.icns --prune --out=mas-build --ignore --app-version=1.0.0 --ignore=.+.o$

Change ELECTRON_VERSION to the correct version of Electron installed in your machine (run “electron -v” if you are not sure).
This will create your appName.app in a new folder named mas-build. This is usually enough if you want to distribute your app. However, a few more steps are required to submit it properly to the appStore.
As you can see, you also need the .icns file with the requested icon format. You can check here to see how to prepare the perfect .icns.

4- Sign your app

You need then to sign your app, so everybody knows it’s coming from a trustworthy developer ūüėČ
The codesign command already exists by default on mac, you will use it to sign your app. Run the following command by properly adding the name of your certificate and the correct path to your appName.app.

codesign --deep --verbose --force --sign "3rd Party Mac Developer Application: $$$$$ (£££££)" PATH_TO/appName.app
codesign --verify -vvvv PATH_TO/appName.app


5-Prepare additional files

5.a- Update the Info.plist

Your app is now signed. The next step is to find your appName.app, right-click and select Show Package Contents.
Go to the Contents folder and open the Info.plist file with a text editor (not Xcode).
Add the following code


Just before

<code><span class="nt"></dict></span>
<span class="nt"></plist>

Here you need to replace TEAM_ID with your teamID, you can find it on your Apple developer account (click Membership then you’ll see a row named Team ID).

5.b- Add child.plist and parent.plist

Create the two following files with the corresponding content:

  • child.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  • parent.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">

Replace TEAM_ID by your Team ID and your.bundle.id by the unique Bundle ID of your app (we previoudly used com.domain.appname).

6- Create a .pkg of your app

Create a new file and name it packageAppStore.sh with the following content.


# Name of your app.
# The path of your app to sign.
# The path to the location you want to put the signed package.
# The name of certificates you requested.
APP_KEY="3rd Party Mac Developer Application: Company Name (APPIDENTITY)"
INSTALLER_KEY="3rd Party Mac Developer Installer: Company Name (APPIDENTITY)"
# The path of your plist files.


codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Electron Framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Libraries/libnode.dylib"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/Contents/MacOS/$APP Helper"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper EH.app/Contents/MacOS/$APP Helper EH"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper EH.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper NP.app/Contents/MacOS/$APP Helper NP"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper NP.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$APP_PATH/Contents/MacOS/$APP"
codesign -s "$APP_KEY" -f --entitlements "$PARENT_PLIST" "$APP_PATH"

productbuild --component "$APP_PATH" /Applications --sign "$INSTALLER_KEY" "$RESULT_PATH"

You need to do some changes on this file on the first lines:

  • l4: change YourApp.app by the name of your app (with the .app extension), in our case appName.app
  • l6: change /path/to/YourApp.app to the path to your appName.app
  • l8: change ~/Desktop/$APP.pkg to the directory where you want to save your final .pkg, don’t modify the $APP.pkg part
  • l10 and l11: Enter the corresponding names of your two certificates
  • l13: change /path/to/child.plist to the path to your child.plist file
  • l14: change /path/to/parent.plist to the path to your parent.plist file

Finally, run the following command to generate your appName.pkg :



7- Launch Application Loader and load the .pkg

If you already installed Xcode, you should also have an application called Application Loader. Launch Application Loader and login with your account. You might need to get an app specific password, for this connect to appleid.apple.com and click Generate Passwords… on the APP-SPECIFIC-PASSWORDS section. Enter a Label (for example Application Loader) and copy paste the code to the Application Loader app.
Click Choose and select the freshly generate appName.pkg. This should automatically identify your app based on the Bundle ID.
Finish the whole process of uploading your app.

8- Complete your app information

You app build should be available on your iTunesConnect account soon. In the meantime, you need to complete the information about your app. Once done, you can select the build that you want to upload to the appStore and click Submit.

9- Some potential issues

If you submitted the .pkg file but it does not appear on itunesConnect, check your email. If you received something like:

Invalid Signature – The executable at path appName.app/Contents/Resources/app/node_modules/robotjs/build/Release/robotjs.node has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

You need to sign the different modules mentioned in this email. For that, just do as follow for each module:

electron-osx-sign appName.app appName.app/Contents/Resources/app/node_modules/robotjs/build/Release/robotjs.node

Voil√† ūüôā You can now enjoy some coffee while waiting for the review. Congratulations!

Source: https://electron.atom.io/docs/tutorial/mac-app-store-submission-guide/

We can work together

Share this post on social media:

June 12, 2017 Adem Bilican No comments

How to draw a Venn diagram in R?

The topic of today is about Venn diagrams, see here for a detailed defition. I will quickly show you how to draw a Venn diagram composed of three distinct datasets in R.

For this purpose you will need the VennDiagram package. Start R and install the required package as follow:


The main command to draw your Venn diagram is:

draw.triple.venn(area1 = 3472, area2 = 3528, area3 = 3492, n12 = 3176, n23 = 3323, n13 = 3182, n123 = 3096, category = c("sample1", "sample2", "sample3"), lty = "blank", fill = c("skyblue", "pink1", "mediumorchid") , cex=2, cat.cex=2, cat.fontfamily = rep("serif", 3))

The resulting Venn diagram will look like :

The explanation of the different numbers (area1, area2, area3, n12, n23, n13 and n123) are represented in the figures below:

June 7, 2017 Adem Bilican No comments

How to launch a job on SGE based clusters ?

As bioinformaticians, we often have to deal with computer clusters. There are different computer cluster systems available such as SGE, LSF… Although the main idea is the same, the commands used to submit a job might be slightly different. In this article I will quickly show how to submit a job to an SGE (Sun Grid Engine) based cluster.

There are two main commands that are very useful :

  • qsub: to submit a job to the cluster
  • qstat: to check the jobs you submitted to the cluster

There are two ways to submit a job to a cluster:

1 – Submission via a script

An example of a script is shown below, let’s call the script file jobscript.sh. In this case, it is essential to specify all the parameters as header of the script.

#$ -N jobName
#$ -q jobQueue
#$ -o /path_to/jobs.out
#$ -e /path_to/jobs.err
cd /folder

Here, we are starting a job with the following parameters:

  • -N: name of the job
  • -q: queue on which to run the job
  • -o: path to the output file
  • -e: path to the error file
  • The rest of the script correspond to the commands we want to run

Some additional helpful headers are as follow:

  • -pe smp 8: number of threads to use for the job (here 8)
  • -cwd: start the job on current working directory
  • -M: email address (to get notifications about the job status)
  • -m [b,e,a,s,n]: status to be notified about (beginning, end, aborted, suspended, no mail)

For more information see: http://gridscheduler.sourceforge.net/htmlman/htmlman1/qsub.html

To start your job, you need to run

qsub jobscript.sh

2 – Direct submission from the command line

There is an alternative way to submit a job from the command line.

qsub -N jobName -q jobQueue -o /path_to/jobs.out -e /path_to/jobs.err [ENTER]

cd /folder [ENTER]


This way the job will be submitted as soon as you press Ctrl+D. You can use several commands by pressing ENTER to separate each of them and start the job by pressing Ctrl+D after the last command.

January 19, 2014 Adem Bilican No comments

Save and share your snippets with canSnippet


UPDATE : canSnippet is not anymore on beta, I created a new page for the project.
canSnippet’s project page.

I am very happy today to introduce you to canSnippet. canSnippet is an open source web-based application to save and share your code snippets. It is my first ‚Äúbig‚ÄĚ project, thus I would like to have as many comments and feedback as possible. Please don’t hesitate to contact me for any question or remark, I will be happy to answer. For this project I used the CC BY license (I am also moving my whole blog under the same license), more information in the creative common by 4.0 page.
I used the following technologies for canSnippet : HTML, PHP, Javascript and sqlite.

Author: ademcan (ademcan@ademcan.net)
Version: 1.0 beta
License: CC BY

canSnippet is an open source web-based application to save and share your snippets.
The advantages of canSnippet are :
– it’s green (literally)
– open source (License CC BY)
– web-based
– easy installation process
– sqlite database
– syntax highlighting (based on prism.js)
– possibility to save private and public snippets
– unique link per snippet for easy sharing
– support many programming languages (html, css, javascript, python, java, php, ruby, c, c++, sql)
– rss feed
– search engine
– browse panel using AJAX
– responsive design
– it’s flat-green¬†ūüôā

Todo :
– search API
– tags support
– including prismjs plugins and themes
– create new non-flat theme

Alternatives to canSnippet :

Installation :
– Download the latest canSnippet.zip file
– send the zip file to your server and unzip
– give the following rights
705 to folders
604 to files
– open the following URL in your web browser
– Follow the unique instruction (i.e. fill in the form)
– Remove the install.php file for higher security
– You are done¬†! Now you canSnippet…


Demo :

Download :
GitHub : https://github.com/ademcan/canSnippet
zip | 7z (v1.0 beta ‚Äď 22.01.2013)

I would also like to thank my two super beta-testers Yome and Bajazet, thank you guys !
Again¬†: this is a beta. I am still working on the code to improve it as much as possible, and I am very open to any discussion about the code and the design¬†ūüôā

Enjoy !

Source: New feed

December 10, 2013 Adem Bilican No comments

[FR] L’identit√©


J’ai √©crit cette courte “histoire” pour ma participation au Prix de la Sorge 2013.
Merci à Yome et Yohan (le luxembourgeois) pour les corrections.


¬ę¬†Ch√©rie, je vais passer chez ma m√®re cet apr√®s-midi¬†¬Ľ s’exclama Christine.
¬ę¬†Fais-attention, tu ne devrais pas utiliser la iTransport si souvent, tu sais tr√®s bien que cette machine a caus√© des ennuis √† certains de ses utilisateurs.¬†¬Ľ
Christine ne l’√©couta pas en rentrant dans sa iBeauty pour se pr√©parer de la t√™te aux pieds en 30 secondes. John se m√©fiait encore plus chaque jour qui passe de toutes ces nouvelles technologies qui avaient d√©sormais envahi leur vie quotidienne. Il ne pouvait pas non plus trop s’en plaindre, lui qui se rendait tous les jours avec la iTransport depuis chez lui de Sophia √† l’Universit√© de Boston o√Ļ il √©tait professeur en √©tudes g√©n√©tiques. Il se tourna sans trop insister vers son √©cran g√©ant pour terminer son projet, allong√© sur son canap√©, le tout transmis aux travers des iElectrodes pos√©es dans son cerveau.
La soci√©t√© Aplle, avait lanc√© la iTransport il y a cinq mois. Cette machine de t√©l√©portation permettait de se rendre en quelques secondes √† n’importe quel endroit du globe disposant d’une autre iTransport. La technologie √©tait bas√©e sur la fission et la fusion des mol√©cules composant le corps humain. Chris Temp √©tait le chercheur qui s’occupait de ce projet au sein de la soci√©t√©. Il √©tait vraiment fier de son dernier bijou. Il ne pouvait pas s’emp√™cher de penser √† l’ann√©e 2001, l’ann√©e du s√©quen√ßage du g√©nome qui avait d√Ľ occuper pendant des ann√©es plusieurs groupes de recherche, dont le fameux Watson. Aujourd’hui, le s√©quen√ßage d’un organisme entier ne prenait pas plus de 5 secondes…
Avec la iTransport les notions de fronti√®res, pays et nationalit√©s avaient compl√®tement disparu. Toutes les communes √©taient au moins √©quip√©es d’une machine, ce qui permettait de se rendre √† des milliers de kilom√®tres pour passer la soir√©e dans un restaurant √† l’autre bout du monde. Dans la tr√®s grande majorit√© des cas, cette machine fonctionnait parfaitement. Cependant, il est arriv√© que la iTransport ne fonctionne pas comme pr√©vu dans certaines situations. Le syst√®me de t√©l√©portation est bas√© sur la fission des mol√©cules au lieu de d√©part et leur fusion dans des proportions et positions exactes √† la destination finale. Une simple erreur de proportion ou position d’une seule mol√©cule a √©t√© fatale pour certains de ses utilisateurs. N√©anmoins le leitmotiv de la compagnie Aplle √©tait clair ¬ęPas de progr√®s sans sacrifices¬Ľ m√™me si le sacrifice devait √™tre une vie humaine. Il restait encore certaines personnes qui ne partageaient pas cette id√©ologie mais elles √©taient trop facilement exclues de la soci√©t√© et consid√©r√©es comme ¬ę¬†attard√©es¬†¬Ľ pour √™tre pris au s√©rieux. John ne faisait pas partie de ces ¬ę¬†attard√©s¬†¬Ľ mais il les comprenait bien, lui, qui avait fait des √©tudes approfondies en g√©n√©tique, r√©alisait bien que ce n’√©tait pas une notion √† prendre √† la l√©g√®re. Cependant, il ne se plaignait pas trop et utilisait la iTransport assez fr√©quemment. Il devait d’ailleurs se rendre √† Oslo la semaine prochaine car il lui serait attribu√© le plus grand prix en g√©n√©tique pour ses travaux de recherches. Il recevra le prix Krogel en g√©n√©tique. C’est en particulier de ce fait qu’il √©tait tr√®s occup√© en ce moment, il devait finaliser ses analyses et surtout pr√©parer un discours digne de ce nom, ce qui n’√©tait pas chose facile, lui qui ne supporte pas d’√™tre mis sur le devant de la sc√®ne.¬†¬†¬†¬†John sursauta. Il venait de faire un cauchemar, il se retrouvait dans les ann√©es 1990. Il vivait dans un bloc en b√©ton et devait tout faire √† la main¬†: saisir du texte au clavier, utiliser la t√©l√©commande, ouvrir la porte, se doucher… S’il ne connaissait pas d√©j√† toutes ces machines bizarres gr√Ęce √† son arri√®re-arri√®re grand p√®re il n’aurait jamais su √† quoi elles servaient. Il aurait certainement eu l’impression de se retrouver sur une autre plan√®te.
Christine était de retour, elle apparut toute souriante au travers de la vitre de la iTransport.
¬ę¬†Bonjour ch√©rie.¬†¬Ľ
¬ę¬†Salut, comment va ta m√®re¬†?¬†¬Ľ
¬ę¬†Elle va tr√®s bien figure-toi, elle m’a annonc√© qu’elle participera √† la remise des prix Krogel √† Oslo.¬†¬Ľ
¬ę¬†Je ne pense pas que ce soit raisonnable qu’elle vienne. De plus, la c√©r√©monie de remise des prix sera retransmise en direct par hologramme.¬†¬Ľ
¬ę¬†Je ne vois pas ce qui te pose probl√®me, si elle participe, c’est pour te faire plaisir.¬†¬Ľ
¬ę¬†Oui, mais tu sais aussi tr√®s bien qu’elle n’a jamais utilis√© la iTransport et que cette machine est fortement d√©conseill√©e aux personnes √Ęg√©es.¬†¬Ľ
¬ę¬†Ah John¬†! Que puis-je te dire de plus…¬†¬Ľ
John se retourna sans trop insister pour continuer son travail. Il devait terminer sa pr√©sentation le plus rapidement possible pour avoir le temps de r√©p√©ter son discours. Il n’√©tait vraiment pas dou√© pour parler en face d’un public, encore moins quand ce dernier √©tait compos√© de grands chercheurs dont le professeur Temp.

Christine se r√©veilla lentement de son second sommeil, servit son caf√© et se pr√©para pour sortir chercher les enfants √† l’√©cole. Christine et John avaient deux adorables filles. Ils faisaient tout pour qu’elles grandissent dans de tr√®s bonnes conditions. C’est pour cela que John tenait aussi beaucoup √† son prix Krogel. Le sommeil avait √©t√© √©tudi√© en profondeur et les chercheurs d√©couvrirent que les humains disposaient plut√īt d’un sommeil polyphasique alors que la soci√©t√© des ann√©es 1990 les avait rendu mono-phasique. Une simple sieste de vingt minutes toutes les quatre heures suffisait largement.

John re√ßu un message t√©l√©pathique de la part de l’un de ses collaborateurs Fredy Curck¬†:
¬ę¬†John, il faut imp√©rativement que tu me retrouves le manuscrit de th√®se de ton ancien √©l√®ve Greg. Je pense que celui-ci peut contenir des informations tr√®s importantes pour mener notre projet √† bien.¬†¬Ľ
John et Fredy √©tudiaient en secret la iTransport. Ils avaient pr√©vu de la d√©monter et d’analyser en d√©tails les technologies utilis√©es. Le but de John √©tant tout d’abord d’√™tre s√Ľr de son utilisation saine et pourquoi pas en faire une base pour ses futures analyses. John s’empressa de se rendre au sous-sol de sa maison o√Ļ il conservait encore bizarrement des versions papier de certains documents, dont le fameux manuscrit de th√®se. Le papier √©tant tr√®s cher, et tout le monde disposant d’espaces √©lectroniques infinis pour sauvegarder leurs documents, il √©tait tr√®s rare de trouver encore des documents au format papier, cela va s’en dire qu’il √©tait encore plus difficile de trouver une imprimante. John √©tait bricoleur et avait r√©ussi √† remettre en marche une imprimante qu’il avait retrouv√© dans les objets de son arri√®re-arri√®re grand-p√®re.
Il retrouva tr√®s rapidement le manuscrit en question et s’empressa de le scanner au travers de ses lunettes pour le transmettre √† Fredy. Il ne pouvait s’emp√™cher de se demander ce que Fredy pouvait trouver d’int√©ressant dans cette th√®se. Il ne se souvient d’aucun r√©sultat tr√®s important au sein de ce manuscrit qui pourrait leur permettre d’avancer dans l’analyse de la iTransport.
¬ę¬†Ok Fredy, voici donc le manuscrit que tu m’as demand√©. Je peux savoir ce que tu cherches exactement¬†?¬†¬Ľ
¬ę¬†Pas maintenant John, il faut que je regarde cela rapidement. La c√©r√©monie des Krogel √† lieu dans moins d’une semaine. Tu imagines si nous pouvions avoir des r√©sultats juste avant cette c√©r√©monie¬†?¬†¬Ľ
¬ę¬†Oui effectivement ce serait une tr√®s bonne chose…¬†¬Ľ
¬ę¬†Papaaa, nous t’attendons pour manger¬†!¬†¬Ľ S’√©cria Sophie, la plus grande des deux filles.
¬ę¬†J’arrive mon amour¬†! Fredy, je dois y aller, tu sais que nous mangeons √† table une fois par semaine, j’attends de tes nouvelles avec impatience, tiens-moi au courant d√®s que tu as du nouveau, salut.¬†¬Ľ

Les capsules nourrissantes √©taient largement suffisantes pour permettre au corps humain de s’approprier tous les √©l√©ments n√©cessaires. N√©anmoins, Christine et John avaient d√©cid√© qu’ils mangeraient √† table une fois par semaine, m√™me si cela semblait tr√®s archa√Įque.

¬ę¬†John, nous avons un probl√®me…¬†¬Ľ, c’√©tait Fredy, sa voix tremblait. John ne pouvait plus le joindre mais il appris rapidement que des forces de l’ordre avaient fait irruption √† son domicile et r√©cup√©r√© tout le mat√©riel n√©cessaire √† l’√©tude de la iTransport. La soci√©t√© Aplle disposant de tous les droits sur le produit, il √©tait formellement interdit d’analyser cette machine. Toute personne essayant de comprendre son fonctionnement risquait une peine tr√®s lourde. C’√©tait horrible, qu’allez-t-il se passer maintenant¬†? John essayait en vain de joindre son ami et de faire quelque chose pour le sauver. Il se rend√ģt chez lui o√Ļ la femme de Fredy √©tait seule et d√©sesp√©r√©e. Il savait pertinemment que Fredy lui aurait laiss√© un message, un signe. C’√©tait bien le cas, certains documents tr√®s importants de Fredy √©taient toujours gard√©s dans leur bo√ģte secr√®te en commun. John ne risquait pas grand-chose, leurs discours avec Fredy √©taient toujours chiffr√©s. Il n’√©tait pas possible pour John de laisser tomber cette affaire. Avec tous les documents il se rend√ģt chez lui pour continuer les travaux¬†; il ne lui restait plus que deux jours avant la c√©r√©monie de remise des prix Krogel.

Ces deux deniers jours, John ne respecta pas son cycle polyphasique de sommeil, il ne dormit pas du tout. En lisant les rapports de Fredy il r√©alisa pourquoi son ami lui avait demand√© la th√®se de son ancien √©l√®ve. Il avait d√©couvert une potentielle faille dans le syst√®me de la iTransport. Le court instant entre la fission et la fusion des particules composant le corps humain √©tait le point faible de la machine. Il devait alors analyser ces ondes de tr√®s grandes amplitudes. La th√®se en question correspondait tout √† fait √† ce qui pouvait aider John et Fredy √† se faufiler au sein du m√©canisme de fonctionnement de la iTransport. John s’empressa de relire la th√®se de Greg et y retrouva effectivement un algorithme permettant la r√©ception et la modification des ondes qui transportent les mol√©cules, les m√™mes utilis√©es dans la iTransport.
John √©tait tout excit√©, en plus de recevoir le prix Krogel, il pouvait devenir le chercheur le plus reconnu de la Terre s’il arrivait √† se faufiler dans le syst√®me de la iTransport. Bien s√Ľr tout cela n’√©tait pas sans risque. Il pourrait m√™me tout au contraire perdre son prix Krogel, mais rien ne pouvait arr√™ter John. Ce projet d√©passait tout ce qu’il pouvait imaginer. Il se doutait que ce syst√®me poss√©dait une voire plusieurs failles et c’est lui qui les d√©couvrirait.

John disposait de deux iTransports √† son domicile, son salaire √©lev√© lui permettait ce luxe. Il regroupa rapidement ses deux machines dans sa salle d’√©tude. Il lui fallait maintenant un cobaye, il ne pouvait pas risquer Katzy, sa chatte ador√©e, de plus ses filles ne le lui pardonneraient jamais s’il arrivait quoi que ce soit √† Katzy. Il d√©cida de se servir d’un simple objet et amena son imprimante avec lui. La iTransport disposait d’un syst√®me de reconnaissance et n’aurait jamais accept√© de fonctionner avec un objet connu autre qu’une particule vivante, ce qui √©tait la raison pour laquelle elle avait √©t√© cr√©√©e. Un des rares objets qui ne serait pas reconnu et donc potentiellement rejet√© par la iTransport √©tait la vieille imprimante qui lui restait. C’est avec un pincement au cŇďur qu’il d√©cida de l’utiliser en tant que cobaye.
Il testa donc rapidement la t√©l√©portation de l’imprimante d’une iTransport vers l’autre. Le transfert √©tait tellement rapide qu’il n’avait pas eu le temps d’intercepter d’ondes, mais comment Fredy avait-il fait¬†? En relisant rapidement les rapports de Fredy il r√©alisa que son ami avait travaill√© dans une chambre froide pour ralentir naturellement les ondes pendant le transfert. John f√ģt de m√™me en se rendant dans le sous-sol de sa maison. En renouvelant le transfert avec toutes les machines en place il commen√ßa √† apercevoir des signaux. L’√©cran affichait des nombres et des lettres qui n’avaient aucun sens tel quel. Il ne savait pas trop comment s’y prendre mais les notes de Fredy allaient lui √™tre d’une aide exceptionnelle.
Il installa rapidement l’algorithme d’identification des ondes sur l’ordinateur principal et r√©p√©ta la manipulation de t√©l√©portation de son imprimante. L’√©cran affichait un message binaire, qui ne repr√©sentait rien aux yeux de John dans son √©tat actuel. La section ¬ę¬†R√©sultats¬†¬Ľ de la th√®se de Greg contenait des informations √† propos de cette s√©quence binaire. Il s’agissait en fait de la composition de l’imprimante. John s’arr√™ta. Que voulait dire la composition¬†? Une explication lui effleura l’esprit mais il ne voulait pas y croire. Il n’y avait qu’une seule solution pour pouvoir confirmer ses doutes, il devait essayer la machine avec un organisme vivant.
Il courut au jardin et trouva une coccinelle sur une feuille de son prunier. John ne pouvait pas faire de mal √† une fourmi mais cette fois c’√©tait pour la bonne cause, il en √©tait excus√©. Il se pr√©cipita √† nouveau dans le sous-sol de sa maison et r√©p√©ta la manipulation avec la coccinelle. Les s√©quences binaires ne s’affichaient plus sur l’√©cran, il ne distinguait plus rien. Il r√©p√©ta la manipulation une dizaine de fois avant de voir appara√ģtre le premier signal. Il s’agissait d’une s√©quence, une suite de lettre cette fois-ci, John lisait
¬ę¬†A, A, C, T, A, G, T…mon Dieu¬†!¬†¬Ľ S’exclama-t-il, ¬ę¬†ils n’ont pas os√©…¬†¬Ľ
Il s’agissait de la s√©quence d’ADN de la coccinelle. John pouvait facilement distinguer tous les g√™nes de la petite b√™te. Il pouvait m√™me en d√©duire le ph√©notype de celle-ci. John √©tait √©bahi, l’ADN, le code g√©n√©tique √©tait la derni√®re identit√© qu’il restait aux personnes. Plus rien n’√©tait secret, les informations personnelles, le groupe sanguin, les empreintes digitales… il ne restait plus que l’ADN… mais cela n’√©tait plus vrai d√©sormais. John √©tait persuad√© que la iTransport utilisait uniquement les informations des mol√©cules pour effectuer les r√©actions de fission et fusion. Il ne se doutait pas une seule seconde que tout le corps √©tait scann√© jusqu’au d√©tail pr√®s du code g√©n√©tique. En analysant en d√©tails les donn√©es transmises il r√©alisa un lien vers une adresse internet¬†: iDbD, il s’agissait certainement de la base de donn√©es o√Ļ toutes les s√©quences √©taient stock√©es.
John s’assis, il √©tait t√©tanis√©, il ne lui restait plus rien, il ne restait plus rien de l’humanit√©. La d√©couverte qu’il venait de faire √©tait une charge trop lourde pour lui. La c√©r√©monie de remises des prix Krogel avait lieu dans moins de deux heures, qu’allait-il faire¬†?…

Image source : Fingerprint Рwikimedia

Source: New feed