craigraw

Creator of Sparrow Wallet
GPG: E946 1833 4C67 4B40

Public Key

npub1hea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq6fg9v2

NIP-05 Address

Profile Code

nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3esppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvcrpyfn

Publishing to

nostr.mom

nostr.oxtr.dev

Author Public Key

npub1hea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq6fg9v2

Show more details

Last Notes

2026-05-22 06:14:43 UTC

- reply

Yes - but you will need to index the testnet chain with Frigate, there is no public server yet.

2026-05-21 11:17:51 UTC

Sparrow v2.5.0 released with:
Silent Payments (SP) wallets
SP-capable Frigate public server from 2140.dev
bitview.space fee rates source
https://github.com/sparrowwallet/sparrow/releases/tag/2.5.0
https://sparrowwallet.com/download
https://blossom.primal.net/066a1c4f7d98325c2f9ec6cb6dde74ddf2d37e195ef58bd3ecc1fe1a112fcc35.png

2026-04-15 13:47:44 UTC

- reply

In my view the answer is not to prevent address reuse. Rather, it’s adopting a wallet address system that eliminates it as a possibility.

2026-04-15 12:34:37 UTC

Your anonymity set is much smaller than you think it is. 70% of spendable outputs are sent to previously used addresses. Data by @nprofile…890u.
https://bitview.space/charts/network/addresses/reused/outputs/share/1y
https://blossom.primal.net/1d69cb97d76d52e94f1a406d54d60091c2a68d5c599fc2c0a164ccebb9231e36.png

2026-04-03 07:11:03 UTC

- reply

I measured the scanning performance on Cake, and estimated 2 years of scanning would take around 9 hours.
Spent filtering makes a big difference, but it’s not appropriate for many clients, including Sparrow. Also the BIP approach requires non trivial data download which means making assumptions about bandwidth.
That said there are use cases for the BIP approach, and I’m glad Dana is working on them!

2026-04-01 18:18:23 UTC

- reply

Yes. Almost all CPUs have integrated GPUs. The CPU fallback path is also optimized.

2026-04-01 14:44:32 UTC

Frigate v1.4.0 has been released with significant performance improvements. It’s not just another release though. Here’s why:
Silent payments is not just a new approach to static payment codes. It's the first serious contender to improve the address derivation system since HD wallets in 2013. HD wallets were a big win over single keys, and silent payments could be a similar leap forward.
Why? The first reason is of course static payment codes, which with BIP353 look like ₿[email protected]. A payment system which requires an back-and-forth interaction for every new payment to maintain receiver privacy is archaic, so this is long overdue.
Perhaps more important though is the corollary: address reuse is eliminated. Because every address is calculated using the transaction inputs - which can only be spent once - every address is guaranteed to be unique, addressing the original privacy problem in the whitepaper.
And as a bonus, the gap limit is eliminated too. The gap limit is how far ahead HD wallets look for transactions, and is the reason restoring a wallet can miss transactions if too many addresses were generated without receiving payments.
With these advantages, you might ask why silent payments is not already the default wallet type. The reason lies in an apparently fatal flaw - scanning for received transactions requires significant computation on every transaction that might contain a silent payments output.
Naively this means retrieving every block and performing thousands of computations on it just to see if it has any outputs to your wallet. This is incredibly onerous, and an immediate non-starter.
Fortunately the silent payments BIP suggested an immediate improvement - reducing the information needed from the block to just one public key per transaction. This was a big step forward, reducing each block to about 50-100 kilobytes of data.
It's not enough though. Catching up a few months takes an hour when on mobile it must occur within a few seconds. Users give up quickly, and iOS severely limits background computation. In practice the mobile wallet experience is unusable.
Further, downloading megabytes of data to scan a wallet is too expensive for many mobile users. And most mobile phones don't have nearly enough compute to attempt the scanning within a reasonable time period. I decided to try a different approach: Frigate.
Frigate is an experimental Electrum server for silent payments scanning. In moving the scanning burden to the server, you give up some privacy. But so long as you keep the client data ephemeral (not saved to disk), privacy is similar to that of Electrum servers for HD wallets.
Performance is essential. The fastest way to perform the computation on all the block data is to put it in a database, and then create a custom database function to perform the computation inside the database. This avoids copying it out for every scan.
This was the first step, and it took scanning a few months of blocks from an hour down to a minute. Promising, but not enough - and the server's CPU was saturated, making it less responsive to other requests.
The second step was performing the compute on a GPU. Because every transaction can be scanned independently, a highly parallel pipeline is possible. The GPU computation was implemented as a database function, and brought a few months of scanning down to a handful of seconds.
Just as importantly, the CPU was freed up to do other things. This was again promising, but not enough - it required powerful hardware, and was still only marginally capable enough for a public server. More was required.
The solution lay in optimizing the computation. Optimization typically gives modest improvements, but using a new library (UltrafastSecp256k1) delivered an incredible ~14x improvement in scanning time on the same GPU. A few months of scanning can now be done in half a second.
This is a breakthrough because it makes silent payments wallets on mobile easy. A public server with a few GPUs can handle thousands of connected wallets, and wallets sync immediately.
And it goes further - Frigate supports CUDA, OpenCL and Metal GPU backends. Practically this means most chips produced in the last decade can be used - integrated GPUs, Apple Silicon, and discrete NVIDIA and AMD boards - allowing existing nodes to leverage unused GPU capacity.
Frigate is still experimental. But it proves for the first time that silent payments wallets are practical for widespread adoption. This is not only a long overdue upgrade for Bitcoin wallets, but a significant step forward for privacy.
https://github.com/sparrowwallet/frigate

