The bitcoin whitepaper is just 9 pages.
What's even more incredible is that everything that makes people say their mind was blown when reading it is explained in the first 4 pages.
The remaining 5 pages could have just been left out and clarified on the mailing list as Satoshi did with many other details not mentioned in the whitepaper.
https://bitcoin.org/bitcoin.pdf
You can use it by adding it as a custom relay feed, its pretty good but not completely as intended, I’ll need to add a toggle to override chronological ordering and allow posts already seen to fully take advantage
It asks the keychain for the nsec of the logged in npub, so either the keychain has the wrong nsec or the its asking with the wrong npub, not sure how either of those can happen.
When you go to your own profile and tap edit profile does it reveal the correct npub but the wrong nsec? That would mean its somehow wrong in the keychain
Ok I just checked all the code paths where the private key is set and its possible to turn a read-only account into a normal account by entering the private key, but it doesn’t check if the private key belongs to that read-only account, oops 😬
So what probably happened is you had a read-only with your main account and then at some point turned it to a normal account but with a different nsec.
If you have a Mac with iCloud keychain sync you could manually fix this in Keychain Access, on the phone its not possible I think, I’ll need to add some tooling in Nostur to recover from this.
yea I debugged some more and it does actually check if the private key belongs to that read-only account so that can't be it. I did some DB updates in the past, maybe I missed something related to bunker accounts. Could it be that the "wrong" nsec is the bunker client key?
I think you could try to add existing account again and it should override the wrong keychain data, if that works I don't need to add extra tooling to recover
It's a bit tricky, it used to work like that, but when I added support for iCloud keychain sync there can be the situation where someone is logged in on 2 or more iCloud devices and logging out on 1 device would also unexpectedly logout on all other devices as well because its using the same keychain, so to be on the safe side I remove the account from Nostur on logout but not from the keychain.
It’s still on the todo list to also remove from keychain, but with warnings to back-up key first etc.
I think there might be something else going on in the linked post, it looks like a reply to a highlight (9802) of an article (30023), and an e-tag to the article is added as root, probably the article shouldn't be added at all and the highlight should be root but I'm not sure, will look into it some more later
Seems pretty good, so far I will keep using it.
Nostur does use the “since” filter on relay feeds, and it won’t add older posts above newer posts when updating the feed, not sure if that breaks anything
I will add that, for nests it already works but zap streams still use the older video player that I need to rewrite a bit to keep playing in background
I have this little NUC (small computer) that I've been using for ~8 years now to run my bitcoin/lightning node and everything else related. I've been using it as a playground to just try everything, I've installed and reinstalled so many things, I ran it with FreeBSD (my fav), Ubuntu and in the last years Debian, it's been running pretty stable with very little maintenance. But a few days ago it would't boot anymore, disk full, the 500 GB internal SSD isn't enough anymore for full blockchain + indexes and I don't want to run it pruned, it's also connected to a 2 TB external USB HDD but that one is a bit slow. I've moved some things around a few times to make it work again but now its not booting anymore with a totally unrelated error about a wifi device (wtf, its not even using wifi), so after all these years of experiments and bloat I've decided to just start over with fresh install, same NUC, bigger disks, reinstall OS and restore config. This time I'm going to install the minimal just to:
- Connect my wallets to my own bitcoin or lightning node
- Look up transactions on my own blockchain explorer
- Connect a BitAxe solo lottery miner
Bookmark this post if you want to follow along as I will post my updates as replies.
#sidequest #hobby #server
https://media.utxo.nl/wp-content/uploads/nostr/6/4/64ac813ca13e3401ab85bfcf77f819cd031f49326c512d89a0a1b4a44b805830.webp
Next is installing software. I used to compile from source but updating was always a hassle, and step 1 is always please install a gazillion unknown dependencies that conflict with other dependencies. I will now just download the binaries and verify the signatures, I want to try to just have a few binaries, some scripts, and data, nothing more, keep it lean and simple.
https://media.utxo.nl/wp-content/uploads/nostr/0/8/08d003cc7a15cb0de1afd58be18c95bc7661813df93d767862188912c05c2604.webp
well the blocks have finished copying but bitcoin core won’t start because half the blocks are missing, I had forgotten that I symlinked blocks to another directory some time ago, and I deleted that directory 😅
so I’ll be syncing from the genesis block now.. to be continued
bitcoind has finished its sync, now I can start electrs. I wasn't sure how slow the sync would be so I tried it first from scratch but it was going very slow, would probably take days, so instead I copied over the data from my old disk, which was around 50 GB.
With bitcoind running, electrs running, I can start the mempool backend and my now local block explorer is working:
https://media.utxo.nl/wp-content/uploads/nostr/d/8/d8c3aee4a8967d6602e352d1522084b6e2b77d3f440b766413d27f564b87b235.webp
now I should also be able to start lightning lnd but I was getting errors:
[ERR] LTND: unable to create partial chain control: unable to determine if bitcoind is pruned: unable to detect bitcoind version
I vaguely remember @Derek Ross posted about a special config flag and after some digging around that was it:
nostr:note18lz63u08tdtxslhznayxw6sq6f7t0mu4vtt6fd6lvfxek0h29d9qtgf8hm
lnd can’t connect to bitcoin core v28 without it, after adding the flag the problem went away and my lightning channels are back online.
are you trying to restore your account? If you still have the “deleted” account in Nostur you can go to Edit profile, update your name/info and save. That should be enough to broadcast your restored profile to relays and other apps
123 days of analysis paralysis, help me decide between Nostury and Nosturix in the comments.
There have been many great suggestions, but I still want to keep it close to Nostur instead of a total rebrand.
The main problem was with pronunciation, are you talking about nostr or nostur, you can't tell the difference verbally. Nostury or Nosturix makes it clear, but which one? I like them both
nostr:note1357tnyjuhlzvwr6ut0zentdngkntz8y9vuh7x3vskdltakp294es3u9s5a
I tried to add nostr.build early on but was never able to figure out the API or what I was doing wrong, but with NIP-96 it was easy to add :)
@quentin actually already cleaned up the list but I see now that commit never made it in the right branch, will be corrected soon
nostr is censorship resistant because:
1. the follow list is decentralized
2. there are multiple relays
Normal users can resist censorship by switching relays, or ultimately run their own relay and they cannot be censored on follow lists because each follower owns their own follow list, it doesn't even need to exist on a relay, can exists primarily on everyones own device while syncing to relays.
Relays stopping spam doesn't mean nostr can be censored, it just means whatever was stopped was something no ones care about enough to either be followed or hosted on a different relay.
Oddbean new post about login | logout
Notes by Fabian | export