-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify docket links on any website to any website and add [R] links #358
Comments
I think an example would help here. Imagine that you're a pro-openness attorney that's at a corporation. The corp is subscribed to Docket Bird/Alarm/PacerPro/etc, and you get an email from them for whatever reason, because their service is great and the folks that decide on tools picked that one for you. In the email, there's a link to the docket on their website. What we can do is put our link next to it, so people can look up the case on CourtListener, contribute to it there, etc. I'm also open to doing a bit more than just an [R] icon. It could have a dropdown with additional features like "search this docket", "buy on PACER", etc, though this is getting harder! |
Yeah, I think putting the permissions prompt behind a setting would make this much more palatable, but I don't know that we can come up with a complete list of domains where we'd want to look for links to dockets. |
Just got a request to add PACER Monitor scraping to the extension. |
We've been timid on this front, but I think it's reasonable to be a bit more aggressive, if we can. We should start identifying links to other websites that host dockets, and start injecting our little [R] icons next to those links, so people can open our docket pages, if the other one isn't great, requires a login, whatever.
This can live behind a permissions prompt, and can be an option in the settings that is defaulted to off, but I think the idea is useful and sound. The permissions prompt would expand our permissions boundary to include all domains, not just RECAP ones.
The text was updated successfully, but these errors were encountered: