On Matrix, as long as you have your username and password, it’s not possible to get “locked out” due to not having your keys. In fact, your keys are only necessary if you plan to participate in encrypted chats, in which case it’s obvious that losing your key will mean losing access to old messages. However, you will still be able to receive new messages by generating a new key.

I use MediaMTX. You can stream to it with whatever (I use OBS). You could even publish it to a website behind an iframe.

Question: How can I make a simple app with libadwaita?

Reply: Fork GNOME.

How many windows do you usually have open in a workspace? Wouldn’t the usual Meta+Direction shortcuts be quick enough for 2-4 windows?

Yeah you can mitigate it. Doesn’t change the fact that if you have no CPU time available, the audio is not getting played.

Audio from low priority processes is expected to stutter under high CPU load. I experience this a lot when playing music while compiling programs.

Probably something like “sudo this_gui_app”. This is not possible under Wayland. But who knows? This guy is being as vague as possible with details.

Sway or Hyprland for compositor, Waybar for status bar, fuzzel for app launcher, swaync for notifications, wleave for logout menu.

Everything should work across Hyprland and Sway except for Waybar worskpaces, you need a different configuration for them.

You have a higher chance of solving this issue if you ask in #webrtc:matrix.org

Desktop users (except for business) don’t make Microsoft any money, so they probably don’t care.

Do you specifically need ffmpeg? If it’s just screen recording from the terminal, wl-screenrec has the best performance (meaning low CPU usage) for Wayland screen capture. It does require the new screen capture extensions so it will depend on your compositor.

You can use your own server.

I’d say wl-screenrec (https://github.com/russelltg/wl-screenrec) shows the best screen capture performance on Linux. I guess it could be even better since Wayland has released newer protocols and newer versions of the protocols used in wl-screenrec.

You can allow guest accounts, although it’s disabled by default in synapse.

Call supports depends on the client you’re using. Element is usually ahead in features implementation, but you can get a list of clients and filter by features in the matrix website.

Also I’m not sure what the other person meant by easy to setup. Matrix servers are notoriously hard to setup when compared to anything most things you would find yourself selfhosting, specially with WebRTC/TURN. I think there’s an ansible playbook somewhere, but I never tried it.

You’d make a great tech CEO.

I sincerely hope your reply in the mailing list was satire .

Is there another example of this happening in Facebook aside for the openKylin post? I looked around and every article is only talking about this specific DistroWatch issue.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2356

wlroots doesn’t support HDR.

TRULY modern OS

What does this even mean? So iOS, MacOS, Windows11, Linux aren’t modern?

a way better compositor than wayland (in fact, android has the best compositor in the world, compared to ANY OS)

Wayland is not a compositor, it’s a protocol. SurfaceFlinger can totally be made in Wayland. Saying SurfaceFlinger is better than Wayland is like saying words are better than English.

A properly modified desktop OS based on it (better than Samsung’s DeX for example), that is also able to run normal Linux apps, would be a huge winner.

Nobody will ever use this on Linux, unless it is implemented in Wayland. It is infinitely more likely for Android to rewrite its compositor for Wayland than SurfaceFlinger being adopted as Linux’s main compositor.