

Okay? Just because it’s possible does not mean the avg instance will bother, much less avg person


Okay? Just because it’s possible does not mean the avg instance will bother, much less avg person


No, but basically no instance will do that, and for the vast majority of people on this planet just self hosting it is so far out of their knowledge that forking it would be inconceivable for them


I literally installed it the day before yesterday, the first page of logs was applied x blocklist, applied x blocklist… Unless the pyfedi repo is unofficial?


I’m not going to look through the code for proof for an online argument, but the reason I believe that is because there is/was code that searched for anonymous and No. in any uploaded image, and failed with a fake error message when you try to upload it


Literally yesterday I tried hosting a piefed instance, with no intervention, it applied these exact lists, and there was no option to change it which is why I switched back to self hosted lemmy


What? You mean lemmy? I have one. If you mean a different piefed instance, that’s what I was saying, you’d need to fork the pyfedi repo to remove the list, it’s on every instrnce of piefed


“Changing the setting” would involve forking the codebase, as it’s hardcoded iirc


That’s a small subset of parents though, most schools use Chromebooks with enterprise enrollment and no Linux dev environment


*schools and corpos


I tried to remove it with uBO and it still wouldn’t let me scroll no matter how much I zapped


While phones may cause some issues, the blatant disregard of any issues bans cause by administration and lawmakers makes it hard to trust reports of success for me, as in my experience, the removal of phones seems to wall off school from students lives, even during breaks and makes students stressed and feel overworked for no reason but “phone bad”


The point of the stays halo series is the unified memory, so an additional GPU wouldn’t be very useful, no?


Wifi/router side parental controls are laughably easy to get around


The main benefit is the strix halo cpu uses unified memory, thats why it’s soldered, not bc it uses laptop parts


That is all fair, and I’m sure there’s other issues with Wayland, but really all my issuis come down to xwayland problems. I didn’t realize KDE was dropping x11 though, that is unfortunate


I know CRTs are good(ish), but there not a standard use case. Also most mainstream des support both x11 and wayland


Yeah it does?


So your argument for x11 is Wayland doesn’t work on crts and doesn’t let all programs access clipboard and kb events freely? If you are using a cat, then use x11, thats why it’s an option


Its 17 yrs old now, and most wms use it, some don’t, but almost all either support it or require it, and the only issues I’ve had are due to electron not having ozone on by default. I don’t think it’s progress necessarily, but it’s most definitely on par with x11 by now
Ok, but the only reason for there to be default blocks with no env var to disable, no command flag to disable, and no setting to disable is to want them to be applied to every instance