We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What's the problem you want solved? For some reason the Markdown renderer is taking %70B9TI2hP5QMU59Lx9ozRD5Uh/E7tq4o1Ox8TP07XIg=.sha256 and pointing you to http://localhost:3000/thread/%70B9TI2hP5QMU59Lx9ozRD5Uh/E7tq4o1Ox8TP07XIg=.sha256. That's wrong, and it should be URI encoded as http://localhost:3000/thread/%2570B9TI2hP5QMU59Lx9ozRD5Uh%2FE7tq4o1Ox8TP07XIg%3D.sha256 instead.
%70B9TI2hP5QMU59Lx9ozRD5Uh/E7tq4o1Ox8TP07XIg=.sha256
Is there a solution you'd like to recommend? Nope, not sure why this is broken yet.
The text was updated successfully, but these errors were encountered:
Is this still the case since e7c38e3
Sorry, something went wrong.
I believe so, the problem is upstream in SSB-Markdown, reported as ssbc/ssb-markdown#55
Fix Markdown link bug
57558e5
Problem: Some sigil links were broken because of a bug in SSB-Markdown that was recently resolved. Solution: Upgrade SSB-Markdown. Fixes: fraction#242
c4aaf47
Successfully merging a pull request may close this issue.
What's the problem you want solved? For some reason the Markdown renderer is taking
%70B9TI2hP5QMU59Lx9ozRD5Uh/E7tq4o1Ox8TP07XIg=.sha256
and pointing you to http://localhost:3000/thread/%70B9TI2hP5QMU59Lx9ozRD5Uh/E7tq4o1Ox8TP07XIg=.sha256. That's wrong, and it should be URI encoded as http://localhost:3000/thread/%2570B9TI2hP5QMU59Lx9ozRD5Uh%2FE7tq4o1Ox8TP07XIg%3D.sha256 instead.Is there a solution you'd like to recommend? Nope, not sure why this is broken yet.
The text was updated successfully, but these errors were encountered: