Kind replies

 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?

 Reply

Yeah definitely fair! I know exactly what you mean - and I'm generally going for low hanging fruit 😅

 Reply

I've had it fed back to me that sometimes the way I come across isn't great - so yeah definitely friendly nudge - but it someone keeps doing it after many attempts to educate them, it also kinda feels like they're actively deciding not to be more inclusive? It's a difficult one, but "I'm used to saying it" goes only so far before being lazy, ignorant, or actively harmful

 Reply

I'm known at work for championing inclusive language, and I call it out regardless of how person saying it identifies. Regardless of how the folks in the group feel at the time, it continues people using it and feeling that its OK. Those people will then use it outside of that circle, and they will inevitably make someone feel unwelcome. I feel its one of those things that, although can be a pain to rewire our brains, does make a difference, and trying to move to a more inclusive place to be is a great end goal

 Reply

Yes that's correct - if you wanted to continue using your primary identity URL, you'd need to update <meta> tags / Link HTTP headers.

For that reason, and to reduce risk of accidentally pushing something to my live site, when testing my staging infrastructure, I chose a separate identity, www.staging.jvt.me which simply hosts <meta> links to my staging server.

 Reply

Riz I am so sorry to hear that. Sending love to you all, let us know if there's literally anything we can do to help 🤗

 Reply

If you go the personal website route (which I'd recommend) there's https://brid.gy which let's you tweet from your website so you can still reach your following, as well as ie via RSS