Object Appears at Wolf Creek Pass (S) FAA Camera
https://ia800101.us.archive.org/7/items/xsited-Q0V16oP1SJY/Q0V16oP1SJY.mp4
https://weathercams.faa.gov/map/-107.59166,36.88187,-105.25294,37.8261/cameraSite/97/details/camera/11943/loop


My talk on the past, present, and future of nostr is online.

https://youtu.be/XUsk7cqZyKU


cosmicpsyop

defy conformity, rebel against the system, and  be thankful


Buenos días...

https://nostr.build/i/nostr.build_66acc8e9417f139630f00d78730d9660b74f339895c28688ed02a2327af56b84.jpeg


i appreciate the sentiment.  it is not you it is me and the primary reason i went down that winding road of non-custodial lightning.   first custodial wallet was disabled due to jurisdictional issues.  and after searching through some notes just now this one has decided to pack it in.  probably not the only one and fitting for my travel log.


C/C++ developers: noscrypt v0.1.4 just released (minor bug fixes)

noscrypt is a mostly portable C library that simplifies nostr specific cryptographic operations into a high level api, such as signing, verification, and of course encryption, without getting in your way. noscrypt is also the reference C implementation of nip44!

https://github.com/VnUgE/noscrypt/releases/tag/v0.1.4


traveled that road.  scales payments for sure,  but not users.  self custody lightning is tough and a bit chewy.  🙂


nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx  in the most recent nostr:npub10uthwp4ddc9w5adfuv69m8la4enkwma07fymuetmt93htcww6wgs55xdlq you spend a few minutes addressing accusations regarding your integrity around simultaneously supporting nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl and having a vested financial interest in the success of Cold Card. You said the SeedSigner project is “incredibly important” but continue in the same breath to deny they are competitors and described SeedSigner as only reasonable to be used as a fallback if we lived in a world where devices like Cold Card don’t exist. Far from an endorsement.

You have historically supported the SeedSigner project and I appreciate the support. There’s 100+ ways the SeedSigner project could be better. Your most notable grievance of SeedSigner seems to be solely focused on physical security attributes when comparing the two air gapped Bitcoin signing devices. Specifically you don’t like that SeedSigner doesn’t have a secure element.

Secure elements are great tech, but you never cover the actual trade offs on RHR. You gloss over how Cold Card is verifying firmware at boot on behalf of the user. You don’t discuss the trade offs at all. The verification of firmware at boot on a Cold Card requires trust in Coinkite. The user isn’t verifying, Coinkite is. You also make it sound like it’s an impossible task to verify firmware for SeedSigner.

IMO you’re getting sucked into stupid polarizing debates around Cold Card vs SeedSigner. I think Cold Card and SeedSigner are both great in their own ways. They make different trade offs and actually complement each other really well in a multisig setup with Sparrow Wallet. I personally have no issue with you recommending a Cold Card over a SeedSigner if you prefer the trade offs. Totally reasonable if you asked me. It’s way more important people self custody Bitcoin using cold storage.


Thank you nostr:nprofile1qqsfc93uwdgl3qetpz6kewewp9vkp5w9qcxadv8yv85p8u8sw3v3r8spr3mhxue69uhkummnw3ez6ur4vgh8xetdd9ek7mpwv3jhvtcprdmhxue69uhkummnw3ezummjv9hxwetsd9kxctnyv4mz7qgewaehxw309aex2mrp0yhxummnw3exjcmp9e3k7mf0zeg2qy for this incredible conference. Nostr sparked a movement I was searching for well over a decade. It really does feel like we're taking back the Internet, one app at a time.

Stack sats, seed torrents, run relays, zap nuts, open PRs. Here is my humble contribution to this amazing event. The image says "wicked". 🫡
 https://image.nostr.build/40657caea0c979a521b0de3b46bebac969f7f421c379da48fb1c6ef0c14c7ffc.jpg

🎥👇

https://youtu.be/OHqxp-Hrx9k


https://youtu.be/PWKd9aoZ-Cg?si=GUM-x5R9nhma6G85
This is gold.
Thanks nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc


Just read the "Dark Skippy" attack ( darkskippy.com ) from Lloyd Fournier and Robin Linux (h/t Alex Waltz). Nice write up! I've always thought it should be simpler than grinding, though (but the grinding in that attack is very practical). I feel like a variant of what they call 'predetermined nonce attack' on that page could work. If I make a *big* assumption - that the attacker has access to the victim's wallet's xpub - then I think you can extract the master secret from only 1 signature or 2 signatures, without any grinding or pollard rho. With 2 signatures the full master secret of the wallet; with 1, only the xpriv for the (BIP32) account (so compromises only 1 account; but many wallets just use one account anyway!).

Let's see if there's any error in these steps:

