Avatar
ponymontana💜⚡
3d03c53608415b1d718c7786ee10bdb4e67bced32207e32880ee9e44301a19ec
drastically ungovernable taxes disrespector, ANCAP LIBER*

They never try to be appetible to bitcoiners even for a second, like trezor did doing bitcoin only firmware and releasing foss hardware/firmware for their device. Ledger is the most fiat and shitcoin company I can think of.

I frankly like a lot nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqj9swg4 and I have a lot of hope in it. For the estamp I think it is a clever idea and it will be applied to other things, like public notes and data-blobs.

Another thing I expect is that the estamp-to-message feature will be useful to give some sort of priority to our important chats and messages but that the not-so-important messages will flow mostly free across relays, like most of interactions with notes on nostr arent economic transactions.

nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqj9swg4 why not use existing web-of-trust for managing contacts? If someone really wants ephemerality can always bootstrap a burner-npub, but the default way I think should be npub reuse across clients and so login in keychat trough existing nsec or better trough a signer-app like amber

theres the final "." at the end of the note that breaks the link to github

nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqj9swg4 whats the "fallback" in case I try to message a npub that doesnt have the keychat app (or, in general, in case of incompatibility)?

Because I tried to nip17 a npub from amethyst and I ended broadcasting to relays my clear text private messages, without noticing nothing in UI.

I would have expected a "hard stop", instead of "the other party is not compatible, lets send in clear".

This was very scary, and I'm not willing to try other solution unless problems like that are gone.

jewish dont need to do nothing to please god, god elected them himself and he is pleased just by the fact that they are jewish

Chromium has merged the WebAssembly interpreter submitted by a Microsoft Edge engineer:

https://chromium-review.googlesource.com/c/v8/v8/+/5509903

Once this reaches a Chromium stable release, Vanadium will support WebAssembly by default instead of requiring turning on JS JIT via drop-down site settings. Example of a site using it is Mutiny Wallet.

Chromium has a V8 Optimizer toggle for disabling the 2 optimized tiers of the Just-In-Time (JIT) compiler to greatly reduce attack surface. However, it doesn't disable baseline JIT and therefore still does dynamic native code generation. They did this to avoid breaking Wasm.

In Vanadium, our JIT toggle fully disables the JIT and therefore currently loses Wasm support. An increasing number of sites are depending on Wasm with no fallback to JavaScript. Most of these sites perform perfectly fine with only the fast V8 interpreter and no JIT compilation.

Vanadium has JIT compilation disabled by default as part of the security focus. This Wasm interpreter will be a nice usability improvement for sites depending on it with no fallback code since users won't need to toggle on the JIT compiler for the site unless it performs badly.

no, I rethinked about that, I'm disturbed by the circular bullshit here:

1) my website need to do computationally intensive tasks, so need wasm to do it efficiently.

2) I dont provide a interpret-based fallback becasue I dont intend to provide my service trough it, I choose wasm as a requirement.

3) lets put another giant piece in the chrome codebase just to inefficiently interpret code that is not intended to be interpreted.

I dont think is bad overall that chromium and vanadium adopt it, I think that a code project that add this kind of stuff with this kind of logic is doomed to ever be insecure, frequently zero-dayed, less and less manageble and customizable by third party (and individual users) and a giant pile of uncomprensible garbage.

Chromium is at one more giant new commit to solve the security problem as government is at one more regulation to solve inflation

Chromium has merged the WebAssembly interpreter submitted by a Microsoft Edge engineer:

https://chromium-review.googlesource.com/c/v8/v8/+/5509903

Once this reaches a Chromium stable release, Vanadium will support WebAssembly by default instead of requiring turning on JS JIT via drop-down site settings. Example of a site using it is Mutiny Wallet.

Chromium has a V8 Optimizer toggle for disabling the 2 optimized tiers of the Just-In-Time (JIT) compiler to greatly reduce attack surface. However, it doesn't disable baseline JIT and therefore still does dynamic native code generation. They did this to avoid breaking Wasm.

In Vanadium, our JIT toggle fully disables the JIT and therefore currently loses Wasm support. An increasing number of sites are depending on Wasm with no fallback to JavaScript. Most of these sites perform perfectly fine with only the fast V8 interpreter and no JIT compilation.

Vanadium has JIT compilation disabled by default as part of the security focus. This Wasm interpreter will be a nice usability improvement for sites depending on it with no fallback code since users won't need to toggle on the JIT compiler for the site unless it performs badly.

thats cool

lightning network today works better then monero, I think it makes it totally obsolete.

But I understand other point of views, and that monero, as all things, can be used for good by well informed people.

This doesnt confute my prior statement: newbies are being scammed by monero shitcoiners thinking it has property that makes it usable in the long term and so it is valuable to hold. They will learn the hard way as other shitcoiners, they are not better then ethards for the "muh privacy" meme.