matt
Matt Corallo

Not sure there’s much else in that post? Only other point you made is that the only other relays are mostly for hobbyists stuff, which I think is mostly true. Don’t disagree so why respond to it :).

2024-11-17 21:03:49 GMT

- reply

Making the assumption that every relay is going to see ~every post is very much not the same as assuming there will only be one relay. You’re just putting words in peoples’ mouths, then.

2024-11-17 19:58:44 GMT

- reply

The comment about relay being an optimization was somewhat nitpicky, you’re just using the wrong term (technically the relay is a proxy between all the PDs’ and the app view, the app view stores all the posts too and you could drop the relay and replace it with the app view(s) connecting to all the PDSs directly).
The “App View” is a server that returns the posts to display in the feed to clients (eg the mobile app). In practice the App View is what *has* to have a full copy of all the tweets, much like a nostr relay works in practice today.
Clients simply making the same request to multiple App Views wouldn’t result in having to rewrite or throw anything away, I have no idea why you’re suggesting that - in general you’ll get the same response from each, just have to merge them on the client side.

2024-11-17 03:13:54 GMT

- reply

The “relay” is an optimization and you can run your own. I think you’re confusing it for the actual data store, which can also run your own though indeed no one does. Maybe your info is out of date?

2024-11-16 19:16:10 GMT

I don’t really understand this kind of criticism (and not to pick on Will here, it seems to be from ~everyone).
Bluesky took a different approach - first build a product people want whose technology supports decentralization, and add the features the geeks want later. It’s easy to shit on their lack of decentralization, but Bluesky has made clear and consistent progress on that front since day one, and I assume they will continue to do so.
The result has been a product that’s growing (those user stats are pretty realistic, doubly so when you look at the number of accounts actually posting real content) way more than nostr with tons of anti-centralization features that nostr is missing (anyone can create a feed algorithm, and there are many, decentralized content tagging is a really cool innovation - different “adult content” tagging services, opt-in different moderation services, etc).
The federated model of Mastodon led to a trainwreck of fiefdoms run by weirdly obsessive and controlling mods, but Bluesky took that and addressed the issues by splitting moderation from hosting.
Sure, Bluesky’s hosting model means you don’t get the relay-redundancy that sets nostr’s censorship resistance apart, but that’s not all that hard to add in the future (with the sync assumption they make making it easier to make efficient, too).
Building the kinds of stuff Bluesky has on nostr is gonna take a huge investment, we can’t leave folks like Will stuck building critical nostr apps by himself. #note1vpt…ann4

2024-11-11 23:46:11 GMT

- reply

And yet it’s growing at a rate that nostr isn’t. Sadly “supports an algorithmic feed” seems to be a pretty important feature if you want users to join a social media platform. Luckily nostr could support such a thing, but we have a lot of catching up to do.

2024-11-06 16:32:53 GMT

Not that Kamala wasn’t a pretty poor candidate or that Trump didn’t generate excitement, of course, but the economy is a *really* strong headwind in any election. Don’t overread the general populace’s desire to “vote crypto” or for any other specific issue. #note1vpz…td56

2024-11-06 16:28:54 GMT

- reply

A lot of the “Trump won because….” takes feel incredibly US-myopic. This was the year of more democratic elections across the world than almost any other and nearly all of them “surprised” in how strongly they voted against the party in power (both left and right). The universal rule of politics remains undefeated - people vote their pocket books.

2024-11-01 02:24:09 GMT

- reply

Memtest doesn’t tend to get your CPU hot, though. Different things can fail at different utilization levels…

2024-10-26 12:40:30 GMT

- reply

#nevent1q…j399

2024-10-26 02:21:10 GMT

One team is led by a fraud who thinks he knows how to handle a sword, the other hires an actor who can dress up in a puppet outfit and convincingly hold a sword. We are not the same. https://image.nostr.build/ebe171cabf0cd2820da3c97d687225246664ea70f15e12417c7264d44c27f356.jpg

