fyi, going to https://pubky.app/onboarding does not work on Vanadium out of the box - it's a black screen
You have to go into the settings and add a site specific exception for Javascript JIT (improve performance at the expense of security)
Might be worth looking at, as there are a lot of Graphene users out there
Actually this site is a complete non starter - it asks you to agree to a bunch of terms, then it asks for a load of personal data and suggests you download from known spyware companies (apple / google) and to request an "invite code"
We're curious about pubky - how to get involved without the above?
Found the repo. Core appears to have a wasm dependency (problematic on graphene)
The pubkey readme points to another source which 404s (maybe it's private?)
The link is for a total rewrite we are working on, it will be open-sourced once it actually works.
why wait?
Why care?
I'm interested. I'm a pubky user.
why fight everyone about everything, including those who are inclined to be interested in your work?
I'm trying to cut you some slack and you're making it really difficult.
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!
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
Why does WA not work with Graphene? It is interpretable instead of JIT
WebAssembly hard depends on JIT in the browser. Same actually applies to Chrome and such. JIT bugs cause a lot of exploited in the wild vulns so its disabled by default for hardening.
You can toggle JIT off per-site on the top left menu. The site loaded for me after using that.
Microsoft Edge has a JIT-less wasm interpreter they tried upstreaming but Chrome ended up not keeping the work upstreaming so its just an Edge thing.
Pubky.app requires zero personal data of any kind, you are a liar.
All apps require terms of service, including Nostr apps. In fact, relays should be providing them too. (some Terms protect users, all terms are to clarify the relationship between the provider and user)
The Pubky Ring app is open source and available for sideloading if you dont trust Google/Apple. You also can use pubky.app without Ring at all.
The site asks for "Your name" and "tell me about yourself". That is personal data! Users may not realise they are doxing themselves. As app developers we must be responsible for the safety of our users, who may not realise the legal jeopardy of posting opinions under a real identity.
oh no
social media app asks for name/bio
I wonder who else is doing this (everyone, including Nostr)
I personally find Pubky flawed but this is bullshit
I tried to install the Pubky Ring app and the link from Google Play Beta is bad.
Odd that it didn't work from the beta page. Thank you.
