It just seems like you are pressing from weird angles that are of no use to you. There are so many other things to ask about, no?

My fine sir, the new application simply does not exist yet. We do not normally publish pre-alpha software, most people don't.

Could we post some half-done code anyway? Sure. But why? So we can tell literally everyone interested not to use or even assume anything about it yet?

Or, we can wait til it is usable, maybe a couple months, and share it with everyone in a useful clear way.

I have more unfortunate news, we have other projects that arent published yet either. Some also that we put down and never published at all.

It is our decision what to share, just like everyone else. And we have shared so many cool things as open source and totally free. Have a look at those!

Reply to this note

Please Login to reply.

Discussion

Yes, agreed, I am pressing on it from "weird angles" but they are of use to me - this is how I evaluate new things. The open/closed nature of the code and the feasibility of self-hosting are among the most important aspects I consider.

I've just never understood the "It'll be open-sourced eventually" mentality.... Build in the open from day one, ignore the audience - you are already well practiced at taking a lot of shit and letting it roll off.

Honestly it always felt suspicious to me. If you know you're going to open source something eventually, why not do it sooner and let the same parties who will be interested next year take a look today?

The only reasons I can think of to not do so are: Shame/embarrassment of initial work; worry that someone else will build the same thing; no actual intention of opening it up. Maybe there are other motivations but I can't think of them.

You are missing one very important nuance.

Every relevant instance I recall of "It'll be open-sourced eventually" is regarding software that has users.

Like how Keet is released, has users, but is not open-sourced (afaik).

This is not that. Every single aspect of Pubky that anyone uses is open source already.

We perform a significant amount of R&D, and we have various projects at various stages. Some amount of internal order is required for us to operate. This is how we operate.

The great thing is this has zero affect on your ability to learn about, use, or build with Pubky.

Regarding your ability to self-host, it should be much easier in a few months, after we ship a homeserver purpose-made for that.

all reasonable points, thanks.

I eagerly await the homeserver