1. 7

    I recently built a split ortholinear keyboard out of iris PCBs than runs QMK firmware. Here is a picture of it and here is my customized layout.

    1. 1

      Very pretty.

      1. 1

        Thank you!

    1. 1

      I enjoy seeing articles such as this where people make their editor of choice work for whatever language they need. I wish I wasn’t so tied down and spoiled by msvs and autocomplete. I’m curious why autocomplete is pretty much either love/hate for most people too.

      EDIT: Also under the “About” section I can’t reach the link for Indigo: https://chapters.indigo.ca/ - IP Address could not be found/ DNS_PROBE_FINISHED_NXDOMAIN.

      1. 2

        Omnisharp for emacs autocomplete works very well. I’m not saying vscode isn’t better but as someone who uses emacs every day, the c# experience is more than passable.

        1. 1

          Hmm. Does https://indigo.ca work for you?

          1. 1

            Yeah that does.

        1. 2

          Does anybody have any experience using this? I’d be curious to hear about what it’s like working with.

          1. 1

            I think it’s brand new, so it’s still kind of experimental.

            1. 1

              Yeah, I know it’s new. I was just wanted to see if anybody in the community had actually used it.

          1. 3

            We’re a small shop (~15 folks, ~10 eng), but old (think early 2000s, using mod_perl at the time). Not really a startup but we match the description otherwise so:

            It’s a Python/Django app, https://actionk.it, which some lefty groups online use to collect donations, run their in-person event campaigns and mailing lists and petition sites, etc. We build AMIs using Ansible/Packer; they pull our latest code from git on startup and pip install deps from an internal pip repo. We have internal servers for tests, collecting errors, monitoring, etc.

            We have no staff focused on ops/tools. Many folks pitch in some, but we’d like to have a bit more capacity for that kind of internal-facing work. (Related: hiring! Jobs at wawd dot com. We work for neat organizations and we’re all remote!)

            We’ve got home-rolled scripts to manage restarting our frontend cluster by having the ASG start new webs and tear the old down. We’ve scripted hotfixes and semi-automated releases–semi-automated meaning someone like me still starts each major step of the release and watches that nothing fishy seems to be happening. We do still touch the AWS console sometimes.

            Curious what prompts the question; sounds like market research for potential product or something. FWIW, many of the things that would change our day-to-day with AWS don’t necessarily qualify as Solving Hard Problems at our scale (or 5x our scale); a lot of it is just little pain points and time-sucks it would be great to smooth out.

            1. 6

              FYI, I get a “Your connection is not private” when going to https://actionk.it. Error is NET::ERR_CERT_COMMON_NAME_INVALID, I got this on Chrome 66 and 65.

              1. 2

                Same here on Safari.

                1. 1

                  Sorry, https://actionkit.com has a more boring domain but works :) . Should have checked before I posted, and we should get the marketing site a cert covering both domains.

                2. 1

                  Firefox here as well.

                  1. 1

                    Sorry, I should have posted https://actionkit.com, reason noted by the other comments here.

                  2. 1

                    https://actionk.it

                    This happens because the served certificate it for https://actionkit.com/

                    1. 1

                      D’oh, thanks. Go to https://actionkit.com instead – I just blindly changed the http://actionk.it URL to https://, but our cert only covers the boring .com domain not the vanity .it. We ought to get a cert that covers both. (Our production sites for clients have an automated Let’s Encrypt setup without this problem, for the record :) )

                  1. 3

                    I’m still working on a discord bot I’ve been developing for my university’s Math CS and Stats society. This week I wanted to learn Mongo db so I’ve been working on adding detailed user stats and leader-boards that encourage people to be more active, all of which is stored in Mongo.

                    I’m still working on improving the homelab. I finally mounted my projector and ran the wiring as well as getting a chromecast. This week I’ll be setting up sonarr, radarr, couch potato and plex to start accruing media for consumption. In addition I moved from dnsmasq to windows server for dns and dhcp so that I can setup Active Directory allowing single sign on to all my VMs. Before I can set that up I’ll be replacing the fans in the hard drive array that I got since I bought it used the fans are old and loud and I’d like to keep the rack’s volume levels at a reasonable amount.

                    1. 4

                      I’ve been working on a bot for the CS/Math/Stats discord server at my university. I want this bot to be an introductory project for 1st and 2nd years to learn about contributing to an open source project. I spent most of the week refactoring it to be as easy as possible to contribute a module to. Then I wrote up a nice and detailed contributing doc as well as started creating, tagging and flushing out tickets that I’d been thinking about but hadn’t written down.

                      This week I want to add a small tutorial for getting started as well as well as some more beginner friendly stories (and tagging them as such). After that I’ll be posting the link in the server and really encouraging the regulars to take a crack at contributing something to the bot.

                      1. 5

                        Screenshot for those who don’t want to go to twitter: https://u.teknik.io/1tID2.png

                        1. 3

                          https://threadreaderapp.com/thread/966896123548872705.html

                          Unrolled for people who don’t want to read from screenshots.

                          1. 1

                            Even better.

                        1. 4

                          Don’t get me wrong here, the author certainly isn’t wrong, I just don’t see the point of the article. I expected the article to launch into an exploration of how we could fix this without losing legacy support but instead the article just ended.

                          1. 2

                            Yeah, seriously. There’s no need to shout your bug report into the void… take it to vim-dev@vim.org where it belongs.