El pasado noviembre del 2020 tuve la oportunidad de participar en el JSConf México para dar una breve charla titulada: ¿Por qué WebAssembly? En ella comento las razones de su existencia, cómo viene ayudar a Javascript a solucionar los problemas que ese lenguaje no permite hacer (o al menos de forma óptima).

Estaba muy emocionado por participar en este evento por muchas razones. Principalmente era volver a México luego de muchos años y compartir con la gente de allá. Pasar unos días allá, pero debido al COVID-19 se tuvo que retrasar y posteriormente hacerla virtual.

¿Por qué WebAssembly?

Esta charla es una variación de las anteriores que he dado, porque ya WebAssembly es usado cada día y no es tecnología del futuro, sino del presente. Ya hoy en día puedes usarlas sin problemas y entonces cambio el enfoque de la charla a por qué usarla.

En fin, si deseas verla totalmente en español puedes hacerlo a continuación. Una vez finalizada, me gustaría conocer tus opiniones, dudas o recomendaciones respecto al tema.

Why WebAssembly?

Me pareció muy chévere como el audio mi charla fue traducida a inglés. Agradezco al equipo de JSConf México 2020 por realizar esa labor. Gracias a ello, mi mensaje puede llegar a más personas y puedan aprender sobre ésta tecnología. Si prefieres escuchar el audio en inglés, a continuación te comparto esa versión del video.

Fue una gran experiencia participar en mi 2do JSConf, lamentablemente tuvo que ser virtual. Hubiese querido estar allá y regresar a México luego de muchos años (me encanta la comida mexicana real). Compartir tiempo con varios amigos de México como Yuliana y Luis Sanchez y disfrutar de la hermosa cultura del país.

Recuerda compartir este artículo si te gusta o deja tu comentario si deseas preguntar o complementar la información.

La entrada ¿Por qué WebAssembly? Mi charla del JSConf México 2020 se publicó primero en El blog de Skatox.

I’ve owned a TaoTronic TT-BH22 headphones with noise cancellation for a while ago, and I can tell you that despite being quite cheap have worked perfectly for me. Battery life is fantastic (around 40 hours) and noise cancelling, even if it’s not 100% perfect as the professional ones, is more than acceptable.

However, then I bought those I didn’t realize that they had an integrated microphone, and I think that during the first year of use I left this feature forgotten and unused since my SO didn’t recognized it right away. Sad thing is, it wasn’t until my husband tried them on his laptop and his SO recognized the microphone, that we knew about this.

And even sadder than that? We both use the same SO… so it was time to work around this and figure out why it was working on his laptop and not on mine, so if anyone has encountered an issue like this, here’s a solution that should work with every headphone with a built in microphone just like mine.

All problem was this: Like this headphones have a high fidelity sound  (Hi-Fi)  my system didn’t recognized them as regular headphones and “assumed” they didn’t had a microphone, that was it…

Now it was just time to configure correctly the headphone type, however, KDE’s Bluetooth config app is too simple and doesn’t allow more advanced settings, so I installed blueman, which is Gnome’s Bluetooth settings app and allowed me to configure easily my little gadget without going to the terminal. So lets install blueman as root:

[root@libro ]# dnf -y install blueman

And with this app we can configure our Bluetooth devices better. when we open the app the first thing we see is the list of recent devices.

  • We will locate our headphones on this list and right-click it to see the menu.
  • Will select the option “audio profile” .
  • And finally select the option Headset Head Unit (HSP/HFP).

And that’s it, you should be able to see your microphone between the audio device list and select it.

Now this happy girl can walk around the house while makes herself a coffee in between the million meetings we have now during this pandemic.

Let me know if this worked for you, and specially, which headphones did you configured so I can add them to this list.

  • TaoTronics TT-BH22

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

When we are creating a book that will be published at Amazon Kindle Store and we want it to be printed as well as digital, we need to have some important considerations when comes to create the cover.

It’s not just about having an attractive cover that encourage readers to buy, but it also has to be functional when comes to content, paper type and even the thickness of the book itself. Anyway, the idea is to have a working cover that won’t ve rejected by the automated verification process that Amazon holds.

