Side note, Caffeine[1][2] does not disable it's lid switch, but instead disables the automatic sleep behaviour while enabled.

[1] Author link (includes link to source): https://www.intelliscapesolutions.com/apps/caffeine

[2] Original author link (stopped updating before OSX Mojave): https://www.lightheadsw.com/caffeine/

i switched from caffeine to amphetamine due to compat issues and amphetamine does have a mode to disable the lid switch

I'd say it depends on how much they're willing to dive into "growth" mode for the company. If they're willing to spend those Microsoft dollars on product usage being embed everywhere, then sacrificing some short-term monetary gain for businesses that are built around your product would be valuable.

Ooh, intriguing.

I've been using Flux studio session analyser to visualise audio signals for mixing In-ear monitors for live audio[1] from my Cue mix.

Might write a quick dodgy thing to add this to my analysis stack. Could be cool.

[1] https://imgur.com/RFsV3d9

Cloudflare have their own technology that they're using pretty heavily now, turnstile.

https://www.cloudflare.com/products/turnstile/

Don't get any goofy puzzles which is nice.

I think it kind of flows into two trains of thought in the against category. First off, that some people are worried about copywrited, private stuff being included in the training data. I've not read up on copilot recently, so not sure if this is a reasonable thing to be worried about or not.

The other, is that people might be using Github to share stuff they've come up with other developers, but having an AI parse that information means that there's a disconnect between giver and receiver. It removes a chunk of the feedback loop being possible, which makes it so rather than it being a community of developers, it becomes something more akin to content creators and lurkers. That's not necessarily a bad thing, due to it opening up the sheer number of possible usages that end up using something. But it would minimize community feedback.

> https://vdo.ninja

An alternative for a local network is running NDI. That's how for events we stream a bunch of remote cameras (and even computers on the network) into visual displays.

https://www.ndi.tv/

There are NDI apps for most phones etc.

Also NDI native cameras are slowly becoming a thing. I'm really in love with the Logitech Meevo. It's targeted for use with phones, but it works great with computers and OBS too. Drop dead simple to use, and with the POE kit very, very stable. I'd go something like it over a mirrorless camera hack any day.

Thanks, I’ll check this out! VDO will route locally over a LAN when it can, which helps keep latency down, but its always great to compare options.

I've used something similar to this pointing technique when mixing live sound for bands I'm not familiar with.

Standing somewhere in the audience space and listening for & looking at each person on stage individually to ensure they're part of the mix.

Maybe I should implement something physical. Though pointing at the band would usually make them stop and ask what I'm needing

Mirror: https://outline.com/Gzv9W6

Milot and Britt's vision for having an impact on the building industry is going to take a lot of work, but they're one of the few people that seem to have unlimited drive for it. - I worked as a dev for ArchiPro from March 20 - December 21

Feels like it needs some sort of feedback when you type too slowly to get the next word. Plus maybe making it a bit more obvious that you can select a target speed for the WPM.

Agree, I didn't understand that one can change the WPM before reading this thread.

Good point, I've added a help button in the top left corner that briefly explains the concept. Maybe that already helps a bit.

it helps, but I was very confused at first too (the button is not very visible)

Do you have any ideas for the feedback when your speed is to low? I am not a designer and struggle to find ideas that keep the UI as minimal as it is right now while improving the user experience.

I like the minimal feedback as it is right now: you just have to try again.

A hint at what wpm I just typed at would be nice. So if I only hit 50 wpm a 50 off to the side or below the dotted line.

This is fascinating when picking a liminal wpm. Single hand words are so much harder.

I can cruise along until I hit words like "exact"

EDIT: You could make a list of bigrams as people type and average the wpm for words with that bigram, then you could weight the randomly chosen words by the difficulty of the bigrams, to really help people focus on their biggest stumbling blocks.

the dashed line under the input could be briefly turned red (for 400-500ms) when you clear it on fail

I think just a brief "too slow" underneath the input would suffice.