[-] feral_hedgehog@pawb.social 35 points 4 months ago

Construction workers were digging foundations at a local work site and found a Soviet T-34 tank burried in the ground.

Important context:

  • My town is not in Russia or the former USSR.
  • My town is not in Europe either.
  • Our military doesn't even operate Soviet equipment.
  • My town is also not next to a border with a country who might have operated Soviet equipment when it was also not so friendly with my country.

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!"

[-] feral_hedgehog@pawb.social 64 points 5 months ago

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.

[-] feral_hedgehog@pawb.social 30 points 7 months ago

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?)

[-] feral_hedgehog@pawb.social 61 points 9 months ago

One step closer to ⛧ Linux 6.6.6 ⛧

[-] feral_hedgehog@pawb.social 21 points 9 months ago

We'll bang ok?

[-] feral_hedgehog@pawb.social 20 points 10 months ago

"Oi, fuckface!"

[-] feral_hedgehog@pawb.social 39 points 10 months ago

So get comfortable, while I warm up the ~~neurotoxin emmiters~~ chlorine refreshments

[-] feral_hedgehog@pawb.social 26 points 11 months ago

Which edition are you trying to install? Are you using an up-to-date ISO?
I've only ever used the business edition, and it's never given me any trouble.

  1. Head over to the tools section in the megathread at !piracy@lemmy.dbzer0.com
  2. Grab a clean business editon ISO from one of the listed sources.
  3. Create an installation flash drive using rufus.
  4. Make sure all the legacy CSM crap is disabled in BIOS.
  5. Boot off the flash drive and run the installer.
  6. When you get prompted to sign in with a Microsoft account click "Domain join instead" (or something similar).
  7. Create a normal account but leave the password field blank (to avoid having to enter security questions).
  8. After you finish the setup and get into Windows, hit Ctrl+Alt+Delete and set a password.
  9. (optional) Go into settings and either enter your legally obtained key to activate Windows (it should automagically recombobulate itself into a matching editon) or read through the aforementioned tools section for an alternative 🏴‍☠️
  10. ???
  11. ~~PROFIT~~ You've installed Windows.
[-] feral_hedgehog@pawb.social 13 points 11 months ago

I got two Brother laser AIOs (MFC1910W) for my folks and myself.
All I had to do on Arch was install brother-mfc-1910w for printing, brscan4 for scanning and oh-brother for (occasionally) upgrading the firmware, all over WiFi.
I think more user-friendly distros come with these packages preinstalled, so it should just be a matter of opening the printer manager and waiting for it to show up.
Don't think they make the specific model anymore, but any Brother laser AIO should do.

1

The "Browser Default" setting doesn't appear to actually follow the browser's theme and always sets the interface to darkly.
Tested with Firefox and Chrome on Linux and Android with this website used for reference.
Sorry if this is intentional/was posted before.

15

Lets say someone sent me a link to this post on lemmy.ml.
If I click the little federation-link-hexagon-thing button I'm redirected to the same post but on OPs home instance of feddit.uk.
Is there a way to jump to the post on my home instance instead?
The post number differs between instances, so you can't just replace the instance in the URL.
I tried doing something similar to how community URLs work:
{remote_instance}/post/{post_number}

{home_instance}/post/{post_number}@{remote_instance}
But it don't seem to work...
I know you're supposed to browse things from your home instance, but people sometimes link posts in the comments and the only way I found to interact with them is to go back and manually search for them from my instance.

view more: next ›

feral_hedgehog

joined 1 year ago