Depends what you mean by bloat. It has a very large repo, but it compiles into little commands with least privilege execution. A lot of those commands are specifically there so someone doesn’t have to pull in other repos with a larger attack surface. e.g. there is a time sync daemon to replace having to pull in ntp which is a lot more complex and fraught and the one thing most desktops need of NTP which is to set the clock.

Why do you still exist? I try understanding what the purpose of your reply could be? Screenrecords do not work. For plenty of people. Google it. Yet you feel entitled to share you smalldick energy wisdom of “proper way”. That is exactly the vibe of the shit ppl. You do not help Wayland or x11 or anything, you just fap into your own mouth because nobody can ever love you like that. Go get help.

Wow, someone needs to grow up. You laid into Wayland when screen recording doesn’t even go through Wayland. The app asks the WM to screen record via DBus. A more constructive response would have been “thanks I didn’t know that”, or perhaps “oh it’s a driver issue”, or “it’s an issue with that WM/ffmpeg/pipewire or whatever”, or anything else likely to be the underlying cause. But it’s not Wayland. Have you got that? Not Wayland. There is no need to be sore and immature about it.

Screen records do work providing the app asks for a screen cast in the proper way (which BTW is not via Wayland but through a message to a DBus service). The service and the desktop then ask permission from the user if necessary. X11 didn’t give a damn about protecting the contents of your screen and any app whether it was beneficial or malicious could do it with impunity. So you should see this as a major security improvement - you can screen record but only if permission is granted.

Yes it’s been stable for some time with a couple of caveats - you need a decent graphics driver and not be using apps with edge cases.

Here is a simple example of an edge case and it’s not hard to find people blaming Wayland even though with some thought this was a security issue - apps like Zoom, Discord, MS Teams want to do screen sharing which is easy in X11 because it has non existent security - just steal the screen bitmap. That’s a problem.

Wayland (the protocol) provides no means for one app to grab the screen, or other apps. This is by design for security. Instead the app must be a good citizen and send a “i want to screen cast” message to the xdg-desktop-portal (a service provider implemented by GNOME, KDE etc.), the desktop asks for user consent and then the app gets a video stream. So it’s a lot more secure but it requires the app and the WM do things properly.

Desktops and apps have matured and these issues are thankfully going away. I think the biggest hurdle left is proper graphics drivers, especially the problem of getting NVidia drivers working.

I think Wayland just attracts trolls in the same way as systemd does.

I’m glad Wayland is maturing and taking over. Even most of the X11 devs hated X11 which tells you something.

GTK 3 support just in time for GTK 4 & 5

I’ve been using it on and off since 1994. I still have a slackware dist on CD with the 1.1 kernel. I think Linux is great although I still prefer to use Windows, and Linux via WSL which is my optimal set up these days.

That’s more or less it. Linux Torvalds hates the different package managers and dependencies in different dists and versions of dists. He claims it’s virtually impossible to ship products that just run on some random dist and cites his own sideproject which is a sea diving app where he builds binaries for Mac OSX and Windows but can’t for Linux. He also praises Valve for using containers.

In theory it means slightly larger binaries, but the flipside it means Steam for Linux runs on a lot more dists, and so do the games and it’s far easier to test they actually run.

Ubuntu. There are mixes of it but out of the box Ubuntu is about as straightforward a dist to install as possible and it is well supported.

That said “new laptop” and Linux are not always a match made in heaven. You might try it from a boot stick and confirm that things like the GPU, touch screen, touchpad, fingerprint reader, USB C / Lightning all work properly.

The EFF has some info about the practice - https://www.eff.org/pages/list-printers-which-do-or-do-not-display-tracking-dots.

I imagine there are ways and means of obfuscating / anonymizing the dots such as blocking the printer from emitting them (e.g. an empty yellow cartridge that the printer perceives as full), modifying the firmware, using a burner printer, or using a mono laser jet.

As a side issue, most modern bank notes have a bunch of yellow circles integrated into the design on each side. They look random but they’re in a recognisable pattern called a constellation that enables devices like copiers / scanners to recognize when people are trying to copy money or other financial instruments like checks.

It would be better to “git clone” a repo under threat of removal than fork it in Github. That way an entire copy of its history is preserved. It’s possible the forks still exist for now, even if Yuzu removes their official repo, but if Nintendo serves Github the legal paperwork then the forks will get blasted.

That said if someone clones the repo, they probably ought to think twice before putting it back in the cloud without sanitizing / reconstructing the branches & history absent of the bits that got Yuzu into trouble in the first place.

