@Fireduck did you name the future shiny thingy ’channels’ just to make explaining hardware architecture vs. mining just that extra bit more confusing? :P
ha, no
I just haven't come up with another name
since the core concept is people being able to make a communication thing that other people can join
channel seems natural for that but I don't love the name
threads, ropes, lasso
you wrangle the content
based on my programming experience, everyone is afraid of threads
ha, I like it
frayed knots
tons of directions
topology and knot theory are one
fibers, yarns, fluff
bread (bring your own butter)
@Rotonen @Fireduck Snowblossom... `Channels` `Feeds` `Creators` `Distribution`
I like feeds or distribution
Knots
hamster feed
Since knot is not insanely overloaded in our industry
I feel like the joke will be lost on too many people and possibly confusing
@Clueless yep, we want to weed those poeple out quick
being a framework, most people won't be working with it directly
then the addresses can be simple: knot:(base32)
So I'm thinking we go with snow knots, and users "tie in" rather than subscribe
since they are taking a more active role, joining and seeding
thinks about it conceptually (needs a reaction picture)
:smiling_imp:
@Fireduck ’knots’ ’to tie in’ - that’s canine breeding
haha