Posts by uecker@mastodon.social
(DIR) Post #B6piZyKpVHiksHMikC by uecker@mastodon.social
0 likes, 0 repeats
@navi @gemini0 Lol, wasn't xinput2 designed by the wayland guys?
(DIR) Post #B6piZyjI2LHq68oFs0 by uecker@mastodon.social
0 likes, 0 repeats
@navi @gemini0 No, I don't think so. I think Daniel Stone was involved in designing xinput2 and then later decided X was all crap and has to replaced by Wayland (which I think it a much poorer design).
(DIR) Post #B6piZz1ivo231JQybQ by uecker@mastodon.social
0 likes, 0 repeats
@navi @gemini0 yep, daniel stone. https://www.x.org/releases/current/doc/inputproto/XI2proto.txtI very much like x11 with xcb. It seems very clean to me. Where do you see a specific problem?I never did anything fancy with input devices though, so maybe this part is bad. But I notice that xinput had different device types...
(DIR) Post #B6pj3TpZTw4SxGob5c by uecker@mastodon.social
0 likes, 0 repeats
@navi @gemini0 That overall does not look too much different to modern X and xcb to me.
(DIR) Post #B6pj3UFRvilsFWvGQS by uecker@mastodon.social
0 likes, 0 repeats
@navi @gemini0 or so the wayland propaganda says. X had a security extension that isolated clients forever. It did not support some modern extensions. But I had patch to add those and the clients I tried worked just fine. I also do not quite see the issue with 2d global coordinate system. we had 3D desktops with X11 in 90s. maybe it was some hack, but I really can't see what the fundamental issue should be.
(DIR) Post #B6pj3UeyOpBhWgreD2 by uecker@mastodon.social
0 likes, 0 repeats
@navi It is the XSECURITY extension also supported by ssh but usually deactivated. It isolates clients but also then sadly does not expose newer extension needed by modern clients. I still do not get the problem. So there are issues with older clients? Changing the protocol completely will also not make this work for older clients.
(DIR) Post #B6pj3UzXANdOYSU4G0 by uecker@mastodon.social
0 likes, 0 repeats
@navi but people did this with x11. wobbly windows, windows on a cube, 3d distorted windows? maybe I still missing your point.
(DIR) Post #B6pj3VCeNc7tD8cXhY by uecker@mastodon.social
0 likes, 0 repeats
@navi stuff like this: https://www.youtube.com/watch?v=4QokOwvPxrE
(DIR) Post #B6pj3VWVBo0QChuOe0 by uecker@mastodon.social
0 likes, 0 repeats
@navi A popup is just another window, and the wm ultimately decides placement. And don't there is anything of this kind that can not be done on x11.
(DIR) Post #B6pj3VfidXNWfIDl0i by uecker@mastodon.social
0 likes, 0 repeats
@navi What I always found far more interesting is being able to move windows between devices. E.g. from a cell phone to the desktop, or from the desktop to some computer controlling a beamer, etc. This never was supported by GUIs but worked perfectly fine if you implemented it yourself.
(DIR) Post #B6pj3VzDT2yTdlLKOu by uecker@mastodon.social
0 likes, 0 repeats
@kirtai @navi Yes, it was originally part of the GPE palmtop environment. xlib had annoying limitations and also the default error handler was to terminate the program instead of trying to reconnect or something. But easy to do otherwise. I had high hopes for LInux 20 years ago...
(DIR) Post #B6pj3WLY80q4l1nADA by uecker@mastodon.social
0 likes, 0 repeats
@kirtai @navi Well, there was XCB which is great, but just as I thought we will see progress, somehow the people paid to maintain the core infrastructure decided to redesign it. My conspiracy theory is that something like X was not controllable enough for the walled garden some people want to design for us.
(DIR) Post #B6pj3WiakLGpuUZZ7w by uecker@mastodon.social
0 likes, 0 repeats
@navi @kirtai The question is, which one will you still be allowed to use on your systemd system that verifies your identity before you can use some app with remote attestation to watch some local content, and all this on a Rust-hardended system that can not be jail broken anymore.
(DIR) Post #B6pj3X73HOpv8M16Fk by uecker@mastodon.social
0 likes, 0 repeats
@navi @kirtai You could lock down X as well, but in a world where proprietary pixels are not supposed to leave your device, something like X is completely the wrong design.
(DIR) Post #B6pj3X7lElP5AYLfMG by uecker@mastodon.social
0 likes, 0 repeats
@navi @kirtai The technology developed is shaped by the interests that fund their development. To some degree this is ok. But it explains the priorities. Network transpareny is not important, systemd needs to control everything, memory safety is really important, etc.
(DIR) Post #B6psqaBJYeUcQcTRiq by uecker@mastodon.social
0 likes, 0 repeats
@navi @kirtai btw: Just randomly found this:https://wayland.app/protocols/weston-content-protection
(DIR) Post #B807uCW031GVpGl3Oy by uecker@mastodon.social
1 likes, 0 repeats
In the past, one could rely that packages from official debian repository get security updates if necessary. Sadly, nowadays, you need to check with "check-support-status". The two packages which are a problem on my system are: librav1e0.7 and debian-repro-status. For the later I did not realize this was a rust program, I thought it is python because it is so slow.
(DIR) Post #B807uKHPBALPuJzVlQ by uecker@mastodon.social
0 likes, 0 repeats
So probably one has to recompile libavif to get rid of this...
(DIR) Post #B86CbyvlTsbBCXhVOy by uecker@mastodon.social
1 likes, 0 repeats
@DrHyde Why? I started to use it now in one of my projects which supports 18 architectures.
(DIR) Post #B8QnFblEDeU1hktfou by uecker@mastodon.social
1 likes, 0 repeats
@mjg59 Having this followed closely at the time it happened and also having owned an N9, I still believe that "Elop killed non-Android LInux phone" is more than a meme. That Android or iPhone were not beatable is a retroactive description that declares today's winners unbeatable, but is not how things unfolded at this time.