You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once X-Ray has an API, we should do one of the following three things:
Add it as a feature to RECAP for uscourts.gov
Add it as a feature to RECAP, but only run it on uscourts.gov, with a extra permissions request to expand it to more domains (possibly via a setting).
Build a new extension that supports it.
Generally though, the idea is simple: When somebody uploads a document to a website, check if it has bad redactions. If so, alert them.
Right now, option 2 looks pretty great as a middle ground. We start helping filers that have RECAP installed without any additional privacy worries. Meanwhile if people want this turned on everywhere, they can do that.
The text was updated successfully, but these errors were encountered:
We'd need to be careful to do this as opt in, I suppose, since "sending all your docs to our API" is something people would not find amusing without consent.
Once X-Ray has an API, we should do one of the following three things:
Add it as a feature to RECAP for uscourts.gov
Add it as a feature to RECAP, but only run it on uscourts.gov, with a extra permissions request to expand it to more domains (possibly via a setting).
Build a new extension that supports it.
Generally though, the idea is simple: When somebody uploads a document to a website, check if it has bad redactions. If so, alert them.
Right now, option 2 looks pretty great as a middle ground. We start helping filers that have RECAP installed without any additional privacy worries. Meanwhile if people want this turned on everywhere, they can do that.
The text was updated successfully, but these errors were encountered: