DEV Community: mibii

Hunting Vulnerable axios Versions Across Your Node.js Monorepo

mibii — Thu, 02 Apr 2026 10:08:20 +0000

When a dependency ships a bad version, your node_modules tree doesn't warn you. Here's a small PowerShell script that does.

The problem

Large Node.js projects accumulate dependencies fast. A monorepo with dozens of services can have hundreds of nested package.json and package-lock.json files, each potentially pinning a different version of a shared library.

When a specific version of a popular library — say, axios — turns out to carry a bug or a security regression, you need to know exactly where it's referenced, across every file, at a glance. Grepping by hand doesn't scale, and most dependency auditing tools only look at the top-level lockfile.

⚠️ Why these versions?
Versions 1.14.1 and 0.30.4 are the target of this scanner — known problematic releases that should be identified and upgraded as soon as possible.

The approach

The script is a two-phase scanner written in PowerShell. It's designed to be dropped anywhere in your repo and run with a single command — no dependencies, no config files.

Phase 1 recursively walks the directory tree from wherever the script lives, collecting all package.json and package-lock.json files:

$foundFiles = Get-ChildItem -Path $startPath -Recurse -File -ErrorAction SilentlyContinue |
    Where-Object { $targetFiles -contains $_.Name }

Phase 2 reads each file line by line, looking for the keyword axios. Every matching line is printed to the console with its line number, and the keyword is highlighted in red so you can spot it instantly.

for ($i = 0; $i -lt $lines.Count; $i++) {
    if ($lines[$i] -match [regex]::Escape($keyword)) {
        $hitList.Add([PSCustomObject]@{
            Line    = $i + 1
            Content = $lines[$i]
        })
    }
}

💡 Gotcha — reserved variable name
PowerShell's automatic variable $matches is populated by the -match operator itself. Using it as a collection causes a cryptic runtime error: "A hash table can only be added to another hash table."
The fix: name your collection $hitList and use List[PSCustomObject] instead of a plain array.

# WRONG — $matches is reserved by PowerShell
$matches = @()
$matches += [PSCustomObject]@{ ... }  # runtime error!

# CORRECT
$hitList = [System.Collections.Generic.List[PSCustomObject]]::new()
$hitList.Add([PSCustomObject]@{ ... })

The alarm system

Beyond general search, the script maintains a second collection — $alarmList — that fires only when a line contains one of the flagged version strings. This runs in the same loop, so there's zero extra I/O cost.

$dangerVersions = @("1.14.1", "0.30.4")

foreach ($ver in $dangerVersions) {
    if ($lines[$i] -match [regex]::Escape($ver)) {
        $alarmList.Add([PSCustomObject]@{
            Version   = $ver
            File      = $file.Name
            Directory = $file.DirectoryName  # full path to folder
            LineNum   = $i + 1
            Content   = $lines[$i].Trim()
        })
    }
}

After all files are scanned, the alarm block prints a consolidated summary at the very bottom — version found, filename, directory path, and the exact line — so there's no ambiguity about what needs updating:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!                                              !
!   ⚠️  ALARM — VULNERABLE VERSIONS DETECTED  ⚠️  !
!                                              !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  ▶ Version    : 0.30.4
  ▶ File       : package-lock.json
  ▶ Directory  : C:\projects\my-app\services\api
  ▶ Line #     : 1042
  ▶ Content    : "version": "0.30.4",
  ───────────────────────────────────────────────────

The console output also uses color: axios keyword in red, dangerous version numbers in yellow, file headers in magenta — making it easy to scan hundreds of lines at a glance.

Running the script

Save the file as axios-finder.ps1, place it anywhere inside your project root, then run:

.\axios-finder.ps1

If your execution policy blocks unsigned scripts:

powershell -ExecutionPolicy Bypass -File .\axios-finder.ps1

No Node.js, no npm, no extra modules required. It runs on any machine with PowerShell 5.1 or later — which means any modern Windows box, out of the box.

Full script

The complete script with colored output, per-file hit counts, version highlighting, and the alarm block is available on GitHub:

