Skip Navigation

Posts
7
Comments
608
Joined
3 yr. ago

grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out

  • I use a keychron Q3 and Q0. They can be remapped / programmed through a web (chrome derivs as it requires WebHID) or desktop electron app called VIA, which at the time of writing is proprietary. I believe Vial (written in Qt) is being brought up, so that may be an option in the future.

    In terms of managing the firmware, the vendor offers a first party web interface (also leveraging WebHID). The QMK Toolbox GUI is only available on Mac and Windows but you can use the CLI on Linux to get into DFU mode and flash your firmware.

    Not really keen on Logitech as a company but I use Piper to program several of their G series mice on Linux. You can check the libratbag support list to see which hardware can work with it.

  • I feel the same way; I've seen some people around here mention SailfishOS but I didn't really think Jolla were still kicking as a company.

    What's the situation with SailfishOS? In the past I wasn't clear on what aspects of the OS (if any) were open? In the past I was under the impression that the UX /UI was proprietary but I can't remember how I reached that conclusion

    Taking a quick look at the site today, it looks as though certain (maybe enterprise oriented?) software features sit behind a subscription, such as Android app compat

  • Absolutely. They've been getting really popular in wearables (particularly from Chinese brands).

    Several SBC vendors are including rv clusters in ARM based SoCs (which I believe is partially related to what you mentioned) for development purposes.

    I even have a little rv powered ssoldering iron 😊

  • same for AMD graphics since 2019. I wouldn't be surprised if Intel were doing the same with Arc too, though I haven't looked into that yet.

  • yeah it's great to be in a community that has little tolerance for basic tossers

  • Been playing this since demo days. The developer is a chill guy and will actually discuss feedback and implement features which make sense.

    Hop into their community and say hi

  • Really appreciate the insight

  • I didn't realise there were keyword filters. Thanks!

  • proof of liquid floof confirmed.

  • draw.io no longer open source since August 27, 2024

    Jump
  • I suppose some instances cut others off as well (I see only 6 total) so you have a fair point

  • draw.io no longer open source since August 27, 2024

    Jump
  • And despite that, if was still newsworthy enough to be posted like 6 times in total 😅

  • I see. You can temporarily edit your grub before the OS loads. This should afford you the opportunity to boot into the system without EDID modifications, though im not sure if your modified EDID will still load under this scenario. If so, you may need to switch into a CLI session to undo your changes.

  • I'm sorry to hear that. Does this system only have access to this single display? Did you use a kernel command to modify your EDID? If so, are you able to temporarily modify your grub before booting into the OS?

  • Archwiki references a [@<refresh>] (presumably denoted as [@144] for something like 144Hz) property, hopefully that's all you should need to define, though I'm not sure if you'll need to manually recalculate vertical and horz timings or something.

    Maybe this can help fill in any gaps

    https://tomverbeure.github.io/video_timings_calculator

  • I'm aware, I used to use adaway several years ago.

    I had the same feelings as you, in that I needed to have system-wide ad blocking, but I revaluated that requirement a couple years ago and realised that I don't use any apps featuring banner ads and such.

    Several of my apps will just fall back to system webview and Firefox (+uBo) will power that too.

  • naw unfortunately not. It's kind of crazy that they nestle each individual engine within a wrapper. I'm not sure of this brings the api level to d3d11, or if they had to work to bring each engine up for that. Somewhat explains why MCC as a whole was so difficult to back port improvements to, like configurable FOV and weapon model placements, frame rate unlocking and interpolation, custom keybinds, missing assets and such.

    it's kind of interesting seeing the player models rendered in UE when you use the customisation menus; everything looks so glossy and odd.

  • no you're cool