Last Notes
Well shit. Thanks for testing.
Requesting a test zap to new LN address. ⚡
99% of the kind 1984 reports I receive are for events that are not even on my relay.
Added reporting/moderation(NIP-56) to StrfryGUI. It pulls all kind 1984 notes and provides options to mark reviewed, delete event, or ban/nuke pubkey and all events.
This little project is actually becoming useful.
https://github.com/MartialM1nd/strfrygui
https://image.nostr.build/c10acb688e5c015c796a4a3540802558012634b49e32392df2a41fcb5f4afbd9.png
Awesome. You ought to setup a lightning address for zaps!
Block 943483
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943483
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943483
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943483
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943483
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Na Du traust Dich ja was.
😉
Freedom is a road, not a finish line. I do not need to wait until I am fully changed or fully healed before I speak about what has helped me. Even if I have only taken a few real steps, that is already something I can share.
Fear easily keeps me silent. I may think I need to be stronger, clearer, or more consistent before I have the right to say anything. But here the point is different: I am not asked to be a master, only a witness to the little freedom I have already received.
This freedom is not something I produce on my own. My effort matters, my desire matters, and my cooperation matters, but the deeper work is something God does in me. Growing in freedom is not my private achievement, but part of God’s work in my life.
That is why sharing this path can be so simple and so honest. I share because maybe my small piece of lived hope can help someone else take one more step toward freedom.
#lent #12steps #step12
#nevent1q…gqph
If slightly altering future events is creating reality then yes, but that's a stretch tho. The game engine is feeding us the data and we interpret it the best way we can. At this moment in the here and now the separation is useful to make grow happen via the freewill.
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
GM Thursday. And from Canada GN, I'm up far too late 😅
Block 943482
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943482
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
'All models are wrong but some are useful' hits very different today. Have a day. GM
Block 943480
2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Diese Staffel Menschheit lässt wirklich nichts aus. In diesem Sinne Guten Morgen Deutsch-Syrien.
@nprofile…dd2n @nprofile…zxch not all url params are bad xD
Hot Dog Stand, Windows 3.1
https://haven.downisontheup.ca/1b6dfd9ea20a43e9281206f12efbf2bc295742450fb5e51c4b74c98a3e120c05.png
Vorsicht. Dieses Bild zeigt eine digitale Straftat.
https://haven.relayted.de/ebdd8734d06b75907c77bb3eb68d4a1a63d26f7d35483c7fcbe51412382c5c08.png
Gemma 4 :Explosion::white: RELEASED #quantized by many now
#WORD5 #546 4/6
⬛🟪⬛⬛⬛
⬛🟪⬛⬛⬛
🟪🟪⬛⬛⬛
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
Block 943479
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943479
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
So how can we structure such a notification?
The minimum requirement for notifications to make sense is the txid. Then Bob can theoretically find all the relevant information to prove to himself that the notification is legitimate.
But ideally Alice sends more information. In order to fully compute the outputs “from scratch”, Bob needs the previous scriptpubkeys. Those are not within the block data and in most cases are not trivial to retrieve. So Alice should also provide the tweak for the tx. This adds no burden to Alice as she had to compute tweak anyways to compute the output for Bob.
A confirmed blockhash/-height would be very useful for Bob to find the txid faster. This should only be optional though. Providing Bob with the confirming block is going to add a new burden on Alice. Alice then has to monitor the transaction and can only send the notification once she knows the confirming block.
Note: One could also add the relevant outputs to this as well. I’m not certain where I stand on this. The notification and the transaction should be verified. In that process the outputs would be most likely touched anyways. If Merkle proofs were used the confirming height/hash would be required.
Schema
The final content will look something like this:
{
"txid": "5a45ff552ec2193faa2a964f7bbf99574786045f38248ea4a5ca1ff1166a1736",
"tweak": "03464a0fdc066dc95f09ef85794ac86982de71875e513c758188b3f01c09e546fb",
"blockhash": "94e561958b0270a6a0496fa8313712787dcacf91b3d546493aea0e7efce0fc45" // optional
}
*Note that the blockhash is optional and can be omitted by Alice. In that case Bob needs to check what the status of the transaction is.
https://delvingbitcoin.org/t/silent-payments-notifications-via-nostr/2203
#nevent1q…k3pz
Pasting Wordle now works in amethyst @nprofile…2lxp ⭐
Hätte er ein KI generiertes Bild davon gepostet, wie er den Polizisten umbringt. Dann wäre es digitaler Mord. Er würde dann mit der ganzen härte des Gesetzes bestraft.
#Wordle 1,749 3/6*
🟩⬛⬛🟨🟨
🟩⬛🟨🟨🟨
🟩🟩🟩🟩🟩
So how can we structure such a notification?
The minimum requirement for notifications to make sense is the txid. Then Bob can theoretically find all the relevant information to prove to himself that the notification is legitimate.
But ideally Alice sends more information. In order to fully compute the outputs “from scratch”, Bob needs the previous scriptpubkeys. Those are not within the block data and in most cases are not trivial to retrieve. So Alice should also provide the tweak for the tx. This adds no burden to Alice as she had to compute tweak anyways to compute the output for Bob.
A confirmed blockhash/-height would be very useful for Bob to find the txid faster. This should only be optional though. Providing Bob with the confirming block is going to add a new burden on Alice. Alice then has to monitor the transaction and can only send the notification once she knows the confirming block.
Note: One could also add the relevant outputs to this as well. I’m not certain where I stand on this. The notification and the transaction should be verified. In that process the outputs would be most likely touched anyways. If Merkle proofs were used the confirming height/hash would be required.
Schema
The final content will look something like this:
{
"txid": "5a45ff552ec2193faa2a964f7bbf99574786045f38248ea4a5ca1ff1166a1736",
"tweak": "03464a0fdc066dc95f09ef85794ac86982de71875e513c758188b3f01c09e546fb",
"blockhash": "94e561958b0270a6a0496fa8313712787dcacf91b3d546493aea0e7efce0fc45" // optional
}
*Note that the blockhash is optional and can be omitted by Alice. In that case Bob needs to check what the status of the transaction is.
https://delvingbitcoin.org/t/silent-payments-notifications-via-nostr/2203
nost:nevent1qvzqqqqqqypzp0n622gm2vhghyv09hyczjy53gea8cx6qaug6aqk7ua5cag57z8xqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqx3zdpyuzh262slgxqf2evydgfq6jnh27qkdxkj8tufrm88xjuzys8wk3pz
This way zapstore signed the release event, later devs can proof they own the GitHub repo and then take over and sign the packages for that app.
real or not does not matter - what matters is #chrome if u ever give any privileged permission
Block 943478
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
It's mad because peoples' posts on Linked-In Park should be enough to scare anyone off, without all the dystopian shit.
For non play store users
https://github.com/google-ai-edge/gallery
> Every time you open LinkedIn in a Chrome-based browser, LinkedIn’s JavaScript executes a silent scan of your installed browser extensions.
> The scan probes for thousands of specific extensions by ID, collects the results, encrypts them, and transmits them to LinkedIn’s servers.
Block 943477
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
The German Green Party is enjoying their glorious moment of, "I told you so."
Well, you know... They did tell us so.
But I also want my nuclear power station back, buddies. Fair is fair.
👀
https://haven.downisontheup.ca/b9c1400fc8c82481e4660d6654b4c7cbad3def339614198244fad267cc6c92cb.jpg
Nope, not mine either.
Block 943477
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
Block 943477
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
