Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3

Here you go: github.com/DotNetOpenAuth/DotNetOpenAuth - of course, that's just the authentication. There's also the UX (most people don't know what OpenID is / how to deal with it when it breaks), and the provider end: github.com/StackExchange/StackID (note the WEALTH of contributors) and all of the plumbing to make the two work seamlessly together without a ton of annoying hoops for everyone who just wants to log in with an email+password. As much of this as possible has been open source since '08 - that you didn't know this speaks to the present success of OpenID...
– Shog9
Commented Jul 5, 2018 at 23:09
@shog9 GitHub URLs are not responsive to my question. At the (apparently necessary) risk of repeating myself, I am asking whether you bothered to solicit volunteers before terminating support for 13,000 active OpenID users, of which I am one.
– Nemo
Commented Jul 6, 2018 at 0:04
3

Yes, @Nemo. We've welcomed volunteers, we've supported the continued development of OpenID financially, socially and with the work of our developers, and we've stuck with it for years even as the largest OpenID providers have one by one all dropped support or abandoned development, leaving bugs to fester and frustrating the users of Stack Exchange who relied on them. We've had a team of people supporting these users, helping them one-on-one if need-be, as they fought with their negligent providers and struggled to retain access to their accounts.
– Shog9
Commented Jul 6, 2018 at 0:17

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »