you really do not want to create a bidet for superheavy. They just need to create steam gap between exhaust and seel.
TheHolm
Heh, I did about same but on FreeBDS. Plus proxy server to share dialup connection around home.
Time is in the essence. We do not have time to build all these fancy,expensive and mostly experimental stuff. Planet will be already cooked by the time they a ready. There are lots of good potential technologies around. From hight altitude wind, to ocean current turbines, to orbital solar. Problem is none of them is ready for production.
There is are two well tested green technologies capable to provide stable power. Hydro and nuclear. We do not have place to build more hydro in Australia. Nuclear is only option.
Keep burning coal due to radiophobia is just stupid. And we will not get anything else in time.
Call me crazy, but I'm using jellyfin + beet for backend. Native Jellyfin client on PC and Sympfonium on mobile. Works for me. But my library is small less than 50k tracks.
you need to be organised with beet. Import your music one album after an other. use "-t" to be sure that beet is guessing albums correctly. It is lot of work, but once it done it is smooth sailing.
Not realty helpful but SLAAC was working fine on pure Debian at least back to buster. Sorry, do not have that machine around anymore.
Fail to see benefits of going BD. Just run some spare cores will be cheaper and more straightforward.
Or just call a guy to do splicing. It is no longer elite job ( at least in AU). They not charge more than electrician these days.
You can use gitlab. Big and feature rich. or gitea - small neat and have all important features. With gitea add something like "woodpeaker" for CI
Hydro is great. Problem is we will never have second Snow Hydro, there is no place to build second one. And we also nearly out of places to build hydro generation plants. TAS have some resources but transmission to/from is pita.
without memory pressure only inactive and pages without write activity pages are moving to swap. It would be interesting to see memory stats for Lemmy itself. I expect that rest of the stack should be pretty much memory-leak free.
What about deluge on top of OLM ring? Is there any new about it?