| api.distributed.press | distributed-press-organizing | |
|---|---|---|
| 4 | 1 | |
| 72 | 15 | |
| - | - | |
| 7.5 | 0.0 | |
| about 2 months ago | over 1 year ago | |
| TypeScript | ||
| GNU Affero General Public License v3.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
api.distributed.press
- Scheme in Scheme on WASM in the Browser
-
Show HN: File distribution over DNS: (ab)using DNS as a CDN
I think the obvious match here is how IPFS can use a dnslink TXT file to point to the content-addressable top of an IPFS-distributed static web https://docs.ipfs.tech/concepts/dnslink/ . This is how a lot of dweb/web3 websites maintain and advertise a non-http mirror. It works out of the box for sites served using https://distributed.press/ (non-commercial, open source) or https://fleek.co/ (hosted).
If you use Brave, or have the IPFS browser extension, you can access sites like https://ffdweb.org/ as an option, or preferentially.
-
Show HN: Compost – A DWeb-native magazine about the digital commons
This should be a link to https://distributed.press/
-
IPFS Support in Brave
There are several new and exciting decentralized web protocols. I am working on a tool to publish to all of them. Right now it publishes to IPFS and Hypercore, and will eventually serve signed plaintext so content can be shared to Scuttlebutt and Aether networks.
For example, this site is published using https://github.com/hyphacoop/api.distributed.press and it can be accessed over HTTP, IPFS, and Hypercore.
https://staging.compost.digital
distributed-press-organizing
-
Show HN: Compost – A DWeb-native magazine about the digital commons
Yes it is published to IPFS and Hypercore. The footer has the ipns:// and hyper:// links, and they ""-linked to IPFS and Hypercore gateways. You can access them directly on the DWeb networks with browsers like Brave (for IPFS), more on that here:
https://one.compost.digital/about/#a-distributed-press
On Beaker you'll have to use the hyperdrive key until DNS support is added:
hyper://dcbc7c15c1682caf55a9ea6287d13a36b064164aa5b1e86f0961f89eb18e1d5f
Apologies for the missing context. We also wrote a bit here about why we are publishing to the Decentralized Web:
https://github.com/hyphacoop/distributed-press-organizing/wi...
What are some alternatives?
multi-account-containers - Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs that preserve your privacy. Cookies are separated by container, allowing you to use the web with multiple identities or accounts simultaneously.
ipfs-companion - Browser extension that simplifies access to IPFS resources on the web
ipfs-deploy - Zero-Config CLI to Deploy Static Websites to IPFS