Aaron Parecki

I just remembered the Lumix LX10 exists.

This does not bode well for the countdown 😬

Wow and the hits keep coming.

I’ve never had a camera overheat on me before one of my Sony cameras before. And 5 minutes of being off later it still won’t record.

The RX100V was recording in 4K too 🤯

What’s the best UHS-II card? I need one to shoot max 4K on an EOS R

I represent the worst position on eating meat which is “I understand it’s very wrong to do it but I’m too lazy to change my consumption habits at all”

What??? Where do you live? On a plane?

Where's everyone from? And what camera & lens are you shooting with???

But they base64 encoded it, so that’s OK, right?

We need a word for "something that is optional but will break everything if you don't do it so we enforce it anyway". It's a defacto-must of some kind?

Thanks for the response. I am trying to understand the specifics of the risk involved here. The site itself is HTTPS however the load balancer/proxy infra sometimes redirect to HTTP for the callback URL

Yeah. I think the right model may be to use Postgres or traditional DBs for *most* of the system, and a blockchain for the parts people will fight over.

So things like upvotes, likes, follower counts — and of course money.

We haven’t seen systems consciously built this way yet.

Great q.

I’d argue that many social apps make use of global consensus on at least *some* values. Could be upvotes vs user counts.

If you can get global consensus on one byte, you can run it again to get global consensus on N bytes (possibly with some upper limit on N).

Yeah. But here’s an interesting factor I think about frequently.

Basically, getting global consensus on one integer (user count) in an implicitly adversarial distributed system like Mastodon was a challenge.

Crypto solves that problem.
https://ansuz.sooke.bc.ca/entry/335

NEW RX100 VII HAS A MIC JACK.

There’s nothing like sitting in on the #ietf TLS meeting to make you realize how little you actually know about how the internet works

@aaronpk OAuth question when you have a sec:

1. User clicks “sign in with XYZ” on my app,
2. User bounces to XYZ’s auth flow,
3. User cancels, denies, etc.,
4. User is bounced to my app’s /auth/failure page.

What’s the “right” HTTP status code for my app’s /auth/failure page?

sure. Trying to do my part in letting the youths know there IS history here ;)

Back in round one of identity wars, this was called the “NASCAR problem” - so many logos to choose from.

https://indieweb.org/NASCAR_problem

Alright let's try this again. On a new flight from LaGuardia to Boston, and the rain has subsided. Still an active flash flood warning.

It looks like we're going to take off here, so far no mentions of delays.

If this works, I'm going to be getting in just an hour before the meeting in Montreal.