https://archive.is/Vj2py

cool! didn’t know that fcitx was also available for android

so you chord z + right hand keys and : + left hand keys?

i think i could get away with just having ctrl under a/: and maybe shift or super under s/l since i have alt under caps lock

i have been running qmk keyboards with capslock bound to esc on tap, alt when pressed as well + evdoublebind to achieve the same for the laptop’s builtin keyboard

i do like the idea of not having to come off the home row for ctrl-* mappings in vim

maybe my comment about gitlab didn’t come across right. i do find oxide’s model to be better and agree with their criticism of gitlab’s.

and as much as you are absolutely right about labour being treated much like any other commodity required for a company to extract value, that is precisely the issue being pointed at here, isn’t it?

we should differentiate and acknowledge that people are more complex than that. their experiment seems to create an atmosphere where work is being done despite compensation not being used as an incentive and instead to enable the worker to do the work.

i personally don’t think this should be a responsibility of a company at all, but rather society (or the state) should assure these conditions… but we are stuck with capitalism and this is a step towards something better :)

awesome! looking forward to it :)

nice work!

maybe somebody here knows… is it possible to turn off the page transition animations? i was expecting voyager to respect prefers-reduced-motion but it doesn’t seem to affect that

so I wonder what the benefit is keeping it in the proprietary format at all

yeah my guess was easier editing and ux when collaborating via github, diffs on json don’t look great

but yaml (for all it’s faults) would still be better haha or now that i think about it:

• https://github.com/hashicorp/hcl
• https://git.sr.ht/~emersion/scfg

both look similar to bru, would share the advantages over json and seem better spec’d/supported

if i wasn’t a terminal person, this looks ideal! no reinventing the wheel for lock-in’s (read business model) sake…

the only thing i don’t like here is their custom bru format. json, yaml or any other standardised markup fit their manifesto better as well imo