vrighter @ vrighter @discuss.tchncs.de

Posts

0

Comments

1,053

Joined

2 yr. ago

because that's not how a phone is used.

But it is how any phone/desktop/laptop pollworks. So you're proving my point. Most can't even tell if the file they want is on the device in the first place, if they use stuff like cloud backups. To those people, the file is "in google". Not tech savvy

yeah I have a loan with them. otherwise I'd just switch

it is anything but easy to read if your entire file does not fit on a single screen.

it's not becoming boomers. It's about rarely meeting one who knows that, for example, wifi is not the internet. I'm not asking for detailed tech knowledge. But getting a blank face if asked something as simple as "where did you save the file?" or replying with "in the gallery/google photos" means you are not tech savvy. these are the absolute basics.

would be cool, but it won't solve the whole problem. Apps like kde connect need accessib ility permissions to sync notifications with the desktop, for example. It won't run if any unknown app has those. (like, my custom keyboard compiled from source)

firefox for most things. Chrome for my banking. The banking app refuses to run on my unrooted phone, because I have apps from f-droid installed, and I have a custom keybooard. And their site only works in chrome. Fuck hsbc

but gen z is not tech savvy. They can use a browser. and watch youtube. They never advance past that stage

except that it can, and regularly does, regurgitate copyrighted works verbatim.

so the creator of gif himself was deliberately transgressive?

i love the dougdoug ones for that

but in games, triple buffering is the norm

I had lots of cars the size of burgers though, when I was a little child

that's just how the code is rendered. There's still all the usual constructs

except that they literally say it is.

!

because we can

doesn't have to be a cube

new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No 'but that's insecure', no 'but why would you want to do that' (for setting a window icon or positioning the window ffs). Support existing applications. I'm not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it's already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.

As an example, the accessibility protocols. They're good to have. Except they're opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.

The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You're just the one looking down on people like me for wanting functionality in existing apps to be "not literally impossible to implement"

I do not care about security risks. If something made its way onto my system, I've already lost. I just want one implementation of something that gets the job done. And by "gets the job done" I mean it allows us to do things better, not disallow us from even having the option to do things because someone had their tinfoil hat on too tight. Ffs you can't even set your window icon. I don't care if kde has implemented that feature. If I use that, I'd be supporting kde, not wayland. It won't work on other des and so the maintenance burden increases drastically.

"almost" being the key word there.