is some prop not showing up? I see the video one

And merge wallet sdk / video is an empty page because of the "hey everyone" being indented luigi1111w

the what

the indentation here repo.getmonero.org/monero-project/c…ission-Concept-Video.md?plain=1#L28

made a merge req with fix luigi1111w attempt 1

oh I finally understand the issue

i think an attempt 2 is required - still an empty page lol

jeffro256 full-time development 2023Q3 has moved to funding! ccs.getmonero.org/proposals/jeffro256-full-time-2023Q3.html

Hi everyone, A new project just launched from our dear owner of kyun.host : reiya.io

an anonymous tor relay crowdfunding (using XMR). Check it out

thats pretty cool

Kyun need to add "Monero node offers"

like 200GB HD (that grow slowly as the blockchain grow so it never run out of space.

RavFX[m]: > <@gfdshygti53:monero.social> Kyun need to add "Monero node offers"

> like 200GB HD (that grow slowly as the blockchain grow so it never run out of space.

I've already tried syncing monero node on its hdd

they're design for high-capacity and at 70% it just become impossible to sync

someoneelse49549: Maybe add like 16GB of SSD storage to fix that sync issue (LVM2 kung-fu)

just do that : waw7epjul5xeacm4niblpgihdtg3atxyqek…ad.onion/index.php?article=hdd_sync

someoneelse495495:

<RavFX[m]> "just do that : waw7epjul5..." <- oh that's cool

I didn't know about that

Wallet SDK for Android has moved to funding! ccs.getmonero.org/proposals/vd-wallet-sdk-android.html

VostoEmisio Animated Tail Emission Core Concept Video has moved to funding! ccs.getmonero.org/proposals/VOSTOEM…SIO-TailEmission-Concept-Video.html

valldrac: ccs.getmonero.org/proposals/vd-wallet-sdk-android.html

merged :)

<naphtha[m]> "> <@gfdshygti53:monero.social..." <- yeah but he propose to use a small ssd for caching. Which significantly accelerate the syncing on hdd

that would mean having 2 disk images for each vm no? one hdd one ssd

Yes

unless i do the caching on the host

^ rq?

?

Doing the caching on the host would contaminate the cache (except if it's totally reserved for the VM hdd

need to be specifically configured as "write cache" too

What's written on the HDD is written on the cache

What's read from the HDD is **not** written on the cache.

That way you get 16GB+ worth of cached block (the latest one)

* need to be specifically configured as "write cache" too... (full message at <libera.ems.host/_matrix/media/v3/do…a3e7cc351fdff350c30491b4add451138c8>)