Kind replies

 Reply

Yeah I think as you've said elsewhere it's especially difficult as colleagues may not be as up to date on this stuff - are you able to maybe wrap the libraries into some guardrails? So things are easier and safer to use?

 Reply

I've got a tonne of great ones I'm planning on putting in a picture frame then hanging up instead of it being on my laptop, but I've still not done that either 😅

 Reply

Depending on what you want to do, you may be able to follow how Terence Eden has done it before in https://shkspr.mobi/blog/2019/12/add-review-to-goodreads-from-schema-markup/

 Reply

The onus isn't on people to dig into settings to find where they've been opted-in to something public. It should be private by default, and have the option presented to you so you can make an informed decision

 Reply

Glad to hear everything is OK!

 Reply

"likely weren't" - this is the whole point! "likely" implies that there were people who were affected, having the risk of assault, rape, or murder. It's very unlikely that we'll know for sure, but making a feature opt-in to literally protect people isn't the end of the world. "negative default settings" was the state of play before the change. They didn't give people a choice, and didn't provide sufficient support to users to understand this. So by making the change, we're now in "positive default settings"

 Reply

It only had high social appeal because no one knew it was on, so you're lamenting something that never truly was. But as we've said, if you want to continue using it with others, all you need to do is enable it before running together

 Reply

I mean, you still can use the feature can't you? It's not like Andrew has gotten Strava to completely remove the feature. If you, and anyone you run with, want to turn it on, he's given you the link 🤷🏽‍♂️

 Reply

Sorry, only just seen this. As mentioned on the event, link is available for members of the Tech Nottingham Slack

 Reply

Sorry, I wasn't clear. In JSONWebKeySetTest we're reaching out to a real set of endpoints.

However, I can't seem to find a public OAuth2 server that supports RFC8414 to write a test.

I was thinking of using something like Wiremock to create a fake server so I can stub it out, and wondered if you'd be happy with that as a change to the existing tests in JSONWebKeySetTest?