Tom Lehman

"Remember me" means "keep me logged in on this browser until I click log out". I.e., the behavior of "remember me" shouldn't depend on what I've done on another browser...

I think the solution is to save a new remember_me token only when the use changes his password, not when he logs in with a "remember me" request. I.e.: -...

> If you don't also keep expiration info on each browser, than the expiration will take effect from the time of the first browser, even if the last browser asked...

> No no, what I meant was, the token the attacker is sniffing right now, is already obsolete, because when the user sends me his token, I give him a...

All methods are throwing this error, and yet it works fine for me when I directly access the URL (though I'm using `api.chartbeat.com`)

Hi! I'm running into this problem as well. Just curious if a fix is still in progress. Thanks! Love the gem!

FWIW you can hack around this with something like `Foo.remove_instance_variable(:@_memoized_bar)`. Not pretty but half a loaf is better than none!

Re-upping this as my above code is not correct in that, when you do a reverse resolution, there is no automatic validation that the resolved name actually points to the...

That's fair. It is an EVM-wide thing but it's a pretty specific project, even if it is arguably the most iconic. If only there were an organization with millions of...

That makes sense! FWIW what I had in mind was more "OZ + `numberMinted`" versus "ERC721A - `startTimestamp`." Like is this not an improvement over what we have today in...