École des Bro-ArtsFeb 20
On the flip side of the #OnlineSafetyAct, my personal blog gets waaaay more traffic than woof.group. I've opted to geoblock the UK there. Quick implementation notes: https://aphyr.com/posts/379-geoblocking-the-uk-with-debian-nginx
Geoblocking the UK with Debian & Nginx

Show threadJohann z. Baag (ej af Puss-B.)

@aphyr So, if the UK/Ofcom starts targeting the Fediverse, server admins have at least three options:

* Geoblock the UK; or
* Block every server that allows sexful and other content that kids of UK must be protected from; or
* Ignore the #OnlineSafetyAct, and risk legal trouble.

Have I got this right?

Feb 21 at 3:03pmWeb
Show threadÉcole des Bro-ArtsFeb 21
@zenfin We opted to declare ourselves out of scope, but if Ofcom decides instances of our scale *are* in scope, yes, I believe those are essentially our only options. I haven't heard anything from mastodon.social, and they're almost certainly large enough to fall in scope, so right now it looks like they're choosing option C. https://blog.woof.group/announcements/out-of-scope-of-the-online-safety-act
Out of Scope of the Online Safety Act

Woof.group has made extensive efforts to assess the impact of the UK's Online Safety Act (OSA). After working through Ofcom's detailed gu...

Woof.group Announcements
Show threadDerick RethansFeb 21

@zenfin @aphyr I think woof.group (if Ofcom decides they are in scope) is trickier as they specifically allow adult content.

Our instance doesn't and we've changed our terms: https://github.com/phpcommunity/policies/commit/a5539fde1b390709e0897b86385265314a1e866b

The CC-BY risk assessment is at https://github.com/derickr/online-safety-assessments/blob/main/mastodon-phpc.social.rst

I don't believe you'd need to proactively block servers that have sexful content, but rather remove actual illegal content that hits your server.

Ofcom also said that trouble is unlikely as long as you engage with them. I'd do an assessment.

Merge changes to implement Online Safety Act's ICU G1 · phpcommunity/policies@a5539fd

Policy documents for PHP Community. Contribute to phpcommunity/policies development by creating an account on GitHub.

GitHub
Show threadÉcole des Bro-ArtsFeb 21
@derickr @zenfin I'm not sure about that part. If phpc.social were to be found in scope, I believe you'd have to implement highly effective age assurance and take down public pages/APIs. Right now you can find porn pretty quickly on phpc.social:
Show threadRetFeb 21

@derickr @zenfin @aphyr Ofcom also said the exact opposite of that ref. sites hosting adult content in the session specifically about pornography.

I forget the exact wording but Hoskins (I believe) said that the first contact would be to initiate enforcement actions (paraphrased).

Show threadDerick RethansFeb 21

@ret @zenfin @aphyr Not in the session that I was in.

The video is linked in https://buttondown.com/indie-and-community-web-compliance-/archive/4-update-from-ofcom-webinar/

#4: Update from Ofcom webinar

Includes videos of the webinar, outlines a couple of major outstanding issues relating to Mastodon and proportionate enforcement, and suggests what ofcom might do next.

Indie and Community Web Compliance
Show threadRetFeb 21

@derickr @zenfin It was prior to that session. I believe @aphyr documented it here: https://blog.woof.group/announcements/#today-s-livestream-on-pornography

Bottom of that section.

Woof.group Announcements

Woof.group news

Woof.group Announcements
Show threadÉcole des Bro-ArtsFeb 21
@derickr @ret @zenfin I was in that meeting and Ofcom's sessions the previous weeks, and I think we can safely say that Ofcom's public comms on likely enforcement are... confusing, haha. Ret's recalling Hosking's comments here: https://blog.woof.group/announcements/updates-on-the-osa
Updates on the OSA

In today's livestream (58:00), Ofcom's James Proudfoot told service providers, "If people reach out, what's useful is we can talk to you ...

Woof.group Announcements