👉 https://github.com/mibii/axios-bad-version-finder

Found this useful? Buy me a coffee , Drop a ❤️ or leave a comment — happy to extend the script to support other libraries or output formats.

Prop Trading 2.0 (Trade-to-Earn)

mibii — Wed, 11 Mar 2026 23:20:15 +0000

Q-big-One trading core is an alternative to MetaTrader 4/5.

I developed my own trading core and called it Q-big-One.

Event Sourcing + WAL: Full audit trail. Instant crash recovery via event replay.
Full Source Control: Every line is yours. Customise risk, commissions, execution.
Cloud Native: Docker/Kubernetes ready. AWS, GCP, bare metal.
Multi-Asset: Crypto, Forex, CFD — all in one engine with per-symbol config.

Use Cases:

The Ultimate Sandbox

Every broker platform is just a sandbox until orders hit the LP. This engine gives you the exact same technology brokers use to "play" against traders. Understand the mechanics of B-Book, slippage, and stop-hunts by being the one who controls them.

Master the Game by Owning the Board

A-Book / Real Market Bridge

Connect the "Tick Feeder" module to your real Binance/Bybit account via API keys. The core now acts as a massive router. You trade on 100 internal accounts inside the core, and the core aggregates net exposure and hedges it on the real market.

Internal Virtual Volume → Real Liquidity

Self-Hosted "Personal Prop Firm"

Stop paying fees to prop firms for challenges. Spin up your own environment. Create unlimited accounts, run different bots, and act as the Liquidity Provider for your own strategies. Test execution, slippage, and spread widening in a controlled "Matrix" where you control the laws of physics.

Infinite AccountsCustom Risk RulesZero Fees

