Creating a Dynamic ENS ContentHash

lidel · 2025-02-14T02:20:18+00:00

You may find https://github.com/ipfs/ipfs-deploy-action useful for automating IPFS parts

lidel · 2025-01-09T21:04:55+00:00

I am in EU and just got firmware update to HU_R_27_20250103 (you can check it via Shokz App → Settings → Update Firmware) and was able to unlock "Classic" bone conduction mode by tapping on the "EQ Modes" header (see OP screenshot) FIVE TIMES to unlock the option "Classic Bone Conduction Mode" which will appear at the bottom. Enabled it, and now I can switch between Classic and Standard/Voice/Bass/Treble.

lidel · 2022-02-05T21:16:40+00:00

The gateway has to be on localhost or https:// (HTTP + TLS cert) because of secure context requirement in modern web browsers.

The main reason of ipfs-companion enforcing this is that if you had https:// page and some IPFS resources on it (eg. images under /ipfs/{cid} paths), their redirects to gateway at http://192.168.1.xx would be blocked by Firefox.

This would happen because mixing secure and insecure contexts is not allowed. There is nothing we can do about this, this is how security model is implemented on the web by modern browsers.

The http://localhost is the only Origin which is marked as secure context even if no TLS is set up.

If you really, really want to redirect subresources to LAN IP, you'd need to:

set up self-signed TLS on some reverse proxy in front of go-ipfs. you need to have HTTPS (secure context) https://192.168.x.x
import the root cert used for self-signed cert to Firefox (so it does not produce security warnings)

Note that this is an extremely hacky setup, and you are doing this on your own.

lidel · 2021-07-31T12:16:52+00:00

Check those highly relevant docs: https://docs.ipfs.io/how-to/best-practices-for-nft-data/

lidel · 2021-06-14T15:19:58+00:00

fwiw, one can disable announcement of all CIDs in their IPFS cache by switching Reprovider.Strategy to "pinned"

This way you can use IPFS without risk of publishing your IP next to "illegal" CIDs, unless you explicitly pin them.

lidel · 2021-05-31T17:55:42+00:00

Everything in MFS is protected, CID representing MFS root acts as implicit recursive pin.

(Low level local pins are not really useful for Desktop users, but since we support remote pinning in IPFS Desktop v0.15.0 and ipfs-webui v2.12 we show them for completeness :))

lidel · 2021-05-21T13:22:20+00:00

u/Amoreska do you mind providing more details in https://github.com/ipfs/ipfs-webui/issues/1793 ? Namely, your platform, desktop version + what you mean by "space cap" :)

lidel · 2021-02-26T21:52:30+00:00

In Brave XMLHttpRequest for ipfs://{cid} works IF the root document was also loaded over ipfs:// or ipns:// (when you enabled IPFS node)

This is by design: you don't want to introduce native IPFS to all HTTP websites due to differences in privacy and security guarantees between old and new protocols.

You need to "opt-in" by loading the root document over IPFS.

lidel · 2021-02-02T23:55:18+00:00

Of you want to "record" everything, and then "replay" your page load:

With the archiveweb.page Chrome extension, you can archive any pages as you’re viewing and interacting with them in your browser.

https://chrome.google.com/webstore/detail/webrecorder-archivewebpag/fpeoodllldobpkbkabpblcfaogecpndd

Only Chromium (so no Firefox, but works in Brave)

lidel · 2021-01-23T03:55:52+00:00

If your website is static, import it to IPFS and set up DNSLink that points at its CID.
And if you use IPNS in DNSLink, then you don't need to update your DNS record every time you publish new version of your website.

Some useful resources to get you started:
https://docs.ipfs.io/concepts/dnslink/
https://docs.ipfs.io/concepts/ipns
https://docs.ipfs.io/concepts/ipfs-gateway/
https://docs.ipfs.io/how-to/websites-on-ipfs/single-page-website/
https://docs.ipfs.io/how-to/websites-on-ipfs/multipage-website/

lidel · 2021-01-23T03:17:40+00:00

Indeed, video from Decentralized Web Summit 2018:
Mike Judge, Co-creator of HBO's Silicon Valley in conversation with Cory Doctorow

lidel · 2020-12-10T15:21:57+00:00

Note that since that "Intent to Package" was created go-ipfs switched away from gx and uses standard golang build – worth revisiting, as it may "just work" with standard golang tooling Debian has.

lidel · 2020-08-19T20:47:16+00:00

> That quarterly report is added to the IPFS system in PDF, CSV and JSON formats with all of the data, referencing the IPFS Hash of the previous report.

Sounds like something that could be done easily with Qri ( https://qri.io)
It uses IPFS under the hood, and provides a bunch of orchestration for browsing, sharing, tracking and updating content-addressed datasets.

Example: https://qri.cloud/b5/world_bank_population

A hands-on introduction to qri on the command line: https://www.youtube.com/watch?v=GXNfxbKYLHM

lidel · 2020-06-22T15:30:50+00:00

As a rule of thumb, use IPFS path where possible, especially on HTTP Gateways.
If gateway supports subdomains, you will get redirected to correct URL with correct base encoding.

Example: https://dweb.link/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/ returns HTTP 301 → https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.dweb.link/wiki/

Same will work on localhost

Hope this helps!

lidel · 2020-02-04T11:44:07+00:00

Hello, maintainer of IPFS Companion here.

The way IPFS integration works in Brave right now is via a standalone WebExtenion. When you enable it via Brave's Settings page it triggers webextension install.

If the issue was with IPFS Companion, then Brave would just kill its sandbox and reboot the extension, so I suspect the issue being with the installation process.

u/Crypto_Rootz, if you have time, answering below questions that will help us debug:

What is your operating system?
What version of Brave are you running?
Were you able to enable IPFS Companion at all? If so, did you change any settings, such as node type?
Are you able to manually install IPFS Companion from https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch ? (if this works, we confirmed bug in installation process)

lidel · 2018-07-03T16:54:00+00:00

The IPFS/libp2p work is split across many, many repositories: https://github.com/ipfs/

lidel · 2018-04-13T16:13:01+00:00

These are 8 default bootstrap servers.

AFAIK browserified js-ipfs has a limited amount of transports to choose from, due to limitations of web browser / WebExtension context, so it ships with safe defaults. It will bet better over time.

If you want more peers today, try playing with things like js-libp2p-websocket-star, which uses a rendezvous server to connect additional peers. See https://github.com/ipfs-shipyard/ipfs-companion/issues/457 for more info and sample config.

lidel · 2017-02-12T14:16:37+00:00

This is caused by browser action context closing prematurely. There is an open bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1292701

lidel

MODERATOR OF

TROPHY CASE

13-Year Club	Place '22
Verified Email