Instagram advertises accounts to teenagers with a girl strongly resembling a young Lena Katina from t.A.T.u 😉


Instagram advertises accounts to teenagers with a girl strongly resembling a young Lena Katina from t.A.T.u 😉


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.














My apples are almost ripe #pictured


Something crazy is happening in our village. First, the owner of two huskies posts on nextdoor that they ran away from home and asks people to notify him if anyone sees them, warning that they are skittish. Then, about two hours later, the chihuahua owner posts that the escaped huskies killed his dog and also a neighbor’s chicken. The husky owner deleted his first post. Everyone in the village is grabbing their popcorn. It’s sad about the dogs. I’m always afraid that Yuki will run away like that, he’s also a fighter and fiercely hates all dogs in the world except himself.


“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)

Incidentally, in my Tesla, there’s a very clever system for identifying the driver. If I enter the car first but sit in the passenger seat, placing my phone immediately in the central console for charging, and then Nadia enters second but sits in the driver’s seat and also places her phone there, her profile is selected automatically because she’s the driver, even though both phones are on charge under the central console.
So, there are two possibilities: either there is an antenna which can precisely detect that a phone has crossed the driver’s door rather than entering the car in any other way, or there is a camera focused on the driver. In any case, it’s very reassuring that it “just works”.