in summary: there is no free lunch for content storage on the internet.
so in practice most apps built on IPFS storage simply offload the data to 3rd party providers like “web3.storage” and “infura”, right along all those cool monkey pics.
to successfully use IPFS you must either host your own pinning servers or pay to use a 3rd party. otherwise your content is stored on end user devices and automatically garbage collected.
the whole IPFS premise of distributed, always online content is a facade. the system depends on pinning servers for that to work which is ultimately a centralzing force.
sick! I’m rocking some carbo wheels on the old i9 torch. post a pic when you get that thing setup!
trails pictured are from last night in NW Washington state
wore my party shirt
pv

gm 🌄
#[0]
I agree eith #[0] , no delete abd no edit
A Nostr relay that streams SQLite through Litestream: https://github.com/mattn/nostr-relay
Made by the author of the most popular Golang SQLite Library on GitHub.
Holy
Have you written down ideas for the stats api stuff anywhere?
since it’s all self hosted it seems like self signed certs would be fine. perhaps they could update their proxy container to generate certs and provide a root for users to trust during setup.


Who paying for it?