Pure Acetone @pureacetone@qoto.org

PJHw4mf7KRW4KkjCG7sjmA1LUhkNBb5nep

https://bastyon.com/lenovotc?s=2049152b705c8219daa3960d9530c7bb0e43454af82857fb39e68dc43c37883f&ref=PDQmXtWJfd8f6fMtwaxzCuqvLpoN3KbS4o

«Удивляют люди, которые спрашивают:

- А где наши деньги? Растущие доходы? Приличные пенсии? Достойные пособия? Обещанное жилье?

Да вот же они - проходят мимо военными колоннами, проезжают танками и пролетают снарядами и ракетами с непредсказуемыми траекториями»

Между тем у очередного поколения отнимают шанс дожить свои дни в достатке, хотя бы относительном.

И опять повторяется гребаный советский цикл, когда с регулярностью в пару раз за поколение у населения изымаются - тем или иным путем - накопленные ресурсы и доходы.

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

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

Просто ничего не говорят и с нескольких фронтов готовятся усилить давно уже ведущуюся атаку на народные кошельки.

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

Чтобы с лихвой после выборов вернуть в казну то, что пока, из остатков приличий ссыпается мелкими крошками в кормушки.

Цикл, который, похоже, здесь не завершится никогда.
Андрей Никулин

Рубен Яп - Эволюция протоколов обеспечения приватности Firo: от Zerocoin до Spark - PeerTube (xy-space)
https://tube.xy-space.de/w/fNr2jUzcbYg9r5xWdQ6xoe

https://tube.xy-space.de/w/fNr2jUzcbYg9r5xWdQ6xoe

Bloom filters are probabilistic data structures designed to estimate whether something is in a set or absolutely not in a set. Yggdrasil nodes exchange them to share information about which parts of the network contain certain keys. We then use them to forward lookup requests, so the node that owns a key eventually responds with its tree coordinates

Так, для новачка **IPFS Desktop** або **IPFS Companion** – це саме те, що потрібно!

### Чому:
- **IPFS Desktop**: Дуже простий у використанні – його можна встановити як звичайну програму на Windows. Він надає графічний інтерфейс, де ти можеш завантажувати файли, переглядати стан свого вузла (якщо вирішиш запустити свій IPFS-нод), і робити основні дії без потреби у складних налаштуваннях. Це ідеальний вибір, якщо ти новачок і хочеш ознайомитися з IPFS у зрозумілій формі.

- **IPFS Companion**: Розширення для браузера дозволяє зручно переглядати контент з IPFS. Підійде, якщо тобі потрібно лише доступ до IPFS-даних у браузері, не налаштовуючи повноцінний вузол. Ідеально для простого доступу і перегляду IPFS-контенту.

**Перевага цих рішень**: Вони обидва зручні для початківців і не потребують знань командного рядка або складних технічних налаштувань.

Releases · ipfs/ipfs-desktop
https://github.com/ipfs/ipfs-desktop/releases

Releases · ipfs/ipfs-desktop
https://github.com/ipfs/ipfs-desktop/releases

Yes, the installation process for **Kubo** on Windows can be somewhat complex, especially for beginners. If you're looking for an easier way to interact with IPFS on Windows, here are some alternative methods:

### 1. **IPFS Desktop**
- **What It Is**: A user-friendly, graphical application for interacting with IPFS. It includes all the basic functionality without the need to use command-line tools.
- **Installation**: Download the latest version of IPFS Desktop from the [official GitHub page](https://github.com/ipfs/ipfs-desktop/releases).
- **Usage**: After installation, IPFS Desktop offers a simple interface for adding files, viewing your IPFS node status, and managing settings, making it a more accessible alternative to Kubo for many users.

### 2. **IPFS Companion (Browser Extension)**
- **What It Is**: IPFS Companion is a browser extension that allows you to interact with IPFS directly from your web browser.
- **Installation**: Available on the [Chrome Web Store](https://chrome.google.com/webstore) or [Mozilla Add-ons](https://addons.mozilla.org).
- **Usage**: Once installed, IPFS Companion can automatically redirect IPFS links and manage files without requiring a full IPFS node. This is a good option if you mainly want to browse IPFS content rather than host it.

### 3. **Web-Based IPFS Gateways**
- **What They Are**: If you only need to access IPFS content (like files or websites), you can use public gateways (e.g., `https://ipfs.io/ipfs/<CID>`).
- **Pros**: This is by far the simplest way to view IPFS content without any installation.
- **Cons**: You won’t be running your own node, so your IPFS interactions are limited to viewing content rather than contributing to the network.

These alternatives provide similar functionality to the Kubo client but simplify the process significantly, especially for users who are not comfortable with command-line tools or complex installations.

To install **Kubo** (the official IPFS implementation) on **Windows**, follow these steps and note the dependencies needed:

### Step 1: Install Dependencies
1. **Golang (Go)**: Kubo is written in Go, so it's helpful to have Go installed, though it’s not mandatory for using pre-built binaries. You can download and install Go from [the official Golang site](https://golang.org/dl/).
2. **Git (Optional)**: While not required for using Kubo binaries, Git is often useful for managing IPFS code and repositories. Download Git for Windows from [Git’s website](https://git-scm.com/download/win).

### Step 2: Download Kubo
1. Visit the [Kubo Releases page on GitHub](https://github.com/ipfs/kubo/releases).
2. Find the latest version and download the **Windows binary** (usually named `kubo_vX.X.X_windows-amd64.zip` for 64-bit systems).
3. Extract the downloaded `.zip` file to a convenient directory.

### Step 3: Add Kubo to System PATH
1. Go to the folder where you extracted Kubo and locate the `ipfs.exe` file.
2. Copy the folder path.
3. Open **System Properties** (right-click on “This PC” > Properties > Advanced System Settings).
4. Under the **Advanced** tab, click **Environment Variables**.
5. In the **System Variables** section, find and edit the **Path** variable.
6. Add the path to the folder containing `ipfs.exe`.
7. Click OK to save changes.

### Step 4: Initialize IPFS
1. Open **Command Prompt** or **PowerShell**.
2. Run the following command to initialize IPFS:
```bash
ipfs init
```
This creates an IPFS configuration file in your user directory (typically `~/.ipfs`).

### Step 5: Start the IPFS Daemon
1. In Command Prompt or PowerShell, start the IPFS node with:
```bash
ipfs daemon
```
This launches the IPFS node, allowing you to interact with the IPFS network.

### Step 6: Verify Installation
1. To confirm IPFS is working, you can run a test command like:
```bash
ipfs id
```
This should display information about your IPFS node, such as the node ID and addresses.

### Optional Tools and Utilities
- **IPFS Desktop**: A graphical interface for managing IPFS. Download it from the [IPFS Desktop GitHub](https://github.com/ipfs/ipfs-desktop) if you prefer a GUI.

Following these steps will set up Kubo on Windows, allowing you to participate in the IPFS network directly from your system.

Yes, for IPFS applications in Go, **Kubo** (previously known as go-IPFS) is indeed the best choice. Written in Golang, Kubo is the most widely used IPFS client and serves as the primary reference implementation. It is highly optimized for performance, scalability, and stability, which makes it ideal for larger, production-oriented applications and server-based environments.

Kubo's design benefits from Golang's efficiency in handling concurrency and networking, which is particularly useful for IPFS nodes that need to manage multiple connections and large datasets. This implementation also has the most extensive support for IPFS features, community tools, and network updates, ensuring it is frequently maintained and compatible with the broader IPFS ecosystem.

If your project is heavily backend-focused or requires consistent uptime and reliability, Kubo would be the preferred choice due to these performance and compatibility advantages. For Golang developers, it is a natural fit and continues to be the most robust option within the IPFS client landscape.

Here’s an overview of the main IPFS clients, including their release dates, development teams, and general reputations:

### 1. **Kubo (Formerly go-IPFS)**
- **Release Year**: 2015
- **Team**: Developed by **Protocol Labs**, the creators of the IPFS project.
- **Reputation**: Kubo (formerly known as go-IPFS) is the original and most popular IPFS client, with robust performance and high reliability. It is considered the standard for IPFS nodes and is widely used in production environments.
- **Rating**: Kubo is highly rated among developers for its stability and comprehensive feature set, though it can be more resource-intensive compared to other clients.

### 2. **js-IPFS**
- **Release Year**: Around 2017
- **Team**: Also developed by **Protocol Labs** with contributions from the open-source community.
- **Reputation**: js-IPFS is appreciated for its compatibility with web environments and lighter requirements. It is frequently used for in-browser applications that require IPFS access without a server-side setup.
- **Rating**: Known for flexibility, though it’s less performant for large-scale tasks due to the limitations of JavaScript in handling heavy network operations.

### 3. **Helia**
- **Release Year**: 2023
- **Team**: Built by **Protocol Labs** with a focus on modularity and scalability.
- **Reputation**: Helia is a newer TypeScript-based IPFS client designed to offer a more modular approach to IPFS, allowing developers to integrate IPFS functionality flexibly.
- **Rating**: Early feedback from the developer community is positive, especially among TypeScript users, but its adoption is still growing compared to Kubo and js-IPFS.

### Summary of Ratings and Community Feedback
- **Kubo** remains the go-to for most production needs, especially for server-based deployments.
- **js-IPFS** is best for web applications and in-browser use cases.
- **Helia** has promise in TypeScript/JavaScript environments but is still newer and gaining traction.

Each client is widely discussed and supported within the IPFS open-source community, and users typically select based on their project’s specific requirements and environment.

IPFS (InterPlanetary File System) clients allow users to interact with the IPFS decentralized file storage network. Key IPFS clients include **Kubo**, **js-IPFS**, and **go-IPFS**—each with its specific focus, language base, and use cases.

### 1. **Kubo**
- **Language**: Go
- **Primary Use**: Kubo is the reference implementation of IPFS and is the most widely used IPFS client. It’s optimized for the majority of IPFS network interactions and has a rich feature set.
- **Notable Features**: Kubo provides robust support for IPFS features like content routing, file sharing, and storage pinning. It is optimized for performance and stability, making it suitable for general use and production environments.
- **Use Cases**: Best suited for server environments, large-scale applications, and services that need reliable, high-performance access to IPFS.

### 2. **js-IPFS**
- **Language**: JavaScript
- **Primary Use**: Built for compatibility with browser environments, js-IPFS enables client-side IPFS interactions.
- **Notable Features**: This implementation is tailored for applications in which IPFS functionality is embedded directly into web apps, allowing for in-browser IPFS operations. It is less resource-intensive and ideal for lightweight applications but lacks some of the heavy-duty features of Kubo.
- **Use Cases**: js-IPFS is ideal for front-end applications and in-browser usage where users don’t need the full functionality of IPFS, like direct file sharing without a backend server.

### 3. **go-IPFS**
- **Language**: Go (similar to Kubo, as it was the original IPFS implementation)
- **Primary Use**: go-IPFS was the initial IPFS implementation and has now evolved into Kubo. While technically deprecated, it laid the foundation for IPFS functionality and still serves as a model for Kubo’s performance and structure.

### 4. **Other Clients**
- **IPFS Companion**: A browser extension that allows easy access to IPFS directly from the browser, connecting to local or remote IPFS nodes.
- **Helia**: A newer TypeScript-based IPFS implementation aiming to provide enhanced modularity and flexibility, potentially useful for advanced JavaScript/TypeScript developers.

Each of these clients has strengths tailored to specific environments. Kubo remains the go-to for general and server-based IPFS needs, while js-IPFS is excellent for integrating IPFS into web applications.

Navigating the Future: Unveiling Our Roadmap - Scala
https://scala.network/roadmap/

Releases · scala-network/scala-gui
https://github.com/scala-network/scala-gui/releases

Store Your Coins Easily Using Our Secure Wallets - Scala
https://scala.network/wallets/

Проф. Преображенский в X: «Украина сопротивляется - значит, она не жертва, заявил Шлосберг. Просто манифест розового интеллигентского идиотизма. Женщина, схваченная бандой насильников, исцарапала одному лицо, другому заехала коленом в пах - значит, она не жертва. Российская интеллигенция безнадёжна. https://t.co/LhtnWxeSHG» / X
https://x.com/prof_preobr/status/1856305767277633742