Sample use case Prop Trading 2.0 (Trade-to-Earn: (https://qbig.one/)

No loss money, No registration, No charge money. You enter the terminal, see a pool of funded accounts, and hit CLAIM.
The backend mints an anonymous JWT, binds it to your device, and hands you the keys. Strategy flopped? Hit RELEASE, return the account, grab another. Zero friction, zero commitment. Earn your first grade.

Аккаунт эволюционирует: 🔘 Bronze ➔ 🥈 Silver ➔ 👑 Proven Alpha.

Prop Firm offers no-charge options. Prop Firm provides capital (virtual) to everyone; if a trader is successful, they receive PROVEN_ALPHA status, A-Book Bridge begins mirroring it to the real market, and Prop Firm shares the profit with the trader.

Building Your Own PowerShell Security Auditor!

mibii — Sun, 01 Jun 2025 13:19:35 +0000

From Novice to Cyber Helper: Building Your Own PowerShell Security Auditor!

Hey fellow coding enthusiasts!

We all started our programming journey somewhere, and one of the best ways to learn is by building something practical that solves a real (even if small) problem. Today, I want to share the experience of developing a simple yet useful tool in PowerShell: a local system security auditor. This project perfectly demonstrates how you can combine system commands, process manipulation, and even create a graphical user interface (GUI) – all using PowerShell!
We'll go from an idea to an interactive application that not only highlights suspicious activity but also offers to take action.

Let's dive in!

Step 1: The Idea and First Drafts – What Do We Want to Check?
Initially, the task was simple: write a script to quickly assess certain security aspects of a local system. The key areas we decided to focus on were:
Network Activity: Which ports is our system listening on? Are there any non-standard ones or processes with suspiciously high PIDs (Process Identifiers)?
Process Integrity: Are all running processes digitally signed? Unsigned binaries can be a sign of trouble.
The first thought for network analysis was the good old netstat -ano. For checking signatures, the built-in Windows mechanism Get-AuthenticodeSignature.

Initial (simplified) idea

$netstatOutput = netstat -ano | findstr LISTENING

... some text parsing here ...

$processes = Get-Process
foreach ($proc in $processes) {
# ... signature check ...
}

This is a starting point. But we want to do it cooler and more "PowerShell-idiomatically"!
Step 2: The PowerShell Way – Objects Instead of Plain Text
Parsing the text output of netstat is a thankless and fragile task. PowerShell loves objects! And for network connections, there's a wonderful cmdlet: Get-NetTCPConnection.

✅ Key Insight: Instead of parsing strings, Get-NetTCPConnection -State Listen immediately gives us objects with convenient properties like LocalPort and OwningProcess (that very PID). This makes the code cleaner and more reliable.

A more "correct" approach

$listeningConnections = Get-NetTCPConnection -State Listen
foreach ($conn in $listeningConnections) {
$pid = $conn.OwningProcess
$port = $conn.LocalPort
# ... further analysis ...
}

Additionally, we decided it would be useful to see not just the PID for each listening port, but also the path to the process's executable. This is done using Get-Process -Id $pid | Select-Object Path, ProcessName.

Step 3: Graphical User Interface – Making It Pretty and Understandable

Outputting results to the console is fine, but a popup window with a report looks much more professional and user-friendly. This is where the magic of the .NET Framework, accessible directly from PowerShell, comes in!
✅ Key Insight: Add-Type -AssemblyName System.Windows.Forms opens up the entire world of Windows Forms to us. We can create forms, text boxes, buttons – everything needed for a simple GUI.
Add-Type -AssemblyName System.Windows.Forms
Add-Type -AssemblyName System.Drawing # For sizes, colors, etc.

function Show-ResultPopup {
    param ($text)
    $popup = New-Object Windows.Forms.Form
    $popup.Text = "System Audit Result"
    # ... configure sizes, controls (TextBox) ...
    $popup.ShowDialog() # Show the window modally
    $popup.Dispose()    # IMPORTANT: Release resources!
}

Don't forget .Dispose() for forms! This releases the resources used by GUI elements when they are no longer needed.

Step 4: Signature Check – Trust, but Verify

For checking the digital signatures of executable files, Get-AuthenticodeSignature -FilePath $path is our best friend. If the Status property of the result is not Valid, it's a reason for concern (or, as we found out, sometimes a peculiarity of UWP apps).

$signature = Get-AuthenticodeSignature -FilePath "C:\Path\To\File.exe"
if ($signature.Status -ne [System.Management.Automation.SignatureStatus]::Valid) {
    # Suspicious!
}

Step 5: Interactivity – Giving the User a Choice!

Simply showing a list of "suspicious" unsigned processes is half the battle. What if we gave the user the option to try and "kill" (terminate) them right there?
✅ Key Insight: Here we combine System.Windows.Forms.MessageBox to request confirmation from the user and Stop-Process to terminate the process.
Request Admin Rights: Terminating processes often requires administrator privileges. The script should check for this and, if possible, offer to restart with elevated rights.
Confirmation Dialog: For each "problematic" process, display a MessageBox with details (name, PID, path) and the question: "Terminate?".

$userChoice = [System.Windows.Forms.MessageBox]::Show($ownerForm, "Terminate process X?", "Confirmation", [System.Windows.Forms.MessageBoxButtons]::YesNo)
if ($userChoice -eq [System.Windows.Forms.DialogResult]::Yes) {
    Stop-Process -Id $processId -Force -ErrorAction SilentlyContinue
    # Log the result
}

Note the -Force for Stop-Process and error handling (at least -ErrorAction SilentlyContinue or a full try-catch).

Step 6: A Beginner's Headache – Encodings! 😵

During development, especially when we added non-English messages (Cyrillic in our original case) to MessageBox, we ran into a problem: instead of proper characters, we saw "mojibake" (Ð”Ð»Ñ etc.).
✅ Key Insight (and a common beginner mistake): This is an encoding issue with the .ps1 file. PowerShell expects a certain encoding (often UTF-8 with BOM), but the file might be saved in another (e.g., ANSI).
Solution: Always save your .ps1 files containing non-ASCII characters in UTF-8 with BOM (Byte Order Mark) encoding. Most code editors (VS Code, PowerShell ISE, Notepad++) allow you to do this.

What Did We End Up With?

We created a small but functional PowerShell script that:
Analyzes network listeners.
Checks the digital signatures of running processes.
Displays results in a user-friendly GUI.
Interactively offers the user to terminate processes with invalid signatures.

Considers the need for administrator privileges.

Lessons and Takeaways for Beginners:

Use PowerShell's Native Tools: Cmdlets that work with objects (Get-NetTCPConnection, Get-Process) are preferable to parsing text from external utilities.
Don't Be Afraid of .NET: PowerShell integrates beautifully with .NET, opening up vast possibilities (e.g., for GUI creation).
Handle Errors: try-catch blocks and proper use of -ErrorAction will make your script more robust.
Manage Resources: For GUI objects, don't forget Dispose().
Encodings – Your Friend (or Foe): Remember UTF-8 with BOM for files with international characters.
Iterative Development: Start small and gradually add functionality. Our script also went through several stages of improvement!

This project is an excellent example of how you can combine system administration, a bit of programming, and user interface creation with a powerful tool like PowerShell.
I hope this experience inspires you to create your own useful utilities! Experiment, learn, and share your successes.
Happy coding! 💻✨

Uber Taxi Idea for everything

mibii — Thu, 17 Apr 2025 12:48:59 +0000

Uber Taxi Idea for everything.
Do you have something to offer others, but still don't have your own website? Or you have a website or a page on a social network, but you need to increase the visibility of your offers.
The service https://infometka.com let your offers become more and more visible.
The idea of the service is to grow together, and not to create separate, disparate websites that each one has to promote separately to achieve visibility. Infometka on the map - it looks like your mini website on the Globe map. It will connect you with your customers (using a feedback form, links to your social networks, direct chat or bot)

Бесплатный стартовый веб-сайт, для потенциальных клиетов

mibii — Mon, 10 Mar 2025 07:48:10 +0000

В конкурентном мире фриланса, чтобы выделиться и создать лояльную клиентскую базу, требуется больше, чем просто качественное выполнение работы — это предложение реальной ценности с самого начала. Одна из эффективных стратегий — предоставить потенциальным клиентам бесплатный стартовый веб-сайт. Такой подход не только демонстрирует вашу приверженность их успеху, но и закладывает основу для будущего сотрудничества.

Вот как можно преподнести эту идею, чтобы привлечь клиентов, которым нужен сайт, но которые не знают, с чего начать:

Пример аргумента, который следует использовать, когда фрилансер обращается к потенциальным клиентам:

Возможно, вам нужен сайт, но вы не уверены, каким он должен быть. Это нормально, поэтому я сделаю для вас сайт — бесплатно — который просто станет отправной точкой, основой для дальнейшего совершенствования. Сайт, который вы сможете дальше развивать, с моей помощью или с помощью любого другого фрилансера, или даже самостоятельно.
Представьте, что вы получаете свой собственный сайт, который станет вашим собственным путем к новым знаниям и возможностям. Все начинается с желания что-то улучшить, с попыток узнать и понять — как это можно сделать? С помощью чего? Так вы узнаете новое, расширяете свой кругозор. К вам приходят новые идеи, открываются неожиданные перспективы.
Мы живем в то время, когда вопросы становятся важнее ответов. Возникновение вопросов порождает желание найти ответы, а это ведет к росту и развитию. Ваш сайт может стать катализатором этого процесса, помогая вам:

Лучше понять свой бизнес или проект
Найти новых клиентов и партнеров
Экспериментировать с новыми идеями
Учиться и развиваться в мире современных технологий.

Получив бесплатно первую версию сайта, вы, скорее всего, вернетесь ко мне за дальнейшими улучшениями или консультациями по мере развития ваших потребностей. В этот момент мы можем обсудить небольшое вознаграждение за мои постоянные услуги.
Не упустите шанс начать это захватывающее путешествие. Давайте создадим для вас базовый сайт, который станет основой вашего присутствия в Интернете. А затем вместе мы улучшим его, адаптируем к вашим растущим потребностям и целям. Помните, каждый великий проект начинается с маленького шага. Сделайте этот шаг сегодня — свяжитесь со мной, и давайте воплотим ваши идеи в реальность!"

Помогаю своим клиентам продвигать их новый веб-сайт

Вы работаете над веб-сайтом для своих клиентов? Вот дополнительный способ добавить ценность: как только сайт будет готов, предложите своему клиенту возможность разместить информацию о нем на https://infometka.com/. (это совершенно бесплатно). К этому моменту клиент начнет продвигать свой новый сайт и свой бизнес. (это веская причина — клиент не просто получает свой собственный новый сайт, но и начинает бесплатное продвижение)
Эта услуга позволяет любому человеку — будь то стационарный бизнес, например кафе, или предлагающий мобильные услуги, например такси или ремонт дома, — оказаться на карте. Таким образом, ваши клиенты начнут продвигать свой новый веб-сайт и бизнес, что даст им преимущество в охвате своей аудитории. Это беспроигрышный вариант, который может сделать ваше предложение еще более привлекательным.

Приняв этот подход, ориентированный на ценность, вы не только создаете доверие и взаимопонимание со своими клиентами, но и позиционируете себя как партнера в их долгосрочном успехе. Предложение бесплатного стартового сайта может привести к постоянной работе и рекомендациям, что делает его разумной стратегией на сегодняшнем рынке фриланса.

Удачи и счастливого фриланса!

The Most Honest Smart Contract: A Necessary Shift in Tokenization Draft

mibii — Tue, 11 Feb 2025 11:39:45 +0000

Why We Need a Truly Fair Smart Contract

Blockchain technology was meant to free financial systems from centralized control, but today’s token landscape tells a different story. Instead of decentralization, we see projects with hidden privileges, presales benefiting insiders, and distribution schemes designed to enrich a few at the expense of many.

We don’t need another blockchain—we need a smart contract that enforces fairness at the protocol level. A contract that ensures tokens are distributed openly, over time, and without any centralized control.

OpenZeppelin, the go-to library for smart contract templates, provides useful building blocks—but not moral safeguards. No existing template guarantees a fair, time-based distribution with no backdoors for the creator. That’s why this contract is necessary. It ensures that the token's value emerges from its broadest possible adoption, not from manipulation.

The Core Principles of the Most Honest Smart Contract

For a smart contract to be truly fair, it must adhere to the following principles:

Fixed Supply: The total number of tokens must be immutable from the moment of deployment.
Fair Distribution: should provide mechanisms to ensure broad and time-based token distribution.
No Special Preferences: The creator must have no special privileges, no reserved tokens, and no way to manipulate distribution.
No Post-Deployment Control: Once deployed, the contract must be self-executing, requiring no administrative intervention.
Time-Based Distribution: Tokens should be issued gradually over time to prevent early hoarding.
Open Access: Anyone should be able to claim tokens, ensuring the broadest possible distribution.

Why OpenZeppelin Falls Short

OpenZeppelin’s templates are designed for flexibility, not for enforcing fairness. Here’s why they don’t solve the problem:

No Built-in Fair Distribution: OpenZeppelin does not provide mechanisms to ensure broad and time-based token distribution.
These features reflect the industry’s priorities—control, not fairness. That’s why this contract is different. It isn’t just code; it’s a commitment to the principles that blockchain was meant to uphold.

Lessons from Bitcoin: Why Fairness Creates Value

Bitcoin is the ultimate proof that fairness leads to resilience. Its success was not driven by insider allocations or liquidity tricks—it thrived because its creator disappeared, leaving behind an immutable system.

This contract follows the same logic:

No Founder Control: The creator has no special privileges or allocation rights.
No Presale or Private Investors: Everyone starts on equal footing.
Automated, Transparent Distribution: Tokens are allocated based on a predictable and open mechanism, not hidden deals.
This is not just a technical challenge but a moral imperative. Let us build systems that future generations will recognize as fair—systems written not in ink, but in code.

The most honest token should be distributed freely, ensuring equitable access for all. Only through wide-reaching, fair distribution can a token acquire intrinsic value.

In essence, the ideal model resembles testnet faucets—dispensing tokens for testing and development—but with two critical distinctions: a strict cap on total supply and a carefully designed issuance mechanism. This approach ensures fairness, decentralization, and grassroots adoption.

Lets start this journey !

Let's return the words "decentralization" and "blockchain" to their true high meaning. And let's start creating something that, after its creation, works independently even from its creator. Fairest and Most Honest Token Smart Contract Project

Fairest and Most Honest Token Smart Contract

mibii — Wed, 05 Feb 2025 11:02:06 +0000

Lets start this journey !

Let's return the words decentralization and blockchain to their true high meaning.
And let's start creating something that, after its creation, works independently even from its creator.

https://most-honest-token.gitbook.io/honest-token

Develop THE MOST HONEST TOKEN, founded on fixed token emission and the fairest distribution algorithm imaginable.

Token Principles:

No presale, ICO, IDO, or private sale.

No allocations for the creator, developers, or investors.

No hidden reserves or special privileges for any address.

Distribution should be free, requiring only network gas fees.

No post-deployment control: contract is immutable once deployed.

Open-source and verifiable by anyone.

https://explorer.gitcoin.co/#/projects/0xc6ba6f3ab8448f15ba06aeec26fa65abef21f6356c940164f9d7b7673702e524

Podcast - Code Beyond the Hype - "The Most Honest Token"

mibii — Tue, 04 Feb 2025 07:31:59 +0000

Episode Description:

In today’s crypto landscape, we’re bombarded with flashy schemes promising quick riches. From “tap-to-earn” apps where users click pictures for tokens to meme coins hyped on social media, it’s easy to get swept up in the hype. But beneath the surface lies a troubling truth: most of these projects are designed to enrich their creators at the expense of unsuspecting participants.

In this episode, we dive deep into the mechanics of dishonest token distribution models—like tap-to-earn scams and meme coin presales—and ask why no one has yet created a truly honest token. What if we could design a system that distributes tokens fairly, without hidden privileges for developers? Could a decentralized faucet-like mechanism replace exploitative practices?

We’ll also clarify the difference between tokens and stablecoins, explore how trust is built (or broken) in blockchain systems, and discuss why Bitcoin remains a benchmark for honesty despite its imperfections. Join us as we imagine what a truly fair token might look like—and whether humanity is ready for it.

We start this Project

here is the link for detail description

https://most-honest-token.gitbook.io/honest-token

All other podcast - will be here as well:

https://infometka.com/podcast-cbh

Podcast Title: "Code Beyond the Hype: Mastering Backend, Web3, and the Art of Focus"

mibii — Mon, 03 Feb 2025 09:52:26 +0000

Podcast Title: "Code Beyond the Hype: Mastering Backend, Web3, and the Art of Focus"

https://infometka.com/podcast-cbh

Podcast Description:
In a world drowning in tech trends, frameworks, and buzzwords, how do you cut through the noise and focus on what truly matters in programming? Welcome to Code Beyond the Hype , the podcast that helps developers—from beginners to seasoned pros—navigate the ever-evolving landscape of software development with clarity and purpose.

Hosted by Alex, your skeptical yet curious co-host, and Jamie, a seasoned expert with experience spanning traditional web development to the cutting-edge world of Web3, this show dives deep into the skills, tools, and mindsets that actually move the needle. Whether you're building scalable backends, exploring decentralized systems, or just trying to figure out where to start, we’ve got you covered.

In this episode, we tackle the big questions: Why is the backend the heart of any system? How do you choose the right tools for your stack without getting overwhelmed? What makes Web3 so revolutionary—and how can you dive in safely? Plus, we share actionable advice on avoiding distractions, leveraging AI, and staying laser-focused on high-impact work.

Tune in for candid conversations, practical tips, and a healthy dose of skepticism about the latest "shiny object" syndrome in tech. Whether you’re a JavaScript coder mastering Express.js, a Python enthusiast diving into Flask, or a Web3 explorer learning Solidity and Hardhat, this episode will give you the clarity and confidence to take your skills to the next level.

Subscribe now and join us as we decode the art of programming—one concept at a time.

OpenPeer vs LocalCryptos

mibii — Sun, 19 Jan 2025 06:30:41 +0000

LocalCryptos - был интересный и инновационный сервис для P2P торговли криптовалютами, который закрылся в октябре 2022 года после 5 лет работы3.
LocalCryptos воплощал многие идеальные черты P2P криптовалютных платформ:

Самохранение (self-custody): Пользователи полностью контролировали свои средства через веб-кошелек.
Децентрализованный эскроу: Использовались смарт-контракты Ethereum вместо посредников для безопасных сделок.
Криптография в браузере: Позволяла обычным пользователям торговать без установки дополнительного ПО.
Мультивалютность: Поддерживались Bitcoin, Ethereum и другие криптовалюты.
Отсутствие KYC: Не требовалась обязательная верификация личности.

Причины закрытия проекта не совсем ясны. Команда упомянула "внутренние и внешние факторы", которые помешали полностью реализовать их видение. Возможно, сыграли роль регуляторное давление и конкуренция с более крупными платформами.
Несмотря на закрытие, LocalCryptos оставил важное наследие в сфере P2P криптоторговли. Многие современные платформы, такие как Binance P2P, HODL HODL и Paxful4, переняли некоторые из его инновационных подходов к безопасности и децентрализации.
Для тех, кто ищет похожие сервисы сегодня, можно рассмотреть платформы вроде OpenPeer5, которые также фокусируются на самохранении и P2P-торговле без KYC.

https://openpeer.xyz/

OpenPeer
OpenPeer https://app.openpeer.xyz/ - это децентрализованная P2P платформа для обмена криптовалют, которая стремится обеспечить безопасные и анонимные сделки без необходимости доверять третьей стороне.
Основные характеристики:
Не требует KYC
Использует мультиподписные транзакции для обеспечения безопасности
Поддерживает Bitcoin и некоторые другие криптовалюты
Предлагает встроенный чат для общения между пользователями
Имеет систему репутации для пользователей

Сравнение OpenPeer и LocalCryptos

Характеристика OpenPeer LocalCryptos
Тип платформы Децентрализованная P2P Децентрализованная P2P
Криптовалюты Bitcoin и некоторые альткоины Ethereum, Bitcoin, Litecoin, Dash, Bitcoin Cash
KYC Не требуется Не требуется
Механизм безопасности Мультиподписные транзакции Смарт-контракты (для Ethereum) и скрипты (для Bitcoin)
Кошелек Самохранение Самохранение
Веб-интерфейс Да Да
Встроенный чат Да Да
Система репутации Да Да
Статус Активен Закрыт (с октября 2022)

Что касается доверия к OpenPeer, платформа использует проверенные криптографические методы для обеспечения безопасности сделок, что делает ее потенциально надежной. Однако, как и с любым новым сервисом, следует проявлять осторожность и начинать с небольших сумм.
OpenPeer во многом похож на LocalCryptos, особенно в плане децентрализации и отсутствия KYC.

Однако есть некоторые отличия:

LocalCryptos использовал смарт-контракты Ethereum, что позволяло поддерживать более широкий спектр криптовалют.
OpenPeer фокусируется на Bitcoin и использует мультиподписные транзакции, что может обеспечивать дополнительную безопасность для BTC-сделок.
LocalCryptos имел более длительную историю и, соответственно, большее доверие пользователей.
В целом, OpenPeer выглядит многообещающе как преемник идей LocalCryptos, но ему еще предстоит доказать свою надежность и эффективность в долгосрочной перспективе.

Create your own booking form in a minutes

mibii — Sun, 12 Jan 2025 00:44:44 +0000

You can stick a free ad on the globe, make an announcement, make your offer noticeable — you can do this with the help of the “Infometka” service.

Each stick has an interactive form. It is integrates with your Telegram. Get instant requests and bookings requests right in your Telegram app!

How to create — click anywhere on the map, click on the point and fill out the form.

Then fill a simple form

Almost done , finaly to activate your “Infometka” click /Activate in the Telegram bot https://t.me/infometka_bot

Done!

samples:
https://infometka.com/phuket-yacht-charter
https://infometka.com/taxi_hapdeok
https://infometka.com/vancouver-taxi
https://infometka.com/pattaya-taxi

npm error 'node' is not recognized as an internal or external command

mibii — Thu, 02 Jan 2025 05:57:41 +0000

npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node install.mjs
npm error 'node' is not recognized as an internal or external command,
npm error operable program or batch file.

Solving the Puppeteer Installation Issue in Node.js: A Troubleshooting Journey

As developers, we often face challenges while working with different tools and libraries. One of the issues I encountered recently was with installing puppeteer, the popular browser automation library, in a Node.js environment. The error message I received left me scratching my head, and I want to share my troubleshooting journey with you. Hopefully, this post will save you some valuable time if you find yourself in a similar situation.

The Problem: Unusual Node.js Error During Puppeteer Installation
While installing puppeteer, I encountered a strange error that read:

npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node install.mjs
npm error 'node' is not recognized as an internal or external command,
npm error operable program or batch file.

At first glance, this looked like a typical issue with the Node.js installation, and I assumed something was wrong with my setup. However, this was very misleading because all other dependencies and my Node.js app worked fine without any issues. The error was solely related to the installation of puppeteer. So why would Node.js suddenly complain about the node command?

Step 1: Investigating the Root Cause
Given that the error suggested Node.js wasn't recognized, I started by verifying that the Node.js binary was properly installed and accessible from my command line. I ran the following command:

node -v

The response was the expected output, confirming that Node.js was installed and working correctly. This made the error message even more perplexing, as it directly contradicted the results of this simple test.

I also checked the system's PATH environment variable, which should ensure the correct location of the Node.js executable. To my surprise, this didn't resolve the issue either. The error persisted, which led me to believe that the problem wasn't with the PATH configuration but something more specific to how puppeteer handles its installation scripts.

After a half day of trouble shooooot..........

I then realized that the issue might be specific to the way puppeteer handles its installation scripts. It turns out that puppeteer uses a script (install.mjs) to install its necessary components, and this is where things were failing.

Step 2: Trying Puppeteer-Core as a Solution

At this point, after much frustration and multiple attempts at fixing the issue, I stumbled upon a suggestion to use puppeteer-core. This is essentially a lighter version of puppeteer that doesn’t come with a bundled Chromium browser, and it’s designed for environments where you want to provide your own Chromium or Chrome installation.

The command I used was:

npm install puppeteer-core

Surprisingly, this worked without any errors, and the installation completed successfully. The issue was that puppeteer was trying to download and install Chromium automatically, which was likely conflicting with my system’s environment or some other configuration.

Step 3: Conclusion – The Lesson Learned

This experience was frustrating because of the misleading error message. Instead of an informative message related to the issue, I received a generic node not recognized error, which made it seem like a problem with Node.js itself. In reality, the issue was with the specific way puppeteer was being installed, especially when it attempts to download and set up its Chromium dependency.

The solution turned out to be using puppeteer-core instead of the full puppeteer package. This version of the library doesn’t require the automatic Chromium installation, and thus bypasses the issue entirely.

Why This Is Important for Developers

This kind of experience is a great reminder that error messages in Node.js (and any other environment) can sometimes be misleading. A vague or generic message might not be directly related to the root cause. When troubleshooting, it’s essential to think critically about the context of the problem, experiment with different approaches, and don’t hesitate to search for alternative solutions.

This issue with puppeteer also highlights the importance of understanding the libraries and dependencies you’re using. By being aware of the differences between puppeteer and puppeteer-core, you can make more informed decisions based on your environment and needs.

Final Thoughts

If you’re facing this same issue with nodejs, I hope this post helps you resolve it faster than I did. The key takeaway is that not all installation issues are related to the basics, such as Node.js installation itself.

Feel free to share your own experiences and thoughts in the comments below. Have you faced any similar situations where error messages didn’t match the actual problem? Let’s discuss!