Last Notes
Thanks, I'll fix this in the next few days
We've removed it (getrandom + wasm_js feature) because in some context was causing issues (wasm32-unknown-unknown used outside JS).
You can solve the issue by adding the getrandom dep in your Cargo.toml, and enable the wasm_js feature. Make sure to do it for the right getrandom version(s), which can be found in the Cargo.lock
It supports WASM, are you compiling it from macOS?
https://github.com/nostrdevkit/nostr/tree/master/crates/nostr#wasm32-unknown-unknown
Ahh, I got it, this specific page works okay:
`https://account.protonmailrmez3lotccipshtkleegetolb73fuirgj7r4o4vfu7ozyd.onion/start`
This one attempts to send clearnet requests:
`https://account.protonmailrmez3lotccipshtkleegetolb73fuirgj7r4o4vfu7ozyd.onion/mail/signup`
I've just rechecked once again—it appears they no longer make clearnet requests. Probably they fixed something.
It's good if it will keep working with the `OnionTrafficOnly` and `NoDNSRequest` isolation flags. Anyway I don't recommend anyone use Proton without these flags enabled.
Thanks for pointing it out.
The signup page used to redirect to the clearnet version for me the last time I tried. I've just rechecked—there's no redirect anymore indeed, BUT it leaks a lot of stuff to clearnet, using CAPTCHA service for example!
So it's even worse now: it creates an illusion that it's a legit onion-only service, yet I think this signup page won't work with the `OnionTrafficOnly` isolation flag (at least in case it attempts to show CAPTCHA).
https://image.nostr.build/c7088b72d28358826ba7fe4db340dc9ba398f92b00c532e0457802529fb37a9f.jpg
I have created a proton account that way. I don't recall having to do anything special
They disallow creating accounts with their hidden onion service. Must be for a reason.
auth.nostr1.com both drops those and also supports deletion via nip86 additional commands.. See capabilities for reference.
@npub1zfs…w445 thanks for supporting `wss://nip17.com`!
I noticed that NIP-42 is misbehaving there: it's possible to request any 1059 events, unrelated to my conversations, by not specifying the p-tag.
For reference, the most restricting and correct behavior is probably implemented in `wss://chat.wisp.talk`, this responds with `CLOSED: blocked: gift-wrap queries must only be done for events that p-tag the current user`. Or `wss://basspistol.org/inbox`, this responds with `CLOSED: restricted: must query events from yourself`.
Probably less breaking approach would be just silently respond with 0 events (the way `wss://relay.nmail.li` and `wss://auth.nostr1.com` do it).
Me too, since the day they changed their old nerdy green icons and UI to something corporate looking, and governments doesn't seem bothered by them at all.
They have already handled encryption keys to law enforcement in the past
I think that, just as the EU treats Silicon Valley companies like ATMs, Chat Control is looking for yet another excuse. However, the "Chat Control" proposal marks the first time consumers across EU nations have faced such uniform pressure. Merely opposing the legislation on privacy grounds is insignificant compared to its stated intent; proponents can completely refute such objections simply by invoking the "it's all for the sake of the children" argument. It seems that, for the sake of the few (or so lot?) children involved, adults across EU are expected to sacrifice everything, including their online privacy, as a matter of course.
Whether it’s continuing to impose more fines on US companies or asserting its own “digital sovereignty”, the EU now wants to do both at the same time.
and sol stands for solana also...
mby a hidden way of boosting worldcoin, who knows
Personally, I think the agenda leads the money and the money is icing on the cake for them. Some might argue it’s the other way around.
Imagine that you life in a fake democracy where the people you elected do not get to dictate the direction of the policy.
Then a body you can't elect wants to keep pushing this through so they can spy on all chat messages.
They keep trying in perpetuety and if the ones accountable to us let it slip through they permanently may force chat apps to integrate spyware and then you can never vote on it again. Once they pass something you can't elect someone to repeal it since whoever you elect does not have that power.
Example
https://npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac.blossom.band/639e826eec6bc7090d8c2ec4ae85e87b81217ab590ad470d6af9fcda32541a6d.jpg
Also, they are being lobbied by a bunch of private donors to do it
they're obsessed with control of everything. and you're picking up on the programming.
Isn’t it obvious? In an age where you no longer control the flow of propaganda; you must be able to control speech and attack it in every way possible so people self-censor.
It’s to squash dissent.
Control.
My experience with other applications was usually just updating the ndkVersion inside build.gradle
Usually doing this in your app solves the issue but sometimes you need to do it inside the library you use also
It's cool. Always sounded like a fusion of japanese and chinese to me.
I don't see the “auth-request: ...”. Is the relay including it in the CLOSED msg?
Everyone will complain and everyone will still buy it
What exactly are you running?
Yes, pick the chars you want then swap while in combat and do combo attacks and so on.
Odin is fantastic! High-performance, manual memory-managed.
https://odin-lang.org
X censors nostr keywords … I tried. Had absolutely zero views on those posts only 😆
Delivered on so many titles
https://nostr.info/resources/ is a nostr client I'm developing, so please report back issues ;)
When ZapStore? Please add your client to https://nostr.info/resources/
Some of the APIs were not designed as well as they should have been. We’re redesigning and refining them with v1.0 in mind (no ETA yet)
And so much easier that freaking zaps
rust is all about rewriting everything tho
Very cool. Don't do nip4e/MLS.. that is never going to be "simple".
I just took a quick look, and I think the problem is that the relays being added with NONE capabilites. This means they can't do anything (neither read nor write).
Unless you want to use specific capabilities, you can omit that argument in addRelay, so they will be added with the default capabilities (READ + WRITE).
Have you a small example to reproduce it?
We just moved our icons to a font for better performance :)