2024-10-24 13:00:50 GMT

- reply

Hopefully not on testnets!

2024-10-23 22:11:52 GMT

- reply

Yep, that’s why I didn’t say 1000 sats :). Even 100k sats is a lot for a channel, tho, tbh.

2024-10-23 22:02:03 GMT

- reply

The whole point of testnets is that any amount is equivalent. There’s no reason to ever want a whole or event 1/10th a coin.

2024-10-23 02:40:15 GMT

- reply

You can even make bets on leverage 🎰🎰🎰

2024-10-23 02:39:43 GMT

It’s kinda funny that there’s now legal betting on US election outcomes on CFTC-regulated markets through brokerage accounts but you can’t place the same bets at a casino.

2024-10-22 01:55:37 GMT

- reply

Yea, you can do multisig channels (indeed nested musig) for lightning (well, 66%+1, not 50%+1, sadly), but you’re still doing the “I communicate with some third party over your internet before I pay you for it”.
But, yeah just giving people a tiny bit of internet works fine mostly. Even airplane WiFi with credit cards lets you access DNS before you buy…

2024-10-22 01:51:35 GMT

- reply

It’s just a head-of-line-blocking question, though…I imagine mostly you’re not downloading lots of CSS/JS/images, which is the big head-of-line issue HTTP clients have - they can render the page partially in response to each new item they get off the wire.
I assume you don’t, really, though? You presumably get events back from the server in time-order and populate the page down in time-order, so mostly one event stalling the next won’t make all that much difference in UX?

2024-10-21 12:08:29 GMT

- reply

I mean if you drop the TFO requirement it’s easy - just open many connections. But just fetching many resources isn’t sufficient to want QUIC - you have to be doing so immediately after opening the connection(s), the resources have to be non-trivial in size (think 10s of packets, so the text of a note generally doesn’t qualify) and have a need for not blocking one on another, which is generally not the case on a mobile app - server can send the first three things you need to paint the full window first and then more later.

2024-10-20 11:38:24 GMT

- reply

I think the difference is that with ecash the buyer choose who to trust and only trusts them. With your setup the buyer needs to trust the seller to some extent to use their infra to log into a custodial wallet. I’m not sure that’s a great idea.

2024-10-20 03:17:17 GMT

- reply

Errr avoid the multi-connection (and associated initial small window sizes)/head-of-line-blocking tradeoff.

2024-10-20 03:13:32 GMT

- reply

Note that QUIC is useful on the web for helping to and the multi-connection/head-of-line blocking problem. But if you aren’t fetching a bunch of resources from the same server across different streams where you can use each resource individually on its own this doesn’t apply (and it requires integration work to make it apply).

2024-10-20 03:01:40 GMT

- reply

TLS’ only issues aren’t just CAs being a mess, it’s also an anachronistic protocol that just isn’t how you’d design something today. 1.3 is better, sure, but it carries tons of legacy garbage and most clients still have fallbacks and logic for it.
I also dislike QUIC for being a lazy, poor version of TCP. Middleboxes suck sometimes but sometimes do useful things (eg on a plane TCP is terminated before it goes to the sat, improving latency and throughput compared to UDP things with retransmissions, middleboxes can use MSS clamping to avoid fragmentation, etc). QUIC largely failed to consider these things and just said “screw all middleboxes” (compare to eg tcpinc which got similar encryption properties without being lazy). QUIC exists to rebuild TCP in user-space cause kernels sometimes suck, but for those of us with an operating system newer than five years old that’s not a problem we have. Worse, sometimes your OS has specific useful features (eg MP-TCP) that you don’t want twenty apps to have to rewrite. FFS this is literally the point of having an OS! The only promise QUIC made that isn’t as trivial in TCP is FEC, but they gave up on it cause…I dunno why.

2024-10-20 02:52:51 GMT

- reply

Mmm, right, so doesn’t work noncustodially :/. Also sketchy security :(

2024-10-19 23:55:10 GMT

- reply

That doesn’t allow a payer’s lightning wallet to access the internet, though?

2024-10-19 23:54:30 GMT

- reply

Admittedly I wasn’t really thinking about web apps in the above design though. Nothing specific shouldn’t work except that the spec explicitly says wallets can’t open a callback URI that has a scheme of http(s). I was worried about it being a way for a payee to discover the payers IP, but I think maybe it doesn’t matter.

2024-10-19 23:52:20 GMT

- reply

The web client shouldn’t be fetching the invoice, it just passes the whole offer on to the wallet and asks it to pay. When the wallet completes it does a callback to the initiating app.

2024-10-19 22:27:24 GMT

- reply

I think it’s required. If we’re flipping it to have the nostr zapper broadcast the zap (which we should) you need to cryptographically tie the nostr zapper to the payment proof somehow.
I can see the argument for returning the key explicitly (it’s simple, the initiating app is the payer, kinda), but it feels pretty gross (two copies of a key always bad if you can only have one). Seems cleaner to just pass the message in the original URI?

2024-10-19 22:22:50 GMT

- reply

Better late than never. See the Proof of Payment section at https://github.com/bitcoin/bips/pull/1555/files

2024-10-19 22:13:44 GMT

- reply

No no, for offers. Imagine Nostr app wants to zap using BOLT 12. It does a system open for bitcoin:?lno=lnoffer&pop=proofcallback, but it ultimately needs the proof to include “Bob zapped with emoji🫠”. So either the proofcallback has to include the private key or that original URI has to include the string to sign.

2024-10-19 22:06:37 GMT

- reply

Filtering the Internet such that you can connect to your LSP but nothing else is…hard?

2024-10-19 21:39:10 GMT

- reply

Maybe with some fixed prefix though.

2024-10-19 21:38:54 GMT

- reply

I wonder if the initiating app in BIP 21-replacement should be able to specify that string? Probably…

2024-10-19 21:37:22 GMT

- reply

AFAIR QUIC has the same number of round trips as normal TLS if you set the TCP options right. Basically it shaves off RTs because it begins the TLS handshake in the SYN. You can do that with TCP, too, doubly so if you aren’t using a TLS library that sets socket options for you. The claim in your diagram that you need 0 full RTs to do QUIC setup is nonsense, that’s just if you’ve spoken to the server before and it has cached keys, but the 0 RTT TLS stuff isn’t being implemented in generic HTTP stacks because of replay issues.

2024-10-18 21:46:11 GMT

- reply

I’m incredibly, incredibly skeptical that with the amount of data we’re talking about you can even measure the difference in performance on a LAN, let alone the internet.

2024-10-18 00:33:13 GMT

- reply

TLS is a really bad protocol if your doing something greenfield. Please don’t ever use it unless you’re stuck in the web browser world.

2024-10-17 22:21:12 GMT

- reply

I mean it won’t work in a browser anyway? Noise definitely the way to go if you’re building something without compat, and this won’t get compat anyway

2024-10-14 21:26:17 GMT

- reply

Modern btrfs is fine (more likely to catch a hardware error than lose your data). It was bad like a decade ago but…

2024-10-12 01:29:07 GMT

- reply

Honestly I always take that as my watch insulting my fitness…. And usually it’s right 😭

2024-10-12 01:28:03 GMT

- reply

A short-term PR hit trying to force the UN to leave may or may not be worse for PR than the reports of actions in the field over the following months. One is very short-term and the other is very much not.
But really I guess that’s where we just agree to disagree on priors. Sadly, given the evidence of the last six months, I’m not very confident that the IDF is as conservative on decisions of proportionality or care as they were a decade (or two) ago. All evidence points to even close allies having very serious (non-public) questions on proportionality on a regular basis, and given the civilian leadership (who decide military leadership) for the last decade(ish) I don’t find that particularly surprising :(.

2024-10-11 15:15:07 GMT

- reply

I agree that would be great! But sadly the last decade or so of Bitcoin testnet has demonstrated that people mostly aren’t willing to put on the effort required to do so (which is very substantial!).

2024-10-11 15:12:51 GMT

- reply

Ah, I think the disagreement is more on fundamental analysis of the conflict. I’m not suggesting any kind of ethics analysis, but rather that PR is a *major* component in this war, in a way that it isn’t in most other conflicts. Again, a key goal of organizations which seek to destroy Israel is to reduce their standing in the western world, making it less likely they receive lethal aid in the coming decades (and giving these organizations a bigger fighting chance in a decade). This makes negative PR more than just something that looks bad and much more a key part of this fight, strengthening a proportionality argument for shooting towards UN positions (especially when trying to avoid UN personnel). The IDF absolutely understands this, or at least its leadership does, and academic military analysis has given this some treatment.
This is also why I maintain that Israel has been resoundingly losing its war with Hamas since day one, but that’s a very different discussion.

2024-10-11 15:06:52 GMT

- reply

Wait I understood from your above comment that you were looking for a testnet on which you can test your software with your partners. Where are you currently testing software with “competitors”?
In general it seems testnet fragmented a while ago. All the testing I’ve seen done for a year or so has all been on mutinynet (or more often mainnet lol) 🤷‍♂️.

2024-10-11 15:01:35 GMT

- reply

If you’re running a bunch of testing infra and mostly working with partners, I’d absolutely recommend your own signet!

2024-10-11 14:59:47 GMT

- reply

Ugh, threading sucks. But, sure priors or bias whatever. My point is even given the history of that border and the current statements from the IDF, I don’t see why you take one possible reason as so much more likely that the other here.
#nevent1q…349r

2024-10-11 14:58:25 GMT

- reply

The allegation last time wasn’t that they were specifically “sharing with Hezbollah”, but rather that they were putting it on their website, doing so indirectly. Same net outcome, of course, but I don’t see it on their website today.
You’re, again, assuming that Unfil is interacting directly with Hezbollah to assist them, which is a pretty major assumption. Given there are two perfectly reasonable assumptions here - that or that the IDF does not wish the UN to monitor their actions to prevent them from generating further war reports (given the “anti-Israel bias” the IDF has explicitly alleged the UN has), and given we have no other information or claims from the IDF, I’m still at a total loss for why you’re taking one assumption as almost certain and the other as almost impossible.

2024-10-11 14:51:41 GMT

- reply

I mean that’s literally Unfil’s mandate - to watch what happens so they can encourage both sides to reduce tensions and tell the UN who’s job is to do the same?

2024-10-11 14:50:29 GMT

- reply

Cool! I’m admittedly pretty surprised by that, but…cool! Most of the joint-testing I’ve seen done is on various signets (mutinynet is pretty common, signet og too, etc), and having multiple testnets that different groups use seems fine? The whole point of testnets is that they don’t have value, though…

2024-10-11 14:46:49 GMT

- reply

Yea, that’s an entirely plausible argument for why they’re targeting the UN (but you’d think they’d ask them to stop, assuming they are, first). But you spent ten posts here arguing that “probably they’re sheltering Hezbollah” without any evidence and now jump to another argument because the first didn’t fit the facts.
I’d really strongly recommend you check your biases here.

2024-10-11 14:43:40 GMT

- reply

That is not the only instance they’re talking about. That’s just the new one from today. Here’s three specific instances the UN is objecting to, all from the Guardian article from yesterday. https://image.nostr.build/59b14a3f73dd32ecb9be35a9f3890c5431ac781fe929f277b40dec4c99bb1bf3.jpg https://image.nostr.build/e1352d1c5a75f8cd05feb8922ae13cb8b61461b67b565cbcad36ea1563ba4843.jpg https://image.nostr.build/83cb8200c759a80ec4a7872674de1e14074d3596f69e309c4034256ef4b63074.jpg

2024-10-11 14:40:19 GMT

- reply

That doesn’t mean you’re doing it with a broader community, though? There’s basically zero liquidity in testnet3 lightning (or where there is it’s entirely one-sided). Every time I’ve tried to use it I’ve had to open a direct channel and kinda the only destination is yalls anyway?

2024-10-11 14:09:16 GMT

- reply

Hmm? The IDF comments on lots of specific cases. Not everything, certainly, but when things make big news headlines, I’ve generally seen comments.
Anyway, not sure arguing relative percentages is worth it - I’m still really confused why you are talking a *default* stance of “the IDF is right not the UN” rather than a default stance of “I dunno, could go either way, both stances have reasonable motivation”. I fear you are falling into the “all conflicts must have a good guy and because the other side are obviously not it, Israel must be it, and can do no wrong” fallacy that is all too common in conflicts.

2024-10-11 14:05:44 GMT

- reply

Is it? I’m not really aware of much use of testnet to “interact with others”. Testnet lightning has been totally useless for years, and I’m not really sure what else there is?

2024-10-11 14:04:23 GMT

- reply

Not “intentionally”, just some miners got excited when it was still a PR.

2024-10-11 13:40:21 GMT

- reply

Then we fucked up testnet4, should have premined it so that it’s not scarce, and need to have a testnet5 :)

2024-10-11 12:53:17 GMT

- reply

Asking in IRC, generally 🤷‍♂️

2024-10-11 12:52:54 GMT

- reply

I’m a bit puzzled by your claim here. The IDF has had ample opportunity to respond to these events, and has not claimed that they thought Hezbollah was present at the UN positions in this case. If it were the case that they thought that, by now they absolutely would have, yet you keep bringing it up as a likely reason?
More generally, Unfil has never had a mandate of removing Hezbollah positions in southern Lebanon (that’s the Lebanese army/government’s job, of which there basically isn’t one of either). Their mandate is only to monitor. Their specific mandate is to “allow” everything and tell the UN about it.
I’m frankly puzzled about your arguments here.

2024-10-11 12:02:00 GMT

- reply

Please don’t buy testnet coins. If they get a price, we get testnet5.

2024-10-10 23:11:34 GMT

- reply

Man how have I still not been on the pod.

2024-10-10 21:54:24 GMT

- reply

Also apparently the IDF isn’t even claiming it was an intelligence error? https://image.nostr.build/110e17a8792ef0c9b437a4ffa26e8bb03c2d14baba57eab4884eaa0c98b55154.jpg

2024-10-10 21:48:30 GMT

- reply

Not to mention it follows a week or more of Israel explicitly telling Unfil that they should leave, the idea that commanders may wish to ramp up pressure isn’t unreasonable.

2024-10-10 21:46:34 GMT

- reply

Given the only other observers to the incident are confident it was no accident (and it follows several related incidents), I would not carry a default judgement here. There are absolutely strategic reasons Israel would have to fire on a UN position, even if they’re a bit more tenuous than the reason of “bad intelligence”.
And, yea, I’m sure we’ll never know much more. https://image.nostr.build/c78e3554a1f5bd46ca946ed13dd0a5bad70242fb602154dc01d48daf647c4172.jpg

2024-10-10 20:30:13 GMT

- reply

Satoshi’s doing well, thanks.

2024-10-10 19:13:15 GMT

Long live 58K Gang. Bitcoin is the stablecoin now. #note1nvt…tzrs

2024-10-10 16:57:59 GMT

- reply

I wasn’t claiming at all there’s a winning strategy here, quite the opposite in fact, there we strongly agree. (Maybe “the only winning strategy is not to play”, but of course that’s a losing strategy for Netenyahu, irrespective of how one might play that strategy to the benefit of the Israeli and other people).
I wasn’t referring to the overall volume of coverage, though, but rather coverage of realities on the ground, which is something we get fairly little of (even war journalists have limits). Embedded journalists generally only see really limited stuff (because no one wants an embedded journalist to die, so you limit where you bring them!), so I generally write them off entirely.
Rather the coverage I was referring to would be non-embedded journalists or UN reporting within its own formal channels. Non-embedded journalists have been hit a lot by Israeli troops, though of course it’s hard to tell whether they’re being hit more or less than the average person in active warzones in Gaza.
I wasn’t claiming any specific motivation here, just noting that you made a very large leap with the “well presumably intelligence said Hezbollah was using that site”, when there are many other reasons to strike a site.
Sadly, “just wait” isn’t a realistic approach in this conflict because basically no past event ever gets “resolved” - there’s what the IDF says and what Al Jazeera says and what Hamas says and I have yet to see any followup on anything. Even the “we’re launching an investigation” line we’ve heard from the IDF a handful of times appears to always result in internal investigations and no public comments (I believe with only one exception that I’ve seen). Sadly, public opinion is very much a battlefield in this conflict, much more so than in most others, so I don’t think that’s gonna change.

2024-10-10 15:21:09 GMT

- reply

And maybe much more importantly here is the desire to reduce press coverage. After all one of Hamas’ key aims (less so for Hezbollah, but also there too) is to make Israel look bad on the global stage (to reduce long-term support for them from western militaries). In a war zone there’s always things that look bad, so Israel has strongly preferred to not have press or reporting of their actions on the battlefield.

2024-10-10 15:05:56 GMT

- reply

You make an assumption that the only strategic goals sought are to eliminate actual Hezzbolah positions. It’s probably true, but I definitely wouldn’t say anything more than “probably” given Netenyahu’s domestic political risks and need for continued escalation if he wants to avoid jail for old corruption charges.

2024-10-09 22:49:31 GMT

- reply

Tradeoff, but with Alby the routing is done on the client side so if you self-host they can’t trivially see where the payment is going. They can do timing correlation with other information but that’s a much more involved attack. Sadly, today, Phoenix does routing on the server side so they see the payment destination in the clear.
As for esplora, yea, it’s not ideal, but if you’re using a fixed LSP it doesn’t matter - the LSP knows all your on-chain info anyway, and ideally your payments are lightning so the on-chain information isn’t “the interesting part” (aside from any on-chain setup deposits).

2024-10-07 02:44:58 GMT

- reply

Yes I, a fed, am working hard to undermine an app that no longer functions.

2024-10-07 02:32:09 GMT

- reply

Everyone with any tech chops always wrote off Samorai as a joke. The only reason people weren’t vocal about it is cause of how toxic all the asshats who loved it were. None of this means they should go to prison, but getting charged doesn’t mean you were the best, just the loudest and stupidest.

2024-10-07 02:29:47 GMT

- reply

Fair, Wasabi built something good too, and certainly succeeded in user adoption in a way JoinMarket never did (sadly, though for many reasons), but if we jump to a theoretical world where they both have an equal user base, I know which one I’m picking.

2024-10-07 00:37:24 GMT

- reply

Clearly you just need to commit to give more bitcoin talks at Linux conferences :)

2024-10-07 00:36:23 GMT

JoinMarket remains, by far, the best CoinJoin tech ever built. #note1jju…x4s5

2024-10-04 21:59:51 GMT

- reply

Ah, I guess I was misinformed. FERC allows DC ties without triggering FERC oversight (though it seems like an obvious thing for a future overzealous federal government to change).

2024-10-04 21:29:24 GMT

- reply

Err, sorry FERC.

2024-10-04 21:27:27 GMT

Texas appears to finally submitting to DOE oversight by interconnecting ERCOT with the rest of the country.
https://electrek.co/2024/10/03/hell-froze-over-in-texas-us-grid-first-time/

2024-09-29 19:12:31 GMT

- reply

It’s literally front page news. It’s a big deal, but it’s definitely getting reported lol.