1. Attacker uses RNG to generate sequence of 32 byte randoms (b1, b2  ..)

2. First signature that the client requests is generated using b1 as nonce. hence attacker can obviously extract the secret key x1 = (s1 - b1) / e1.

3. We have to assume knowledge of xpub. Given xpub and one private key (x1) from the account branch, then due to unhardened derivation, we can already derive the xpriv for the account (though not for the level above; so this is equivalent to master secret, only for single-account wallets, not for multiple account).

But if we have access to 2 signatures we can exfiltrate anything, including the full master secret:

4. Second signature that the client requests, on (currently unknown) private key x2, is generated using nonce = (b2 + master secret), which is still indistinguishable from random because b2 is. Here we need the xpriv as per above to regenerate (poss. by trial and error, but that's trivial) the correct x2 given the above xpriv derivation. Then attacker extracts master secret = s2 - b2 -ex2.

(Am I wrong somewhere there? Wouldn't be too surprised. But either way, exfiltration via these channels *one way or another* seems like it's very hard to prevent. (I know there *are* anti-exfil measures in existence, so please don't take this as me dismissing them - I haven't even really studied them!).To generate bitcoin signatures on serious amount, use the software that's as easy as possible to vet and has the least layers between your eyes and it .. is my extremely unconventional advice on this topic).


The shutdown of Mutiny Wallet is a result of many factors; directly it was a result of the backbone of the wallet being fundamentally broken at a self-custodial level, and indirectly a result of increasing criminalization of privacy in a world where it is both personally and professionally disregarded.

I am not a Bitcoin maxi, and have never labelled myself as such for the sole reason of knowing better. Bitcoin is better money, and is something I actively want to be adopted, yet I know it is something that can actively be improved upon. The argument for not increasing the block size was always a disingenuous one, as Bitcoin was initially introduced without any block size limits, and one was only created due to early technical issues which have long been resolved; the hatred for Bitcoin Cash was always one born from bruised egos and the admittedly unscrupulous actions of Roger Ver surrounding the .com domain for Bitcoin among other things.

It showed that raising the block size wouldn't immediately result in the centralization of mining pools, or push individual validators out of downloading and verifying transactions on the blockchain. With that being said, Lightning was conceptualized two years before the SegWit split occurred and thus its eventual realization cannot be attributed to Bitcoin Cash; what it CAN be attributed to is its accelerated development.

Lightning is a piece of shit.
At a fundamental level, it was always a band-aid solution to Bitcoin's early block size restraints that no one wanted to revoke after Satoshi's disappearance (which also had a knock-back effect of reducing its natural scalability), despite the 1 MB restriction clearly being introduced as a temporary measure meant to reduce the potential of double spending and a bloated blockchain size similar to that of CSW's Shitoshi's Venture (SV) shitcoin; with very few exceptions which have their own problems depending on the SDK used, it is near impossible to make reliably self-custodial Lightning wallets that don't have their own issues.

Custodial wallets and services obfuscate from users liquidity management, issues underpinning what software is used to power Lightning functionality (LND, Core Lightning, Eclair, etc.) and the necessity of being online at all times; whereas developments in transacting with on-chain Bitcoin have been somewhat realized, very little offline Lightning solutions have even been conceptualized owing to its off-chain nature requiring distinct ways of transactional verification.

It is also a band-aid on a far bigger issue, depending on who you ask, which is Bitcoin's absolute transparency.

Monero was created in the aftermath of Ross Ulbricht's example-making persecution by the United Territories of Israel's government, as no deep/darknet user wanted to experience the level of deanonymization that Dread Pirate Roberts had been subjected to, and wanted to transact with a currency that would guarantee full anonymity whether it be for complicit or illicit purposes. Various voices in the Bitcoin scene that don't immediately write Monero off as a shitcoin (while ironically doing the same for Cash) have proposed taking what Monero does right and gradually implement it on-chain, just to be met derisively either with "Lighting exists, and is better" (it's not) or claims that making Bitcoin more private would result in its crackdown and criminal persecution of anyone using it, which further adds to the fact that Bitcoin's largest problem (yes, more than the corporate influence of Blockstream and deliberately rigid philosophical dichotomy) has been the community's perception around privacy.

Privacy is an absolute human right, and I see it as no coincidence that every effort made to improve Bitcoin's anonymous viability by a group or individual (regardless of my feelings on said software being a band-aid on top of others obscuring larger issues) has resulted in maximum federal persecution towards those daring to get Bitcoin even a quarter closer to where Monero is (which has resulted in it only being able to be obtained through mining or DEX's).

