Cloudflare broke down. Comrade asked a very valid question

Cloudflare broke down. Comrade asked a very valid question

I’ve launched an electronic open source application for my book Recommender Algorithms! It’s a “sandbox” where you can “run” various recommendation algorithms with different settings, and view specific visualizations for each algorithm that help understand how it works. For instance, for algorithms like ItemKNN, SLIM, or EASE, a key visualization is a heatmap of the learned similarity matrix (item-item similarity matrix). This allows you to see which pairs of items the model considers “similar” (or “influencing” each other). For SLIM, for example, a useful “Sparsity Plot” shows that the similarity matrix indeed turned out to be sparse. For associative rule algorithms (Apriori, FP-Growth, Eclat) the visualization is not a graph, but interactive tables with found “Frequent Itemsets” and generated “Association Rules,” which can be filtered and sorted.
Additionally, there is a parametric mechanism for creating a “game dataset” — Dataset Wizard. It works like this – there are template datasets that describe items through characteristics. For example, recipes through flavors. Or movies through genres. The system generates random users with a random set of characteristics from the same set — and there are many sliders to make this distribution more contrasted or complex. Next, a matrix of user ratings of items is created – conditionally, if the characteristics of the user and the item match, then the rating will be higher because “tastes match”; conversely, if they differ, then the rating will be lower. Here too, sliders add noise and scarcity – randomly removing part of the matrix. The characteristics of products and users are not fed into the recommendation algorithm; they are hidden, but they are used to visualize the results.
The third component of the application is the tuning of hyperparameters. Essentially, it’s an auto-configurator for a specific dataset. An iterative approach is used, which is much more efficient than a full search (Grid Search) or random search (Random Search). In short, the system analyzes the history of past runs (trials) and builds a probability “map” (surrogate model) of which parameters will likely yield the best result. Then, it uses this map to smartly choose the next combination to test. This method is called Sequential Model-Based Optimization (SMBO).
The code is open source and will be further supplemented with new algorithms and new visualizations.
Link to the code in the comments.
Link to the site where the code is deployed and where you can check out the application is also in the comments.














“Hello. I am an Albanian virus, but due to the low level of technology in my country, I cannot do anything to your computer. Please kindly delete one file on your computer and then forward me to other users.”
Here’s the 2025 version. The line they ask to insert into the terminal – echo “” | base64 -d | bash
This line contains curl, pointing to 217.119.139.117 whose result is passed to `nohup bash`. And from this address, a script is loaded, of course obfuscated.
Naturally, no available LLM agrees to decrypt it. But Qwen didn’t mind.
Upon execution, the script gathers information from Chrome, Brave, Edge, Firefox, and others, extracting cookie files, autocomplete history, and system login data, collects crypto wallets like Electrum, Coinomi, Exodus, Atomic, Wasabi, Ledger Live, and others, gathers content from the “Notes” macOS app with attached media files, data from the Keychain (passwords), and also scans the desktop and documents for files of certain extensions. The collected data are archived and sent to a remote server with the IP address 217.119.139.117.
To ensure persistent access, the script creates hidden launch services (LaunchDaemons) with random names, making it difficult to detect. It can download and replace the legitimate Ledger Live application with a modified version.
Such is the Albanian virus)


I found a useful Chrome extension – SingleFile. It solves a problem like this – you need to share a browser page that is not public, for example, via iMessage or Telegram. This is not so trivial to do. For example, you can save a .mhtml file from the browser on your laptop, and send it, but only recipients on an iPhone cannot open it. Saving as a standard .html is also not an option, as images and styles are not preserved. Taking a screenshot only captures a small fragment. Installing an extension that creates a long, large PNG of the entire page – this PNG cannot be opened on an iPhone from Telegram at least, only the top renders. Printing to PDF is also not a solution – the result is very poor and highly dependent on the developers’ desire to make a print-friendly version.
SingleFile allows you to create a snapshot of a page from the browser, a regular .html, which can be opened anywhere, with embedded styles and images. But what is especially convenient, before exporting, you can remove anything you don’t want to share through the WebInspector, and it won’t appear in the final .html. The extension is open source on GitHub, and it doesn’t send anything anywhere. Apparently, if there was dynamic loading through JS on the page, it saves not the JS, but the result of the loading, and the JS is cut out.
In general, it’s convenient, a good thing, use it.
(I had an interview released on the internal portal today, and I needed to share it with my family in our family chat)
I finally released a book on #RecSys! It’s called Recommender Algorithms, where I’ve compiled over 50 recommendation algorithms with detailed mathematical derivations, thorough explanations, and code examples.
https://www.testmysearch.com/books/recommender-algorithms.html
It all started early this spring in Germany, when I attended an ACM conference and sketched out the first structure of the book while analyzing the talks from the RecSys track. And now, just six months later, it has come to life.
Why did I write it? Because neither online nor in print is there a single, accessible resource that deeply explores recommendation algorithms of various types and purposes. There are articles focused on small subsets, but collecting and systematizing approaches—from foundational methods to the very latest—seems to have never been done before. I don’t know if I succeeded, but I’d love to hear your feedback.
Please like & share!
P.S. Click at READ SAMPLE to see the first 40 pages. The table of contents is there as well.
https://www.testmysearch.com/books/recommender-algorithms.html
https://www.testmysearch.com/books/recommender-algorithms.html


Finally, I have released a book! It is called Recommender Algorithms — it contains more than 50 recommendation algorithms with mathematical explanations, detailed descriptions, and code examples.
It all started early in the spring in Germany, when I attended the ACM conference and made the first sketches of the book’s structure, analyzing reports on the RecSys stream. And now, six months later, the book has been published.
Why did it appear? Because there is no single, accessible source either online or in print where the recommendation algorithms of various types and purposes are thoroughly examined. There are articles focused on narrow aspects, but to collect and systematize the developments — from fundamental to the most recent — until now, it seems, no one has managed to do it for some reason. Maybe no one needed to. Suddenly, I found I needed to. I don’t know if I succeeded, but I am eager for your feedback.
Available on Amazon and Barnes and Noble. There is a Russian automatic translation (surprisingly, but very decent), but I do not know how to sell it yet.
https://www.testmysearch.com/books/recommender-algorithms.html?FB
(This is not my only book, but today — just about this one.)

Preparing a book for publication on Solr&Lucene. What do you think about publishing such a translation on Amazon? 🙂
The book is about algorithms and under-the-hood engineering. I haven’t seen books from this angle yet, maybe someone will find it interesting.



Microsoft has one very nasty thing with Outlook for MacOS, which for some reason nobody tries to fix. If you have a meeting in 30 minutes, Outlook reminds you with a popup showing the upcoming meetings, where it “highlights” these meetings. Well, in my case, there’s no secret here, I could even share my screen during that time. But it would be nice if such notifications didn’t appear while screen sharing, especially while recording, because screen sharing goes through Teams, which is part of the same package as Outlook.
But what’s worse is something else. If you try to CLOSE this notification window while screen sharing on MacOS (especially if the recording is on), it causes the whole Outlook with all the emails there to pop up. And there might be things there that the viewers shouldn’t see. That is, by _closing_ the window, you suddenly reveal the titles of email messages. Which is completely unexpected (well, until you step on these rakes, then it’s not unexpected anymore).

Bought myself an AI microphone that listens to everything around and provides summaries. Decided to test it once. With it, you can’t even watch reels with the mic turned off on your computer, because it tries to merge and summarize everything it hears 😉
“..The team methodically moved through complex comparisons, but unexpected phrases like ‘Watch the video back if you didn’t notice’ and ‘Don’t be a sucker’ created a quiet, almost poetic dissonance—as if the universe whispered ‘Let it be’ amid spreadsheets and sprint tickets….”
