elvith

Tech Enthusiasts: Everything in my house is wired to the Internet of Things! I control it all from my smartphone! My smart-house is bluetooth enabled and I can give it voice commands via alexa! I love the future!

Programmers / Engineers: The most recent piece of technology I own is a printer from 2004 and I keep a loaded gun ready to shoot it if it ever makes an unexpected noise.

Security technicians: takes a deep swig of whiskey I wish I had been born in the neolithic.

Nach dem Fick herum sind wir also endlich bei Finde heraus angekommen?

Vermächtsnisgeheimschriftsbasis wäre auch nett Ü

In reality, it does make OPSEC somewhat harder, if you have to constantly remind yourself to not use WhatsApp, Telegram (LOL), whatever and exclusively use $CustomSignalFork to talk business. Human make errors.

BUT I really don't think this is worth the loss of privacy as this is in no relation to the gains, that I can see. Also as I intentionally mentioned Telegram above - it's hard to use "right" and this problem does already exist today to some extent which makes the bad trade off still worse. I mean, howany people are you really going "to get" with this?

Maybe I didn't search right, but since I found podlet first, while looking for a tutorial, I was lazy and gave it a try. It's result was enough to get me there. Maybe, had I completely read the podlet docs and checked all optional arguments, o could have gotten a perfect result. But that way, I learned better about quadlets.

Ich bin mir da nicht so sicher, ob das C in CxU wirklich noch für christlich steht...

I'm currently trying to migrate my stack on my VPS from docker to podman. Bonus points if I get it running rootless.

Somehow, podman compose just wouldn't work with my existing docker compose file. I quickly found out that podman has many options, but quadlets are preferred. It took me a while to understand what they even are and their concept. I did get the idea and the concept from the docs, but everything else was demonstrating how to set up a very simple one (think a hello world container). Or I found some blog posts with ready made complex examples for some random stacks that were way over my head. But a simple tutorial on how to map the fields/parts of a docker compose to a .container, .network or .volume file for my stack consisting of several containers in a few networks with a reverse proxy in front of it? Nope.

I'm the end I found podlet and used that to convert a docker-compose. While the result wasn't completely working (e.g. a problem with some environment vars that got passed and switched in a few "layers" that podlet understandably messed up), it was enough to understand all of it with the docs and complete the quadlet. Now I just need to experiment with the rootless part.

Currently, my first and foremost pet peeve is, that different distros use different approaches and utilities, but many blog posts or guides don't tell you what distro they're for. If you google the problem and find the fourth guide on how to solve it and realize halfway through, that it's again e.g. for Debian based systems, while you're running on SUSE or RedHat or Arch or.... can be very frustrating.

I also got this survey and I had the same feeling. It felt more like a patron for their game preservation program with possible features like a members-only-community, interviews or documentation about the preserved games, their publishers/studios and the efforts to keep them running or some kind of loyalty rewards/discount coupons. Maybe even 'special builds' like 'experience the OG version 1.0 of $game'.

There was one option, that I interpreted like 'maybe we will put future compatibility updates after purchase (e.g. supporting Windows 12 or whatever) behind the membership' - but that's purely my interpretation of a single bullet point style line in that whole several page long survey

Du hast halt trotzdem keine Garantie gehabt dass das so bleibt, Sub-Minimum-Spec Gaming hat diesen Nachteil einfach durch die Natur der Sache

Streite ich nicht ab (und bin auch nicht betroffen). Und wie gesagt, bei einem gewissen Alter der Hardware muss man mit Problemen rechnen. Vorallem im Gaming-Bereich und bei "großen" Titeln, die Leistung fordern.

Worauf ich eher raus wollte ist, dass "Minimum Spec" nicht immer so trivial zu Parsen ist. Wenn bspw dort ein Ryzen 5200 gelistet wäre, aber ich einen 3800XT hätte. Kann ich da erkennen, ob mein alter Prozessor wirklich unsupported ist, weil ihm evtl ein Befehlssatz o.ä. fehlt, wenn außer der Angabe des Modells nichts weiter dabei steht? Oder geht es eher nur um die Leistung die in dem Beispiel sicher mehr als ausreichend sein sollte?

relevant

Noch dazu:

Ab den Intel Core 4000 und AMD Ryzen 1000 ist das benötigte AVX2 enthalten. Beide Prozessoren in den Mindestanforderungen sind aus dieser Generation. Mag ja sein, dass bei reiner Leistung auch die Vorgängergeneration einen der genannten toppt und es ist nicht so einfach „erkennbar“, was genau zu der Mindestanforderung geführt hat. Aber ja… bei 12 Jahre alter Hardware bin ich nicht sooo überrascht, dass es Probleme geben kann.

Dumm nur, dass es zuerst funktioniert hat und ein Update das nun lahm legt. Das würde mich in der Situation ärgern - wäre das Spiel direkt nicht startbar gewesen, dann hätte ich noch einen Refund bekommen. Es kann ja durchaus sein, dass es sinnvolle Gründe gibt, AVX2 erst später verpflichtend zu machen - dann wäre trotzdem die Info spannend, warum…

~$ sudo apt assessment