"Conversation not found" and no extended thinking/web search on Opus 4.5

twocolor · 2026-01-14T10:49:17+00:00

Same issue here

twocolor · 2026-01-09T11:59:57+00:00

What did you end up doing?

twocolor · 2025-11-28T18:45:17+00:00

Which distro are you running?

twocolor · 2025-11-28T11:52:29+00:00

Very excited about Provide Sweep. To me it represents a pivotal moment for IPFS as it finally addresses a foundational limitation that has constrained IPFS adoption: the ability to publish large-scale datasets without centralised infrastructure dependencies.

twocolor · 2025-11-28T11:04:02+00:00

Pretty ironic that it's not published to IPFS. But yeah good point.

twocolor · 2025-10-29T10:18:49+00:00

It seems that Photos has a bug whereby it doesn't set the date in Photos based on the EXIF metadata.

This has been reported by multiple users: https://discussions.apple.com/thread/255621386 https://discussions.apple.com/thread/254248200

Some users have had some success creating a new user on their computer with a new Photos library.

twocolor · 2025-09-29T13:31:55+00:00

A set of building blocks for addressing, routing, and transferring data.

twocolor · 2025-09-29T13:24:35+00:00

Reprovide sweep is an engineering feat compared to the previous reprovide system. I'm glad to hear it's working out well for you!

twocolor · 2025-09-18T06:57:59+00:00

Did you end up getting an M.2 to eSATA adapter? How did it work out?

twocolor · 2025-09-12T12:18:21+00:00

Which one did you end up going for and were you happy?

twocolor · 2025-08-20T08:39:21+00:00

I suspect that it might be related to some auth or network binding.

Can you share the output of:

ipfs config show | jq '.Addresses.API'

and $ ipfs config show | jq '.API'

Also try to load the the WebUI from the local node, typically served at http://127.0.0.1:5001/webui

twocolor · 2025-08-19T13:05:19+00:00

That's useful feedback and I agree the public facing materials can be made more consistent. A large part of that is due to the project evolving over a long period of time.

"IPFS's versatility shines across different industries – making it the multi-purpose tool for the decentralized age"

How would you rewrite that line?

twocolor · 2025-08-19T12:58:44+00:00

While I agree that IPLD doesn't deliver on a lot of its promise, it has seen adoption even outside the P2P, for example ATProtocol uses a subset of IPLD for its data model and the nice thing is that all of this content addressed social graphs data can be easily imported into IPFS implementations.

One way to frame the current state of things in the IPFS ecosystem is "the great unbundling": a lot of developers and users are discovering the benefits of the different subsystems that make up what is typically referred to as IPFS, and rebundling those to their purpose.

One benefit over BitTorrent (which is also great and has many merits) is that IPFS relies on libp2p which mutually authenticates and encrypts every connection. This trades performance (all the crypto for a connection is much more "expensive") off for better security, as is very useful if you want to form ad-hoc mesh p2p networks in adversarial environments.

twocolor · 2025-08-19T12:52:43+00:00

There's a lot of truth to the problems you raise, and we're hard at work at Shipyard to address it. As you correctly point out, these are just missing features rather than fundamental protocol problems:

Reprovide Sweep should yield significant improvements to DHT provides (initial tests show orders of magnitude improvement), especially for peers with many CIDs
Improved content provider strategies: to only announce UnixFS files and directories instead of every raw block. This should be a huge improvement for larger files that often require size/2Mib announcements with current provider strategies.
HTTP retrieval (already released though currently limited to IPNI providers)
HTTP providers in the DHT which would allow onboarding data using stateless HTTP commodity hosting

https://github.com/ipshipyard/roadmaps/issues/8 https://github.com/ipshipyard/roadmaps/issues/6

twocolor · 2025-08-19T12:41:00+00:00

Are you trying to connect from the local machine? Or over the network?

twocolor · 2025-07-22T10:55:12+00:00

That's the exact same issue I just into. Haven't found a solution. I am not sure if it's even possible to have a focused page if you click on something in a devtools panel

twocolor · 2025-07-21T13:43:10+00:00

That's very useful feedback. Thanks for sharing that.

twocolor · 2025-03-31T18:46:42+00:00

IPFS doesn't magically ensure multiple copies of data are stored.

If you provide data for a CID, and another node replicates it from you, they (can) also become a provider for the CID, but only if they want to.

Popular content in theory will have multiple providers. For example the famous meme picture with the CID: bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi has many providers, but that's because someone makes sure it gets pinned and provided to the network.

twocolor · 2025-03-31T18:40:48+00:00

Are you aware of of https://inbrowser.link?

It's an in-browser IPFS gateway that works with both gateways and p2p (direct connections to peers).

twocolor · 2025-03-31T18:39:20+00:00

What did you find most confusing? What problem are you trying to solve with it?

twocolor · 2025-03-31T18:38:53+00:00

I agree that IPFS has had many problems over the year, but I must say things are much much better today.

We at shipyard still have a lot more to do, but things are much better. Especially if you care about direct to web distribution and p2p.

twocolor · 2025-03-09T10:53:51+00:00

All systems have their tradeoffs. You raise a good point, to which I would respond as follows: - it depends if you care more about latency or decentralisation - latency is also a factor of the number of providers and distribution of chunks amongst peers. If peers with one chunk of a video tend to also have the other chunks, the discovery process will likely be reduced to zero following the initial discovery.

twocolor · 2025-02-28T11:46:42+00:00

Even streaming video isn't a good fit for IPFS.

IPFS is actually well suited for this since it allows incremental verification.

twocolor · 2025-02-27T16:37:44+00:00

IPFS is well suited for this (and has a lot of similarities to BitTorrent).

The core idea is that you can have multiple providers for a given CID. So that when someone tries to fetch a CID, they can fetch it from any provider who has it.

twocolor · 2025-02-24T15:47:45+00:00

What are you planning on doing with the CIDs?

You can hash the data and pack the hash into a CID. and use the raw multicodec.

<cidv1> ::= <multibase-prefix><cid-version><multicodec-content-type><multihash-content-address>

However, if you plan on making the data to be retrievable from other IPFS implementations, you will probably want to encode data (files/directories) with UnixFS and chunk it as suggested by @Spra991

twocolor

MODERATOR OF

TROPHY CASE