Replies (30)
And by multiple times, I mean "several concurrent grants". You can see why Will misunderstood, and I don't blame him for that, which is why my take away is primarily related to how I screwed up,
The nostr committee being anonymous is just wild to me. I would have liked to have any kind of feedback both during and after my grant period and also on my new proposal. For all I know, they just didn't know where to look for my non-github code, or were just lazy, or maybe just the proposal was shit. I'll never know.
Grant programs run in this fashion seem like they have hurt Nostr. Bad ideas get propped up (for YEARS), squashing good ideas, outfunding non-grant projects and crushing them with infrastructure that free-projects can't afford, muddling the priorities of a normal software cycle and motivations.. Users and usability deprioritized, basically just a license to do whatever you want.
But yeah, feedback, feedback, feedback. Not, ghosted by anon after putting in serious amounts of effort. If they need to be paid to take things more seriously and genuinely help grantees and potential candidates, then they should take a tiny fraction of this money they handle and use it on the board and committees. Tired of hearing they work for free and don't have time so just spend minimum effort on the whole thing. Basically that just means they get paid in other ways (influence) or they would not be doing it. Sus.
no point complaining man. it's a corrupt and disfunctional organization. not worth it. from now on I will self fund via job and potentially VC if it makes sense
I think this is all pretty reasonable. At the same time, "if we had cheese we could make a ham-and-cheese sandwich, if we had ham." I don't know how many people with the skills to evaluate applications would want to take even a paid job investigating and monitoring other people's work. I appreciate that you see this as an operations problem; most people are much more dogmatic about "grants bad".
To me, outside-looking-into a diffuse thing that I have no idea how it works. I think I made many mistakes. For one, the form to apply for a grant is a TEXTAREA of length 3 and has never been updated.. Would that mean applications should be 3 lines long? I pasted in markdown, did that even work? What would be reasonable to ask for? What would they even look at? In retrospect I figured they looked at my "github activity calendar" and thought I wasn't doing anything, because I blocked this calendar from looking at me.
Things like that.. well, it's just a mess and a bad experience yeah.
Can't say I didn't appreciate somehow magically getting my original grant that has long been expired, I did get a mention in the blog that made it seem pretty clear they didn't really read or understand my progress reports of what *I think I accomplished for that year.
well, much like you, my chances of another grant are zero so now I guess I can talk.. #freeeedommm
The form is a little better nowadays, but I understand your point about lack of transparency. You were probably better off than most because at least I know who you are and value your work. The blog posts are compiled by people who aren't deeply involved in the nostr technicals I think; info about my projects has also been inaccurate.
why do you think that?
freedom is worth it. with opensats you have to submit things your working on so that ten31 can give primal the heads up on novel features
Because I'm working in a direction on opensource project(s) that if successful would compete directly with products that the official board has a conflict of interest with. It could harm their businesses if it was successful. This is my guess. Since the actual board *is public knowledge, it is one of the only pieces of information I have with which to speculate on (in addition to the vague denial letter that simply said, was not selected).
You should try applying and see how it goes. I have a high opinion of the integrity of the board/committee. I've not personally seen any behavior that I would read as duplicitous, although of course there will always be conflicts of interest in an ecosystem this small.
I did apply, (recently) in November. Received the boiler-plate response below:
```
Dear Applicant,
Thank you for submitting your grant application to OpenSats. We regret to inform you that your project was not selected for funding.
We received a large number of applications and were unable to fund all of the worthy proposals. The applicant pool was very competitive, which is a great thing to see in and of itself. Unfortunately, your application did not make the cut this time around.
Feel free to apply again in the future:

OpenSats
Apply for Funding - OpenSats
Apply for an OpenSats Grant
In the meanwhile, we wish you the best of luck in your fundraising efforts.
Sincerely,
The OpenSats Team
```
Hmm. I offered to do that job. I'm used to that work and give actionable feedback. Never got a call.
Alexandria has already been turned down, twice. Whatever.
Being so un-transparent on their end, it's easy to just follow logic to the conclusions and then get labeled a consipracy nutjob and gas-lit about "we don't even get paid", "if you don't like it make your own 501c3".
Hehe. I don't think they realize how dumb that sounds. We can't make our own 501c3 because we need that AND someone like jack to fully fund it otherwise, it's a huge waste of money and time to collect 5$ from the poor nostr plebs that are struggling to get by in the internet wasteland.
Yeah, I wish there was more transparency. At the same time form letters forestall a lot of nasty problems when people don't take rejection well (see above for an example).
Unrelated to your application, speaking for myself only and on behalf of no organization (especially not OpenSats), here's my opinion about relay.tools:
- The design and frontend work is not good. Get a designer to come up with user stories, flows, and do usability testing. I have no idea how to use the support portal, the zap image is massive on payment, the sign in prompt in the landing form is hard to find, the wizard is a good idea but poorly executed, there are lots of ugly/wide/compact boxes.
- There are long-standing bugs - my paused coracle-dev relay has a balance of -128713 sats, the relay subscriptions page shows everyone's subscriptions.
- Scope is not focused. There is a LOT that can be done with relay hosting: custom domain names, multiple implementations, nip 86/11/43/29 management, etc. Instead you've added nip 05 (with no explanation of what it is), written clients (I'm sorry, but UI is not your strong suit, and there are much better community clients getting the developers' full attention out there), done stuff with nip 66 (which I personally think is not very useful) and web of trust.
I ended up building caravel because you never added community relay support. This to me is the biggest miss โ as far as I can tell, relay.tools only supports strfry? I thought that one of your goals was to make it easy to set up any implementation. I waited for a long time for this to materialize and it never did.
Anyway, don't take this as me dunking on your project. I know you're not funded and keep working on it anyway, which I really respect. But the things I've asked for as not only a customer but as a potential partner (remember talking about referral codes), you've just not executed on. I would be excited to see you move in that direction, because you're the only person who has substantially done anything like this so far.
This is good feedback, for a few years ago, and even for now. You should try it again, you will see I have made gradual progress with no funding over these years. Part of my recent proposal was to uplift completely what I've done so far into a new code harness, android native app and vision. I agree, UI is not my strong suit, but functionality, stability and usability is. Much like many open source projects, if they get actually used, then the UI becomes what they're used to. Since no other relay management exists, that's why relay-tools is still pretty much the leader here on UI (because we've tested for years, against REAL use cases in the wild, and real users that have real needs).
Design and wizard, updated, and entire feedback loops completed. (I am not a designer and no designers from opensats or otherwise would help me, they would only give me some figma jpegs and then toss me into the wind). With AI I can accomplish much more faster.
@Bohemia made an awesome relay explainer video here documenting how we see relay UIs working in the wild, and what they can do:
As you are aware, relay UIs are not easy to make, nor is provisioning and managing them. Your paused relay, will always accumulate balance, but it will never go into someone else's hands (eg, it cannot be camped). I serve tons of traffic for long dead relays, and to activate them, requires the balance to top up.
I did try to partner with you, but you immediately went off into an area you knew I could not support (non-strfry, untested relay software that requires me holding private keys and much QA with a maintainer that is not available nor cares). I was willing to explore this possibility but you would not even implement NIP86 relay management for moderation and were hell-bent on nip29 only. I tried to meet you half-way here, but the reality is, nip29 was de-prioritized for many reasons, not just those I mentioned here. You may find that running relays, there are a lot of operational costs involved. Many days, of debugging and support, education and non-coding tasks. I am spread thin.
Custom domain names: Yeah I will not support this on my own relay hub for nostr1.com, you can run the software yourself on your own domain (if you do support this in caraval, you will find out why this is hard).
Multiple Implementations of relays: Yes, I want to support this so badly, and will do so, and included this in my opensats proposal, but, see above about QA and operational cost for now I am left to fend for myself and my customers, I have to be ruthless about priorities.
This is awesome feedback tho man, I appreciate it. A well-rounded take of what my failings are and have been. The cool thing is I still spend lots of time moving forward, but to the outside world it will look extremely slow. I have an entire native android app now, and that is the new flagship UI. I am tired of getting dicked around by client devs, so I was required to write my own clients as well. This is probably similar to what you felt, but about relays. If there were no grants involved, that probably would have forced us to partner earlier. But with everyone doing whatever they want, well, this is my point is that it's not really working well for nostr as a whole.
I am happy to have pioneered this far.. Remember, I have been off grant since October 2024. Yet, progress still is being made and I am proud of it. I am sorry you have to take the brunt of some of this Opensats feedback, I had no idea that you are/were on the advisory committee (and zero clue who else), and you putting yourself out there, yeah that's gonna be rough :) Cause I coulda probably used this back and forth, years ago.
We asked for feedback earlier this week.
And received it in a proper reply within some hours.
My feedback above was from just now, clicking round relay.tools. Some things have improved, but it suffers from most of the same problems IMO.
Totally fair to not support the stuff I was building in particular, but I do think multiple implementations would be a big benefit to your users. Specific control panels per relay type would be important too โ haven for example would be very bespoke compared to strfy. But I also get you're spread thin, so am I. You can't do everything you want to do. But honestly, it does seem like you're getting somewhat distracted. How important is an android app vs web? For admin, I feel like web is usually enough.
I also wish more partnership/coordination would happen. But everyone has their own vision, which means nothing gets done. Grants might have something to do with this, but I think it's more because everyone here is so anarchistic.
I could not get a single client to implement a single relay feed and nip86 delete. Amethyst recently came close, but I have to have a tool that can do that, it is the baseline for managing a relay. Either way, relays needed this, so I built it. Now I don't have to run begging to devs for stuff they're not interested in supporting. I did have web, but it was poorly written and footgunned myself working with NDK. Mobile native is better anyway.
Being able to moderate on the fly has been a like having super powers. I've used it plenty of times beyond experimentation. I'm genuinely grateful for the relay tools app. Sorry for interjecting.
haha footgun is such a great expression. yeah,
is built using pure wasm with multiple WebWorkers spawned for different tasks and sending messages between each other. there is a relay/proxy, a fan-out for verification, and then identity, DM, notifications, and some others i forget just now. if you load up the app you can see a list of workers in green down the bottom left that appear showing loading and then turn green when ready, and then it stops the main spinner and presents the login page.
i want to switch that startup process to use the special page you can access top right with the heart monitor icon on the top right so it's a fully unified log viewer, and use it to present the loading process, it's clear and has computer booting vibes which i think is better than a spinner anyhow.
the other thing about the architecture i've created is that the main page wasm doesn't use a virtual DOM, it walks it and rewrites it dynamically. that's why it's so much faster. if you haven't looked at it, i highly recommend you check it out. it's got a few bugs here and there which is partly why i wanted to finish bootstrapping the compiler so the memory model and spawn channels are fully correct and moxie native all the way down. *hopefully* not too much longer before i finish that.
coracle has had relay feeds for a long time (although they use the spec I developed rather than jumble's, which came later). landlubber and flotilla both support nip 86. It just takes time.
Thank you ๐
I lost faith in coracle products because I could never get the user experience how I wanted it. Too many sockets, too many missing events and felt heavy and buggy. I rolled out some of those old relay feed versions and users just wouldn't use them. I could always try again but I am so burnt out on QA other peoples software especially now that I can write my own to the specs I need. Because I am good at QA and it is still under-rated as a valuable use of time.
Same with strfry, I use it because I have thousands of relay connections, synchronization, routing, battle tested and it Never goes down. I do not see any other relay software matching this yet.
Since my grant ended, I am a mercenary, if someone wants to pay RelayTools (eg. Me) to QA a new type of relay and get it all battle ready and work with the maintainers and etc, I'm open to it.
This is my business model, I provide professional services to people that need my expertise.
At the same time I also continue to push the RelayTools vision and software suite, which has been full of friction with devs and their view of commodity relays and zero mgmt (many of which have never run a production relay). Fortunately there are still some projects to work on that excite me as a relay operator. Like WoT, or what I call Web of Access, and apps that can manage relays. But you don't like those ๐ so... Yeah. Maybe you'll like it more after dealing with wild west relay running or maybe nip29 completely solves it in a different way. These relays get hammered to death even just not accepting any events.. Many problems to solve and its all work that seems to an outside observer like nothing is changing or being done. But it is. Much actually.
I look forward to hearing more about how things go, and I am always available for consultation.
Consulting makes sense, although I would not expect maintainers to be customers, but rather people who want to stand up a relay hosting product of some kind.
I never really understood why you wanted particular clients/features? Just to scratch your own itch? Allow people to use relays the way relay tools meant them to be used (early relay-as-community)?
Also I don't know why you think I don't like web of trust or nip 86. I helped popularize web of trust (coracle was the first client to show wot scores, I had pip and straycat on my podcast), and I built landlubber.coracle.social.
I don't expect anything, but why would you expect really anything of me either? Being off grant since '24 I think I'm paving the way both as an OSS business model and nostr tech. Yes I still believe relays ARE communities.. And while strfry can't do nip29, I still do not see why or how it would benefit my business to implement it. Other types of relays sure in a generic sense, but supporting those in the OSS codebase does not mean I would roll them out to nostr1.com until they had some mileage on them. Do they? Does any of these relays operate without crashing or runaway resources? Without complete rewrites every 6 mo, with no upgrade paths? Even if they did, I do not really know why I would do anything at this point if its not part of some kind of contract or if I firmly believed it was better faster stronger.
If you happened to read my proposal, I specifically mentioned installing all these different types of relays. But it's a lot of work, and I can't just work for free that much right now.
That's fair, nip 29 is a disaster and has had a fair amount of churn. The benefit to you would be that you would have had about 30 more signups which I got instead.