Yuzu gave them the opening to sue though. If they had been more circumspect - “Oh this is to develop homebrew / indie games nudge nudge” then maybe Nintendo wouldn’t have unleashed the lawyers or done so ineffectively. After all it wouldn’t be Yuzu’s fault if some wicked website corrupted their pure intentions by releasing device keys or patches that allowed their emulator run commercial games. But they were more blatant than that.

Also from an empathic perspective, of course Nintendo were going to sue. Yuzu should have known they would since that’s what console platforms do when something interferes with their profits. Yuzu is doubly bad since it interferes with hardware sales and game sales unlike custom firmware / cartridges which only affect game sales.

Of course the genie is already out of the bottle. Yuzu’s source code and binaries were on github for anyone to clone / fork. All the games are out in the wild. The piracy will carry on. I think it’s fair to say the NSP is effectively dead as a platform at this point. If a NSP2 turns up this year, as rumored, then I expect it will have revised anti-piracy measures and potentially a heavy online service aspect to go with it - it’s far easier to detect pirates and wield the banhammer when a device is online.

If you look at any modern desktop application, e.g. those built over GTK or QT, then they’re basically rendering stuff into a pixmap and pushing it over the wire. All of the drawing primitives made X11 efficient once upon a time are useless, obsolete junk, completely inadequate for a modern experience. Instead, X11 is pushing big fat pixmaps around and it is not efficient at all.

So I doubt it makes any difference to bandwidth except in a positive sense. I bet if you ran a Wayland desktop over RDP it would be more efficient than X11 forwarding. Not familiar with waypipe but it seems more like a proxy between a server and a client so it’s probably more dependent on the client’s use/abuse of calls to the server than RDP is when implemented by a server.

Some US news websites still geoblock European visitors rather than fix their site to not track the ever loving fuck out of visitors who say no. So imagine what they’re doing to their domestic visitors.

A lot of subjectivity about what is a success or not, but I would say many nationalised companies (and most were only nationalised for 20-30 years) were absolutely stagnating and/or suffering from widespread union disruption and should have been cut loose. But just picking out a handful of privatisations that went well, I think British Telecom, British Gas & British Airways did much better as privatized companies. Some privatisations went not-so-well - look at steel or coal privatisations or British Rail.

And an example of successful nationalisation - hospitals & doctors were a loose arrangement of private / charitable causes before being nationalised as the NHS. I think we can agree the situation is far better for everyone as a public health service than if it were run for-profit.

That’s literally uncomparable. Government does things that ignore profit. That’s what government is for. The provide services at a loss. The only “profit” might be things like societal improvement, education, security, and such.

People pay taxes that fund the government. If the money is wasted then services suffer. So it’s not profit or loss but they must deliver value. Value is harder to quantify than profit but governments have to figure a way out of doing it and provide incentives to staff to deliver it.

This is something you really can’t say one way or the other.

I could cite examples of sick, failing government owned companies that did better under privatization, or simply shouldn’t have been governments owned in the first place. On the other hand, I could cite disastrous privatization efforts that should never have happened because they were vital services, or in the national interest. I lived through most of it in the UK when they were privatising stuff left right and centre - some succeeded, others didn’t.

And if they stay under the control of government then they need incentivization and means for measuring success. Success doesn’t just mean profit but it does mean value and quality of service. And in some ways that would require operating similar to if it were a private company.

I live in Europe where trucks are fairly rare but you still see large SUVs, 4x4s and vans around. My own feeling is that certain classes of vehicles should be considered commercial for the purposes of insurance, taxation, VAT, inspection, tolls, permitted usage and everything else. The legislation already exists for commercial vehicles so extend it to these kind of vehicles.

So is someone must have a stupidly oversized vehicle purely for personal reasons they can enjoy all the bullshit and restrictions that goes with it. Doesn’t stop them complying but making it more onerous to do it will take demand for these vehicles off the market entirely.

Nothing provided it is an honest and upfront with consent from the user. The problem is vast majority of affiliate links are non-consensual, buried in articles and in the worst case are the reason that pages even exist - “top ten dishwashers”, “50 gifts to buy your wife for Christmas” etc. clickbait garbage. I doubt most visitors even understand that’s why the pages exist or the financial remuneration they get from making these lists.

So it would not be a bad thing that if a browser to detect an affiliate link and ask you if you wanted to follow it as-is or strip the affiliate info out with a checkbox to remember the decision for the site.