Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51451 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2013-07-29 08:58 -0700 |
| Last post | 2013-07-29 08:58 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: MyOpenID.com no longer supported Ethan Furman <ethan@stoneleaf.us> - 2013-07-29 08:58 -0700
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2013-07-29 08:58 -0700 |
| Subject | Re: MyOpenID.com no longer supported |
| Message-ID | <mailman.5238.1375113535.3114.python-list@python.org> |
On 07/29/2013 02:11 AM, Antoine Pitrou wrote: > Le Mon, 29 Jul 2013 00:55:53 -0700, > Ethan Furman <ethan@stoneleaf.us> a écrit : >> Excerpt from http://meta.stackoverflow.com/q/190442/176681: >> >> Janrain no longer actively supports MyOpenID, and announced on >> Twitter that their users should proceed with caution. >> >> This decision was made by Janrain, [snip] >> >> I know the Python bug tracker allows MyOpenID logins; if that is your >> only login method you should add another that doesn't depend on >> MyOpenID. > > I don't understand. The tracker allows any (sufficently compliant) > OpenID provider, not just "MyOpenID" or > "MyCorporateOpenIDWithTrademarks". That is true, but if your OpenID provider is MyOpenID (as mine was) then it would be wise to get another. -- ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web