2026-03-10 09:14:52 UTC

- reply

Sparrow v2.4.2 has been released to fix issues in the transaction editor and improve certificate pinning for TLS connections.
Support has also been added for v3 transactions in the transaction editor.
Changelog here: https://github.com/sparrowwallet/sparrow/releases/tag/2.4.2
https://sparrowwallet.com/download/
#nevent1q…cf58

2026-02-17 08:38:20 UTC

- reply

Sparrow v2.4.1 has been released to fix higher CPU usage on some platforms due to a screen layout issue.
In addition, it's now possible to configure a custom wallets directory by opening a wallet from a non-default location.
Changelog here: https://github.com/sparrowwallet/sparrow/releases/tag/2.4.1
https://sparrowwallet.com/download
#nevent1q…cf58

2026-02-17 05:59:21 UTC

- reply

Sorted, appreciate it

2026-02-10 07:16:41 UTC

Sparrow v2.4.0 released with:
Send to silent payments hardware wallet support
Address display chunking
Wallet discovery for USB hardware wallets
Codex32 support
Trezor Safe 7, Ledger Nano Gen5,
Keycard and Keycard Shell support
https://github.com/sparrowwallet/sparrow/releases/tag/2.4.0
https://sparrowwallet.com/download
https://blossom.primal.net/897bd9b3a40ced86fcfa696cbe3fb260c42c4a60ffc72c3d99f9bdf9640622c9.jpg

2025-12-12 13:55:23 UTC

- reply

Sorted. Thanks for the heads up.

2025-12-12 13:45:22 UTC

- reply

Some wallets (eg Trezor Suite) do not allow you to create a second account if the first one is unused. Sparrow does, however. Otherwise all correct.

2025-12-11 04:57:14 UTC

- reply

You can do it with Sparrow, how much it helps is difficult to say - depends on your threat model.

2025-11-15 16:17:24 UTC

- reply

Agree

2025-11-06 11:25:37 UTC

- reply

Download from https://sparrowwallet.com/download/, verify and install - the method differs depending on your OS

2025-11-06 11:06:00 UTC

- reply

Just added in v2.3.1

2025-11-06 11:05:31 UTC

- reply

Best to update for that, currency rate providers change APIs

2025-11-06 10:50:52 UTC

- reply

Sparrow v2.3.1 has been released to restore BIP32 derivations for consolidation payments in PSBTs.
In addition, hiding amounts is now supported, and the keystores that signed a multisig transaction are now shown on the transaction tab.
Changelog here: https://github.com/sparrowwallet/sparrow/releases/tag/2.3.1
#nevent1q…gzzk

2025-10-31 15:46:12 UTC

