Hi there,
I need your help frens! I have setup 23 relays for my profile but every time I interact with the interface some of those relays get removed and others added.
Here's my workaround with screenshots to help explain better.
When I hit refresh and shortly after click on the "Relays" button on the top bar I see my 23 setup relays correctly:

After a few seconds new relays are added but not activated:

If I click "Set relays" now all works as expected with my 23 relays until I click anything on the side bar. If I don't do this exercise some of my relays are ignored and new ones are added:

I tried to clear cookies, clear database and all that I could find. Any idea what can cause this and how to fix it?
Even with this, #nostrudel is the best. πͺ
Thanks! π π€
His fans don't get it he's just playing for them the notes they want to hear.
He's not dumb. He is able to manipulate large crowds like puppets.
He can in fact go from "we are decentralized and above nation state noone can harm us" to "if this bill passes the whole crypto industry is doomed and so we are call your representative now" in one sentence while the cardano fans are taking bukkake like bobbleheads.
wonder why the son chose commuting and ramen noodles over these two
Actuallyβ¦. Alors onβ¦.. #BENANCE
https://video.nostr.build/15f42f436ecec45b4d77918763edcb56ed96d967fd9e70d62c04100995f5fbca.mp4
Source: jonzzyTV on Twitter
Benance: It really whips the llama's ass. Meeee!
Thanks for the zap nostr:npub1q6k0dl0dgaqd7tgezslhss8q6mcpru2cjy6h3z7atfjncyp2jeds560529 π«
I see, that makes sense. Reading in 128 byte segments would be very slow, I don't know what I was thinking. π
I found another clue:
/** The pre-allocation chunk size for blk?????.dat files (since 0.8) */
static const unsigned int BLOCKFILE_CHUNK_SIZE = 0x1000000; // 16 MiB
/** The pre-allocation chunk size for rev?????.dat files (since 0.8) */
static const unsigned int UNDOFILE_CHUNK_SIZE = 0x100000; // 1 MiB
/** The maximum size of a blk?????.dat file (since 0.8) */
static const unsigned int MAX_BLOCKFILE_SIZE = 0x8000000; // 128 MiB
It should be closer to the real answer I hope. It's indeed fun to find out the internals of such program like bitcoind.
Those who know C++, how does bitcoind (Bitcoin Core) read/write data from/to disk? I'd love to tweak certain settings for my public node. Is bitcoind using specific page sizes? Please answer here, if possible:
https://bitcoin.stackexchange.com/questions/120567/page-size-of-read-and-write-operations
I'm not qualified by any means to answer just trying to help and learn at the same time so treat this comment accordingly.
The line 22 in bitcoin/src/util/readwritefile.cpp suggests that it reads the file in 128 byte portions unless it's the end of the file. Could it be the case?
At the same time I would assume that any modern OS is capable to manage this transparently and efficiently without user intervention so just for my curiousity why you think this might be the bottleneck?
- Hello an welcm to Andrstns teevee ma namis Jack Duckspr, Ozzy'z behin' da camera, and THIS IS:
- Matt π
no π
fuck relays π‘
thanks for pointing out π€
I have not muted anyone.
Interresting, I checked in nostrudel some pending posts and all disappeared after a few seconds all what's left is approved by Alice. I should look with another client.
This whole mod thing feels very wrong on this little island of free speech.