When comes to select our book properties, we not just have a wide sizes variety, but also we have to decide is it will be printed on black/white or color. Besides, we will have to choose the thickness and quality of the paper, so we can begin to estimate the size and cost of our book.

For this example, we will assume we are creating a cover for a 6″x 9″ (15.24 x 22.86 cm) book

The most important when comes to create a book cover are the dimensions, since it won’t matter to have a fantastic cover that crops, is unreadable or is misplaced and not aligned correctly. This is why we will use an online service that will help us run the necessary calculus to save time and effort:

Lets asume we have a 100 pages book, and we will use a White paper for color impressions.

This type of paper has a thickness of 0.002347″ (0.00596138cm)

This web allows us to play with several options that include pre-formats to start writing our books, generate the ISBN bar code, but the option we really need is the KDP Cover Template Generator. So click on it

On this form, we will have to fill the data requested on each field just as follows:

  • Width: 6
  • Height: 9
  • Page count: 100
  • Paper type: select white colour
  • OPTIONAL ISBN-13:Leave this in blank
  • OPTIONAL Price Barcode: Just leave this in blank
  • Formats: Select the ones that I put on bold, which are usually already marked
    • PDF
    • PNG
    • IDML (InDesign)
    • SLA (Scribus)
    • ODG (OpenOffice)
  • Your email address : hi@gmail.com
  • Your email address (again): hi@gmail.com
  • Consent to email: Check this last field to consent that you want them to send you an email.

Finally click on the “Email Cover Template” button and this will display a popup with the option to leave a donation. Remember to always leave a tip if you can since this services don’t have funds beyond their own users.

If you can’t make a donation, then simply select the first option that says “No thanks, just email me the template” .

Either you make a donation or not, you will finish the process with this donation page again, but this time with a success message that ask you to check your email and download your guides. Just do so and download either the png or pdf with the desired layout. I’m gonna open it with inkscape to start designing my cover.

We add the image with our layout to inkscape and adjust the size of the canva to the one at the image (the outside). This will allow our design to already include the cut margins or bleeds that always give us a headache.

We will design our cover following the guide lines and respecting the margins, only writing our content on the white parts of the layout. We will include our title, images, description but remember to leave the space for the ISBN since Amazon will add it automatically in case you don’t have one.

It’s important to mention that the section we usually forget is the name at the book mold. Make sure that this text is within the white line at the very center of the layout without touching the red border so it pass the Amazon KDP filters.

To work more comfortably, I set the layout image to a 60% opacity and put it on top of everything, that way I was able to see every element below the layout and move them better. But this is just a personal recommendation.

Once happy with your design, just delete the layout image, export your cover at 300DPI and you will be set to upload it at Amazon KDP.

Let me know if this tutorial was useful and if you created your book cover easily with this tips!


This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

This days I had to send a multiple page PDF with a bunch of pictures on it, but requirements said that it needed to be smaller than 5Mb. With Ghostscript I was able to transform a 10.9MB file into a 1.2Mb without loosing quality, since it was mandatory that the small letters contained on the PDF were completely readable.

To work with ghostscript first you need to install it:

[tatica@libro ]$ sudo su –

[root@libro ]$ dnf -y install ghostscript

Then we exit the root mode and locate at the folder where we have the file, in my case:

[root@libro ]$ exit

[tatica@libro ]$ cd /home/tatica/Documentos/archivo-maestro.pdf

To run ghostscript let me first explain you the options you can choose, and what you can archive with each one of them:

/prepress (default) Higher quality output (300 dpi) but bigger size

/ebook Medium quality output (150 dpi) with moderate output file size

/screen Lower quality output (72 dpi) but smallest possible output file size

In my case, I want the file to be compress, but not to loose quality, so I ran my script with the ebook option:

gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/ebook -dNOPAUSE -dQU
IET -dBATCH -sOutputFile=archivo-resultante.pdf archivo-maestro.pdf

and that’s it. Remember that the output file comes first, and the file you want to convert comes at last (I know, tricky). If you used it, let me know how did that work for you!


This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!
h-entry es un formato simple y abierto para contenido episódico o con marca de fecha en la web. h-entry se usa a menudo con contenido destinado a ser sindicado, p. ej. publicaciones de blog. h-entry es uno de varios estándares de microformato abiertos adecuados para incrustar datos en HTML.