Emelia Smith

Maybe `fyi.frontpage.richContent.*` or something? If you want to be specific. Another word might be "contentFragment" or something

So maybe the key change would be to move: ``` { "type": "union", "refs": ["fyi.frontpage.richtext.block#plaintextParagraph"] } ``` Out of the `fyi.frontpage.feed.comment` namespace and into `fyi.frontpage.richtext` such that it's reusable across...

This would be a good idea!

I suspect this may be related to: https://github.com/inrupt/solid-client-js/pull/1545 Though it might be worth testing if this works for you: ``` const thing = getThing(dataset, getSourceIri(dataset) + "_:Thing") ```

Also related: https://github.com/inrupt/solid-client-js/issues/1511

Seems to also be in https://github.com/inrupt/solid-client-js/issues/948

In [OAuth Client ID Metadata Documents](https://drafts.aaronpk.com/draft-parecki-oauth-client-id-metadata-document/draft-parecki-oauth-client-id-metadata-document.html#name-server-side-request-forgery), the language we currently have is: > Authorization servers fetching the client metadata document and resolving URLs located in the metadata document should be...

> Can you provide an example for such an attack in the Fediverse? Whilst I'm not certain if we've seen this attack vector actively used in practice, it is still...

We'd probably need guidance that this applies not just to Activities and Objects, and fetching said resources from remote servers, but also to media files from Image / Video /...

> the biggest threat for current Fediverse deployments is Elasticsearch, which has an internal HTTP API that isn't always secured well. I think modern ES deployments have made this much...