Comment by ~jplatte on ~scoopta/wlrobs
I'm not sure which OBS backend I'm using. OBS isn't using Xwayland though, if that's what you're asking.
As for the wlrobs backend, I'm using screencopy (dmabuf doesn't work for me).
Ticket created by ~jplatte on ~scoopta/wlrobs
I'm getting the following error message when I re-focus OBS after streaming or recording for a while.
The Wayland connection broke. Did the Wayland compositor die?
This always results in OBS crashing.
Ticket created by ~jplatte on ~sircmpwn/dispatch.sr.ht
Currently, one can include all secrets in a task, or none. It would be good to be able to only allow a subset.
Comment by ~jplatte on ~sircmpwn/hub.sr.ht
Closing in favor of https://todo.sr.ht/~sircmpwn/sr.ht/20
REPORTED RESOLVED DUPLICATE
Ticket created by ~jplatte on ~sircmpwn/hub.sr.ht
This affects multiple sourcehut sub-projects (I've noticed it in commit messages on builds.sr.ht and readme.md's on hub.sr.ht and git.sr.ht):
When multiple underscores are used inside of a word, they are used for emphasis. While this is what the original markdown does too, most renderers I've seen deviate from it and CommonMark also specifies this deviation. I find it rather annoying to have to escape underscores in project_names_with_underscores and such, so would appreciate it if sourcehut could adopt CommonMark or otherwise change this behaviour.
Ticket created by ~jplatte on ~jplatte/ledybar-mod-i3-workspaces
Ticket created by ~jplatte on ~jplatte/ledybar
The end goal for this project is to not require a JS engine at all and implement the limited DOM modifications needed for the function of ledybar directly in Rust.
A first step towards this would be to move away from the quite high-level webkit2gtk, instead using a lower-level API for webkit or potentially another browser engine (ideally servo, but that seems like it's simply not documented well enough yet).
This would also mean we could get rid of the dependency of gtk, which is convenient but in the first days of working on ledybar already led to issues. Instead wayland interaction would be done through smithay-client-toolkit (which also means X11 support would become harder but I don't care that much personally).