-
@ f03df3d4:a4d4f676
2025-05-19 16:50:33
Block 897430
23 - high priority
15 - medium priority
10 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ e7bf8dad:839ef3db
2025-05-19 16:50:33
Block 897430
23 - high priority
15 - medium priority
10 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ f03df3d4:a4d4f676
2025-05-19 16:45:33
Block 897430
15 - high priority
10 - medium priority
7 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 74ffc51c:1d6d1856
2025-05-19 16:44:20
Clarification of my thoughts and a brief explanation of how I get to where I am currently for anyone interested:
Miners and nodes were originally pretty much the same thing.
They aren't now.
What happens when the incentives of miners and the incentives of nodes become misaligned?
Miners want to get revenue from any source imaginable - stuffing spam into blocks is potentially lucrative.
Nodes of course do not have any immediate incentive to relay this stuff and certainly don't benefit from storing it or competing with it and paying higher transaction fees as a result.
The theme coming from
@darosior
is that Core must do what is incentive compatible for *miners* - i.e pay attention to what it is spammers want to store in the chain and quickly or preemptively adapt Bitcoin Core as quickly as possible to relay this to prevent any large miner soliciting it out-of-band and developing a competitive edge against miners who are "stuck" with the transactions being relayed around the network.
His concern compounds with the idea that if Core fails to do this, it will be unadopted and lose market share to an implementation that does.
However we have seen significant migration away from Core, for perhaps the first time ever, to Knots, which takes a different approach - it concerns itself with the incentives of people running those nodes who, as mentioned, do not wish to be relaying junk data around the network and storing it for free.
So if we are concerning ourselves with the incentive compatibility of Bitcoin Core, why is the incentive the actual users of that software to not participate in spam not a part of the discussion when it is so clearly relevant? Knots has jumped to about 10% of the listening nodes over the course of May from less than 2% before that.
This, I believe, is where the rift between Core and those angry with Core formed because Core's response to this is generally to say that nodes are being short-sighted. Their desire to reject spam is going to undermine more subtle things in the longer term. This was expressed initially in a crude and insulting manner which further deepened the rift but - no matter how much we might want to dismiss them as genius devs somehow missing the forest for the tress - are they correct?
More simply - are nodes doing themselves a disservice by opting out of the relaying of spam in the hopes that at the very least, they aren't participating in the hypershitcoinization of Bitcoin?
How bad are the tradeoffs for nodes if they do this?
1. If Core is "incentive incompatible" (at least with regard to miners/spammers who both clearly want to use Bitcoin to store non-Bitcoin stuff) is there going to be un-adoption of Core?
So far the only un-adoption we have seen is a (from my perspective) a few thousand nodes switching from Core to Knots - this isn't really fakeable like some suggest with AWS because you'd have need to have spun up Core nodes far in advance of this battle in order to send this signal by having them switch.
The "incentive compatible" alternative is Libre Relay - this of course does the opposite of what Knots and its updated filters permit - it preferentially peers with fellow trash-enjoying nodes in what is (to my mind) a misguided effort to fight what they call censorship. Of course I fundamentally believe that censorship resistance doesn't come in the shape of nodes relaying what is against their own interest.
Libre Relay is nowhere near as widely adopted as Knots. So Core, if wanting to maintain marketshare must take more into consideration what has actually happened to Core as a result of its incentive incompatible design (from the perspective of *nodes* rather than *miners*).
They must convince us that Knots users are making a mistake in philosophy, not just more immediate concerns around practicalities and risks of running something that isn't Core. Those are valid of course but let's assume Core and Knots are of equivalent standard and reliability and just focus on differences in approach and design philosophy here as its what is relevant to this discussion.
2. If we filter spam, fee estimation will get worse.
It can get better actually, assuming there is one decently sized miner on the network respecting those filters. There is of course - most of the DATUM miners on OCEAN use Knots with fairly close to default policy so this can prevent you from *overpaying* fees.
The worsening of fee estimation in the other context - accidentally underpaying because there's so much unconfirmed spam that you just aren't aware of - is much easier to correct for. Simple RBF will suffice.
I don't think it's anything anyone can really care about due to the unpredictable nature of the blockchain anyway. You have no idea if you'll be in the next block or not. The extent to which you do is the extent to which we "know" what *should* be in the next block which is basically just an artifact of centralization and a mistaken celebration of that fact.
You don't know who will find the next block, what will be in it, how long it will take, or how many other people are going to jump in "the" queue after you broadcast your transaction. Core's heuristic around fees work well without knowledge of other people's mempools, this is by design. Thus, I have widely asserted that concerns around fee estimation are nonsense with the above reasoning and I have yet to have anyone dunk on me with some superior understanding.
3. Block Propagation will be slower if we filter spam. Mining will centralize in general.
Slower block propagation sucks for small miners trying to be part of the big club as Antoine points out. The big boys will have a private intra-relay network - a walled garden in which you must belong to not be at a disadvantage with necessarily slower verification times.
Firstly - if you filter something that still generally makes its way around the network, you'll cache it and your verification speed will be just as quick as if you didn't filter so this is a non-argument. I genuinely think most people, including Core devs are just unaware of `blockreconstructionextratxn` so they believe there to be an issue that there just isn't.
But what if the filters are so effective that the private club has to solicit this stuff out-of-band and it never existed in the first place to the filtering nodes?
Then I say we are screwed. These miners control the blockchain at that point. We have concerns orders of magnitude more significant. They can reorg the chain, make double spends and generally wreak havoc. The fact that they haven't is not something we can rely on hence the need to actually decentralize mining not just screw around and make a gesture of concern in relaxing spam filters in the hopes that it doesn't get slightly worse.
We are at this point already so I have no idea why we are discussing inconsequential factors such as spam mitigation vs enthusiastic relaying as though it has any relevance here. Foundry can already 51% attack the network.
---------
This is roughly how I end up at my position - being a vocal advocate for putting the incentives of those running nodes over anyone else in the ecosystem. I do not consider spammers to be "Bitcoiners" but even I did, their needs would be always placed further down the food chain than those of nodes. Just as they were with those who wanted huge blocks for permanently cheap transactions.
The rate at which I am having to revise and reevaluate my position has rapidly decreased compared to a few weeks ago where admittedly I was making far more technical inaccuracies than now.
Everything I read from Greg Maxwell or other long standing and respected developers in the space goes along familiar lines at this point and fails to justify this new, laissez-faire approach to spam attacks that carries a heavy burden of proof versus adhering (as Knots does) to Bitcoin's historical precedent where folks none other than Greg himself would propose extreme counter measures to spam should some new protocol for shitcoining-on-bitcoin suddenly hit escape velocity and start creating a genuine problem for Bitcoin nodes.
-
@ f03df3d4:a4d4f676
2025-05-19 16:41:12
Block 897430
10 - high priority
8 - medium priority
6 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ e7bf8dad:839ef3db
2025-05-19 16:40:52
Block 897430
11 - high priority
8 - medium priority
6 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 63fe6318:330504ed
2025-05-19 16:10:07
No major issues so far, i can see performance maybe being an issue soon though the chat can be pretty laggy sometimes
-
@ 63fe6318:330504ed
2025-05-19 15:59:12
Published v0.7.0 of the zap.stream app
## Added
- Show "copied to clipboard" message on iOS
- Badge awards in chat feed
- Badges assigned to users in chat
- Share stream button on stream info modal
- Timeout feature, timeout viewers for x seconds
## Fixed
- Auto raid redirect loop
- Always show open in wallet button
**Full Changelog**: https://github.com/nostrlabs-io/zap-stream-flutter/compare/v0.6.0...v0.7.0
-
@ f03df3d4:a4d4f676
2025-05-19 16:35:33
Block 897430
8 - high priority
6 - medium priority
5 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 63fe6318:330504ed
2025-05-19 12:00:47
Probably build something on top of owncast to publish to nostr
-
@ ee9d979e:3fadff64
2025-05-16 16:41:20
GM folks.
3 days of war room efforts handling outage recovery, likely extending into the weekend... I'm still on it. Managed to squeeze in a couple of interviews and deal with urgent family matters (across countries and continents) in between.
10 years ago, I would have been stressed like there was no tomorrow, barely sleeping the few hours I had, worrying about everything. Not today. I think I'm finally beginning to mature. I'm not trying to control things outside of my reach, or stressing out about imaginary scenarios.
It took me almost 40 years, but I’m finally grasping how to play the game of life. There's a Brazilian saying: "A vida a gente tem que saber levar."
Old folks love this one. It's hard to translate directly into English, because its wisdom and simplicity carry a lot of unspoken meaning. But at its core, it conveys the idea that we need to know how to navigate life and roll with the punches.
If you're going through difficult times right now, know that things eventually fall into place. Live your best life today, regardless of external circumstances. Take care of yourself and your family. Do your best and ignore the noise.
#GM #LifeLessons #KeepRolling #IgnoreTheNoise
-
@ e7bf8dad:839ef3db
2025-05-19 16:30:33
Block 897430
6 - high priority
5 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 63fe6318:330504ed
2025-05-18 10:38:52
What app
-
@ 9c86d775:e02240c9
2025-05-19 16:37:57
This is a lie.
-
@ ee9d979e:3fadff64
2025-05-15 18:25:50
How much will it cost to refit the plane so that Trump can use it as Air Force One? How long will it be used before it needs to be refitted again, once Trump leaves office (assuming he’s not Palpatine and doesn’t just... stay... in power)? Who’s paying for it? I mean, it’ll end up transferred to the "Trump Presidential Library Foundation" (whatever that is), right? It doesn't need to be rigged to do a lot of damage.
-
@ 10aaa39c:b325c2c2
2025-05-19 16:36:51
GM bro
-
@ 63fe6318:330504ed
2025-05-17 16:49:27
Pixel 9 Pro
-
@ cbab7074:f9f0bd61
2025-05-19 16:30:33
Block 897430
6 - high priority
5 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 1ea4ae84:b59a2ae8
2025-05-19 16:50:27
https://image.nostr.build/270c7187fa58a4fe9ef89925bf500ac3401e55843a93abe471658d26e96a906a.jpg
-
@ a34b99f2:c540c5bd
2025-05-19 16:50:24
1947/897430/377214
-
@ 63fe6318:330504ed
2025-05-17 13:21:23
I had reports like this before and told them I am not hosting that content and they never replied
-
@ b7ccd493:6ba2260f
2025-05-19 16:50:22
都要摇旗呐喊让苦难来的猛烈些，快了，有钱赶紧跑！慢了就出不去了
-
@ f03df3d4:a4d4f676
2025-05-19 16:30:33
Block 897430
6 - high priority
5 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ ee9d979e:3fadff64
2025-05-15 18:02:07
Hi, still absolutely screwed with this incident. Sorry folks, hopefully I'll be able to do something fun tomorrow :). Please don't close any of the two PRs yet if possible.
-
@ f03df3d4:a4d4f676
2025-05-19 16:25:33
Block 897430
5 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ f03df3d4:a4d4f676
2025-05-19 16:20:33
Block 897430
4 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 9a664c49:056682aa
2025-05-19 16:50:17
なんでやねん。
https://x.com/you_yokkaichi/status/1924392407333998634?s=46&t=UmIhl5pwyXmJN3IAkvLKTw
-
@ ee9d979e:3fadff64
2025-05-14 13:21:44
Been there, done that 🤣
-
@ 7db2a324:6339be5c
2025-05-19 16:36:34
GM it's morning! Time to greet the day.
-
@ 9c86d775:e02240c9
2025-05-19 16:35:51
I thought we were moving away from fiat.
-
@ ee9d979e:3fadff64
2025-05-14 13:21:18
PS: nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99urf278z, nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hsh2c3z4, apologies for not getting back to you on GitHub just yet. I’ll review the PRs + Commits and work on Blossom stuff as soon as I'm done with the fiat mining stuff.
-
@ 63fe6318:330504ed
2025-05-17 12:14:30
GM
https://nostr.download/291e91d27d817d0ff9f294c780a256e3b19f7b9d19472c6914d936c3c47bf0b0.mp4
-
@ e7bf8dad:839ef3db
2025-05-19 16:20:33
Block 897430
4 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ b133bfc5:49d5789d
2025-05-19 16:15:34
Why does a gpu need an m.2 slot?
nostr:note12s74lqjedxlfdwml5ch84er63r39la2ve96veldcazzh3jdt5j4sjlfey6
-
@ f03df3d4:a4d4f676
2025-05-19 16:15:33
Block 897430
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ e7bf8dad:839ef3db
2025-05-19 16:10:33
Block 897429
5 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 63fe6318:330504ed
2025-05-16 22:01:35
Well that doesnt impact me so I don't really care only that im not being poisoned while walking down the street
-
@ 63fe6318:330504ed
2025-05-16 21:47:47
Also no toxic gases emitted
-
@ c3ae4ad8:e54d46cb
2025-05-19 16:50:17
Been vibe cooking. I got leftover chili with cauliflower rice. What's for lunch where you are?
#foodstr #cooking #keto
https://m.primal.net/QwIj.jpg
-
@ ebb93aa6:7d9e5f6f
2025-05-19 16:33:46
just don't forget me 😜
-
@ f03df3d4:a4d4f676
2025-05-19 16:10:33
Block 897429
5 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ f03df3d4:a4d4f676
2025-05-19 16:05:33
Block 897429
4 - high priority
4 - medium priority
4 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 79fe1cd3:41c2e04f
2025-05-19 16:50:13
You trolled the shit out of Cash app 🤣
-
@ 68c90cf3:99458f5c
2025-05-19 16:33:11
+1 for Bhutan
-
@ ee9d979e:3fadff64
2025-05-14 13:19:04
GA folks. Been stuck in an "emergency war room" since yesterday dealing with outages, the inevitable consequence of cheap devs armed with AI under pressure, while execs and managers pretend their greed and "culture of urgency" had nothing to do with it.
For now, I’ll leave you with Sammy Hagar, Joe Satriani, and friends dreaming about Van Halen!
https://youtu.be/tye-TXrIEN8
#GM
-
@ ee9d979e:3fadff64
2025-05-14 09:44:29
Amethyst is in a good position to set the example... Some users won't like it, but devs are doing it regardless. E.g., nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpr3mhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6tcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7ne6u4e started blocking NIP-04 on Haven 6 months ago. My own build has an obscure flag to re-enable it as there are still laggards using NIP-04 to message me and clients that don't support anything else. If you ask me I wouldn't blame you for removing NIP-04 support from Amethyst at all.
-
@ 63fe6318:330504ed
2025-05-16 16:12:32
Pushed v0.6.0 of the zap.stream app
# Added
- Custom zap amount
- Simple profile editor
- Live running timer on stream info
- Following streams on all stream lists
- Embedded note mentions with note previews
# Fixed
- Hide zap button on chat modal for profile with no lightning address
- Trim chat comments
- Stop video player when navigating off stream page
**Full Changelog**: https://github.com/nostrlabs-io/zap-stream-flutter/compare/v0.5.0...v0.6.0
-
@ 63fe6318:330504ed
2025-05-15 14:10:46
Unique users on nostr.download content (24hrs)
https://npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49.blossom.band/854063f752339560153250aec7341295311ae84c623a3a620ae856a568f58c72.png
-
@ 63fe6318:330504ed
2025-05-14 19:42:51
lol had to add nsec login because no amber on iOS, but I’ll add bunker login later
-
@ f6803bf8:6112b2aa
2025-05-19 16:50:11
One down, 19 to go 😳
#Bitcoin #HosKasi Adi 🫵🏾🇸🇴
https://blossom.primal.net/e40d73ba9a749d4ba7674951a41bf12bee10bfa02d3a0ef2fd0efbd9fcb777ac.jpg
-
@ b1b4105a:19aa52d5
2025-05-19 16:50:00
✄------------ 1:50 ------------✄
-
@ 63fe6318:330504ed
2025-05-14 19:34:28
iOS testflight should be live now
https://testflight.apple.com/join/5Qh7mfvU
nostr:nevent1qqs8wc2g2dk2rq9sgnn97qgz430zwnt292cnhpp3kvc5hf8yd2admtspqqpzqcl7vvvdckzc8nlpdqg0smwsncvtl4m240py5qypec59dues2p8dqvzqqqqqqy4v2j22
-
@ 9c86d775:e02240c9
2025-05-19 16:30:39
Yep.
-
@ 0403c86a:66d3a378
2025-05-19 16:29:15
That's the best Hot take until now 🗽😁
-
@ 12cfc2ec:6967f1d9
2025-05-19 16:03:44
Oddly i was thinking the same thing when i was listening to this last night
-
@ 63fe6318:330504ed
2025-05-14 15:34:18
javascript sucks
-
@ 17538dc2:71ed77c4
2025-05-19 16:00:57
Who are the #linux maxis on nostr?
Creating a Linux following.space follow pack
#asknostr
-
@ cd8de9fd:e4df7e7f
2025-05-19 16:26:47
他没能从这里拉到客户
-
@ 63fe6318:330504ed
2025-05-14 15:28:49
https://www.youtube.com/watch?v=SC2eSujzrUY
-
@ cbab7074:f9f0bd61
2025-05-19 16:00:53
Block 897429
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ bfde2252:6c7b8dc2
2025-05-19 16:24:38
Very good thanks 💪🏻
-
@ 1ae011cb:1257a556
2025-05-19 16:00:33
Block 897429
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ f9bc8797:1e3a4a57
2025-05-19 16:49:55
We can pinpoint the age of 🌍 and the ☀️ to 4.6 billion years is 🤯. By decoding the decay of atoms in ancient rocks & modeling the Sun’s nuclear heart, the timeline of our cosmic origins emerges.
-
@ ee9d979e:3fadff64
2025-05-14 09:28:21
Got it. I mean, NIP-04 is deprecated, but I do understand that losing messages during the transition is bad.
Amethyst is Okay...ish in this regard, although it took me a while to figure out that the spy with a hat thing was a toggle button between NIP-04 and NIP-17 when writing messages.
-
@ 45f195cf:3cab7627
2025-05-19 16:49:54
And we will have new things like that for bitcoin in the future
-
@ ee9d979e:3fadff64
2025-05-14 09:19:42
0xChat?
-
@ 93332f1e:95ae4735
2025-05-19 16:22:43
I use linux.
-
@ ee9d979e:3fadff64
2025-05-13 20:52:12
It's hard to do any sort of sane maths when there are plenty of "unlimited" data contracts around. You have to dig into the small print, fair usage policies, etc. My own contract is one of these "unlimited" ones for £16 per month. I have no idea what the upper limit is, but I know that I once used over 3 TB without any warnings or speed throttling. I don't know if they'd cut me off if I did that regularly, though.
https://www.uswitch.com/mobiles/sim-only-deal/1c09ffba66e232e3589552ca968823e5bf3f720d
As for a more typical "normie" contract, my wife is paying £8 per month for 50 GB, so 16p per GB. If you trust Google's BTC quotation, that's 0.000002 BTC ÷ 0.00000001 = 200 sats.
I don't know how much was lost or added due to FX. Honestly, for my own plan above, it gets dangerously close to "a sat isn't small enough to pay for 1 GB".
-
@ ee9d979e:3fadff64
2025-05-13 14:39:59
Thanks, will do later today. You are very welcome. This is how we build Blossom and Nostr ;).
As usual I'm making a total mess and leaving scattered comments all over the place. So just pointing this one as part of the "Extensions should be mandatory" campaign 🤣.
https://github.com/fiatjaf/khatru/pull/45#issuecomment-2876789665
-
@ e7bf8dad:839ef3db
2025-05-19 16:00:33
Block 897429
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ 63fe6318:330504ed
2025-05-14 13:28:20
Published v.0.4.0 of zap.stream app with todays changes, going to setup iOS testflight today maybe ill drop a link later for that..
# Added
- Chat raids
- Stream info card to display summary / cards
- Follow / Unfollow buttons on stream info card and chat modal card
# Fixed
- Unfocus chat when sending message
- Filter non-hls streams
**Full Changelog**: https://github.com/nostrlabs-io/zap-stream-flutter/compare/v0.3.0...v0.4.0
-
@ 16854972:19596a70
2025-05-19 16:20:49
Looking forward to it, keep us posted, thanks.
-
@ f288a224:1da1792c
2025-05-19 16:49:50
You a rock star Qw 🤙
-
@ f03df3d4:a4d4f676
2025-05-19 16:00:33
Block 897429
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ ae5a910d:23cd8371
2025-05-19 16:49:46
Get nostr address nostr:npub1sma67s58kmv8wxlf7ar4f7v9lny5vv9gsk3f4vyws424r0s75fksx8k6x5
-
@ ee9d979e:3fadff64
2025-05-13 13:05:48
Reposting this here, even though I know it might be an unpopular take on Nostr (since it actually applies some common sense to immigration matters 🤣).
[ANGRY RANT]
Naturalised British citizen here, came through the legal work visa route. I’ve paid enough in taxes, visa fees, NHS surcharge, and more to keep a few of the anti-immigrant crowd on the dole for their entire lifetimes.
I just want to say: making legal immigration to this country even harder than it already is will backfire spectacularly.
When I moved here, I had equally strong job offers in Ireland (where I was living) and Germany. If the 10-year rule for settlement had been in place at the time, I would’ve certainly chosen somewhere else.
And if you're thinking, “Gee, that’s exactly the point!”, then good luck finding a British citizen willing to do what I do (at any salary), and even better luck spreading the tax burden that folks like me have been carrying among yourselves.
Also, the idea that “immigrants are depressing wages” doesn’t apply to skilled workers. If anything, you need to earn well above average just to qualify for a UK work visa. What’s actually going to happen is that companies will move these jobs abroad, where they can still find the skilled people they need.
[/ANGRY RANT]
#UK #Immigration
-
@ cb6cea34:f2a9ed25
2025-05-19 16:18:37
GM friend
-
@ 63fe6318:330504ed
2025-05-14 08:32:27
No, but it makes you wonder if we should be eating these things at all
-
@ ec9bd746:df11a9d0
2025-05-19 15:57:18
I'm not an influencer is just shorter way of saying I'm small, tiny and completely insignificant influencer and my influence is minute.
-
@ 4a93cff3:0471df3b
2025-05-19 16:11:32
#GM FREN HAVE A FABULOUS 🌟 DAY TODAY
-
@ ee9d979e:3fadff64
2025-05-13 10:36:58
Morning nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99urf278z. Many thanks!
Yes, this makes sense. The "default implementation" redirects GET /{sha256}[.ext] to some other URL containing {sha256}[.ext], as per the specs (and I’d love to make the extension non-optional to avoid Content-Type shenanigans, as per my ticket on your repo).
Of course, since Khatru is more of a framework, we need to leave the functionality open to extension, and the user can indeed write a custom handler to redirect to a URL that doesn’t end with {sha256}[.ext]. But I don’t see much that can be done in Khatru to prevent this, other than maybe adding a line or two to the docs asking users to keep the hash intact in redirect URLs.
I had to do some... Interesting things.... on my IPFS POC to accommodate this. I ended up exposing a URL with both a CID and a SHA256 of the blob to conform to both specs. But it's working and blobs can even be mirrored to picky Blossom servers like blossom.band while serving the main blob P2P (proxied to http by a IPFS gateway) :). How cool is that?
As for this sentence from the specs, if I open a small PR making codes 307 and 308 official, would you mind?
> If the endpoints returns a 301 or 302 redirect it MUST redirect to a URL containing the same sha256 hash as the requested blob.
https://github.com/hzrd149/blossom/blob/master/buds/01.md#:~:text=If,blob.
Both status codes also work with GET, and browser behaviour around caching, etc. is way more predictable than with 301 or 302. Also, we’ll need this if we want to properly redirect, say, OPTIONS requests in the future without some of the browsers converting it to GET.
-
@ 17538dc2:71ed77c4
2025-05-19 15:55:43
You mention “In general I like to know what I'm signing”
In your experience, which apps led you to not be sure what you are signing on nostr?
For example, “amethyst and amber signer on android”.
-
@ 63fe6318:330504ed
2025-05-13 17:29:02
Im eating a salt lamp atm
-
@ a012dc82:6458a70d
2025-05-19 16:11:03
Gravity? Inflation? Neither exist when you
-
@ 7776c32d:45558888
2025-05-19 16:49:45
Thanks for the info 🤙
-
@ ee9d979e:3fadff64
2025-05-12 23:18:59
In the UK, it is thankfully dirt cheap. Plus, at least in London, every pothole has free WiFi. Travelling abroad often ends in nasty surprises, though. I think that nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpr3mhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6tcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7ne6u4e’s country 🇨🇦🇨🇦🇨🇦 was the most expensive one I’ve seen so far. Canadian ISPs really like to screw tourists. I paid 80 CAD for a prepaid SIM and data package that would cost about £5 around here. My last trip to Canada was when I learned to research eSIMs before travelling.
-
@ d679b0f4:8229ac9a
2025-05-19 16:49:41
⚡️ats cool!
nostr:note19g2ettdf872n7r64rye5l0gp5w8xlhhm3htz3hwmx3kk9c5p7z0sk926gu
-
@ 4a93cff3:0471df3b
2025-05-19 16:11:02
#GM FREN HAVE A FABULOUS 🌟 DAY TODAY
-
@ ae5a910d:23cd8371
2025-05-19 16:49:41
https://m.primal.net/Lmdx.jpg
https://raw.githubusercontent.com/ray-bun/Twitter_Bitcoin_Lightning_Tipping_Bot/master/memes/19.gif
https://btcforplebs.com/images/btcforplebs_profile.gif
nostr:npub120jgpm9gl7lzwtjeklr7rg9nkty4g7whhgq0u8qz2n5s0fkrca0qlh5qug 🐳 zapped nostr:npub1w4rz7n0vunaau499xh86p84s6v5mmgys48p0nmttt7w36takc9dsf4382j 33,333 sats
💬 Full Send
#fatzaps #zap #nostrzap
-
@ 4a93cff3:0471df3b
2025-05-19 16:10:33
#GM FREN HAVE A FABULOUS 🌟 DAY TODAY
-
@ 4a93cff3:0471df3b
2025-05-19 16:09:52
#GM FREN HAVE A FABULOUS 🌟 DAY TODAY
-
@ f03df3d4:a4d4f676
2025-05-19 15:55:33
Block 897429
3 - high priority
3 - medium priority
3 - low priority
2 - no priority
1 - purging
#bitcoinfees #mempool
-
@ ee9d979e:3fadff64
2025-05-12 22:32:02
nostr:nevent1qqsrv6mqmdyqwc2qqknaq7qmfw88jqwuvtlg9kxut0rac8dp9g2kl7cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxhp4gqj9gyhxfdrqugy2hjgh2ldvapdwpdj9avk7fyemmpa49vacpsgqqqqqqsyzlzl8
#asknostr
-
@ 63fe6318:330504ed
2025-05-13 17:25:21
So if I just east salt directly what am I enhancing the taste of? My mouth?
-
@ 63fe6318:330504ed
2025-05-13 17:22:16
Whats up with salt, some foods have no taste without it... like is it just the salt that tastes good or what?
-
@ 63fe6318:330504ed
2025-05-13 15:31:53
Pushed v0.3.0 of zap.stream app with todays improvements:
# Added
- Stream goals rendering / zapping
- Auto-update stream info (viewers/title) while on stream page
# Changed
- Chat message modal design (Icons open reactions/zaps)
- Performance of stream lists and chat (ListView)
# Fixed
- Login state after restarting app
**Full Changelog**: https://github.com/nostrlabs-io/zap-stream-flutter/compare/v0.2.2...v0.3.0
-
@ ee9d979e:3fadff64
2025-05-12 21:12:17
cc: nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj76n9d3k8jenfwd5zumrpdejqzyrhwden5te0dehhxarj9emkjmn9qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpz4mhxue69uhkg6t5w3hjuur4vghhyetvv9usqg9aft37vl3fjex5jstjycwug5u4ez0kh5h8w3jzudnpyut3m7up75s86zm2 as you were also interested in redirect functionality.
-
@ 2f29aa33:38ac6f13
2025-05-19 16:49:41
Previous cycles: “Bitcoin changes you”
This cycle: “You change Bitcoin”
🤦♂️🤡🌎
-
@ 4a93cff3:0471df3b
2025-05-19 16:09:22
#GM FREN HAVE A FABULOUS 🌟 DAY TODAY
-
@ ec9bd746:df11a9d0
2025-05-19 15:52:36
Which apps for what? I'm sorry this conversation feels a little bit AI-bot-ish.