Frigate v1.2.0 has been released.
Frigate is an experimental Electrum server testing efficient Silent Payments scanning with ephemeral keys.
The major feature in this release is GPU acceleration of the cryptographic computation required for Silent Payments scanning. This provides a dramatic (over 10x) performance improvement over CPU computation, and makes a public Silent Payments Electrum server a practical reality for the first time.
To learn more, see https://github.com/sparrowwallet/frigate

2025-10-03 10:14:55 UTC

- reply

Silent payment addresses are a new form of static payment address, where the actual bitcoin address that you send to is determined from both the silent payment address and the transaction inputs.
This means you can pay to the same silent payments address while ensuring bitcoin addresses are never reused. This both simplifies the payment experience and makes it more private, at the cost of increasing the burden on the recipient to scan incoming transactions for their payments.

2025-10-03 10:00:10 UTC

Sparrow v2.3.0 released with:
Send to Silent Payments
Pay to DNS address
Min fee rate from server
And more: https://github.com/sparrowwallet/sparrow/releases/tag/2.3.0
https://sparrowwallet.com/download/
https://blossom.primal.net/22b9ebb4fa588cb2229cf0b014fdf1c6c4ebae7c91f4bce23c2c55924c08a63c.jpg

2025-09-09 18:45:07 UTC

- reply

Yes 👍

2025-09-09 15:15:56 UTC

- reply

I’m aware. Unfortunately it’s almost impossible to choose an English name which is not already used in a software project somewhere.

2025-09-09 14:12:28 UTC

Announcing Frigate.
Frigate is an experimental Electrum server testing efficient Silent Payments scanning with ephemeral client keys.
Note that Frigate is currently a proof of concept for supporting Silent Payments on Electrum servers, and not a replacement for Electrs, Fulcrum etc.
If you are a developer interested in exploring Silent Payments scanning, check out https://github.com/sparrowwallet/frigate

2025-06-10 06:59:41 UTC

- reply

Sparrow v2.2.3 has been released to fix some issues scanning QR codes on Linux, and includes other minor improvements.
Release notes: https://github.com/sparrowwallet/sparrow/releases/tag/2.2.3
#nevent1q…mcjs

2025-05-22 12:56:24 UTC

- reply

Sparrow v2.2.2 has been released to fix a minor issue introduced in v2.2.1 when creating a wallet on a new installation.
Release notes: https://github.com/sparrowwallet/sparrow/releases/tag/2.2.2
nevent1qqszm2pjnt464tu242awrwkyvqgt590rvsf2lk7lgj0glpae0ts0eps8xmcjs

2025-05-21 10:04:48 UTC

- reply

Sparrow v2.2.1 has been released to fix an issue starting Tor on recent macOS versions, as well as other minor fixes.
Release notes: https://github.com/sparrowwallet/sparrow/releases/tag/2.2.1
nevent1qqszm2pjnt464tu242awrwkyvqgt590rvsf2lk7lgj0glpae0ts0eps8xmcjs

2025-05-20 08:55:05 UTC

Sparrow v2.2.0 released with:
• Recent Blocks view
• Improved camera support
• Dark mode improvements
And much more: https://github.com/sparrowwallet/sparrow/releases/tag/2.2.0
https://blossom.primal.net/b1542e8a86802d105266ecffbf7bbb935d83a3c63ec9b0a16bc9c1919fceb297.png

2025-04-06 12:12:37 UTC

- reply

It’s fine. There is a chance of address reuse if you hand out a change address to someone and they use it after the wallet has already used it for change.

2025-02-28 04:55:13 UTC

- reply

You have to import the wallet over USB first.

2025-02-27 16:01:18 UTC

- reply

Open a Github issue.

2025-02-27 10:44:01 UTC

Sparrow v2.1.3 has been released with OneKey hardware wallet support, expanded wallet labels (BIP329) export, and some remaining Lark integration fixes.
Release notes: https://github.com/sparrowwallet/sparrow/releases/tag/2.1.3
Download: https://sparrowwallet.com/download/

2025-02-08 14:03:22 UTC

Sparrow v2.1.2 has been released to fix a bug with transaction file loading, and signing on older Ledger devices.
https://sparrowwallet.com/download/
#note1sd7…yju0

2025-02-04 20:31:39 UTC

Sparrow v2.1.1 has been released to fix a technical issue when scanning for USB hardware wallets on certain macOS devices.
https://sparrowwallet.com/download/
#note1sd7…yju0

