#ipfs

#discord IS LITERALLY THE PROBLEM!

It's worse than any #IRC, #Mumble or even the old #TeamSpeak & #Skype for that matter.
It combines the disadvantages of #Forum, #paywalled #documentation, #chat and #voicechat with 0 redeeming qualities (unlike #Zulip & Mumble & #XMPP+#OMEMO) it's just an #InformationBlackhole!

I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.

And I'd rather subscribe to the #LKML and see my inbox getting hosed than using any shitty #SaaS!

Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.

I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools

Public Chat? IRC!
Group Voicechat? Mumble.
#Documentation? #mkDocs-material.
1:1 Chats? XMPP+OMEMO.
E2EE Group Chats? #deltaChat.
E2EE Calls? #WebCall.
Filehosting? #IPFS, #BitTorrent, oshi.at, etc. ...
…

Check @alternativeto and @european_alternatives for options.

Если важна доступность, можно посмотреть в сторону #IPFS. А через какую площадку будут распространяться ссылки на видосы, хранящиеся в IPFS, не имеет значения, это может быть и Mastodon. Но и это не отменяет необходимости иметь копию у себя, хотя если видосы будут популярны, хранение может поддерживаться сетью само.

Если кто страдает от того, что #ipfs #kubo жрёт слишком много памяти, можно определить две переменные окружения: GOMEMLINIT и GOMAXPROC. Мне удалось таким образом загнать ipfs в рамки одного гигабайта.

Видимо тут go как джава:
— Сколько тебе нужно памяти?
— Да!

Видео "Пробуем запустить IPFS и опубликовать в нем простой сайт" от Sergei Udalov демонстрирует процесс установки и использования IPFS (InterPlanetary File System) для хостинга веб-страниц.