Despite my positions likely going to lead to pushback from those who insist that Bitcoin is absolutely perfect as is, and that I'm a filthy shitcoiner who shouldn't have an opinion on anything, I want to thank  nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv for creating the easiest self-custodial Lightning wallet to exist and for hosting your company's version of it as long as you did; it was what introduced my younger brother and girlfriend to self-custody and the bright spots of Lightning when it all clicks and DOESN'T lead to financial loss (still bitter about that,  nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 lol), and its app store independent nature allowing the focus to be on making the wallet better rather than capitulating to companies that can both fuck off as far as I'm concerned allowed Mutiny to become THE hub for Bitcoin's future developments in admittedly contentious areas like Cashu that has its ardent supporters.

May the best come to you, and continue to come to sound magic money.
nostr:note1mnyfl9hjck35mw67hd659j6a2gxltmyhzq684lm99xnf6wzyeunsh33fy8


Airport Facial Scans Now Standard
https://ia601502.us.archive.org/5/items/xsited-TKL230985/airportfacial.mp4


The road to Terminator Skynet is complete
https://www.vox.com/future-perfect/360952/summer-travel-airport-facial-recognition-scan
https://www.techspot.com/news/96871-tsa-ready-nationwide-deployment-facial-recognition-system.html
https://www.tsa.gov/news/press/factsheets/facial-recognition-technology
https://www.washingtonpost.com/technology/2022/12/02/tsa-security-face-recognition/
https://www.yahoo.com/news/tsa-now-photo-fly-why-230007498.html


counter culture https://image.nostr.build/89ebe179823b2bd2d9c1725e9194986750aa4dbdce135a8b945a192cff16467a.jpg


Courts Close the Loophole Letting the Feds Search Your Phone at the Border
https://beforeitsnews.com/libertarian/2024/07/courts-close-the-loophole-letting-the-feds-search-your-phone-at-the-border-2819922.html
"The Fourth Amendment still applies at the border, despite the feds’ insistence that it doesn’t. "
https://knightcolumbia.org/documents/ymerpfopdw


... getting my ass handed to me right over here.   lots a notes though.


after the great internet take down last month -- building, recovering, and archiving some creators collections, but for the most part ...


nice!


the antithesis of why i thought we were all here


time for peace time
https://image.nostr.build/eb925661599457ac8198afeb2011477b017ef8d47169b50c41cc45c7708ef139.jpg


New gossip release:

- This doesn't have the latest stuff (like bookmarks) but seemed like a stable place to make a release
- As usually happens, after hours of release processing, I discovered a bug. So there will be a point patch at some point.
  The bug causes the 'pending' messages system to crash, but gossip otherwise keeps working

nostr:nevent1qqstvj73nmvvtj975uk6u3zmsefezahgr6y5dyhg7awcmr69jkxqp6cpz9mhxue69uhkummnw3ezuamfdejj7nwc9am


overlay networking as a gateway drug.  luv it.


memphis https://image.nostr.build/1bbfff8c3d719805c3b48be7b86601a5503dd7c1b732ce0223b1546f02461423.jpg


#dev #CLN

I've spent the last few workdays completely reworking our onion message code.  This was scattered in various places and I wanted to unify it, and also written several years ago and I'd forgotten how the protocol actually works!

onion messages are *double* encrypted; this is the main source of confusion!  At the high layer, they're a series of nested encrypted calls ("onionmsg_tlv" in the BOLT 4 spec), so each recipient decrypts and hands it on: this is exactly the same as we use for payment information.  But inside that is *another* encrypted blob (onionmsg_tlv.encrypted_recipient_data), which requires a tweak which was handed to you alongside the onion, for you to decrypt (into an "encrypted_data_tlv").  Inside that is all the information about where to send next, any restrictions, and allows you to calculate the *next* tweak to hand on (it can also override the next tweak).

The double encryption is necessary because there are *three* actors here: Alice wants Bob to send her a message, without revealing her identity. So she gives Bob a "blinded path" which goes via Charlie: this path contains Charlie's pubkey (where to start the path), a blinding tweak, and two encrypted blobs for Alice to put into each layer of the onion message.  The first an encrypted blob which Charlie can read, which contains her pubkey so he knows where to send it next.  The second is her own, and contains a secret specific to the purpose of this message, so Bob can't play games trying to use this blinded path for anything else ("hey, are you the same node as this previous payment?") or use a different blinded path for this purpose.  She can also add dummy hops (we don't yet), which she will simply absorb, to obscure the path length from Bob.  You can add padding to make the hops indistinguishable (we don't yet).

Bob puts the actual stuff he wants to send Alice into the final onion call (often including his own blinded reply path!), along with the encrypted blob.

Importantly, even if Bob were sending a message *not through a blinded path* he would use the same double-encrypted format: that's so Charlie can't tell whether a blinded path is being used or not, even though it's slightly less efficient.  Crypto is cheap these days, too.