2025-02-04 11:53:11 UTC

Sparrow v2.1.0 released with:
• Lark for USB hardware wallets
• Ledger multisig wallet registration save
• Jade Plus USB support
• Restore tables sort & sizing on wallet load
• PSBTv2 support
And much more: https://github.com/sparrowwallet/sparrow/releases/tag/2.1.0
http://sparrowwallet.com/download/

2024-12-09 13:49:04 UTC

- reply

I’m not aware of a published issue. But entropy quality is to some extent a scale, and there have been reports of funds lost from early hardware wallets that are difficult to explain by other means. I’d love to see more rigorous review of hardware wallet entropy.

2024-12-09 08:22:47 UTC

- reply

Glad you enjoyed it :)
I don’t agree with this absolute statement though - there are many factors in security. For example, it is entirely possible for a hardware wallet to have poorer entropy (for seed generation) than a software wallet, and it is in general harder to evaluate hardware wallets on this criterion.

2024-12-03 16:10:26 UTC

- reply

Yes - thanks

2024-12-03 12:04:21 UTC

- reply

Yes. It should already “just work” but this will make it work better.

2024-12-03 09:59:57 UTC

Introducing Lark.
Lark is a Java port of HWI, a library used by many wallets to communicate over USB with with hardware wallets like @npub19ca…qj29 , Ledger, Trezor, @npub1tg7…cxmt and @npub1jg5…6n8n Jade.
HWI is a good example of the ‘single dependency’ situation in the famous xkcd comic. Until now, there has been no project like it.
However, with all the wealth stored on hardware wallets (especially those that can only communicate over USB) it's important to have multiple implementations. Lark represents the first complete reimplementation of all common USB HWW clients in a language other than Python.
Even though HWW manufacturers have used a dizzying array of different communication protocols and standards, Lark seeks to be identical to the HWI API, providing direct interchangeability and a more robust ecosystem.
All common commands are supported, and there is some additional functionality, such as retrieving a wallet registration from Ledger devices to avoid re-registration on every signing.
Lark is available as a command line application, and as a Java library for JVM-based applications. Hardware wallet manufacturers are invited to test their devices before it's integrated into Sparrow Wallet.
See https://github.com/sparrowwallet/larkapp for docs and binaries.
https://m.primal.net/Mmkq.jpg

2024-09-18 13:23:18 UTC

- reply

Java is one of the most popular languages for open source development, but specifically it has an open source native desktop GUI framework which is modern, cross platform, mature, and well maintained (unlike most other languages).

2024-09-18 12:43:23 UTC

Sparrow v2.0.0 released with:
SLIP39 shares recovery
Trezor Safe 5 support
Ledger Stax and Flex support
Update to Java and JavaFX 22
And more: https://github.com/sparrowwallet/sparrow/releases/tag/2.0.0
https://sparrowwallet.com/download/

2024-08-21 05:27:16 UTC

- reply

🙏

2024-07-22 06:35:18 UTC

- reply

It’s part of the sparrow repo - see the com.sparrowwallet.sparrow.terminal package. Nice project btw!

2024-07-21 06:50:14 UTC

- reply

Creating a new wallet and selecting the different script type is the easiest approach. Note that Nested Segwit should be considered a legacy script type though - Native Segwit offers better privacy.

2024-07-21 06:47:52 UTC

- reply

You can do this if you create the new account with a watch only keystore, but I haven’t seen a compelling reason to add this as a general feature.

2024-06-21 14:07:38 UTC

It is a flaw of the deeply self-interested men of the world that they assume that idealists are fools.
- Christian Cameron

2024-05-14 09:30:09 UTC

Sparrow v1.9.1 released with:
Testnet4 network support
Increase gap limit to sign
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.9.1
https://sparrowwallet.com/download/

2024-04-25 15:16:03 UTC

In light of recent developments, Sparrow v1.9.0 has been released which removes the Whirlpool client and other Soroban related features. All wallets and accounts are still accessible.
https://sparrowwallet.com/download/

2024-04-24 09:25:25 UTC

Sparrow v1.8.6 released with:
Wallet search improvements
All open wallets summary
Mix from Postmix
Import Samourai backup file
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.6
https://sparrowwallet.com/download/

