DEV Community: Nahue

Bots de Twitter y diarios de Uruguay 🇺🇾

Nahue — Sun, 26 Apr 2020 03:00:00 +0000

Bueno, hace unos días hice públicos unos bots que armé para monitorear las noticias que publican algunos medios de prensa uruguayos 🇺🇾

El país

📰 @elpaisuy
🤖 @ep_diff

El observador

📰 @ObservadorUY
🤖 @ob_diff

La diaria

📰 @ladiaria
🤖 @ld_diff

Montevideo portal

📰 @portalmvd
🤖 @mp_diff

Semanario Brecha

📰 @SemanarioBrecha
🤖 @sb_diff

Les cuento un poco más 👇

Primero que nada, pueden verlos a todos juntos funcionando en esta lista. Por supuesto, la idea es sumar más medios (LaRed21, La República, etc), así que si tienen alguno para sugerir, ¡me avisan! ☝️

¿Para qué? 🤔

Para ver cómo los distintos medios van moldeando la redacción de la noticia, desde que nace la noticia hasta que pasa el editor y le pone el “toque editorial”. ✍️

¿Cómo funciona? 🧐

Los bots leen la fuente RSS de cada medio cada hora. Si hay una diferencia respecto de la lectura anterior (sea URL, título o contenido), simplemente lo tuitean en un hilo.

Si detectan nuevas diferencias, continúan publicando sobre el mismo hilo. 🤖

Tiene varias ajustes para hacer aún. Por ejemplo, @portalmvd tiene problemas de acentos y todo el tiempo se detectan cambios por eso. Tengo que hacer que omita este tipo de cosas. No aportan a las diferencias que me gustaría destacar. Es un monitoreo editorial, no de redacción.

Otro caso de ejemplo es que @ladiaria cada tanto pone que se llegó al límite de consultas (la querida suscripción). Tendría que poder detectar que eso en realidad no es un cambio en la noticia.

Detalles que iré mejorando.

¿Cómo lo hice? 👨‍💻

Investigué lo que hizo @j_e_d con sus bots, que hacen lo mismo que acá pero sobre medios argentinos como Clarín o La Nación y encontré varias cuestiones interesantísimas…

Del proyecto este, nacen dos que toman caminos distintos para hacer lo mismo: leer fuentes RSS para realizar el monitoreo.

Uno armado por @xuv, que es sobre el cual se basa por ejemplo el laburo hecho por @cuasiperfecto en su bot @canillita_uy que hace lo mismo que estos bots que publico hoy, pero todo en la misma cuenta-bot de TW (desarrollado casi a la vez que esto, apenas unas semanas antes jaja).

Y otro armado por @edsu, que se llama “diffengine” (DE) y es sobre el cual partí yo. Me gustó más este porque además de publicar las diferencias en TW, las guarda en @internetarchive que, como ya sabemos, guarda para siempre lo que le pidamos.

De todos modos, a diffengine le hice algunos agregados, ya que por ejemplo publicaba todo, sí, pero de forma aislada y no como hilo. Así que mi primer mejora fue esa: que se publique en forma de hilo aquellas noticias sobre las que encuentran diferencias en el tiempo.

Hubieron otros agregados más técnicos:

el cambio de motor de gecko a chrome,
el paso de sqlite a postgresql,
la posibilidad de generar una URL de autorización para las cuentas bots que quiero que usen este motor
y finalmente, poder guardar datos sensibles a nivel de variables de entorno. Esto último para poder compartir el código del proyecto pero sin compartir datos sensibles.

Estas mejoras técnicas se hicieron para poder subir todo esto a servicios como Heroku, cosa de que quede corriendo en la nube y que no precise de mi máquina local para vivir.

Así que bueno, los que quieran chismear el código de diffengine + agregados, lo pueden hacer en la repo que tengo forkeada. 👇

nahuelhds / diffengine

track changes to the news, where news is anything with an RSS feed

Por otro lado, dejo también el proyecto que conecta los bots con este motor, acá 👇

nahuelhds / diffbots

