Version 1.0.0 of Git IPFS Remote Bridge is now available with significant IPNS compatibility update!
Additional information is available in IPFS Discuss post.
#IPFS #Git
Additional information is available in IPFS Discuss post.
#IPFS #Git
GitHub
GitHub - ElettraSciComp/Git-IPFS-Remote-Bridge: Git IPFS Remote Bridge
Git IPFS Remote Bridge. Contribute to ElettraSciComp/Git-IPFS-Remote-Bridge development by creating an account on GitHub.
❤3
IPFS Desktop v0.47.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.47.0
#IPFS
=> 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.47.0
#IPFS
docs.ipfs.tech
IPFS Desktop | IPFS Docs
IPFS Desktop gives you all the power of IPFS in a convenient desktop app - a complete IPFS node, plus handy OS menu shortcuts and an all-in-one file manager, peer map, and content explorer.
🔥3
Kubo v0.39.0
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
- HTTP Routing V1 (
- HTTP Kubo RPC API (
- Command Line Interface based on (
- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.39.0
#IPFS
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
/ipfs and /ipns) functionality for trusted and trustless content retrieval- HTTP Routing V1 (
/routing/v1) client and server implementation for delegated routing lookups- HTTP Kubo RPC API (
/api/v0) to access and control the daemon- Command Line Interface based on (
/api/v0) RPC API- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.39.0
#IPFS
Quiet v6.4.1
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%406.4.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%406.4.1
=>https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%406.4.0
=>https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%406.4.1
#Tor #IPFS
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%406.4.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%406.4.1
=>https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%406.4.0
=>https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%406.4.1
#Tor #IPFS
❤4
Berty v2.471.0
=> https://berty.tech
=> https://github.com/berty
Berty is a privacy-first messaging application built on top of the Wesh Protocol.
Secure and private:
- Messages are end-to-end encrypted by default
- Metadata is kept to a minimum
- No phone number or email address is required to create an account
- Built to retain its properties even when used on adversarial networks
Censorship-resilient:
- Decentralized, distributed, peer-to-peer and serverless
- No internet connection is required, thanks to BLE technology and mDNS.
Open:
- Free forever and open-source
Berty is designed to be used as a communication tool when all other traditional messengers fail. Berty Messenger serves the following use cases:
- When you need to share sensitive information over untrusted networks, for instance while traveling
- If you want to communicate anonymously
- If you want full control over your data and thus don't want to rely on third-party servers
- In countries that actively monitor and temper with their network, restricting its use and censoring some of its contents
- In areas with weak or no connection at all
Berty is still under active development and should not be used to exchange important data.
Changelog:
=> https://github.com/berty/berty/releases/tag/v2.471.0
#IM #IPFS #P2P
=> https://berty.tech
=> https://github.com/berty
Berty is a privacy-first messaging application built on top of the Wesh Protocol.
Secure and private:
- Messages are end-to-end encrypted by default
- Metadata is kept to a minimum
- No phone number or email address is required to create an account
- Built to retain its properties even when used on adversarial networks
Censorship-resilient:
- Decentralized, distributed, peer-to-peer and serverless
- No internet connection is required, thanks to BLE technology and mDNS.
Open:
- Free forever and open-source
Berty is designed to be used as a communication tool when all other traditional messengers fail. Berty Messenger serves the following use cases:
- When you need to share sensitive information over untrusted networks, for instance while traveling
- If you want to communicate anonymously
- If you want full control over your data and thus don't want to rely on third-party servers
- In countries that actively monitor and temper with their network, restricting its use and censoring some of its contents
- In areas with weak or no connection at all
Berty is still under active development and should not be used to exchange important data.
Changelog:
=> https://github.com/berty/berty/releases/tag/v2.471.0
#IM #IPFS #P2P
Berty Technologies
Berty · Berty Technologies
We build tools to enhance communication freedom
🔥3
Agregore v2.21.1 - View Local Sites
=> 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.21.1
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent
=> 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.21.1
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent
Agregore v2.22.0 - Search provider overhaul
=> 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.22.0
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent
=> 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.22.0
#IPFS #IPLD #Hypercore #Gemini #SSB #BitTorrent
🔥1
IPFS Desktop v0.48.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.48.0
#IPFS
=> 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.48.0
#IPFS
docs.ipfs.tech
IPFS Desktop | IPFS Docs
IPFS Desktop gives you all the power of IPFS in a convenient desktop app - a complete IPFS node, plus handy OS menu shortcuts and an all-in-one file manager, peer map, and content explorer.
Kubo v0.40.1
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
- HTTP Routing V1 (
- HTTP Kubo RPC API (
- Command Line Interface based on (
- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.40.0
=> https://github.com/ipfs/kubo/releases/tag/v0.40.1
#IPFS
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
/ipfs and /ipns) functionality for trusted and trustless content retrieval- HTTP Routing V1 (
/routing/v1) client and server implementation for delegated routing lookups- HTTP Kubo RPC API (
/api/v0) to access and control the daemon- Command Line Interface based on (
/api/v0) RPC API- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.40.0
=> https://github.com/ipfs/kubo/releases/tag/v0.40.1
#IPFS
❤1
Agregore v2.23.0 - DID protocol handlers, small fixes, ARM linux
=> 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.23.0
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
=> 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.23.0
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
Agregore v2.23.1 - force dark or light mode in settings
=> 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.23.1
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
=> 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.23.1
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
❤2
IPFS Desktop v0.49.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.49.0
#IPFS
=> 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.49.0
#IPFS
Agregore v2.24.0 - Did Renderer, Download page
=> 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.24.0
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
=> 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.24.0
#IPFS #IPLD #Hypercore #Gemini #BitTorrent
Kubo v0.41.0
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
- HTTP Routing V1 (
- HTTP Kubo RPC API (
- Command Line Interface based on (
- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.41.0
#IPFS
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
/ipfs and /ipns) functionality for trusted and trustless content retrieval- HTTP Routing V1 (
/routing/v1) client and server implementation for delegated routing lookups- HTTP Kubo RPC API (
/api/v0) to access and control the daemon- Command Line Interface based on (
/api/v0) RPC API- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.41.0
#IPFS
Kubo v0.42.0
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
- HTTP Routing V1 (
- HTTP Kubo RPC API (
- Command Line Interface based on (
- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.42.0
#IPFS
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
/ipfs and /ipns) functionality for trusted and trustless content retrieval- HTTP Routing V1 (
/routing/v1) client and server implementation for delegated routing lookups- HTTP Kubo RPC API (
/api/v0) to access and control the daemon- Command Line Interface based on (
/api/v0) RPC API- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.42.0
#IPFS
👍1
Quiet v7.3.0
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%407.3.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%407.3.0
#Tor #IPFS
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%407.3.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%407.3.0
#Tor #IPFS
Quiet v8.0.0
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%408.0.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%408.0.0
#Tor #IPFS
=> https://tryquiet.org/
Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one's own. In Quiet, all data syncs directly between a team's devices over Tor with no server required.
NOTE: Quiet is not audited and should not be used when privacy and security are critical. It lacks basic features and probably won't replace your Slack or Discord yet. That said, it works surprisingly well and we use it daily as a Slack replacement.
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/desktop%408.0.0
=> https://github.com/TryQuiet/quiet/releases/tag/%40quiet/mobile%408.0.0
#Tor #IPFS
IPFS Companion v3.4.0
=> https://docs.ipfs.tech/install/ipfs-companion/
IPFS Companion harnesses the power of your locally running IPFS node (either through the IPFS Desktop app or the command-line daemon) directly inside your favorite Chromium-based or Firefox browser, enabling support for ipfs:// addresses, redirecting content-addressed websites and file paths to your local Gateway, easy IPFS file import and sharing, and more.
Changelog:
=> https://github.com/ipfs/ipfs-companion/releases/tag/v3.4.0
#IPFS
=> https://docs.ipfs.tech/install/ipfs-companion/
IPFS Companion harnesses the power of your locally running IPFS node (either through the IPFS Desktop app or the command-line daemon) directly inside your favorite Chromium-based or Firefox browser, enabling support for ipfs:// addresses, redirecting content-addressed websites and file paths to your local Gateway, easy IPFS file import and sharing, and more.
Changelog:
=> https://github.com/ipfs/ipfs-companion/releases/tag/v3.4.0
#IPFS
docs.ipfs.tech
IPFS Companion | IPFS Docs
The IPFS Companion browser extension allows you to interact with your IPFS node and the extended IPFS network through your browser. Learn how to install it here.
IPFS Desktop v0.50.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.50.0
#IPFS
=> 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.50.0
This is the last Kubo release with new features from the Shipyard team. Our IPFS work ends on September 30, 2026. Until then we will ship security and bug fix releases if any are needed. After that date, no one at Shipyard maintains IPFS Desktop. If you depend on IPFS Desktop, read the announcement and send us your transition questions before the end of September.
#IPFS
Kubo v0.43.0
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
- HTTP Routing V1 (
- HTTP Kubo RPC API (
- Command Line Interface based on (
- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.43.0
#IPFS
=> ipfs.tech
=> https://docs.ipfs.tech/how-to/command-line-quick-start/
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go.
Featureset
- Runs an IPFS-Node as a network service that is part of LAN and WAN DHT
- Native support for UnixFS (most popular way to represent files and directories on IPFS)
- HTTP Gateway (
/ipfs and /ipns) functionality for trusted and trustless content retrieval- HTTP Routing V1 (
/routing/v1) client and server implementation for delegated routing lookups- HTTP Kubo RPC API (
/api/v0) to access and control the daemon- Command Line Interface based on (
/api/v0) RPC API- WebUI to manage the Kubo node
- Content blocking support for operators of public nodes
Changelog:
=> https://github.com/ipfs/kubo/releases/tag/v0.43.0
This is the last Kubo release with new features from the Shipyard team. Our IPFS work ends on September 30, 2026. Until then we will ship security and bug fix releases if any are needed. After that date, no one at Shipyard maintains Kubo. If you depend on Kubo, read the announcement and send us your transition questions before the end of September.
#IPFS