de
nobody
de279ef2777cca0252b0865ec1bf5375f32122fcda65fdf223a5788718f105ff
account deleted

I have media files served over NFS to my dedicated media server. I have a Ryzen Synology and it doesn't handle transcode well. Have had no speed issues with serving the files though.

I aimed for a 10-15° leg bend at full extension for better power output and comfort. When I got into road cycling in 2020 I played around with it a lot, watched an absolute ton of videos on bike fit.

At the end of the day though whatever works for you and doesn't cause injury is right!

So the #SEC isn't going to appeal the #GBTC decision. Odds keep on going up for a spot #ETF.

#Halving, #fedpivot, ETF... Cards are all lining up for #bitcoin to rip faces in 2024-2025.

https://www.coindesk.com/policy/2023/10/13/sec-reportedly-decides-not-to-appeal-its-bitcoin-etf-court-loss-against-grayscale/

Thanks! My fiance did it so I'll let her know you said so haha

I haven't had a bike fit so I could be set up totally wrong lol But I'm pretty comfortable, can put power down, reach the ground and good reach to cockpit.

Replying to Avatar bookguy

Same

Oh shit, a fixie. You must have legs like tree trunks.

Yea I think you're right. Directly comparing it to my ride, Serg's definitely looks higher. I'm 5'10".

There's only 4500BTC on the network. I'd be shocked if they amass anywhere close to 1000BTC.

I would not be shocked if they rug though...

No issues for me. No NVME caching. I have a RAID5 pool with 6x 7200RPM drives.

It's been a long time but I don't remember my initial sync taking longer than a day.

And I guess for your question about what I recommend: I am very happy with my set up. There's a future point in time where I'm going to need to reallocate more storage to the VM running my node which will be a pain in the ass. But I allocated enough storage that will not happen until sometime 2027. I'm outgrowing this Synology and plan on custom building a rack NAS before that time comes. Likely 2025.

I use a Synology NAS. My bitcoind and lnd are running in docker on a VM.

One thing I learned: don't use an NFS share for your data dir. The blockchain is a ton of little files and disk I/O will make your node SO SLOW.

Can't speak to Citadel though, sorry.

A channel is sort of like a rung on an abacus. All of your counters stay on the rung but you slide them back and forth.

When your counters are mostly on the near (local) side, you're limited on how many more counters can be brought over to your side but you have plenty to send. This is outbound liquidity.

Conversely, when most of your counters are are the far (remote) side, you're limited by how many counters you can send but you can receive many. This is inbound liquidity.