Основные моменты:
Установка IPFS: скачивание и настройка программного обеспечения.
Запуск локального узла: проверка работы и подключение к сети.
Публикация сайта: добавление HTML-файлов в IPFS, получение CID (Content Identifier) и доступ к сайту через шлюз.
Проверка доступности: открытие сайта через публичные IPFS-шлюзы.
Заключение: плюсы и минусы использования децентрализованного хостинга.
Видео подойдет тем, кто хочет разобраться в основах IPFS и попробовать его на практике.
Хэштеги:
#IPFS #Decentralization #Web3 #Blockchain #P2P #SelfHosting #OpenSource #DWeb #InterPlanetaryFileSystem #TechTutorial
Библиография:
IPFS Documentation – https://docs.ipfs.tech
IPFS GitHub Repository – https://github.com/ipfs/go-ipfs
"IPFS Explained: The New Decentralized Web" – YouTube, Computerphile (https://youtu.be/5Uj6uR3fp-U)
"The Future of Decentralized Storage with IPFS" – Medium article (https://medium.com/@ipfs)
Protocol Labs: Research on IPFS – https://protocol.ai
Если нужно что-то дополнить или изменить, дай знать.

Пробуем запустить IPFS и опубликовать в нем простой сайт → (https://www.youtube.com/watch?v=O2bIdH2vPZw)
#Sergei_Udalov → (https://www.youtube.com/@SergeiUdalov)
@youtubabot: 720p

IPFS Desktop v0.42.0
=> https://docs.ipfs.io/install/ipfs-desktop/
An unobtrusive and user-friendly desktop application for IPFS on Windows, Mac and Linux.
A desktop client for IPFS.
You don't need the command line to run an IPFS node. Just install IPFS Desktop and have all the power of IPFS in your hands. Powered by Web UI.
IPFS Desktop allows you to run your IPFS Node on your machine without having to bother with command line tools. With it, you have the power of Web UI on tip of your hands plus a handful of shortcuts you can find on settings.
Changelog:
=> https://github.com/ipfs/ipfs-desktop/releases/tag/v0.42.0
#IPFS

Hm,
somehow the google „AI“ says that Deno got special IPFS CIDs.
That sounds terrible not interoperable.

I suggest that #IPFS does not follow googles proposal and that a CID is the same in every language !!! (!)
@deno_land

Quiet v4.0.3
=> https://tryquiet.org/
While apps like Slack, Discord, and Signal use central servers, Quiet syncs messages directly between a team’s devices, over Tor, with no server required.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%404.0.3
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%404.0.3
#Tor #IPFS

### Search in the IPFS Network: A Detailed Overview
#### 1. Understanding the InterPlanetary File System (IPFS)
The InterPlanetary File System (IPFS) is a decentralized and distributed file storage system that aims to connect all computing devices through a single file system. Unlike traditional file storage methods, IPFS uses a unique approach to storing and accessing files, directories, websites, and data. The key difference is the shift from centralized systems, where information is hosted on specific servers, to a distributed network where content is spread across multiple nodes. This decentralization significantly improves fault tolerance and reduces censorship risks.
A fundamental paradigm shift in addressing is a key feature of IPFS. Traditional systems use location-based addressing (HTTP), where finding a file requires knowing its exact location. If a server is unavailable or blocked, the content becomes inaccessible. In contrast, IPFS uses content-based addressing, meaning that files are accessed not by their location but by their unique identifier. This allows content to be retrieved from any node that stores it, making the system more reliable. Similar principles of decentralization and peer-to-peer networking also form the foundation of blockchain technology. While blockchain focuses on ledger immutability, IPFS ensures content integrity and availability. This complementary nature makes them powerful tools for developing decentralized applications.
#### 2. Peer-to-Peer File Sharing
IPFS operates as a peer-to-peer network that enables direct file sharing between users without relying on central servers. Any user in the network can provide a file by its content address, and other participants can request and retrieve it from any node that stores it. The active role of users as both consumers and potential content hosts distinguishes IPFS from traditional client-server models, promoting a more collaborative and distributed internet.
In the client-server model, users primarily download data from servers. In IPFS, a user downloading content can also temporarily become a host for that content, helping to distribute it more efficiently among others.
#### 3. Content Addressing vs. Location Addressing
The traditional web (HTTP) uses location-based addressing (URLs) to access content from specific servers. IPFS employs content-based addressing, where files are identified using a unique Content Identifier (CID) derived from their content. The shift to content-based addressing ensures that the same content always has the same identifier, regardless of its location. This is crucial for data integrity and efficient search.
If, in a traditional system, a file is duplicated across multiple servers, each copy has a different URL. In IPFS, all copies of the same file share the same CID, allowing the network to efficiently locate and retrieve any instance.
For a clearer comparison, the following table contrasts HTTP and IPFS:
| Feature | HTTP | IPFS |
|---------|------|------|
| Addressing | Location-based (URLs) | Content-based (CIDs) |
| Storage | Centralized servers | Distributed network of nodes |
| Content Identity | Depends on server location | Independent of location, based on content hash |
| Resilience | Vulnerable to server failures and censorship | High resilience due to distributed nature |
#### 4. Content Addressing with Content Identifiers (CID)
When content (files, directories, etc.) is added to IPFS, it is broken into smaller blocks. Each block's content is cryptographically hashed to generate a unique fingerprint. This hash, along with metadata about encoding and the hashing algorithm, forms the Content Identifier (CID). Cryptographic hashing ensures that even a single-bit change in content results in a completely different CID, maintaining content integrity and verifiability.
If a user requests a file by its CID, the IPFS client can re-hash the received data and compare it with the requested CID. If they match, the user can be certain that the data was not tampered with during transmission or storage.
#### 5. CID Structure
CIDs consist of different components, including:
- **Multicodec:** Identifies the content format.
- **Multihash:** Contains the cryptographic hash of the content and information about the hashing algorithm used.
- **Multibase:** Defines the encoding scheme for text representation (e.g., base58, base32).
- **Version:** Indicates the CID format version (v0 or v1).
The self-descriptive nature of CIDs, due to the inclusion of multicodec and multihash information, enables IPFS to handle various data formats and hashing algorithms consistently, supporting scalability. As new data formats or more secure hashing algorithms emerge, IPFS can integrate them without breaking compatibility, as the CID itself contains the necessary interpretation information.
For better understanding, the table below illustrates the main components of CID:
| Component | Description | Example (conceptual) |
|-----------|-------------|------------------|
| Version | Indicates CID format version | v0, v1 |
| Multicodec | Defines data format (e.g., raw, directory, git commit) | raw, dag-pb |
| Multihash | Contains the hash function used and the cryptographic hash | sha2-256, Qm... |
| Multibase | Encoding used for CID string representation | b58 |
#### 6. CID Versions (v0 and v1)
IPFS has two main CID versions: v0 and v1. CIDv0 is the original format that uses a multihash encoded in base58 and always starts with "Qm". CIDv1 is a newer format designed to ensure backward compatibility and includes a multibase prefix and a codec identifier. New projects are generally advised to use CIDv1 for future-proofing. The evolution of CID formats reflects the ongoing development and improvement of the IPFS protocol to enhance flexibility and compatibility.
#### 7. CIDs as Unique Identifiers
The same content added to different IPFS nodes using identical settings will always generate the same CID. Any difference in content, even in metadata, will result in a different CID. This deterministic relationship between content and its CID ensures content deduplication across the network, saving storage space and bandwidth.
If multiple users upload the same file, IPFS recognizes it by its identical CID and stores only one copy of the data, referenced by all users.
#### 8. Content Discovery Mechanisms in IPFS
IPFS uses a **Distributed Hash Table (DHT)** to locate peers storing specific content identified by its CID. The DHT is a decentralized system that maps CIDs to IP addresses, acting as a distributed directory that enables nodes to find content locations without relying on a central authority.
When a node requests content by its CID, it queries the DHT to find which peers in the network advertise having the relevant data.
#### 9. Peer-to-Peer Exchange Protocol (Bitswap)
Bitswap is a message-based protocol used by IPFS nodes to exchange data blocks. A node looking for specific content can query its connected peers to check if they have the requested CID without needing to repeatedly search the DHT.
Bitswap optimizes data transmission by allowing nodes to request and exchange blocks directly with peers who have them, leading to faster content retrieval.
#### 10. IPFS Content Routing System
Content routing in IPFS is the process of determining where to find a specific CID in the network. Besides **Kademlia DHT** and **Bitswap**, other mechanisms can be used, such as **mDNS** (for local network discovery) and **delegated routing via HTTP**. A multi-faceted approach to content routing improves reliability and efficiency in different network environments.
#### 11. Accessing IPFS Content
Users can set up an IPFS client (node) on their devices to interact directly with the IPFS network. This allows them to upload, download, and share files directly with other IPFS peers. Running a local IPFS node ensures full participation in the IPFS network.
Some web browsers, such as **Brave**, offer built-in IPFS support, enabling users to access IPFS content directly via `ipfs://` URLs.
**IPFS Gateways** are centralized services that allow users to access IPFS-stored content using standard HTTP/HTTPS protocols through traditional web browsers. Gateways translate IPFS CIDs to retrieve the corresponding content and serve it over HTTP.
#### 12. Implications and Considerations
- **Decentralized content discovery** improves **resilience against censorship** and **single points of failure**.
- **Increased data availability** since content can be fetched from multiple nodes.
- **Potential acceleration of content delivery** through peer-to-peer sharing.
- **Security concerns**, as IPFS can be exploited for hosting phishing sites and malicious content.
Despite its advantages, IPFS requires strategies for **detecting and mitigating harmful content** while preserving its decentralized ethos.
#IPFS #Decentralization #ContentAddressing #Web3 #Blockchain

I wonder if the #fediverse could utilize #IPFS to reduce the number of instances throwing around media files like crazy.

Is anyone already sharing their blog through #IPFS ?

I'd like to start and I'm thinking of just using #tiddlywiki maintained/updated locally via tiddly desktop.

Is anyone willing to share how they're doing it?

IPFS Companion v3.2.0
=> https://docs.ipfs.tech/install/ipfs-companion/
IPFS Companion harnesses the power of your locally running IPFS node (either through the IPFS Desktop (https://docs.ipfs.io/install/ipfs-desktop/) app or the command-line daemon (https://docs.ipfs.io/install/command-line/)) directly inside your favorite Chromium-based or Firefox browser, enabling support for ipfs:// addresses (https://docs.ipfs.io/how-to/address-ipfs-on-web/#native-urls), redirecting content-addressed websites and file paths to your local Gateway (https://docs.ipfs.io/concepts/glossary/#gateway), easy IPFS file import and sharing, and more.
Changelog:
=> https://github.com/ipfs/ipfs-companion/releases/tag/v3.2.0
#IPFS

Quiet v4.0.2
=> https://tryquiet.org/
While apps like Slack, Discord, and Signal use central servers, Quiet syncs messages directly between a team’s devices, over Tor, with no server required.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%404.0.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%404.0.1
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%404.0.2
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%404.0.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%404.0.1
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%404.0.2
#Tor #IPFS

My esteemed followers, you have posted a total of 375,809 statuses to the #fediverse. 22% of you have posted in the last 24h. You are a chatty bunch! ;-)

Check out my new #sideproject: *fedi-followers*. A privacy-friendly fediverse #followers explorer as #localonly #staticwebapp, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

https://fedi--followers-data0-one.ipns.dweb.link/

#decentralization #mastodev #esmodules #importmaps #nobuild #indexeddb #preact

I've built a thing.

Sometimes my follower count seemingly fluctuates at random. To understand why, I dug into the #MastodonAPI and eventually created "fedi-followers":

A privacy-friendly #fediverse #followers explorer as local-only static web app, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

https://fedi--followers-data0-one.ipns.dweb.link/

#mastodev #javascript #webapp #staticwebapp #nobuild #esmodules #importmaps #nativemodules #indexeddb #preact #htm

@goldfishlaser thanks! I am always on the lookout for any decentralizing technologies.

This #meshtastic looks good, but I'm primarily interested in such platforms or networks which can handle #tcpip or #ipfs .

Agregore 2.8.2 - Font Based Syntax Highlighting
=> https://agregore.mauve.moe
A minimal web browser for the distributed web
- Enable people to make and use local first apps using the web
- Be minimal (fewer built-in features, leave more to the OS)
- Be open to anything p2p / decentralized / local-first
- Rely on web extensions for extra functionality
- Work with mesh networks / Bluetooth Low Energy networks
Changelog:
=> https://github.com/AgregoreWeb/agregore-browser/releases/tag/v2.8.2
#IPFS #IPLD #Hypercore #Gemini #SSB #bittorrent

Вот хэштеги, разбитые по конкретным программам из сборника **"Anticensor File Pack Black Day"**:
### ** Безопасные мессенджеры**
- **Jami** – #Jami #P2PMessenger #Decentralized #Privacy #SecureMessaging
- **Element (Matrix)** – #Matrix #ElementChat #EncryptedMessaging #PrivacyChat #Federation
- **Gajim (XMPP)** – #XMPP #Jabber #EncryptedChat #SelfHosted #PrivateChat
- **Tox** – #ToxMessenger #P2PChat #NoCensorship #SecureChat #AnonComms
- **Briar** – #BriarApp #MeshNetwork #DarknetChat #OfflineMessaging
### ** Анонимный веб-серфинг**
- **Tor Browser** – #Tor #OnionRouting #DarkWeb #PrivacyBrowser #NoTracking
- **Mozilla Fennec** – #Fennec #FirefoxMod #PrivacyFirst #NoAds #OpenSource
### ** Децентрализованные файлы и сети**
- **IPFS Desktop** – #IPFS #DecentralizedWeb #Web3 #NoCensorship #FileSharing
- **IPFS Binaries** – #IPFSNetwork #P2PFiles #InterPlanetaryFileSystem
### ** Терминальные утилиты**
- **Termux** – #Termux #AndroidTerminal #LinuxOnAndroid #HackingTools
- **Termux API** – #TermuxAPI #Automation #ShellScripting #CLI
### ** Шифрование и безопасность**
- **PGP (Pretty Good Privacy)** – #PGP #EmailEncryption #PrivacyTools #CyberSecurity
- **DeltaChat (PGP Mail Client)** – #DeltaChat #EmailEncryption #PGPChat #SecureMail
### ** Антицензура и обход блокировок**
- **Antizapret Proxy** – #Antizapret #Proxy #BypassCensorship #FreeInternet
- **Bol-Van DPI Bypass** – #DeepPacketInspection #DPIBypass #InternetFreedom
Эти хэштеги помогут привлечь внимание нужной аудитории: пользователей, активистов, журналистов, разработчиков и защитников цифровых свобод.

Вот список подходящих хэштегов для этой темы:
### **Основные:**
#Privacy #Security #Anonimity #Encryption #CyberSecurity #Darknet #P2P #IPFS
### **Для пользователей:**
#Whistleblowers #Activists #Journalists #Hacktivism #PrivacyTools #SafeCommunication
### **Для технической аудитории:**
#Monero #PGP #Tor #Jabber #XMPP #DPIBypass #Proxy #OpenSource
### **Против цензуры:**
#NoCensorship #InternetFreedom #Antizapret #BypassCensorship
Эти хэштеги помогут привлечь внимание тех, кому важны анонимность, безопасность и свобода информации.

Agregore 2.8.2 - Font Based Syntax Highlighting
=> https://agregore.mauve.moe
A minimal web browser for the distributed web
- Enable people to make and use local first apps using the web
- Be minimal (fewer built-in features, leave more to the OS)
- Be open to anything p2p / decentralized / local-first
- Rely on web extensions for extra functionality
- Work with mesh networks / Bluetooth Low Energy networks
Changelog:
=> https://github.com/AgregoreWeb/agregore-browser/releases/tag/v2.8.2
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent

Agregore 2.8.2 - Font Based Syntax Highlighting
=> https://agregore.mauve.moe
A minimal web browser for the distributed web
- Enable people to make and use local first apps using the web
- Be minimal (fewer built-in features, leave more to the OS)
- Be open to anything p2p / decentralized / local-first
- Rely on web extensions for extra functionality
- Work with mesh networks / Bluetooth Low Energy networks
Changelog:
=> https://github.com/AgregoreWeb/agregore-browser/releases/tag/v2.8.2
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent