Correct ^_^
Tank was likely captured in Egypt in the 50s or 60s, and transported to a military workshop next to the city - probably to study Soviet armour.
Years later the city was expanding, so they decided to move the base someplace else and someone decided to just burry the thing instead of transporting it again.
At least, that’s the official, “logical” explanation that we got that conveniently ignores the possibility of secret Soviet space-time travel experiments!
Construction workers were digging foundations at a local work site and found a Soviet T-34 tank burried in the ground.
Important context:
There are some plausible theories, but to this day nobody really knows how it got here or why it got burried.
Ohh and the real kicker: the street this all happened on is named after an indigenous tank, so the news headlines all basically said “Tank found on Tank street!”
There’s a very nice (albeit somewhat outdated) talk here.
In a nutshell, both X11 and Wayland are protocols that define how software should communicate to (hopefully) display stuff on your screen.
Protocols as in there’s a bunch of documentation somewhere that says which function a program must call to create a window, without specifying how either program or function should be implemented.
This is great because it allows for independently written software to be magically compatible.
X11 is the older protocol, and was working fine good enough for many years, but has issues handling a bunch of modern in-deman technologies - issues which can’t be fixed without changing the protocol in a way that would make it incompatible with existing software (which is the entire point).
Plus its most used implementation - Xorg, consists of a huge and complex codebase that fewer and fewer people are willing to deal with.
Wayland is the newer protocol, that mostly does the exact same thing, but better, in a way that allows for newer tech, and completely breaks compatibility in order to do so.
The trouble with the whole situation was that in order to replace X with Wayland basically the entire Linux graphics stack had to be rewritten - and it was, with raging debates and flame wars and Nvidia being lame.
They also wrote a compatibility layer called Xwayland that lets you keep using older X-only apps which somehow manages to outperform Xorg.
Now we’re at the point where major distributions are not only switching to Wayland by default, but also dropping support for Xorg completely, and announcing that they’ll no longer maintain it, which is why posts about it keep popping up.
Ads on a computer??
He got his monitor mixed up with a TV screen or something lol
Thought this was about Valve’s Wine fork and was very confused 😅
Here’s a great documentary about it!
https://youtu.be/vw9zyxm860Q
So I had the brilliant idea of googling for “lemmy global post links” right after posting this and of course it’s already an open issue 😅
Kinda depends on how much you’re familiar with low level programming.
For a quick check to see if it’s for you start by learning a little about how a processor works here (the first episode can get a bit condescending at times, but it’s good info).
Then try diving into a disassembly CTF like MicroCorruption.
If you (somehow) enjoy both those things, consider learning C and specifically how to use it to break things through shellcode.
C Programming: A Modern Approach, and The Shellcoder’s Handbook are great resources for that (look here for instructions on obtaining them 😉).
Yeah but OP is upset about not being able to share or resell the game, which isn’t possible after using the key, even with the physical copy…
I haven’t bought a physical copy of a game in a while but don’t they all come with a key that you must associate with an online account nowadays?
Sure it can, with waypipe (like, for a while now…)
Just
waypipe ssh <host> [command]You can even run X apps over this through cage even when X11 forwarding is disabled by the host (because, you know, the security issues…)