mr_donk

They don’t seem to do it anymore, but for a while the title on Disneyland.com would kinda sparkle in HDR when you loaded it on the right hardware/sodtware (safari on MacBook Pro for example). Was actually pretty subtle and animated out so it was more of a “wait, did I just see that?” sort of thing.

yeah, that's probably more along the lines of what I was thinking, actually, you just worded it better :)

Don't you think the next step is a programming language that isn't even meant to be human readable? What's the point of using an LLM to generate python or Swift or whatever? The output of the LLM should be something that runs and does whatever it's been asked to do... why should the implementation be some programming language that was designed for humans to grok? Once that's true the idea of it being maintainable becomes moot, because no one will know what it is in the first place. I don't think we're there yet, but that seems like the eventual destination.

For me, the killer app for me has been sidecar… I work from home, and like to work outside in the summer. I’ve been using my MacBook Pro and my iPad as a second display via sidecar.

One unadvertised feature of this is that you can use the pencil as a mouse on your Mac in this configuration, which is handy for virtual whiteboard type stuff on your Mac where you’d normally be stuck with a mouse.

You need to define the room in Alexa ecosystem then this works fine. You tell it a room, and what devices are in it, then it’s “smart” about it. Don’t have Hue specifically, but Alexa doesn’t import room springs from other ecosystems I’ve used, you have to redefine them.

Any source of what brands/varieties are smoked vs not?

I’m able to get quite a few types imported from South America, but from my attempts at translating the packaging and trying to Google things, I can’t tell what’s smoked or unsmoked.

Came to say this, happy that someone else did. It changed my life. I now have a graveyard of weird ergonomic devices and wrist arm braces, and can happily code all day on my laptop keyboard in any position. A few years ago I couldn’t write 2 lines without excruciating pain.

Start with `git rebase -i` to clean it up (reorder/squash), then create new branches and `git cherry-pick` the related commits into 3 branches. Submit PR/MR for those...

At least, that’s what I’d do. Curious to hear other ideas.

You need to use either the built in Mac client or something like Remotix if you’re using Windows. Every other vnc client I’ve tried performs terribly as you say.

This is amazing! With this codec and enough processing power, you could do this bidirectionally and have enough bandwidth to stream a two way realtime voice chat using 2400bps modems over a standard analog phone line!!! ... Oh... Wait a minute...

Much of the target audience would be much more comfortable with pen and paper.

Maybe in 20 years an online version will be better.

I don't know about it being so easy for someone with an actual impairment...

My only experience was with my mother, who recently passed away from a stroke. She was diagnosed with Alzheimer's in her early 60s.

I have no trouble believing this easy test would be impossibly hard for someone with dementia, even in the early stages. At the beginning, my mom seemed fine to anyone she'd meet, yet would routinely not know what day of the week it was. She'd cover for it by saying things like "since I don't work, every day seems like Saturday". She probably would have failed the test right there.

The AppleTV part of the app is native tvOS.

It's using SSE as well... there are a few ways to do it, here's an example https://github.com/neilco/EventSource/ I'm doing something quite similar in swift, had I known about this, I probably would have just dropped it in!

Every player uses their own phone and that part is just straight JavaScript.

> Now that we know we don't need the up and down arrow keys, what about the left and right? Unfortunately, these keys are still needed for single character movements

Don't ctrl-f and ctrl-b work?

My experience was almost identical to the author's. As improbable as it sounds, reading the book and following it's advice completely eliminated my RSI pain after 3 years of dr visits (steroid cream), physiotherapy (tens, ims, massage, art, etc), and every ergonomic input device I could get my hands on failed to help. My RSI was starting to bother me even when I wasn't at a keyboard, to the point where it hurt to drive. I'm the last person I would have ever expected to use some "new age" treatment, yet as soon as I started to read the book, my pain lessened and was 100% gone within a month. I strongly agree with the author's premise about emotions playing a role in this, and in my case the onset of RSI corresponded with a very stressful time in my life.

Maybe this won't be the case for you, but it certainly was for me. I can once again type on a normal keyboard all day with no pain. 2 years ago I would have never believed this possible. If you're in a similar situation, you should give it a shot. It costs nearly nothing, and has helped many people (read the book's reviews on Amazon).

The book is actually The Mindbody Prescription.

This cured me of 3 years of horrible RSI pain. I did go to Doctors, physiotherapists, chiropractors and acupuncturists and had anti-inflammatory creams, you name it. Nothing worked for more than a couple days... and this was a last resort. I wish I would have tried it sooner, but I doubt I would have given it a shot if I wasn't desperate.

Read this for a well written account from a hacker: http://aaroniba.net/articles/tmp/how-i-cured-my-rsi-pain.htm...

Then buy the book and read it. It'll cost you less than an MS Natural Keyboard, not to mention all the other crap (wrist braces, heating pads, etc etc).

I posted on the previous article as well, and on RA's blog as "concerned bystander", lest you think I'm just stealing his ideas ;)

I've done some googling and found a reference saying AirPlay is supposedly licensed by Apple for $4 per instance to device makers.

http://tech.fortune.cnn.com/2011/03/24/airplays-hidden-agend...

Assuming RA would have been able to license it for the same price, they would have to charge $7 for the feature to make up the difference, which is pretty steep on the App store. The bigger question is: Would Apple give them a license? My gut says no, not for an iOS application, but who can say?

I asked on the "under the microscope" blog if Apple mentioned licensing at all in what little communication they've had... I noticed RA never seems to mention licensing, not sure if it's an intentional omission or just coincidence. They had to know going into this that they were playing with fire using the leaked key.

If Apple does claim the removal was over non-public APIs, I think they're being disingenuous. I can't believe a developer like RA would be doing that knowingly or not.

That's my point. Isn't getting the private AirTunes key equivalent to the DeCSS case?

If Apple had just made a proprietary undocumented protocol, that'd be one thing, and I'd agree that Apple wouldn't be able to force licenses on people. Absent the private key, there wouldn't be anything to stop you.

However, they made a proprietary protocol, sold licenses to use it and implemented a key enforce the license. Isn't circumventing the private key equivalent to circumventing copy protection? They obviously intended to restrict it to licensees, the way the DVD people intended to restrict CSS to licensees.

