<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for jasonkarns</title><link>http://disqus.com/by/jasonkarns/</link><description></description><atom:link href="http://disqus.com/jasonkarns/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 23 Sep 2025 05:46:26 -0000</lastBuildDate><item><title>Re: One of area’s oldest donut shops and pizza shops could both lose homes, business claims</title><link>https://614now.com/2025/food-drink/one-of-areas-oldest-donut-shops-and-pizza-shops-could-both-lose-homes-business-claims#comment-6772467803</link><description>&lt;p&gt;Where is the link to the petition!?!?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Tue, 23 Sep 2025 05:46:26 -0000</pubDate></item><item><title>Re: ‘USA Today,’ names  the Ohio State Fair as one of the country’s best; Find out where it ranked here</title><link>https://614now.com/2025/explore-columbus/usa-today-names-the-ohio-state-fair-as-one-of-the-countrys-best-find-out-where-it-ranked-here#comment-6751351203</link><description>&lt;p&gt;where is the link to the usa today article? do we not know how the web works anymore?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Tue, 12 Aug 2025 13:59:44 -0000</pubDate></item><item><title>Re: Ohio’s first and only ‘water coaster’ now open</title><link>https://614now.com/2025/hot-topics/ohios-first-and-only-water-coaster-now-open#comment-6723185566</link><description>&lt;p&gt;Kalahari in Sandusky has a water coaster&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 16 Jun 2025 12:57:10 -0000</pubDate></item><item><title>Re: Celebrity chef leaves role at prominent Downtown restaurant</title><link>https://614now.com/2025/food-drink/celebrity-chef-leaves-role-at-prominent-downtown-restaurant#comment-6677580326</link><description>&lt;p&gt;ICE? Probably trump and ice.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Thu, 27 Mar 2025 10:00:26 -0000</pubDate></item><item><title>Re: Meet the historic Columbus bar that’s open 21 hours a day</title><link>https://614now.com/2025/sponsored/meet-the-historic-columbus-bar-thats-open-21-hours-a-day#comment-6669137569</link><description>&lt;p&gt;Did y’all write this whole post and not even tell anyone WHERE IT’S LOCATED&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Wed, 12 Mar 2025 20:35:17 -0000</pubDate></item><item><title>Re: Better Know A Ruby Thing #6: Methods and Access Control (part 1) – Noel Rappin Writes Here</title><link>https://noelrappin.com/blog/2024/05/better-know-access-control-part-1/#comment-6469955682</link><description>&lt;p&gt;It might be worth suggesting readers use `__send__` instead of `send`. I believe `__send__` is the recommended approach these days. It was added since `#send` is already a common enough method name that classes would need to use that method in their own domains. (`Mailer#send`, `Message#send`, etc)&lt;/p&gt;&lt;p&gt;It also has the nice side effect of being awkward enough to look at that it calls attention to "hey we're doing maybe a naughty thing".&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Thu, 30 May 2024 10:00:00 -0000</pubDate></item><item><title>Re: So We've Got a Memory Leak… | Steven Harman — Maker &amp; Breaker of Things</title><link>http://localhost:4000/so-we-have-a-memory-leak#comment-6376043260</link><description>&lt;p&gt;Ah, yep. Makes sense. Apologies for the pedantry. I find a lot of folks over-export because they don’t fully comprehend what it actually does. So I’m sensitive to examples that demonstrate that. 😅&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Fri, 26 Jan 2024 08:25:47 -0000</pubDate></item><item><title>Re: So We've Got a Memory Leak… | Steven Harman — Maker &amp; Breaker of Things</title><link>http://localhost:4000/so-we-have-a-memory-leak#comment-6376032015</link><description>&lt;p&gt;The DUMP_PID didn’t actually need exported, right? Looks like it was only used in the running shell?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Fri, 26 Jan 2024 08:07:16 -0000</pubDate></item><item><title>Re: The Empire State Building changed colors for an hour in honor of Columbus last weekend; Here’s why</title><link>https://614now.com/2023/hot-topics/the-empire-state-building-changed-colors-for-an-hour-in-honor-of-columbus-last-weekend-heres-why#comment-6343488066</link><description>&lt;p&gt;Anyone else recognize that gesture for what it was?&lt;/p&gt;&lt;p&gt;Had the Crew lost the ESB would have used… the exact same colors. LAFC is also black and gold.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Tue, 12 Dec 2023 23:33:07 -0000</pubDate></item><item><title>Re: Apple two-factor authentication feature now blocks SMS autofill for phishing attacks</title><link>https://9to5mac.com/2022/01/31/apple-two-factor-authentication-autofill/#comment-5716464436</link><description>&lt;p&gt;amazing, thanks! I had no idea it was a standard&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 31 Jan 2022 15:32:12 -0000</pubDate></item><item><title>Re: Apple two-factor authentication feature now blocks SMS autofill for phishing attacks</title><link>https://9to5mac.com/2022/01/31/apple-two-factor-authentication-autofill/#comment-5715957638</link><description>&lt;p&gt;Does apple have a definitive page dedicated to explaining their format and restrictions? Where would one refer people who are interested in complying with the proper format?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 31 Jan 2022 10:00:19 -0000</pubDate></item><item><title>Re: Apple releases macOS 12.2 with Safari security patch, improved ProMotion scrolling</title><link>https://9to5mac.com/2022/01/26/apple-releases-macos-12-2-with-safari-security-patch/#comment-5709303235</link><description>&lt;p&gt;It was appropriate because I was literally screaming it in my head while typing :D&lt;/p&gt;&lt;p&gt;The bluetooth mute bug is completely breaking conference calls on monterey.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Wed, 26 Jan 2022 17:29:06 -0000</pubDate></item><item><title>Re: Apple releases macOS 12.2 with Safari security patch, improved ProMotion scrolling</title><link>https://9to5mac.com/2022/01/26/apple-releases-macos-12-2-with-safari-security-patch/#comment-5708986727</link><description>&lt;p&gt;PLEASE TO KNOW IF BLUETOOTH MUTING BUG FIXED IN THIS RELEASE&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Wed, 26 Jan 2022 14:05:18 -0000</pubDate></item><item><title>Re: Poll: Do you think Apple will release a replacement for the discontinued HomePod?</title><link>https://9to5mac.com/2021/03/13/poll-do-you-think-apple-will-release-homepod-replacement/#comment-5302626167</link><description>&lt;p&gt;If they do, I hope beyond reason that it will be indoor/outdoor capable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Sat, 13 Mar 2021 11:51:55 -0000</pubDate></item><item><title>Re: Hands-on: Level Lock easily converts deadbolts into HomeKit smart locks [Video]</title><link>https://9to5mac.com/2020/06/09/level-lock-review-homekit-smart-lock-video/#comment-4947217540</link><description>&lt;p&gt;Love the idea of this lock. Seems like a great addition for secondary doors? (garage access door, for instance?)&lt;/p&gt;&lt;p&gt;I'm curious about the Yale Assure lock mentioned. I presently have the Yale Nest lock (with Starling Home Hub for HomeKit compatibility) but would prefer to move my nest hardware to be native homekit, as much as possible. However, I've heard mixed reviews on the Assure lock. It seems to be essentially the same hardware. Does anyone have experience with it? I've heard the HomeKit/wifi module goes bad occasionally and needs to be replaced (typically at a cost). It also seems that the Assure lock doesn't support scheduling of guest access as is possible within the Nest app.&lt;/p&gt;&lt;p&gt;Worth switching from Yale Nest to Yale Assure to move more natively HomeKit (and have one less Google device in the house?)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Tue, 09 Jun 2020 11:24:48 -0000</pubDate></item><item><title>Re: Vulcain Review</title><link>https://nordicapis.com/vulcain-review/#comment-4807111988</link><description>&lt;p&gt;Agree. Regardless of the skill of the devs or the parsers chosen, functions simply aren’t part of the JSON spec. So a response that is wrapped in a function isn’t JSON, by definition.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Sun, 23 Feb 2020 20:32:21 -0000</pubDate></item><item><title>Re: How to extract your TOTP secrets from Authy</title><link>https://www.pommepause.com/2014/10/how-to-extract-your-totp-secrets-from-authy/#comment-4648511069</link><description>&lt;p&gt;Still works for authy 2.6.0 (I made the edits manually, I didn't copy the entire app.js file) but the changes still work great!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Fri, 11 Oct 2019 10:03:27 -0000</pubDate></item><item><title>Re: Why I miss Rails | chanind.github.io</title><link>https://chanind.github.io/rails/2019/03/28/why-i-miss-rails.html#comment-4401011011</link><description>&lt;p&gt;&amp;gt; Meteor was the closest the JS world has come to something like Rails&lt;/p&gt;&lt;p&gt;Ember is exactly what you're talking about&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Fri, 29 Mar 2019 08:39:17 -0000</pubDate></item><item><title>Re: Experiment 01 — Smooth Scrolling</title><link>https://blog.feedly.com/experiment-01-smooth-scrolling/#comment-4080668034</link><description>&lt;p&gt;I prefer the new scrolling, however I rarely scroll through the list of articles. I much prefer to start at an article and progress through them that way. So while I do prefer the new smooth scrolling, I don't think it will impact my day-to-day much.&lt;/p&gt;&lt;p&gt;Though when I _do_ use the "today" view, in the old format I was constantly afraid of accidentally marking a bunch of articles as read. I would guess that the new scrolling format should make that harder to do accidentally? (I hope)&lt;/p&gt;&lt;p&gt;It seems a lot of people _want_ to mark articles as read in the today view. I'm throwing my vote _against_ that. For my workflow, I vastly prefer to ruthlessly prune the articles to which I'm subscribed, such that I actually read the ones to which I'm subscribed. So I rarely want to mark an article as read without actually viewing it. (Hence my annoyance with the old paged format where I'd frequently mark articles read by accident.)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Thu, 06 Sep 2018 10:19:04 -0000</pubDate></item><item><title>Re: To gist and back again</title><link>http://remysharp.com/2018/01/05/to-gist-and-back-again/#comment-3694661174</link><description>&lt;p&gt;Yep, jq is awesome!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Sat, 06 Jan 2018 10:03:22 -0000</pubDate></item><item><title>Re: To gist and back again</title><link>http://remysharp.com/2018/01/05/to-gist-and-back-again/#comment-3694196331</link><description>&lt;p&gt;Any reason why you wouldn't just clone the gist using git, instead of the gist-api/curl/jq hackery?&lt;/p&gt;&lt;p&gt;The clone URL for a gist is just: &lt;code&gt;https://gist.github.com/&amp;lt;gist_id&amp;gt;.git&lt;/code&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Fri, 05 Jan 2018 23:06:09 -0000</pubDate></item><item><title>Re: How to write async await without try-catch blocks in Javascript</title><link>http://blog.grossman.io/how-to-write-async-await-without-try-catch-blocks-in-javascript/#comment-3595128604</link><description>&lt;p&gt;Could either use bluebird's filtered catch (assuming the providers expose their error types) or, intersperse `.catchThrow` at every step. Both of these options, IMO, are cleaner than forcing async/await here which is not adding any value other than disconnecting an inherently dependent chain of actions. The disconnection of the dependencies is harmful here and introduces the workaround. A simple promise chain makes the inherent dependency chain _explicit_ and clean, IMO.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Wed, 01 Nov 2017 11:41:31 -0000</pubDate></item><item><title>Re: Migrating towards Yarn and Webpack</title><link>http://engineering.wingify.com/posts/migrating-towards-yarn-webpack/#comment-3580912913</link><description>&lt;p&gt;:+1: final comparison with npm5 and common cache cleans:&lt;/p&gt;&lt;p&gt;nocache: (unsure if these are comparable because screenshots do not indicate whether the relevant lockfiles existed or not)&lt;/p&gt;&lt;p&gt;with cache + lockfile:&lt;br&gt;  npm5 - 5s&lt;br&gt;  yarn - 1s&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 23 Oct 2017 13:18:57 -0000</pubDate></item><item><title>Re: Migrating towards Yarn and Webpack</title><link>http://engineering.wingify.com/posts/migrating-towards-yarn-webpack/#comment-3580569826</link><description>&lt;p&gt;Wait, why are you only cleaning npm's cache but not yarn's?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 23 Oct 2017 09:46:40 -0000</pubDate></item><item><title>Re: Migrating towards Yarn and Webpack</title><link>http://engineering.wingify.com/posts/migrating-towards-yarn-webpack/#comment-3580564496</link><description>&lt;p&gt;Nice, thanks. Might be worth updating the post with this info. As it stands, it feels a bit like a strawman post given a publish date of Oct 4.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jasonkarns</dc:creator><pubDate>Mon, 23 Oct 2017 09:43:02 -0000</pubDate></item></channel></rss>