Honestly, if you aren’t curious enough to learn new things that’s on you — don’t blame it on the name. Do you really think the paid relay model is sustainable today? Static upload payments for unlimited downloads?
Discussion
Hey princess, if feedback isn't appreciated, don't ask for it!
Feedback on tech, not branding and marketing. I just simplified the explanation in these few notes. If you can’t understand the tech, don’t bash the project and associate it with shitcoinery. This is as trust-minimized as it gets! ⚡️🐝
Your original question was about why you haven't been able to get traction with devs. That's a marketing question.
is there any code for this yet?
Yes a ton
marketing tech to devs who have got cosy with being the gatekeepers so much they write lists of their own awesome mates is virtually impossible. even though their behaviour is clearly immature and narcissistic to anyone reading it from the outside.
It's ok to have friends
for anyone who is serious about tech the hubris filled ramblings of a bunch of jumped up web developers is quite comical. guys who are clearly exploiting the "trending" algorithm that is the default and what every user first sees, to brag about how l33t they are is tragic.
they don't care about the actual tech making it into anything like a late beta let alone release grade.
You are lashing out over some **private** feedback I gave you for your consideration when I told you that your website looks like shitcoinery with the marketing bla, the "whitepaper" and the made up names.
Not understanding tech is not the same as not having time to read through every shitcoin project's "whitepaper".
He might also be referring to what I said, where either I'm too stupid to understand the project, or the project doesn't make sense. But I wasn't making any claim about which option is true, maybe I am stupid.
No, neither of you are stupid… you just haven’t taken the time to learn the computer science. Did everyone understand bitcoin instantly without learning CS? No… it takes time.
If it can be understood in a glance, then it probably is pretty rag-tag. This isn’t an app — it’s a server setup. Go dig into Strfry and see how complicated Negentropy is compared to FOREST. FOREST is a walk in the park in comparison.
it is a big problem. consistency is a huge weakness in the nostr design and it's such a big problem that an ad hoc solution was applied in the most popular relay, and the solution is far from ideal.
what is more concerning, though, is the amount of circle jerking going on among a small set of very prominent users, who act as though they are the gatekeepers and that they defend the moat around the tech so that outsiders can't do anything towards it.
the tech is so primitive that if it doesn't get a formal mechanism for consistency, it will fork into one that does and leave them behind.
I know what negentropy is for without having to understand it. The way you've positioned your stuff requires understanding in order to know what it's for.
actually, no, i've been observing the same thing.
go look at the talk video. it's in SD. you can't read anything of the slides he made.
making a judgement of a project building on nostr based on you personal aesthetic and not even looking for a second at its technical merits shows exactly where the problem lies here.
mids who want everything to be about them and are riding the trending algorithm while attacking the very system they are propped up by.
anyone with any understanding of distributed systems can tell you that the protocol of nostr is severely lacking in any mechanism for consistency.
not only that, your complaint is completely ridiculous. the whitepaper for scionic merkle dags is like 5 pages long and it's got nothing to do with shitcoins, and it's main author is someone who has academic chops and past work behind them.
part of the reason why it bothers me is because i've had a substantial amount of a protocol design, mostly implemented, for about 9 months now and can't find any way to bring it any further, even though it solves the problem of scaling with teh tor network, and creates a general paywalling mechanism for resource access online, without compromising privacy of users, and with the capability to protect the providers as well.
Where is this project? Is it nostr related? Is there a NIP for it? Is it integrated into any clients or relays?
does the NIP exist at all for the mechanism by which relays figure out what they have and what they need to ask for?
how is nostr going to get adoption without being able to cope with a large userbase, while not resulting in relays turning into clusters on AWS and nothing new achieved?
as far as i know, iris.to has early support for FOREST annotations that is transparently compatible with standard notes.
So are you saying you've also been working on FOREST? Or something else?
If a NIP doesn't exist to solve the problem you're interested in, write one.
I gave Colby feedback in private which he pulled into the public. I like to share criticism in private (and praise in public) cause those rambling in public come across as big cry babies but as he pulled it into the public: I explained how my **first impression** was that of yet another shitcoin. The whole layout of the page with a whitepaper looked like a template I have seen literally more than 100 times over the recent years. I'm a developer. I'm dedicating all my time to Bitcoin and related tech but don't have infinite time, so I use heuristics to dismiss certain projects and as I felt the project might not be as bad as the first impression, I let him know my first impression in private - only to get insulted in public.
I get it, marketing is not my strong suite neither, so I still have not muted the two of you but a constructive, friendly conversation does look differently.
I didn’t even ask for your advice, but I was actually talking about hodlbod’s original comment.
I get that it’s hard to understand. I’m doing everything I can to find ways to simplify it.
The gist is there have been 3 generations of Merkle Trees discussed in that paper. It started with Classic Merkle Trees back with Ralph Merkle.
IPFS made Merkle DAGs so you could support folders and collections of files.
We made Scionic Merkle DAG Trees to shrink the size of the Merkle DAG branches, which provides scalability in an unprecedented way.
you call that comment feedback?
reads like ad hominem