Storage is not easy when you don't have massive amounts of free land. This is an ongoing debate in Europe, and in one particular country a leaky storage was discovered just a month or two ago. Again.
And there is no guarantee that what we build today is not going to be a massive liability in 50 or 200 or hell, 500 years. But the companies and people who are responsible will not even exist at this point.
What about the storage for the used fuel? This is a massive problem for any country not occupying half a continent.
Man könne auch eine gewisse Zeit crossposten, und darauf hinweisen. Ich fände es super, ein paar communities auf den Server mit content zu versorgen. Diese dann zu folgen = mehr Traffik auf die neue Communities.
You would be better off with a dongle. I have one which supports hi-res audio and has plenty of power to drive my over ear audionerd headphones. Phone jacks and DACs can't ever match that.
I was considering grabbing a last minute legacy license, but I really don't have a use case for unraid. I need a NAS for storage and a few VMs. And my apps run on generic SBCs or NUCs which I manage through ssh/ansible. So yeah, TrueNAS it is for me as well.
You are not far off. In my previous project we attempted to rewrite a desktop app and we started with a skeleton crew. Hiring for the frontend was tough, we got one very good xaml (wpf / winui etc) dev in the first year. Then, in the middle of the corona lockdowns, for 12 months we kept only getting mediocre candidates from across the world, with no relevant experience whatsoever. Then we found our second full time frontend dev, who only stayed 3 months and once he saw how clueless management is, bolted.
Funnily enough the aforementioned manager experts started asking what's wrong and why we 'fail to fill the positions'. We were stuck in the native desktop world product-wise, an unattractive and challenging tech stack with difficult problems to solve, with poor management and low budget. That's what was up. Now I'm happily working on the backend / web / cloud side of things and I'm definitely not looking back or picking up another tech lead position for a project with non existent team to start with. /o\
What are the advantages of using the plugin (Remotely Save) over just using dumb sync with Syncthing? Conflicts I assume?
Hey you absolute idiot. This is history, not a narrative. Get the f out.
As someone with years of Go experience, this thing bites me or my team in the ass at least once every six months. Sometimes tests catch it, other times the tests get written after the fact and made to fit the implementation. Hilarious bug hunts ensue. I'm happy for this proposal moving forward.
Interesting, I'll take a look before Google shuts down yet another app I use. Does it support sharing and syncing over something other than nextcloud?
Ansible everything and automate as you go. It is slower, but if it's not your first time setting something up it's not too bad. Right now I literally couldn't care less if the SD on one of my raspberry pi's dies. Or my monitoring backend needs to be reinstalled.
Too late for that