Bots que tuitean las ediciones que se vean realizando en las fuentes RSS integradas

Cualquier idea o mejora sobre esto, ¡me avisan!

Solving MariaDB errors on Travis CI

Nahue — Sun, 21 Jul 2019 03:00:00 +0000

ERROR 1698 (28000): Access denied for user ‘root’@’localhost’

You need to use sudo in the line execution. Yeah. Just that.

I had this .travis.yml file

addons:
  mariadb: 10.4

before_script:
  - mysql -e 'create database testing;'

Notice the mysql -e 'create database testing;' line. The fix was using sudo

addons:
  mariadb: 10.4

before_script:
  - sudo mysql -e 'create database testing;'

SQLSTATE[HY000] [1698] Access denied for user ‘travis’@’localhost’

This error happens because Travis by default uses dist: xenial which is not fully compatible with the MariaDB addon yet.

The solution is setting dist: precise in your .travis.yml file

dist: precise

# ... rest of your config file

And that’s it. Hope it helps!

Basic Travis CI configuration for Laravel

Nahue — Sun, 21 Jul 2019 03:00:00 +0000

After some hours of trial and error, I’ve came up with this basic .travis.yml file ready to work with my Laravel project.

Note: my Laravel is 5.8 version and works with MariaDB and PHP 7.2.

# .travis.yml
dist: precise

language: php

php:
  - 7.2

addons:
  mariadb: 10.4

cache:
  directories:
    - node_modules
    - vendor

before_script:
  - cp .env.travis .env
  - sudo mysql -e 'CREATE DATABASE testing;'
  - composer self-update
  - composer install --no-interaction
  - php artisan migrate --no-interaction -vvv

script:
  - vendor/bin/phpunit

The .env.travis file is versioned and contains the following code.

# .env.travis

APP_NAME=Laravel
APP_ENV=testing
APP_KEY=base64:Dhtsut2yoe1Oc7Glgl4zPrGLQEKECbi3NoRNQh2N4/c=
APP_DEBUG=true
APP_URL=http://localhost/

DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=testing
DB_USERNAME=travis
DB_PASSWORD=

BCRYPT_ROUNDS=4
CACHE_DRIVER=array
MAIL_DRIVER=array
QUEUE_CONNECTION=sync
SESSION_DRIVER=array

Publishing your Expo Standalone App with push notifications into the App Store. The easy way... 😅

Nahue — Fri, 19 Jul 2019 03:00:00 +0000

Let’s do a simple check.

Did you receive a undetermined status from the push notifications permission? ✅
Did you receive an email saying something about ITMS-90078: Missing Push Notification Entitlement after delivering your app through the Application Loader? ✅

Making the push notifications work 📱

It took my two days and several hours to find out… 😡

The answers are on several Github issues and some threads in the Expo forums. I’m just gathering some of the info together. Basically you need to do two things.

Enable push notification for your app identifier. ☝️
Rebuild with Expo clear provisioning file parameter. ✌️

Enable push notifications on your App ID’s Identifier

As it’s mentioned in this GitHub issue:

In order to fix this, you need to enable “Push notifications” for your app on the app store.

Login to https://developer.apple.com/

Go to the “Certificates, Identifiers and Profiles” section

Select “App IDs” in the Identifiers section on the left column

Choose your app ID, edit it and check “Push Notifications”. Save changes

Generate a certificate for the production push service: go to the “Certificates” section, and follow the assistant to add a “Apple Push Notification service SSL (Sandbox & Production)” certificate for your app. Acute readers will notice that expo does not need this certificate since it uses a key to talk to Apple directly

TL;DR: Expo needs to enable the “Push Notification” service when creating the app in the Apple Developer Portal

Rebuild your Expo app

Second, I’m sure you already has published you app, so what you need to do is change the expo.ios.buildNumber in your app.json file and then rebuild the app clearing the provisioning profile like this. 👨‍💻👩‍💻

expo build:ios --clear-provisioning-profile

In that way Expo will generate the build with the Push Notifications that are now activated in your App ID Identifier.

Finally, upload it again from the Application Loader. You should be fine.

