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.
Does this mean I can stop setting MOZ_ENABLE_WAYLAND?
Or is it just enabling the compilation of Wayland sections (which I thought happened a while ago?)
Are we reading the same article?
You assume they’ve read the article 😬
Finally finished Inscryption.
Holly shit what a game.
Looked around some more - maybe it’s because they’re all GTK apps?
https://unix.stackexchange.com/questions/178070/why-does-shiftinsert-paste-from-clipboard-in-some-applications-and-primary-in-o
There’s a bug open for Firefox and you can change VSCode’s behavior by putting this in your keybindings.json:
{
"key": "shift+insert",
"command": "editor.action.selectionClipboardPaste",
"when": "textInputFocus && !editorReadonly"
}
Not sure why either of them are messing with a “standard” shortcut…
If you want a more system-wide solution there are utilities that let you sync the PRIMARY (on selection) and CLIPBOARD (Ctrl+c) buffers mentioned in the Arch Wiki entry.
One step closer to ⛧ Linux 6.6.6 ⛧
Yeah no way, the 90s were something like 10 years ago and… wait now we’re in…
Ohh… Ohh no…
Right so just installed xscreensaver - automatic blanking and locking is indeed broken BUT it does display all the pretty animations just fine! (at least on Sway)
Don’t really have time to mess around with it but maybe try figuring out which mechanism is used for screen locking in your environment (in Sway’s case it’s swayidle) and get it to start xscreensaver right before calling the real locker program?
BTW you can get xscreensaver-settings to come up by unsetting the WAYLAND_DISPLAY variable:
env --unset=WAYLAND_DISPLAY xscreensaver-settings
Philosophical BS: I don’t think it’s correct to say that Wayland doesn’t support screen savers, but rather that it doesn’t support XScreenSaver, or, more accurately, the mechanisms it uses for screen locking and idle-detection.
As others have pointed out, equivalent functionality has already been implemented and is used by various screen lockers. What appears to be missing is something to take this functionality, and display an animation instead of just locking the screen.
I noticed that all of XScreenSaver’s animations are actually separate binaries in /usr/lib/screensaver/ so we basically need a locker that speaks Wayland’s locking protocol, but also takes and runs those binaries in full screen mode.
Or maybe XScreenSaver’s dev can be convinced to add support once the protocols are stable?
Wait there’s places without mandatory driving lessons?!
Late 20s Israeli. Can and do, though overall manuals are in a steep decline.
I think most people here still drive them as learners though - mainly to have more variety when renting a car abroad.
“Oi, fuckface!”
NEED A DISPENSER HERE!
Been using this futon mattress for half a year - best sleep I’ve ever had.
Keep in mind though that this is coming from someone who is fine sleeping on two folded up blankets 😅
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…)