Prior discussions: https://hn.algolia.com/?q=stop+killing+games

Official website: https://www.stopkillinggames.com

Comments URL: https://news.ycombinator.com/item?id=44360326

Points: 9

# Comments: 3

Worse, it's distracting.

Do you find the natsec argument to be compelling considering:

> TikTok I think has the largest share of American's attention out of all the social media?

https://help.archive.org/help/how-do-i-request-to-remove-som...

Because it is possible with G-Hub, I was just curious if anyone knew what the gap is between SteerMouse's support and G-Hub's support for the seamless G-Shift/shift key experience. I don't know enough about hardware to make a guess.

I'm 100% fine with using a separate OS to config the mouse, since my layout is not app specific. Despite the button layout difference, this will definitely be the mouse I try out next.

So when you click a button on the G600 (and most other mice with side buttons), the button fires when you press down, just like the Mouse 1 or Mouse 2 button. On the G600, there is a third click button to the right of the right click, which is called G-Shift. When pressed, all of the side buttons have secondary assignments. Since you have to hold G-Shift to access this other layer, the macros are often referred to as chords in mouse customization software like Steermouse, since it requires two buttons to fire.

To configure this, you need the G-Hub software, which is in a nightmarish state on macOS. To get around this, I use Steermouse. Steermouse lets me get around this, however with one trade off. If a side button has two assignments (one when pressed by itself, another when pressed with the G-Shift), then the button does not actually fire when its pressed, but instead fires when the button is depressed/let go of. I imagine this is just how Steermouse handles buttons which have more than one assignment.

I haven't found a suitable replacement that is as robust as steermouse. Its one of the first apps I install on my mac, but this is one killer feature that I've only found in the G-Hub app.

My issue with SteerMouse is that when creating chord macros, it forces the original macro to only work when depressed, rather than activating upon press.

I haven't been able to find a suitable replacement. Curious if anyone here on HN has worked around this in any way?

Correct me if I'm wrong, but doesn't this track 100% with the bills stated intent: to prevent foreign adversaries from having this kind of influence?

I don't think the US is making an argument that data collection, surveillance, and propaganda are bad and then selectively only choosing to enforce these ideals on China. I think the US is making the argument that a company which belongs to an adversary and operates an a domain that is out of bounds from US regs/enforcement is a NatSec issue.

The bill isn't a criticism of TikTok's operation, its a criticism on its ownership and how that ownership + influence creates an exploit that poses a threat to NatSec.

This kind of reactionary framing feels like an attempt to put Facebook and TikTok on a level playing field, but the premise of the bill is about tech ownership and influence by companies of or from a foreign adversary.

Facebook is a US company. What am I missing here?

Yes, they are officially recognized as a foreign adversary. They're the first country listed:

https://www.ecfr.gov/current/title-15/subtitle-A/part-7/subp...

Being able to have a modular Mac was really something and I exploited that to tailor my machine to my use case (television/video production). I never had issues with bluetooth or WiFi, nor did I have ever have an issue with Apple's services like iMessage/Facetime.

What sucked about the process was staying current with system updates. Updates within the macOS release went without a hitch, but my hardware was aged out in newer macOS versions which made upgrading a bit too much like surgery, and since this hackintosh was my production device, that wasn't something I wanted to roll the dice on.

Having switched to apple silicon, I do kind of miss that freedom, but I've found that same freedom just by doing things a little less hacky. Instead of a board I can add drives to, I just setup a NAS, instead of using an old PCIE HDMI capture card, I got a more modern USB one, etc.

For a long time, Hackintosh was an opportunity to do things my way, and that experience led me to learning experiences that have improved my day to day that I otherwise may not have learned. It was a freeing experience. Today I still do things my way, but these days my way is more focused on convenience for the things that should "just work" so I put my attention on things that matter, rather than things that shouldn't, such as modifying my EFI before a macOS update to trick macOS into thinking I have the iGPU of a newer chipset because Apple dropped support for Skylake on a new release.

Good times, the headaches were worth it in hindsight.

Generating good images is easy but generating good images with very specific instructions is not. For example, try getting midjourney to generate a shot of a road from the side (ie standing on the shoulder of a road taking a photo of the shoulder on the other side with the road crossing frame from left to right)...you'll find midjourney only wants to generate images of roads coming at the "camera" from the vanishing point. I even tried feeding an example image with the correct framing for midjourney to analyze to help inform what prompts to use, but this still did not result in the expected output. This is obviously not the only framing + subject combination that model(s) struggle with.

For people who use image generation as a tool within a larger project's workflow, this hurdle makes the tool swing back and forth from "game changing technology" to "major time sink".

If this example prompt/output is an honest demonstration of SD3's attention to specificity, especially as it pertains to framing and composition of objects + subjects, then I think its definitely impressive.

For context, I've used SD (via comfyUI), midjourney, and Dalle. All of these models + UIs have shared this issue in varying degrees.