#nodejs

Usar el método adecuado, hace que los datos trabajen de forma óptima ! 🧭ES

Bad Quarto just put out Run Run Run, a collection of code poem where the source code and output fit on a single page.

Here is a photo of my contribution: A Map of Possible Spaces. It's a single line of Node!

The widely used minimatch npm package patched CVE-2026-27904, CVE-2026-27903, and CVE-2026-26996, fixing ReDoS vulnerabilities affecting Node.js glob pattern processing.

Source: Socket

Good templates can dramatically change your sales margin by enhancing the overall user experience and visual appeal of your online store. A clean, professional, and well-structured template helps customers find products easily, builds trust, and encourages faster purchasing decisions.

It also improves website speed, mobile responsiveness, and SEO performance, attracting more visitors and converting them into buyers.

Okay so the authentication for spotify is hard for me to understand and requires user authentication, then making a token request that while expire in an hour. So i focused on what I did know how to do and what I had access to token wise. The Spotify developer home page has a temporary access token for demos. I took that token and made a function to make get request to the API and two functions for top tracks and top artists. Then made some functions to print them in my terminal. Here is what my end product looked like in the terminal.

The data for tracks is proving to just show a years worth of listening even though I specified long_term in my get request.

Here is my code:

I tried just doing track.artist but Spotify handles that as multiple artists so I had to handle them as such.

Next Steps: Tackling the user authentication and token requests and including it in this code.

When I started this, I thought this was going to be easy: just improve the timers so that if a user refreshes the browser or reconnects to the game, the gathering action doesn't drop. What I failed to understand is that I still have no clue how to use Redis or Sockets.

After several days of wrangling with this thing, I somehow managed to figure out what seems to be a somewhat robust (and working!) solution.

I also ended up finding (and addressing) several more issues with my original gathering POC.

I made sure that all gathering logic is centralized on the back-end, eliminating front-end trust, which should help protect against cheating and exploits.

I also did what I naively set out to accomplish: Front-end UI now actually restores the visual status of ongoing gathers after reconnects or refreshes.

This was an absolute pain in the ass, and I hated every minute of it.

Now onto the next challenge that will make me crippled with self-doubt and question my ability to use my brain.

An accurate depiction of me trying to figure out Redis, Sockets and NodeJS: