#14 OAuth support 3 days ago

Comment by ~stacyharper on ~whynothugo/pimsync

Maybe at least you should support using using oauth access keys? https://github.com/pdobsan/oama

#123 Transito: not null constraint failed agency.agency_name 14 days ago

Ticket created by ~stacyharper on ~mil/mobroute-tickets

While loading the 2006 provider

#624 Documentation not very accessible on phone a month ago

Comment by ~stacyharper on ~mil/sxmo-tickets

You should be able to install every -doc subpackages for all your installed packages using "apk add docs". Then sxmo-utils-docs should be there, and you can use "man sxmo".

That being said, you right, we should improve how website on mobiles devices.

#622 wofi doesn't return a failure code if it's killed a month ago

Comment by ~stacyharper on ~mil/sxmo-tickets

I also want to note the user might have picked nothing with Shift+Enter. Our scripts should handle that too

#622 wofi doesn't return a failure code if it's killed a month ago

Comment by ~stacyharper on ~mil/sxmo-tickets

I think we should also fix the scripts that continue on empty picked entries. Most of them should already do so, but we probably rely a bit too much on this specific dmenu behavior. More generally, being killed and exiting 0 seems completely okay

#600 Conky doesn't show on wayland 3 months ago

Comment by ~stacyharper on ~mil/sxmo-tickets

Right!

REPORTED RESOLVED CLOSED

#615 Responsiveness / latency optimization of sxmo menus 4 months ago

Comment by ~stacyharper on ~mil/sxmo-tickets

Not at all. This one is only used by the retro-compatible script.

#615 Responsiveness / latency optimization of sxmo menus 4 months ago

on ~mil/sxmo-tickets

Thank you for the reply ~stacyharper. Are you referring to the SXMO variable "$SXMO_THRESHOLD" here?

#615 Responsiveness / latency optimization of sxmo menus 4 months ago

Comment by ~stacyharper on ~mil/sxmo-tickets

#TODO: button events

There is probably some overhead the multi press timeout in bonsai / sxmo_multikey.sh, how much? See also #574.

#sxmo_appmenu.sh / sxmo_hook_contextmenu.sh

On the bonsai side, there isn't much extra latency. Except for the tiny unix socket initialization on client and server sides.

But we effectively feels a lot of latency, because the tree is designed this way. To emulate the behaviors we want, we have to wait a bit of time after most of the key events. Meaning single click start a timer after which, when no new events are received, we dispatch our scripts.

We could reduce the timeout duration (that I've increased a bit at some point). That could make the feeling better, but would also increase the difficulty to trigger the two-clicks.

#614 Calls not working on Pixel 3a XL 4 months ago

on ~mil/sxmo-tickets

Do I have to unsubscribe from each ticket separately? I also don't want to receive messages about new tickets.

On 2/2/25 10:02, ~stacyharper wrote:

ah, nvm. This is a todo :D Similarly, you can unsubscribe if you are not authenticated with:

Similarly, sending an email to ~username/tracker-name/ticket-id/subscribe@todo.sr.ht or ~username/tracker-name/ticket-id/unsubscribe@todo.sr.ht will (un)subscribe the sender to the ticket.