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

Common JSON-LD contexts should be bundled with Mastodon #9411

Closed
ThibG opened this Issue Dec 2, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@ThibG
Collaborator

ThibG commented Dec 2, 2018

In many cases, remote JSON-LD documents have to be loaded to parse/canonicalize JSON-LD documents.
This is the case for outbound statuses, which require at least https://w3id.org/security/v1, https://www.w3.org/ns/activitystreams, and https://w3id.org/identity/v1.

The last one is currently unavailable, so any instance not having it in cache is currently screwed.

Such documents used to be bundled with Mastodon, but that was reverted in d40ef11. I don't think saving a few MB of RAM was worthwhile here.

@nightpool

This comment has been minimized.

Collaborator

nightpool commented Dec 2, 2018

ThibG added a commit to ThibG/mastodon that referenced this issue Dec 2, 2018

ThibG added a commit to ThibG/mastodon that referenced this issue Dec 2, 2018

@kit-ty-kate

This comment has been minimized.

kit-ty-kate commented Dec 2, 2018

My instance (lesbiab.space) didn't have it in cache and is not able to send anything since those servers were down

kit-ty-kate added a commit to kit-ty-kate/mastodon that referenced this issue Dec 2, 2018

@nightpool

This comment has been minimized.

Collaborator

nightpool commented Dec 2, 2018

@kit-ty-kate can you try deploying #9412 and seeing if that fixes the problem? looks like you're already trying

kit-ty-kate added a commit to kit-ty-kate/mastodon that referenced this issue Dec 2, 2018

@Gargron Gargron closed this in #9412 Dec 2, 2018

Gargron added a commit that referenced this issue Dec 2, 2018

Gargron added a commit that referenced this issue Dec 2, 2018

Gargron added a commit that referenced this issue Dec 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment