thinkbud

Can you elaborate on your view about "no copyright infringement intended" being related please?

So the LLM is working as intended?

I do not share your view of old timey sales pitch, at least for the talk about systemd nspawn OCI container support.

If anything, that talk was a tad low effort, with even dismissive answers — "Yes" and "No?" as full answers to audience questions, with no follow up?! Still very informative though!

My only disappointment with this year's geopolitcs-enhanced (always a welcome addition to tech by the way, as tech is ultimately steered by politics!) FOSDEM is a great underrepresentation of mainland China, and more generally the whole Global South. It is sad to see this omission in a time when the EU's free movement needs more like minded allies than ever. And what can be more free than that untethered by the chains of empire.

Sure, there was some mention of Brazil in some talks. And yes, a couple of China specific speakers etc, but in my view this is almost cancelled by the inclusion of topics about taiwan. Similarly the China focused talks mention "specific risks" stemming ostensibly from a differing system of governance.

Almost as if corporate sponsorships induce self censorships which limit true organizing effort.

I can confirm that this sort of phenomenon has happened to me and am as curious as you are to find out more about it

Ironically, Google's Pixel build of Android does not include UDF support - the filesystem does not work on a USB stick like FAT32...

I am in the same boat. There is an about:config flag to revert the behavior and use old menus. I am not sure whether the new mac-native context menus even have a notion of access keys, so I am not hopeful for a fix.

Do any informed US readers here know what are the implications of the FAA ADS-B privacy ICAO address program[0]? Will this reduce the possibility for hobbyists to have oversight over such flight operations?

[0] https://www.faa.gov/nextgen/equipadsb/privacy/

Last week, I tried this on an AMD 3400g (Vega 11 amdgpu) with that specific environment variable and my results were: - vainfo told me it (VA-API) can decode vp9 and h264 among others - mpv plays vp9 and h264 using vaapi - firefox log mentions using VA-API in h264 playback but in vp9 nothing related is printed

Maybe firefox whitelisted only h264 for hw decode?

Ok, I admit that "not worth it" is better rephrased as "not the end goal". If the end goal is interactive gestures, one-off discrete gestures are welcome as an intermediate step or halfway solution.

Ideally the input framework would know if the streamed gesture was consumed real-time, and if not (e.g. no support for such interactice gesture in some program), the one-off event is issued.

This reminds me of current xorg libinput two finger scrolling / wheel event. Xinput2 is the relevant keyword but I am not sure exactly how it all fits in, only what I can observe: - applications that don't know about multi finger scroll/pan listen for and accept classic mouse4 / mouse5 events and interpret them to scroll in steps if relevant. As an example, xev x event testing uility is not xinput2 aware AFAIK nor are classic x or older gtk programs - applications can be xinput2-aware (e.g. eog Eye of Gnome image viewer, but maybe also any non-ancient gtk3 application as well), in which case they can scroll more directly (pixel-smooth) and with appropriate acceleration / smoothing / inertia (gtk-specific ?). In firefox there's an env var like MOZ_USE_XINPUT2 which tells firefox it can do this smoother wheel handling, not sure if it's required or automatic these days. To test received events including xinput2, there is utility xinput --test-xi2

As a closing anecdote, there's an interesting interaction bug I have experienced with xfce where both xfwm will react to Super+scroll (compositor-level full screen zoom), and the application under the mouse pointer will also react to the scroll up/down. I have not deciphered the interactions here but it depends on app under mouse cursor...

Exactly, gestures without interactivity are honestly not worth it in my opinion.

Honestly the write up seems ok but does not evoke optimism to me. I can't help it but to me macOS and it's multifinger gesture support is not about how many gestures it supports or which actions it supports, but the fluidity of the execution of gestures with animations.

When you start pinching/unpinching fingers apart, the zoom happens in sync with your finger spacing. As soon as you start pinching, the application seems to receive with the event stream all the x and y coordinates so that pan and zoom can be done simultaneously in lockstep with the finger positions and spacing on the touch pad.

Similarly when you pull 2 or 3 fingers from the side to e.g. go back a page, the reveal animation starts, or an arrow appears, and you can change your mind mid gesture by reversing the finger movement and the animation feedback is helpful enough to tell you that indeed the gesture will be canceled.

I honestly hope that the developers interested in improving this in libinput and stack have the same understanding that gestures are not about recognizing the one-off side/pinch movement with a couple of fingers, but about low latency fluid interaction of fingers with visual animation feedback tightly coupled. The other (one-off) type of gestures where you swipe your three fingers to the left and then after a sampling interval the framework or stack receives a ThreeFingersLeft swipe event (with length or time or xy values) is IMO a very underwhelming experience.

Perhaps Memory Resource Controller is the best term? From the memory cgroup documentation [0]:

> NOTE: The Memory Resource Controller has generically been referred to as the memory controller in this document. Do not confuse memory controller used here with the memory controller that is used in hardware.

[0] https://www.kernel.org/doc/Documentation/cgroup-v1/memory.tx...

Deja Vu.

> you can send the callee the message the caller gets when the callee answers

This is the exact same type of bug that was in libssh: https://www.nccgroup.trust/uk/our-research/technical-advisor...

"possible to bypass authentication by presenting to the server an SSH2_MSG_USERAUTH_SUCCESS message in place of the SSH2_MSG_USERAUTH_REQUEST message which the server would expect to initiate authentication"

Also, Apple had a FaceTime bug of very similar nature:

https://www.theverge.com/2019/1/28/18201383/apple-facetime-b...

"you begin calling somebody via FaceTime Video from within the Phone app. Before that person picks up, you can swipe up to add your own phone number to the call. Once you’ve added yourself, FaceTime immediately seems to assume it’s an active conference call and begins sending the audio of the person you’re calling"