Vincent

Hi both - since this icon is no longer present on the website in the current state, there's nothing to do here anymore, sorry!

I implemented support in a client library (`@inrupt/solid-client`). The implementation can be seen here: https://github.com/inrupt/solid-client-js/tree/master/src/acl I did not (intentionally, at least :) ) diverge from the ontology.

Thanks for reporting. Looks like this is an upstream bug: https://github.com/vercel/next.js/issues/35674 Presumably, a workaround would be for us to use a ~~JPEG~~ PNG image and let Next.js convert that to...

> the dashboard throws errors if OneRep is down or returning bad results, instead of falling back to our local cache. Shouldn't we solve that by catching the errors in...

@rhelmer I was thinking of closing this, since it doesn't seem to be a pressing issue anymore, especially when we move off OneRep - though perhaps it relates to the...

> Also seems fishy that we have both ESLint [no-unused-vars](https://eslint.org/docs/latest/rules/no-unused-vars) and TypeScript-y [@typescript-eslint/no-unused-vars](https://typescript-eslint.io/rules/no-unused-vars) rules enabled. Oops, that's my fault. We should probably disable the former, and apply the configuration we...

Thanks for reporting @dshin-moz. Since this is related to the extension, I'll move it to the correct project. In lieu of a proper fix, it might be good to be...

Thanks for the report! Since this affects the extension, I'll move it to the extension project.

Thanks for reporting. This will be fixed by https://github.com/mozilla/fx-private-relay-add-on/pull/462, which we're hoping to release in the not-too-distant future.

Thanks for the report! Since this affects the extension, I'll move it to the extension project.