Now, if Alice gives Bob a blinded path to Charlie and Charlie is Bob's peer, he can simply send the onion and the first blinding tweak to Charlie.  But if Alice needs to send the message via Dave to Charlie, she needs to prepend a step.  That's not quite possible, naively, because blinding tweaks are generated *forwards*, and she needs Charlie to get the right blinding tweak from Dave, and Alice has no way of making that happen.  So inside Dave's encrypted blob, she uses next_blinding_override to tell Dave to hand that blinding override to Charlie instead of the normal one.  I just implemented this for Core Lightning (previously we would simply connect to the first node, which is privacy-compromising and should only be done as a last resort).

These blinded paths have some nice properties: you can't use part of them (you don't know the blinding factor except for the first one, so you can't start in the middle, and you can't replace any data), you need to use all of them.  They can contain timelimits to avoid easy probing, too: a classic measure would be to see if the path fails when a given node is down, but that takes time.  The spec insists all errors within the blinded path are the same, and originate from the entry: this loses some analytical power on failure, but makes probing harder.  The entry point is supposed to add a random delay (we don't yet!).  There may still be implementation differences, but they're hard for Bob to probe (and Alice doesn't need to, as she set up the path).


many different forks and in-house maintenance efforts fragmenting features and interoperability due to different versions being released rather than from a single repo.  but it happens all the time.


it is a badass piece of software and dont mind investing time to pushing it forward.  i gathered some notes on what that might look like to avoid fragmentation.  you seem organized and doing some kewl stuff.  what is your interest in this project rather than the 'other' efforts?


a Relay Test Suite is in the works...

I've already got ideas for 94 tests and as I write these tests they expand out into even more tests.

I hoping that exposing relay behavior will drive relay software towards consistently supporting the same way of doing certain things, and that this will help nostr compatibility.

Tests include things like:
* Can the public write events?
* Can an authenticated person write somebody else's events?
* Does the relay respond to minimally constrained filters?
* Does limit 0 give an EOSE?
* When you write an event and get OK-true, can you read it directly back?
* Does limit behave properly when a filter has multiple pubkeys and multiple kinds?
* Does it require AUTH to read DMs and giftwraps?
* When submitting a replaceable event, are the prior events replaced?
* When submitting a replaceable event with newer ones already present, is it rejected or ignored?
* Does deletion of a replaceable event preserve the events that are newer than the deletion event?
* Does it prompt for auth initially?
* How large of an event can it handle?
* Does it verify signatures?
* How does it react to invalid UTF8?
* Does it handle all JSON escape codes? What about surrogate pairs?
* Does it preserve field order in events?
* Does it preserve fields in events not defined by the nostr spec?
* How many subscriptions does it allow simultaneously?
* Do events with negative created_at values work?  What about exponential notation? What about numbers that won't fit in a u64?

... that kind of thing.

If you want to help contribute, even if you just have an idea of what to test, come on over to https://github.com/mikedilger/relay-tester and give feedback, open an issue, or better yet submit a PR.

What about the other things I'm working on?

* Gossip is on pause while we wait for the UI developer to handle some personal affairs, then we will have annotations and NIP-17 DMs.
* Chorus is stable and upgraded to use Pocket
* Pocket has been completed and is stable too, but I haven't tried to make it useful outside of the scope of a relay yet.


no worries.  no problems.  i try to avoid spending time proving or correcting misjudgments.  just didn't realize the project went dark.  weird.  what are you seeing?


strange init. definitely was interested.


reclaim you before its too late
https://media.nostr.build/av/43a2a61addf0dbf69794eacd3aecf073d4a292110c92bfbbc595771bc4e8b981.webm


Behind The Woodshed - Democracy The Weapon
https://ia903204.us.archive.org/9/items/BTWRLM580/BTWRLM580-20240609-Master.mp4
2024-06-09 - BTWRLM580 - Democracy The Weapon - 1:59:45
$710M, Air Travel, Android, Archive, Ban, Battle, Biden, Billionaire, Bio-Weapon, Blunder, Brain Damage, Brink, BTW PSA, Can’t, Cancers, candidates, Carnival Mirror Reflections


New DHS publicity about REAL-ID
https://papersplease.org/wp/2024/05/22/new-dhs-publicity-about-real-id/


Federal Real ID-Compliant Licenses or ID Cards Will Become Mandatory for US Domestic Air Travel
https://reclaimthenet.org/federal-real-id-compliant-licenses-or-id-cards-will-become-mandatory-for-us-domestic-air-travel


true


After etsy suspended my account to shake me down for a serious amount of personal info, i resorted to finding some one local with a printer.  i need to learn more about the craft, but as i understand there was no resize using pla+ for two copies for standard front and back.   the 8000mAh would fit, but the battery shown is the 5000mAh.  i damaged the power switch popping the board back out of the case. still scratching head over how the speaker attaches to the side.


prayer board: i wish i can go to the arcade everyday.

https://image.nostr.build/072a9390530a580f6ce5e9ee1a4e12f41c7a4832a36380076538d1a72df8aa5e.jpg


GM
https://m.primal.net/IADV.jpg


i had come to the same conclusion.  i've had all the parts and just needed this print.   nice to have a printer to sort out some of the sizing issues discussed.   good luck.


Look nice.  Is that the slim or standard print size?


any results on case?


spoken like a kleptocrat


The TSA Plans Big Digital ID Push in 2024: Trading privacy for convenience.
https://reclaimthenet.org/the-tsa-plans-big-digital-id-push-in-2024


"IF WE CAN'T DO THINGS THAT ARE EASY. HOW CAN WE DO THINGS THAT ARE HARD." - ALEX GLEASON 2024

nostr:note13u40dq3j4jzaxzskslvtp0n2e6f9annj4pdf3v69zx6fg0hjh7hqgg4m5q

https://media.gleasonator.com/36562c522065df37b6705c26d42a5a889fc9a3a0a34caab8955ac0d6e4b6a741.webp


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;dfgklj;fdgkj;ldfgs


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;dfgklj;fdg


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;dfgklj;fdgkj;l


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dkl


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjl


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;dfgkl


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgk


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgk


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgklj;dfgklj;


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfgkl


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
D


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3
Dklasgkjlsdfg


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;

## h3


# cosmicpsyop collab

## h2
skadkljdg
## h3


# cosmicpsyop collab

## h2
skad
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjk
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagk
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl;
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjl
## h3


# cosmicpsyop collab

## h2
skadkljdgsa
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgj
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgsk
## h3


# cosmicpsyop collab

## h2
skadkljdgsaadsgjkdsagkjladgskl
## h3


# cosmicpsyop collab

## h2

## h3


# cosmicpsyop collab

## h2

## h


# cosmicpsyop collab

## h2

##


# cosmicpsyop collab

## h2


# cosmicpsyop collab

## h


# cosmicpsyop collab

##


# cosmicpsyop collab


#cosmicpsyop collab


cosmicpsyop collab


molestation or radiation

https://m.primal.net/HbZh.jpg


#bitcoin plasma ball . ..... built with #blender geometry nodes!

https://v.nostr.build/OGzY.mp4


the #bitaxe has landed.  many thanks to @DCentralTech nostr:npub1ql2zzp3g6yndgz05js7wdc4qkr88wkyne5nw2cc7csrtzqs0yeesgwrxya0 nostr:npub1wtgd9ccg76awlp29zl3h466l89wr7hsut0n3ucmtr95h4t29jc6srlsxp2 making it simple.
https://image.nostr.build/c48fbb2ae38dcac49007308c632ec8594fb29d4b1f35d0438bdca4a29b364226.jpg


facial recognition flawed / defense
https://video.nostr.build/6e223946866a1dfdec58aec261a6e06fa003d5c35b7f7e6939773733a4a5f308.mp4


deleted


https://media.nostr.build/av/316ab61167bf136204980be1bec84d3642b9684540941a74037309f50a841247.webm
Talking Heads - Once In A Lifetime (Gigamesh Remix)


Your body is your internet
https://www.purdue.edu/newsroom/releases/2019/Q1/your-body-has-internet--and-now-it-cant-be-hacked.html


'Could you just rewind me your last 24 hours for me, please?'

https://video.nostr.build/9c46ef31bb58ffcc7d8b3a26fb44a4874115584761eadf234399fe55f4ab6324.mp4


The IMF releases  “a virtual handbook” on CBCDs, the  purpose of which is to serve as a “reference guide for policymakers and experts at central banks and ministries of finance.”

Your guide to navigating the system to work an alternative private one #bitcoin
https://www.imf.org/en/Topics/fintech/central-bank-digital-currency/virtual-handbook


Another one...
https://image.nostr.build/16ec97f00364a114ff9c1e1ca8373af7ebdbf620046b0f8ef6107821561d9145.jpg


Thanksgiving dinner Gangnam style
https://image.nostr.build/8792a345b6f433afed782ad431329e717fc79f4d2a84a27d4ad2461b9fa3ed36.jpg


GN

https://image.nostr.build/dd2ac0b9111629d71e937bcccadf09500d89eac92a524dfb6d347771ea2cce61.jpg


N Seoul Tower 🗼

https://image.nostr.build/c7327668b8d0e8a563ba44771fb08653555f73a2365b680be314d18e28f9a848.jpg


GM

https://image.nostr.build/8938de75dd43c3dd108f355b58a9ddf38a42fd028c164a9eedb8f60c32200563.jpg


League of Legends World Championships in Seoul

https://image.nostr.build/5f8523e0ea060cfa72375ccbdda3f37fb103925b0627c8251c5590a7648379dd.jpg

https://koreajoongangdaily.joins.com/news/2023-10-09/sports/esports/League-of-Legends-World-Championship-descends-on-Seoul/1886022


Korean celebrity kimchi dumpling
#foodstr
https://image.nostr.build/6863e45d6ac5d2d9d988e8b6115b4b0733a83d345cfd1b8e7c200729aafaa3ca.jpg


gn

https://image.nostr.build/477663dd1cf46812f1e4b6bc4859e240bc97520f117ef150c9bf383d42006dca.jpg


just taking the pig out for a walk.🐖😆

https://image.nostr.build/86316e5ac50f917aeec46b6419e591afe78630eed34b04ac236345d617f4bd87.jpg


Good one.  With all the facial and finger scan collection posts at the airports now and no opt-out path they might as well just go straight to the anal probe.


Taiwan beef noodle soup #foodstr #food

https://image.nostr.build/e66b372e099ddefe185d825c643aefd48f5fcc3e1567ef6101f65fe0a45386cb.jpg


i was seeing these bags of chips laying around everywhere. during board demo, next to a new laptop, and on this medical equipment pictured here.  well the story goes that these shrimpy flavored crisps make the hardware run better or keep it running.  either way I bought a couple bags to put on my node. 🤣
https://image.nostr.build/95bd012ba219bf3bb0035a9e7c8a83bcee5dfe1b73b869555184b42d2452ae19.jpg


Our replacements have arrived.
https://video.nostr.build/3c97792fa967bfcc320ce8a7a31a45efc0b0838f29137e5cdf626bb128cdcb03.mp4


Antiwar

https://image.nostr.build/3d441565d121850a5dad921844a75f6bd8a75e509cd741e6bd97bde3b3c7150f.jpg


now with facial scans and finger prints. i read nose swabs are being added this week to eight airports for the return trip home. a biometric cornucopia we should opt-out of in mass.


not cool indeed.   i remember a happier dude when you shared your special indian candy with me in tokyo.  cheers.


Into believing the #Taiwan news 😅 https://image.nostr.build/59b20d9e5098b6ae1f077d559b19875b920f89310f15fdd7fc7d96d25d980032.jpg


Take the time to learn #Bitcoin https://image.nostr.build/4910825d02d6a34179ddc351b826fcde55719ec8a5577ccd3a5e08f04f74b783.jpg


The State of Facial Recognition
https://hackmd.io/@cosmicpsyop/B1ChSBTl6


Tamsui sunset

https://image.nostr.build/59c87e52e1f20d6291ced87491ee580a8c6efe979d7fe30d9135bee986cc74cb.jpg


reclaim you

https://media.nostr.build/av/43a2a61addf0dbf69794eacd3aecf073d4a292110c92bfbbc595771bc4e8b981.webm


Airport biometrics for all： The future is now


human being See MONSTER.
—Ballentine's Law Dictionary (1930)

monster A human being by birth, but in some part resembling a lower animal. A monster hath no inheritable blood, and cannot be heir to any land.
—Ballentine's Law Dictionary (1930)

https://m.primal.net/HPhA.jpg


especially when they had a regular and child version push cart.


GM

https://image.nostr.build/7a35804aba501dc341a059f49ed3648e3a6e4b51a02b7bd658ed939e3bd8f192.jpg


.tw cart basket - basket cart

https://image.nostr.build/239018439a0879be2850c8d44665d500fe6529031d6f361c9cbc5f26c1a262cb.jpg


GN

https://image.nostr.build/9af4f867e7de46e94141e9804327e67740cbf2774d42ceb08c88b3e2ca737dba.jpg


rare find  indeed.  my pockets still hold yesterdays papers, wrappers. and receipts.


oh my, #bitcoin accepted at bic department store however only using a specific wallet.  never the less, the largest vendor I have encountered.

https://image.nostr.build/38f49fd9d2adf7107eb8c49b47ff53f78adad90d9dbb546f095d56303b780cf4.jpg


Ghibli Clock

https://image.nostr.build/f7bd9b1ab56b31789a01640edabd428261b64d775e672df7e94da27db0eb5091.jpg


We have many many activists, artist and innocent individuals in prison just for not wanting the ruling regime.
Can you please search for #freetoomaj and support that too. He is only a specimen of the common case of severe injustice in #iran


Were these the taxi’s at #nostrasia?
Damn I really missed a lot….

https://video.nostr.build/c70a24c9d1a1ba77f25ee7e01668e5386a3739fe5cd0c9e955b3b92f7598b00b.mp4

#nostr


I want to extend my sincerest thanks to the organizers and volunteers of #nostrasia in #tokyo. It was  a great privilege to participate and meet such brilliant people who all aspire to #build a platform we all deserve.  Pretty damn excited about the #sovereign future I see.

https://image.nostr.build/972f27a190b9d844429e4cb8b99a8178568e3a4d72002434eee0a849804ea589.jpg


prayer board: i wish i can go to the arcade everyday.

https://image.nostr.build/072a9390530a580f6ce5e9ee1a4e12f41c7a4832a36380076538d1a72df8aa5e.jpg


happy halloween 🎃 from harajuku  https://image.nostr.build/b36db63f5a55ab1e4d62372f7d1d002c79e37e54b92269b31038108038dbeba4.jpg


Gotta ❤ #Nostrasia
https://image.nostr.build/dc7ddf94258758cba4ea41bbba11b77fc6ad04c8b51216ae4da322a411fd1789.jpg


deleted


西雅圖-塔科馬國際機場 -> 成田国際空港 -> 臺灣桃園國際機場
@npub1qh8h83v4ec6n6mlwd4pac7g87x7vh6m26y80awqkwk7x8yhd7a5qv389kp

https://image.nostr.build/c37b93655410c2a30e451a2ef06c426ae5bd8a387f2e2e1999808910c9395fc7.jpg


California's "First" City San Jose by Millard Sheets

https://image.nostr.build/68e95e2f91aa42fed2d386e4c30356d0bd782bdbf174c49a5f8e56e11cfdd914.jpg


moon over olympics

https://m.primal.net/HOqi.jpg


gm

https://image.nostr.build/4f6a6662c4ac097884148458d0ceb18194193c6bd1974b0b2410a4ee6399746c.jpg


Buenos días...

https://nostr.build/i/nostr.build_66acc8e9417f139630f00d78730d9660b74f339895c28688ed02a2327af56b84.jpeg


Thanks to Harvard University, you can now virtually enter the Great Pyramid of Giza in 3D and 360º  🤩
Try it: https://giza.mused.org/en/guided/266/inside-the-great-pyramid
https://video.nostr.build/277a1bc5744fbc9ce10241f49cfee4cc15451884913347be50d08231633d1a78.mp4
#pyramid  #giza  #360  #3d  #tour  #amazing  #harvard


gnarly, dude
https://m.primal.net/HObt.jpg


Toe Truck
https://m.primal.net/HObr.jpg


A Technical Analysis of the #Nostr Protocol 🤙🏻
#grownostr #security #privacy #analysis

Nostr is an emerging protocol that allows users to publish short messages called "events" in a decentralized, censorship-resistant, and cryptographically verifiable manner. It has the potential to enable privacy-focused social networking and web3 applications.

This analysis examines Nostr's technical design, highlighting key components, vulnerabilities, and areas needing improvement. It is intended for readers with a passing knowledge of cryptography, networks, and blockchain technology. Casual users may find some sections challenging, but I aim to reward patient, focused reading with deep insights into this novel protocol.

# Overview 💻

Nostr utilizes digital signatures and public-key cryptography to authenticate events published by users. Users generate a private/public key-pair, registering their public key on the network. This key serves as their identity. Users sign events with their private key before publishing to relays. Relays then distribute the events across the network. Clients can verify event integrity via the signatures.

This high-level architecture offers censorship resistance and verifies event provenance. However, complex challenges emerge when examining Nostr's design through a technical lens.

# Cryptographic Foundations 🔒

Nostr identities are generated as secp256k1 key-pairs. This offers compatibility with external systems like Bitcoin and Ethereum which utilize the same curve. Key-pairs are generated on the client side, ideally using a secure random number generator with sufficient entropy.

Once generated, the key-pair should never be transmitted. The private key in particular must be kept secret. Nostr clients are thus responsible for properly securing keys. Future clients should support encrypted local storage, multi-factor access control, and seed phrase backups. Weaknesses here compromise identity ownership.

All Nostr events are signed with Schnorr signatures using the author's private key. Schnorr offers a space-efficient signing algorithm but relies heavily on random nonce generation. Poor entropy pools during signing open the door to compromise via nonce-reuse.

Fortunately, the nonce is not revealed on-chain, limiting exploitability. Nonetheless, clients should implement RFC 6979 deterministic nonce generation. This eliminates randomness as an attack vector.

# Sybil Resistance 🫂

Nostr's open design allows anyone to generate a key-pair and immediately participate. There is no imposed cost-of-entry or identity verification preventing Sybil attacks — a weakness compared to systems like Bitcoin.

A single actor could trivially generate millions of identities. Combined with Nostr's re-posting mechanics, this amplifies the potential scale of disinformation campaigns. Similar techniques have been exploited on social platforms like Twitter.

Nostr currently lacks robust Sybil resistance. Possible mitigations include rate-limiting new key generation, requiring Proof-of-Work, and leveraging Web-of-Trust style reputation systems. Careful design is needed to prevent undue centralization.

# Metadata Privacy 📝

By default, Nostr events are publicly accessible. They contain metadata including the author's public key. Clients can correlate events across relays to profile users. This reduces privacy, especially for less tech-savvy users unaware of the risks.

Future Nostr clients should make pseudonymous and encrypted usage easy. Predefined "personas" with distinct keys, ephemeral keys, mix networks, and metadata stripping should become standard privacy tools.

However, blindly encrypting all content poses discoverability challenges. Search, filtering, and network analysis rely on accessible metadata. There are open research questions around balancing privacy and utility.

# Censorship Resistance 📛

Nostr's decentralized architecture should make censorship technically challenging. There is no central entity that can eradicate content or ban users.

However, Nostr's relay infrastructure poses centralization risks. A handful of large relays could potentially collude to censor events or de-platform targets. Nostr needs robust incentives for relay operators to prevent oligopolies.

Censorship at the relay level also remains an open challenge. Existing systems like Secure Scuttlebutt explore concepts like relay "matchmaking" and sharding events across diverse relay groups.

# Spam Prevention 📬

Nostr's public nature makes it vulnerable to spam. Computational Proof-of-Work and fee mechanisms have been proposed but neither is foolproof. Clever anti-spam that resists censorship and gaming remains an open research problem.

Basic rate-limiting on new key registration, events published, and introductions sent helps but is trivial to circumvent. More advanced techniques like fees weighted by account reputation, staking mechanisms, and selectively applying Proof-of-Work based on risk factors warrant exploration.

# Secure Key Management 🔐

Nostr's security model depends on users properly managing private keys. If users select weak passwords or store keys improperly, malicious actors can compromise their identities.

This poses an enormous challenge given that most users lack crypto-security knowledge. Nostr clients should implement multi-factor authentication, encrypted local storage, and easy-to-use backups like seed phrases. Usability testing is critical — security mechanisms that seem too complex may be ignored or circumvented by users.

Platforms like Keybase demonstrate the difficulty of making key management accessible. Nostr clients should learn from past efforts while recognizing the uniquely sensitive nature of social networking data.

# Scalability 📈

Nostr's throughput is limited by its relay infrastructure. Early testing suggests relays can comfortably handle 2000 events per second. Further optimizations like compression, sharding, and efficient routing algorithms will help.

But fundamental scalability limitations remain. Relays are constrained by bandwidth, storage, and real-time event processing. As adoption grows, demand may overwhelm relay capacity. Possible mitigations include sharding the network into relay clusters and introducing client-side caching.

Incentivizing a robust relay network is critical for scalability. Nostr currently lacks effective incentives for operating high-capacity relays. Ongoing research into decentralization-compatible business models is essential as utilization increases.

# Conclusion 👨🏻💼

This analysis reveals that while Nostr offers a novel approach to decentralized social networking, complex technical challenges remain. Sybil resistance, metadata privacy, censorship resistance, spam prevention, key management, and scalability all warrant additional research and protocol evolution.

Nonetheless, Nostr represents a promising step forward in an era of centralized platforms and compromised user rights. With transparent analysis of its strengths and weaknesses, collaborative research, and responsible protocol design, Nostr may yet fulfill its aspirational goal of user empowerment. The road ahead will require vigilance, creativity, and a commitment to the open, decentralizing ideals which motivate this project.


Over the past months I've tested various #bitcoin hardware wallets / signing devices using Sparrow Wallet and Specter Desktop multisig setups. Without going into their security models, here is the good, bad, and neutral of the devices in no particular order
https://void.cat/d/MHQ4WnEUyMydFC1vRA6QHL.webp


does look promising for nerdminers
https://m.primal.net/HODH.jpg


👀💪🏻

https://twitter.com/DCentralTech/status/1693263948714234093?s=20 https://cdn.nostr.build/i/bf114157c11be2f820ff9bbc23bade5a7bf90dc2245d613e7b6fe100271b4e8c.jpg


bitaxeUltra release coming soon!

This fully open source #bitcoin  miner has a single BM1366 ASIC (from the S19XP). It runs quiet and cool at just about 500 GH/s https://image.nostr.build/eb14cbe38f0812e27c65ef19fde3925c1ec7d5fc7454b5ba811dbf5ec9871065.jpg


New setup screen for the OrangeClock 🧡🕰
https://orange-clock.com
#OrangeClock #bitcoin https://image.nostr.build/f6c08a4f968414e326b8fd3fe8089d2fe5229ccd7efbe886a4e12d27927d8784.jpg


Zaanse schans
https://image.nostr.build/ab5de91a23b31ec6131c9786e4e34078b5697199bfeb57d7478b4354b87aa87d.jpg
http://francescakee.com/about/


Your lucky day

https://i.imgur.com/jP3H93r.jpg