[snowblossomcoin/channels] Issue opened by fireduck64
Current implementation writes new chunks even if a file is unchanged from a previous block. This is silly.
[snowblossomcoin/channels] Issue closed by fireduck64
what do i expose myself to by upgrading my node?
at least storage level write amplifications seem to be something you are ironing out
The only big difference in 1.6.0 is the address and tx index will be rewritten as a hashed trie, just like the utxo set.
This makes the logic for reorgs a lot cleaner
But beyond that name registration we argued about a bit ago none of the channels content goes in snowblossom nodes
good
so what’s a channel node getting exposed to?
unless you subscribe to a channel, nothing other than the DHT data
which simply a mapping of channel IDs to peers
make a merchant api so people can buy capacity with snow
that i’d host, but fuck manual admin effort
I was thinking there would be a market for people to pay others to be a peer/seeder
limited capacity and bidding for the resources
i can host something like the snowblossom site you are apparently dogfood already?
yeah
as you so nicely ask in the spof wiki page
but it is almost exclusively me talking to myself
I am also going to clone the git repos into a channel
which is probably more important than any of the sites
repos and the main site i’m on board for
Cool