<?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 swards</title><link>http://disqus.com/by/swards/</link><description></description><atom:link href="http://disqus.com/swards/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 24 Aug 2020 14:26:55 -0000</lastBuildDate><item><title>Re: How to use React Testing Library Tutorial</title><link>https://www.robinwieruch.de/react-testing-library#comment-5043432188</link><description>&lt;p&gt;This is a great article.  Would love to know a little more about act() and what you did in the final test - where you awaited the promise `await act(() =&amp;gt; promise);`.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Mon, 24 Aug 2020 14:26:55 -0000</pubDate></item><item><title>Re: Rails Benchmarking - Cache Store Latency</title><link>http://adamnengland.com/2015/09/18/benchmarking-rails-cache-latency/#comment-2794197403</link><description>&lt;p&gt;Awesome thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Wed, 20 Jul 2016 18:14:49 -0000</pubDate></item><item><title>Re: Why Passwordless Authentication Works</title><link>http://www.sitepoint.com/passwordless-authentication-works/#comment-2358042593</link><description>&lt;p&gt;Craigslist has been doing this since the beginning I think. It's a a good site for this UI, people don't come back to the site everyday, but when they do they need to access their account.  A little extra time was worth it and made the onboarding process simpler.  It was only later they added passwords.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Fri, 13 Nov 2015 12:13:08 -0000</pubDate></item><item><title>Re: The Time Everyone “Corrected” the World’s Smartest Woman</title><link>http://priceonomics.com/the-time-everyone-corrected-the-worlds-smartest/#comment-1867633294</link><description>&lt;p&gt;Remember - Monty is trying to pick the car, the only way he can't do that is if the car is already picked - a 1/n chance. His odds are 1-1/n, or 2/3 with three doors.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Sat, 21 Feb 2015 08:49:56 -0000</pubDate></item><item><title>Re: http://localhost:3000/news/2009/06/12/my-news-item</title><link>http://localhost:3000/news/2009/06/12/my-news-item#comment-10833870</link><description>&lt;p&gt;Cool - what up.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Sat, 13 Jun 2009 03:12:46 -0000</pubDate></item><item><title>Re: TwitterAuth: For Near-Instant Twitter Apps - Intridea Company Blog</title><link>http://www.intridea.com/2009/3/23/twitter-auth-for-near-instant-twitter-apps?blog=company#comment-8686371</link><description>&lt;p&gt;Just a couple tips - looking through the code of the gem was helpful to see how it worked, what helper methods were added, and what controllers/actions were in there.  And, Rake Routes gives a good overview of the urls and restful resources.  That's where I saw the url for oauth_callback and realized I shouldn't have changed it.&lt;/p&gt;&lt;p&gt;The Gem code can be found by doing a $gem list twitter-auth -d to find the directory of the gem.  Open it in your editor from there.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Sat, 25 Apr 2009 12:21:35 -0000</pubDate></item><item><title>Re: TwitterAuth: For Near-Instant Twitter Apps - Intridea Company Blog</title><link>http://www.intridea.com/2009/3/23/twitter-auth-for-near-instant-twitter-apps?blog=company#comment-8669374</link><description>&lt;p&gt;I got this working and everything is good now - First, don't change the default url for the callback - that needs to be '/oauth_callback' in the Twitter App Registration settings to match twitter-auth's expectations.  If you change it, update routes to have the new url send you to {:action=&amp;gt;"oauth_callback", :controller=&amp;gt;"sessions"}.&lt;/p&gt;&lt;p&gt;The other symptom I was seeing was not related.  When I landed on twitter at &lt;a href="http://twtter.com/oauth/authenticate?" rel="nofollow noopener" target="_blank" title="twtter.com/oauth/authenticate?"&gt;twtter.com/oauth/authenticate?&lt;/a&gt;.. I was not logged in, but was when I landed at &lt;a href="http://twitter.com/oauth/authorize?" rel="nofollow noopener" target="_blank" title="twitter.com/oauth/authorize?"&gt;twitter.com/oauth/authorize?&lt;/a&gt;... &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Fri, 24 Apr 2009 18:47:41 -0000</pubDate></item><item><title>Re: TwitterAuth: For Near-Instant Twitter Apps - Intridea Company Blog</title><link>http://www.intridea.com/2009/3/23/twitter-auth-for-near-instant-twitter-apps?blog=company#comment-8668443</link><description>&lt;p&gt;I'm not seeing this go so smoothly.  One big issue - when the round trip returns, I'm not signed in.  Another, smaller, but maybe related - when I get to twitter (at /oath/authenticate?...) I am not logged in.  If I try it from another consumer app on the web, it works fine.  Makes me think there's something odd with my configuration, but my setup is on a new rails stack.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">swards</dc:creator><pubDate>Fri, 24 Apr 2009 18:05:14 -0000</pubDate></item></channel></rss>