2024-04-11 11:30:47 UTC

Sparrow v1.8.5 released with:
Whirlpool over decentralized Soroban
Restart in different Home Folder
Faster initial server connections
Upgrade to HWI 3.0.0
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.5
https://sparrowwallet.com/download/

2024-04-10 07:57:27 UTC

- reply

Correct. I haven’t yet heard of a good reason to expose them that would justify the additional risk.

2024-03-29 16:01:37 UTC

- reply

Could be a driver issue. See https://help.blockstream.com/hc/en-us/articles/900005443223-Fix-issues-connecting-Jade-via-USB

2024-03-07 18:49:56 UTC

Sparrow v1.8.4 has been released to fix a build issue affecting Sparrow Terminal. The normal desktop app is unaffected.
That said, for those who already upgraded to v1.8.3, it's a good opportunity to test the Download Verifier :)

2024-03-06 17:21:21 UTC

- reply

Hard refresh :)

2024-03-06 14:16:48 UTC

Sparrow v1.8.3 released with:
PGP download file verifier
Coldcard Q1 support
Trezor Safe 3 support
Improved QR reading
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.3
https://sparrowwallet.com/download/ https://image.nostr.build/dd9ad8e9ad16b81e4b1638d76cad23e7c094d6314e9773605188297a375f524f.png

2024-03-03 11:53:14 UTC

If you are ever in South Africa, a visit to Bitcoin Ekasi in Mossel Bay is well worth it! #note1zmu…teu8

2024-01-18 10:57:44 UTC

Sparrow v1.8.2 released with:
Improved transaction tree
Quicker transaction tab loading
Reduced rescans on Bitcoin Core
Effective fee rate for CPFP
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.2
https://sparrowwallet.com/download/

2024-01-16 11:02:01 UTC

- reply

1. Check out the most recent Sparrow release. 2. SeedSigner is providing very minimal, arguably incomplete PSBTs so without another PSBT to combine with (as would be the case with that function) Sparrow doesn’t have enough information to load them on their own.

2023-11-28 05:01:36 UTC

- reply

Fwiw I don’t think any dependencies are required for BC UR if you limit the scope of data types. Not even CBOR is required if you just transmit txs and psbts.
Would like to see a clearer, technical explanation of why it’s so problematic to implement.

2023-11-22 16:37:32 UTC

- reply

No, but it would be interesting 🤔

2023-11-22 09:55:05 UTC

Sparrow v1.8.1 released with:
Fee rate estimation from oxt.me
Export transactions with historical values
Wider range in fee range slider
And more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.1
https://sparrowwallet.com/download/

2023-11-18 17:44:16 UTC

- reply

Yep should work…

2023-11-09 12:28:44 UTC

Sparrow v1.8.0 released with:
Transaction diagram captions
Larger and denser QR display
Search all open wallets
Airgapped message signing
Satochip and Krux support
And much more: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.0
https://sparrowwallet.com/download/

2023-09-09 13:35:55 UTC

- reply

Thank you!

2023-09-09 13:35:18 UTC

- reply

There is certainly an argument for this - it really depends on whether the change is really doxxic or not.

2023-09-01 05:58:00 UTC

- reply

Try turning off Prevent Computer Sleep in the Tools menu. There are other applications you can use to achieve this functionality, or better yet run Sparrow Terminal for background mixing without the need to keep your desktop awake.

2023-08-31 11:34:20 UTC

Sparrow v1.7.9 released with:
Wallet accounts summary dialog
Keystore labels in descriptor QRs
Rename labelled UTXOs by changing matching related transaction labels
HWI v2.3.1
More: https://github.com/sparrowwallet/sparrow/releases/tag/1.7.9
https://sparrowwallet.com/download/

2023-08-24 05:39:29 UTC

- reply

Yes, just increase the gap limit. Settings > Advanced, then close and click Apply.

2023-08-14 05:48:22 UTC

- reply

Hey Emmanuel. Yes, OpenIMAJGrabber is still used for the native webcam capture. Zbar is just doing QR recognition.

2023-07-18 15:38:30 UTC

- reply

I think you’ll be pleasantly surprised.

2023-07-18 14:28:49 UTC