Wasn't there some case where printer manufacturers were doing something to stop 3rd parties from making cheaper ink/toner? How did that go? Maybe it's a more apt comparison (for the record, I honestly don't remember how this case turned out, so I don't know if I'm helping or hurting my argument).

That's a good point... I based my assumption on the fact that they require a private key for receiving, but not sending.

I guess that doesn't necessarily prove anything...

I did put stolen in quotes every time I used it because I'm not sure that is the correct term.

Here's how I see it. AirPlay is something Apple sells a license to. Assume Rogue Amoeba didn't buy a license, but used someone else's, and then sold the functionality that buying the license would have entitled them to.

What's that? Piracy? DMCA violation? Within Rogue Amoeba's rights? I don't know. Is Apple allowed to lock things down by requiring keys? Maybe they're in the wrong.

To me, this is similar to trying to sell software that uses DeCSS to play DVDs rather than licensing CSS. Regardless of my opinion, it doesn't seem to be legal (in the US, anyway).

Is that legitimate? If so, how is it different than other forms of piracy?

When I posted my reply regarding AirFoil a while back, the article wasn't loading... now that it is, you can see the developer actually explains Apple's stance and gives an example of why they do what they do.

He says: "But then something remarkable happened. Apple approved Air Speakers – an app that enabled you to stream audio to your iOS device from iTunes and iOS devices. Using the private key of the AirPort Express. Sadly it was a horrible app. Synchronization wasn’t even implemented, so the audio was hopelessly out of sync, when sending audio to multiple devices."

I believe this is why Apple requires you license AirPlay. Not so they can make a quick buck (I'm sure the license fees are trivial to Apple), but so they can make sure things that work with AirPlay don't behave as the author claims the AirSpeakers app does.

They later claim that AirPlay implemented the key to stop piracy; "The encrypted stream was initially implemented in order to protect the transfer of DRM-encrypted iTunes Music Store audio content," but doesn't back this statement up. I think they implemented the key requirement to enforce their licensing. I can't back this up either, other than it explains Apple's actions better than his theory. The licensing isn't there as a profit center, but to give them some quality control so that AirPlay doesn't get a bad reputation for being difficult to use or unreliable.

The thing that doesn't make sense is that supposedly Apple rejected this for using private APIs. This doesn't sound like the case.

It'd be interesting to know what the AirPlay licensing terms are like, and whether or not the AirFloat developer or Rogue Amoeba approached Apple to license AirPlay (I'll guess no).

There's 2 parts to AirTunes (the part of AirPlay that Airfoil and AirFloat use), Sending and Receiving. Up to now, AirFoil only used the AirTunes protocol to SEND streams to AirPlay devices. If you reverse engineer the protocol you can send to any AirPlay device. No problem.

It's harder to make an AirPlay receiver, because iTunes won't send anything to an AirPlay receiver that doesn't encrypt the request with the proper private key.

You can only get this key legitimately by licensing AirPlay from Apple (which is why all AirPlay compatible speakers are licensed by Apple).

Someone managed to extract the private key from an AirPort express by removing the flash chip and reading it externally. They then published this "stolen" key on the web. Prior to that, it was impossible to make anything that would receive AirPlay streams from iTunes, even though the protocol was widely understood (it's basically just RTSP).

A bunch of open source implementations on other platforms (PC/Mac/Windows) were released.

Rogue Amoeba's AirFoil speakers for Mac/PC included this functionality. However, up until this last update, they never included it in their iOS application. Their stated reason for this was they couldn't figure out a revenue stream to make this work (AirFoil implements it's own music transmission protocol. You bought the Mac software for $20, then got the receiver software for free. Under this model, making the free product able to receive streams from iTunes without the Mac software would have cut out their revenue producing server from the picture). The latest release included this AirPlay receiving feature as an in-App purchase. Since they've had the code to do this for a while, and it seems like this method is probably preferable to most users and therefore likely more profitable, the delay seems odd.

My speculation is, they've been using the "stolen" key, and were hesitant to draw attention to themselves by trying to get software using it approved on the app store. Eventually potential profit won out, and they went for it. It got approved by the (probably) less technically savvy app review team that doesn't know about the requirements of a licensed key to make AirPlay reception work. It was noticed later by some Apple engineer who is familiar with the protocol and was then pulled.

Since the private key is necessary to make this feature work, they either needed to license it or use the "stolen" AirPort Express key. If they licensed it, I don't think Apple would be pulling it. Since Apple does license this to people, it would be unfair to their licensees to turn a blind eye to people using the "stolen" key. If it became apparent they were letting it slide, it would lead to a proliferation of unlicensed (potentially crappy/flakey) devices that might not meet Apple's quality standards.

I think the speculation about Apple wanting to include something similar in a future iOS release is irrelevant here. Maybe they would, but I think this reasoning seems more likely.

tl;dr - this sounds nuts, but it worked for me

I did this... got one of his books (they're on kindle, ibooks and audible) and read it. i had rsi that increasingly got worse over a 3 year period until i couldn't drive, tried pretty much every non-surgical thing i could find (multiple doctors, creams, physio, ART, acupuncture, TENS, stretches, exercises, posture examined by ergonomist, different keyboards, switching mouse hands, trackpads, footpedals, foot mouse (wouldn't you know it, my knee started getting rsi), vitamins, supplements, break software with increasingly frequent breaks, switched to dvorak, wacom tablet for handwriting/mouse replacement), and things were still trending worse. it was hard to hold my new daughter for more than a couple minutes, and i was trying to figure out what work i could do that wouldn't involve a computer.

i can still remember running across sarno's book online on a random google search for rsi treatments, the way people remember where they were when they heard about the challenger explosion or 9/11. within a week of reading sarno's newest book (name escapes me now, but it is offputtingly new-age sounding), i had next to no pain, after a month, i'd say i was healed. it's now been 10 months, and i don't even think about my arms anymore, or follow any sort of treatment regimen. i'm literally back to normal. if someone had told me this was possible a year ago, i wouldn't have believed them, i thought i was going to be babying my arms and counting my keystrokes for the rest of my life. in fact, my physiotherapist told me in no uncertain terms that i'd be dealing with this for the rest of my life.

sarno's theory in a non-medical nutshell: there's nothing wrong with your arms, the pain is caused by limited blood flow to your arms/wrists/fingers. the lack of blood flow is caused by your unconscious. why is your unconscious doing this? to distract you from dealing with painful emotions. why your arms and not your back or something else? your subconscious isn't dumb, and knows what will seem plausible to you. how do you fix it? by understanding that it's happening (not, as you might expect me to say at this point, by dealing with your emotions/stresses through therapy). the last part is what most people seem to get hung up on, and most of sarno's book is trying to convince you that this isn't a crackpot theory.

here's the caveat, which is explicitly discussed in the books as well. sarno thinks most rsi (and other chronic pain) is caused by what he calls tms, but it's possible there is something physically/mechanically wrong with you, so you should see a doctor first to discount this. in my case, i'd already seen several and had conflicting diagnoses and recommended treatments that got me nowhere, so i dove right into the sarno treatment.

here's a couple links that you can read about it in more detail, but seriously, buy the book or get it from http://aaroniba.net/articles/tmp/how-i-cured-my-rsi-pain.htm... http://tmswiki.wetpaint.com/page/Repetitive+Strain+Injuries+... http://podolsky.everybody.org/rsi/