IMPORTANT! If clearing the provisioning profile doesn’t work, try clearing all with the command:

expo build:ios -c

API de Votaciones Argentinas 🇦🇷

Nahue — Tue, 16 Jul 2019 23:22:55 +0000

Acabo de publicar Cómo Votó. Por ahora es simplemente un API disponibilizado para consultas. No requiere autorización y está documentado lo suficiente como para que cualquier nerd que haya manejado APIs en algún momento de su vida, pueda interactuar con ella. 🤓

Pantalla de bienvenida del proyecto

El proyecto está en estado alpha por lo que es inestable y va a sufrir cambios; pero lo interesante es que ya puede utilizarse para generar consultas rápidas y hacer aplicaciones o clientes web con esta información. 🎉🎊🥳

Podés leer más sobre parte del proceso de elaboración del API en el post original, acá:
https://nahuelhds.dev/datos-abiertos/2019/07/16/Votaciones-Argentinas-API-Un-ID-para-el-Congreso.html

What is the best config for a Vue project?

Nahue — Tue, 25 Jun 2019 14:01:01 +0000

I work with VSCode and I can't make the debugging work properly with vue files. No matter if it's a vue-cli or a nuxt based project.

I can only manage to work with debugger statements wich is very annoying and time consuming.

I need recommendations or examples. Thanks in advance.

PS: I know I can debug through Chrome DevTools. I just want the full XP of debugging all inside the IDE, like I do with React or Angular

Setup Dark Mode in Slack on MacOS

Nahue — Mon, 24 Jun 2019 10:26:23 +0000

July 2019 update 😭

The Slack version 4.0.0 is not compatible with this solution. Need to investigate and if we can do this in this version as well.

June 2019 update 💁‍

Added a bonus step at the end (on my blog only), for automating the dark theme implementation with a simple double-click. 😁
Dark mode has arrived for mobile apps. Read it in the Slack blog itself. Desktop dark mode still in progress. Hopefully we can use this little hack here.
Updated the rawgit.com links to jsdelivr.com.

Credits to this Gist.

First, configure the general theme 👨‍💻

Close Slack
Open this file /Applications/Slack.app/Contents/Resources/app.asar.unpacked/src/static/ssb-interop.js
Append this at the very bottom

document.addEventListener("DOMContentLoaded", function() {
  let tt__customCss =
    ".menu ul li a:not(.inline_menu_link) {color: #fff !important;}";
  $.ajax({
    url:
      "https://cdn.jsdelivr.net/gh/laCour/slack-night-mode@master/css/raw/black.css",
    success: function(css) {
      $("<style></style>")
        .appendTo("head")
        .html(css + tt__customCss);
    }
  });
});

Second, choose a proper sidebar theme 💅

Go to Preferences / Sidebar
At the end of that page, choose to set a custom color
Paste this custom theme:

#171717,#404245,#424242,#ECF0F1,#4A4A4A,#FAFAFA,#2ECC71,#00A362

You can see other sidebar themes at Slack Theme. The one I chose is Green Lantern.

Enjoy the darkness 😈

That’s it. You can now open Slack and see the results!

¡Bonus step! Automatize this 🤓

Every time Slack makes a little update, you’ll need to manually add that little script again and again.

Well, not anymore. Read it on my blog

Enable SSL with OpenSSL and WAMP on Windows 10

Nahue — Sun, 12 May 2019 22:22:02 +0000

This is my environment: Windows 10 x64, WampServer Version 3.0.4 64bits and Apache 2.4.18

TL;DR

The instructions are on this post inside the WampServer forum.

If you can't start Apache, possibly there is something bad in your config. My issues are described in the next section. You can see your errores executing httpd directly on cmd.

cd \\wamp\bin\apache\apachex.y.z\binhttpd -t

That will show you the errors inside the configuration file and the line as well.

Important

It’s necessary to use a non-native OpenSSL version from WAMP. I downloaded mine from SourceForge’s page. The downloaded file was https://ufpr.dl.sourceforge.net/project/openssl/openssl-1.0.2j-fips-x86_64/openssl-1.0.2j-fips-x86_64.zip

