How about just firewall France and discover if legislators find cause to pass new laws.

Once you start hosting an instance that has open registration, it’s not just “their house” anymore. They are providing a service to people. They do so willingly. Arbitrairly blocking instances because you don’t know how something works and don’t bother to check it isn’t the way to host a free and open instance.

You seem to be uniquely bad at reading so this is comment is the start of this subthread you originally replied to. Nobody ever suggested they COULDN’T implement any rule they please. It was never a point anyone brought up for you to be refuting. It is literally you dishonestly trying to steer the discussion away from the actual point of discussing SHOULD they.

The discussion is not whether they can set those rules its should they and should we keep participating

So is discussion on the topic of piracy that doesn’t include actual links to content.

The law in the US is that you aren’t responsible for what your users post unless you are specifically legally notified and furthermore the communities at issue don’t host links to infringing content they host discussions on the topic

Feel free to leave if this is how you talk to people

They CAN do all of those things but people would be right to critique them for it. Freedom isn’t freedom from criticism or complaint. Furthermore they want this to be a functional community as much as their users do which is why this discussion even exists.

It would be preferable if you would lie less. Evil pirate uploads potentially_infringing.mp3 to to filehost. Filehost actually serves potentially_infringing.mp3, a community on db0 hosts a link to potentially_infringing.mp3, lemmy.world caches locally a copy of data from db0. Of those the one guy directly uploading the information is at risk of an extremely unlikely single digit thousands of dollars.

Nobody not even evil pirate himself is at risk of decades in prison or millions in debt. Companies responsibility basically ends at taking stuff down when specifically notified of infringing content.

Your argument is that user hosts infringing_song.mp3 on file_host, a community on lemmy.ml has a link to filehost and lemmy.world has a cached copy of the text containing the link to lemmy.ml which has a link to filehost and you think lemmy.world has legal exposure?

On most phones the end result will look fairly poor AND it will be a pain in the ass.

For practical purposes its capturing revenue from OEMs and users. Android being open source if they didn’t completely sabotage an actual open source market they could well find OEMs or third parties capturing those dollars or indeed those unearned dollars evaporating in a competitive market. Think the IBM PC and Microsoft.

SU software has been a thing for about as long as android about 20 years or about. Has otherwise legitimate su been a source of unattended exploiting?

The obvious risk factors are that users shall be tricked into granting inappropriate permissions to otherwise malicious or compromised software that they have deliberately installed. Outside of mobile platforms this is considered an acceptable risk that competent users can consistently successfully manage on their own hardware.

In fact if you look at actual users even those with very limited technical know how the primary thing that

The secondary risk is that users with no legit source of tools to root

if you use an exploit to gain SU what makes you think a malicious app can’t do the same

They can. 99% of computer security is still not installing malware or being tricked into taking actions that enable your own harm. That said often rooting methods involve physically pressing keys while booting to access the boot loader, ADB, running things with with expansive permissions. Malicious apps install via play store with reasonable permissions will generally have a much harder time breaking out of the sandbox.

Or better yet, find a new exploit in the SU management software you installed

Historically “sudo” tools haven’t been the source of many issues whereas a multitude of problems flowed from complex memory unsafe code.

As soon as you root, you can no longer guarantee root activities are not taking place unbeknownst to you

You can never guarantee this however if you are careful what you install you will remain safe same as it was before.

Building on top of wlroots is still a different scope of problem than writing a window manager for X. Pretending its the same thing doesn’t change the fundamentally different architecture even if it certainly makes it easier.

Out of all the libraries isn’t recent KDE the only fucking one that supports proper scaling of xwayland windows without turning it into a blurry mess? KDE which nice as it is lacks most of the nice tiling features of i3wm or the per monitor workspaces? Let me rip out and throw away a highly functional Nvidia GPU and come on down!

Don’t worry in another fucking 10 years all problems will be solved in the meanwhile I’ll just be fucking using non-beta software. Pardon me if I’m a little annoyed. Wayland has been the future for a while now.

I switched to using Linux in 2003 and have by my assessment got quite a bit of value over the last 20 years maybe you shouldn’t have waited?

X has a singular fully functional implementation into which you can slot a wide variety of components. Because everything is a component that slots into the singular X implementation forking has both a low benefit and a high cost.

Wayland is just a protocol everyone must implement with a semi useless reference implementation that nobody would ever use. Nobody forks Wayland they just implement it as they must the X approach isn’t available.

It’s apples to oranges. A meaningless comparison. Its more just churn than innovation on the part of desktops.

The article is 3 years old and some things are only presently being fixed NOW and due to filter down to stable distros in 2024. Furthermore wayland proponents have been claiming its totally ready for prime time and not broken at all since 2015 while promoting AMD GPUs that at that point in time still sucked hairy balls.

For most of its 15 year history implementations have been woefully and obviously insufficient. Nobody forked X because nobody needed to. Its feature complete and has been for a long time and there was nothing wrong with using X while Wayland implementations see progressive improvement.

It would be great it implementations had a full set of features 15 years in just saying.

Doesn’t that drastically limit your monitor support like to ONE?