Post
Quite big (albeit entirely expected) #OnlineSafetyAct news from Ofcom for a Monday morning:
> Given the urgent need to better protect women and girls online, we are now adding a recommendation to our codes that certain sites and apps expand their use of automated technology – known as ‘hash matching’– to detect illegal intimate images shared without consent, such as explicit deepfakes.
There is no need to panic!
This is not in force yet, as the revised code will need to go through Parliament first.
This will be a mere formality, I expect, but nevertheless it needs to happen, and it is scheduled for later this year.
Obviously, there's nothing stopping a service from implementing the recommendation sooner.
@neil <sings in billy connolly voice> no need to panic. no need to cry ... https://www.youtube.com/watch?v=jqafaCSzCYM
Ofcom's recommendation is limited to:
1) Providers of user-to-user services that are high risk for intimate image abuse and either:
a) whose principal purpose is the hosting or dissemination of regulated pornographic content; or
b) are file-sharing and file-storage services; or
c) have more than 700,000 monthly active UK users.
2) Providers of large (more than 7 million monthly active UK users) user-to-user services that are medium risk for intimate image abuse
3) Providers of large general search services.
@neil seems (for once) fairly sensible. Where do the hash lists come from for this stuff? If you have an abusive image of yourself published online, for instance, how does one get it added to a hash list to stop its dissemination? Is there a proper process for that?
> Where do the hash lists come from for this stuff?
They are encouraging platforms to sign up with stopncii.
But the stopncii process for signing up looks very manual, and unlikely to scale well. There is also no indication of cost.
Install bonfire.cafe
Get the full app experience
