watermill VS ipfs-search

I’ve successfully worked on projects using an asynchronous event-driven way of connecting services. I really like the decoupling of business logic and the events triggering it. I highly recommend https://github.com/ThreeDotsLabs/watermill to be more flexible when it comes to choosing the actual technology driving the async patter. It might be NATS today but requirements might change and you need to change. Watermill prepares you for this.

Highly recommend https://watermill.io lib for building async apps (using among others pub/sub patterns). It greatly decouples your code from the underlying technology and gives you the freedom to choose depending on the environment (e.g dev, prod). For dev or small scale purposes, it supports pub/sub purely based on go channels.

Look at this library: https://github.com/ThreeDotsLabs/watermill

Watermill is a good pubsub abstraction. You can start with native go channels and grow into a cloud pubsub or Kafka/Pulsar if you need to.

These conditions have led me to discover two packages watermill.io and go-kit. Both of these seem to do what I want and I am thinking of implementing the project using watermill and go Chanels and deploying to a server or some sort.

github.com/ThreeDotsLabs/watermill package provides a framework for building event-driven applications. It allows easy communication between independent components by decoupling the sender and the receiver.

My personal favorite tools: - https://github.com/go-kit/ for building services (although it's not necessary a great tool for prototyping) - https://github.com/gorilla/mux router (although it's been recently deprecated, so I'm looking for a similar, maintained library) - https://entgo.io/ ORM - https://watermill.io/ for messaging

Checkout https://watermill.io/

Admarus is a decentralized alternative to ipfs-search

You can also use this search engine: https://ipfs-search.com

ipfs-search.com doesnt allow user submission, but you can use tools like public-gateway-cacher to increase the chances that their dht listener hears of it.

IPFS Search https://ipfs-search.com

There's not any main search portal that I know of. I mean, there's this, https://github.com/ipfs-search/ipfs-search / https://ipfs-search.com/ Which afaik looks at the DHT traffic or similar. I'm not great at getting useful results from that, maybe you'll have better luck. r/IPFS_Hashes is a place for people to post things they're hosting.

There is already ipfs-search.com, which uses an open source byte analyzer to figure out what type of file it runs into.

IPFS though has a search engine, https://ipfs-search.com/#/, which seems to work pretty good.

ENS (.eth, .sol, .luna), Unstoppable domains, handshake/namebase, IPFS websites, onion/i2p/zeronet/freenet/lokinet and others will need to get indexed and accessible by a search engine easily by a normal user. Until then, all of these trying to counter ICANN are pretty much useless.

I didnt look into the wallet’s transactions yet, but i searched the NFT names on this IPFS search engine https://ipfs-search.com/ and it came up empty. I don’t know all the specifics of which NFTs end up on the ipfs but the dumb ones my little bro and I minted for curiosity on Solana were on there. I dont know if the search engine is comprehensive, but it’s something—another data point.

https://github.com/ipfs-search/ipfs-search#building

Nodes announce the hashes they know about so you could sniff this gossip and then build a search engine on top of it which is how ipfs-search works.