ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Lucretia has quit []
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
leon-p_ has quit []
st3r4g has quit [Read error: Connection reset by peer]
st3r4g has joined #wayland
FluffyFoxeh has joined #wayland
<FluffyFoxeh>
Is it possible to make something like this work under Wayland?
<FluffyFoxeh>
It's an OBS plugin that overlays your mouse and keyboard inputs on the stream
<FluffyFoxeh>
I guess you could use evdev, sudo would be needed however
<soreau>
it is possible, you could do it as e.g. a wayfire plugin
<FluffyFoxeh>
Preferably compositor agnostic
<fluix>
yeah, you could do it by reading the events directly (libinput I'm guessing)
<fluix>
but as you said, you need the relevant permissions
nerdopolis_ has quit [Ping timeout: 480 seconds]
<FluffyFoxeh>
It'd be nice if there were a way to have these "god mode" APIs in wayland, with a way to authorize certain applications to use them
<FluffyFoxeh>
is that planned?
<fluix>
I mean, if you were to "authorize" then there's nothing god mode about them :P
<fluix>
I believe there's work on security contexts to allow/prevent certain things (like screensharing, for instance), but nothing production-ready yet
<FluffyFoxeh>
More surgical hotkey/action binding features are good too, but sometimes you really just need to see all the input. Also allows a hotkey to still perform its usual function (like having my mouse Forward button as push-to-talk, but also still working to move my browser forward)
<FluffyFoxeh>
good push to talk keys are hard to find, even harder when it has to be exclusive :)
<FluffyFoxeh>
For example, I wrote a script to monitor "xinput test" to mute/unmute a pulseaudio source (so I could have push-to-talk when using Zoom), because when I tried xbindkeys, it would eat the event.
zebrag has quit [Remote host closed the connection]
<daniels>
emersion: err, the DMARC record is explicitly set p=none ... ?
<daniels>
or do you mean that DMARC cannot be used anywhere unless DKIM also signs a certain set of headers, because relaying email and DMARC are not actually really compatible?
<emersion>
hm, so
<emersion>
the presence of the DMARC DNS record tells recipients to check DKIM/SPF and fail DMARC if none succeeds
<emersion>
p=none does tell recipients to not take action
<emersion>
but it still shows a big warning in my client
hill has quit [Remote host closed the connection]
<emersion>
but yeah, arguably that's fine
hill has joined #wayland
<daniels>
I'm not trying to say it's ideal :)
<daniels>
but just trying to understand the failure mode & interactions
<daniels>
thanks!
<emersion>
sorry for the false alarm!
andyrtr has quit [Read error: Connection reset by peer]
andyrtr has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
MrCooper has quit [Remote host closed the connection]
hill has quit [Remote host closed the connection]
MrCooper has joined #wayland
andyrtr has joined #wayland
andyrtr has quit [Read error: Connection reset by peer]
andyrtr has joined #wayland
<daniels>
np, it makes sense now I understand what's happening
<daniels>
triggering red flashing lights when we send mail through lists certainly isn't ideal :P
leon-p has joined #wayland
leon-p has quit []
slattann has quit []
nik has joined #wayland
gryffus has joined #wayland
<daniels>
emersion: fwiw DKIM was partly done but not yet completed for $reasons, have kicked the ticket