Sparrow v1.7.8 released with:
Taproot message signing (BIP322)
Improved QR scan performance
Rename wallet support
RBF with initial minimum fee set
More: https://github.com/sparrowwallet/sparrow/releases/tag/1.7.8
https://sparrowwallet.com/download/

2023-06-22 11:16:51 UTC

- reply

My new desktop background

2023-06-22 11:00:18 UTC

- reply

Amazing! 👏👏👏

2023-06-22 10:52:47 UTC

Sparrow v1.7.7 released with:
Improved mempool fee rates chart
Multiple improvements for a high fee environment
Performance optimizations for large wallets
Better usability on @BorderWallets grids
More: https://github.com/sparrowwallet/sparrow/releases/tag/1.7.7
Download at https://sparrowwallet.com/download/

2023-06-17 06:05:55 UTC

- reply

What is the exact error? Best to ask on the Telegram group https://t.me/SparrowWallet

2023-06-06 06:00:18 UTC

- reply

The other groups are scams. What’s your TG username?

2023-05-14 13:40:40 UTC

- reply

Dojo is unrelated to the Whirlpool coordinator - it’s the server app/protocol that Samourai uses to load wallets.

2023-04-27 17:14:40 UTC

- reply

Maybe all accounts in a wallet would be a better idea - I believe there is an open issue for this

2023-04-05 05:19:48 UTC

- reply

Fresh install - there’s no auto update

2023-04-04 15:28:18 UTC

Sparrow v1.7.4 released with:
Border Wallets support for memorizable seeds
Bundled Tor updated on all platforms
Autosuggest last BIP39 word
Darker dark mode
Download: https://sparrowwallet.com/download/
Release notes: https://github.com/sparrowwallet/sparrow/releases/tag/1.7.4
https://nostr.build/i/nostr.build_deb493d7aef9a914b7d59378205547b1796f71ed6617552d3b551661532f7c85.jpg

2023-03-08 13:08:51 UTC

An alternative to Tor that has users stream sats to pay relays seems like an obvious next step in network level privacy tools. Streaming sats would greatly increase the costs of the DDOS-style attacks that affect Tor so much, and provide an incentive for relay operators.

2023-03-01 08:37:41 UTC

Sparrow v1.7.3 released with:
Bitcoin Secure Multisig Setup (BSMS) import and export
Configure an external block explorer to view transactions
Upgrade to HWI 2.2.1
More: https://github.com/sparrowwallet/sparrow/releases/tag/1.7.3

2023-02-28 11:49:13 UTC

- reply

Correct, if you’re using the Bitcoin Core server option. You’d need to delete the Core wallet as well, called sparrow or cormorant.

2023-02-25 20:47:50 UTC

- reply

Will check it out 👍

2023-02-25 20:46:27 UTC

- reply

Sure, that’s true. We’ll have to see if the pros outweigh the cons.

2023-02-24 13:22:17 UTC

- reply

Yep, it’s not too far off now, but unsure if it will see much adoption tbh. The need to do two rounds with each signer is a major downside, particularly if they are geographically remote.

2023-02-15 18:39:01 UTC

- reply

Done! Thanks for the heads up

2023-02-15 13:53:41 UTC

- reply

Thanks - my current desktop pic 😁

2023-02-15 13:02:21 UTC

- reply

Likely routing failure then. I’ll open up some more channels.

2023-02-15 12:59:23 UTC

- reply

I wonder - it seems his work was so fundamental it was hidden from most web developers by being included as a dependency in other higher level projects.

2023-02-15 12:56:11 UTC

- reply

Made a minor change to btcpayserver, it may help.

2023-02-15 12:49:25 UTC

- reply

Nah, I suspect he derived personal significance and value from doing the work. Clearly (IMO) he valued that too highly, but I do understand it - when your work has such broad impact on the world, it’s hard to keep perspective with other more mundane matters in life.

2023-02-15 12:18:59 UTC

- reply

No plans, sorry

2023-02-15 12:17:53 UTC

Thanks for the welcome all! Good to be here.

2023-02-15 12:16:07 UTC

- reply

Hey, thanks for the donation. Not sure what’s up, it’s working on my side using Zeus. What app are you using?

2023-02-15 07:45:14 UTC

This hits hard: https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md