Errors that I’ve faced

Native OpenSSL on WAMP: “Can’t find ordinal (…)”

On WampServer 64bits, the OpenSSL executable doesn’t work on Windows 10 64bits, so you need to download a working version for it.

My particular error was “The ordinal 113 could not be located in the dynamic link library”. The solution was to install OpenSSL on my own, like described above.

WAMP httpd: “invalid command SSLCipherSuite”

Uncomment the line from the httpd.conf file.

LoadModule ssl_module modules/mod_ssl.so

You can follow the instructions from the source.

Source: http://impradeep.com/invalid-command-sslciphersuite-perhaps-misspelled-or-defined-by-a-module-not-included-in-the-server-configuration/

WAMP httpd: “Cannot load modules/mod_ssl.so into server”

Two possible paths here. The seconds worked for me.

Include the OpenSSL’s DDL in the Windows directory

You have to install a different OpenSSL version. You can see this StackOverlow’s answer and follow the instructions: http://stackoverflow.com/questions/40017498/cannot-load-modules-mod-ssl-so-into-server

Replace libeay32.dll and ssleay32.dll on the Apache directory

It’s weird but those files libeay32.dll and ssleay32.dll that WAMP 64 ships doesn’t work with the SSL module. You need to download an Apache 32bits version and copy & paste them at \\wamp\bin\apache\apachex.y.z\bin.

I took the files from this Apache version.

Explicitly, this link: https://www.apachelounge.com/download/win32/binaries/httpd-2.2.32-win32.zip.

Source: http://serverfault.com/questions/477706/apache-ssl-on-64-bit-windows-not-a-valid-win32-application.

How to delete local and remote tags massively from a git repo in just one line

Nahue — Sun, 12 May 2019 20:24:33 +0000

TL;DR. Give me the magic 🧙‍♂️

WARNING! This is a destructive command. Use at your own risk

Use case: you want to delete the major version 0 and its children.

First, a dry run…

SEMVER=0 && git tag | awk "/^$SEMVER.\*/ { print \\$1 }"

This way you see what you’re about to delete.

Now, if you are certain, then bring the chaos…

SEMVER=0 && git tag | awk "/^$SEMVER.\*/ { print \\$1 }" | xargs -I % sh -c "git push origin :%; git tag -d %;"

Thanos is so proud of you

Notes

The SEMVER variable is a regular expression used inside the awk command. So if you would like to delete only the 0.1 version and its patches (0.1.1, 0.1.2, etc.), you could use SEMVER=0.1 in the command.

Windows users: you can still use GitBash.

I want the details 🤓

Let’s see the entire command again for deleting major version 0 and its children.

SEMVER=0 && git tag | awk "/^$SEMVER.\*/ { print \\$1 }" | xargs -I % sh -c "git push origin :%; git tag -d %;"

This one-line-command actually does the following things:

SEMVER=0 Declaring the SEMVER variable and for later use inside the awk command.
git tag Showing the available local tags in our local git repo.
awk “/^$SEMVER.*/ { print \$1 }” Here we use awk for filtering all the matching versions with the regular expression defined in the SEMVER variable.
xargs -I % sh -c "git push origin :%; git tag -d %;" Then, we use xargs to use the input through the percentage char (%) and combine it with the sh command. We tell to sh to read the execution from a string thanks to the-c argument. Finally, inside the string we execute the git commands to delete the tag remotely first, and then locally as well. Notice we’re using the xargs ’ input through the percentage char (%) here.

Hope it helps!

Undoing unwanted commits on Git

Nahue — Sun, 12 May 2019 03:44:20 +0000

I’m sure that once in a while, it just happens that you made a mistake. That’s ok. It happens.

But what if you commit the mistake. Several times. A headache for sure and so many other horrible things as well.

For those cases, I really recommend giving a read to On undoing, fixing, or removing commits in git. A document made by Seth Robertson.

It contains lot of resources for very incredible situations. I read it sometimes and it helps me out many others.

More at my technical blog